Hello,
I am trying to figure out if there are still many known issues with NCM on Win2008 and SQL Server 2008 Standard. On january 27th Chris said that Win2008 support would be included in the next major release. Is this done yet?
Thanks
Yes, with 5.5.1.
The known Win2008 issues are listed in the Relase Notes here.
Does real-time config change notifications work on windows 2008.
Seems that there could be an issue when NCM creates the scheduled job, the job will be automatically set to run only when user is logged in.
I am moving to windows 2008 server soon. Trying to get all my ducks in a row.
Real-time change notifications should work on Windows 2008. You'll just have to be sure the Windows account used to run Syslog or Trap server (depending on which one you use as a config change trigger) has read-write access to the NCM DB. See “Enabling Realtime Configuration Change Detection” in the Admin Guide.
Having said that, if it's possible to push off the move of NCM to Windows 2008 until next year, I would recommend doing so given the other issues noted in the release notes.
Thanks for the info Chris.
What issues specifically are you speaking about. The only real issue that I see is the issue with the scheduled jobs. Which does seem like too big of a deal to me. Are there other issues that I did not see when reading it? Or maybe the scheduled jobs issue is a bigger problem than I think it is. It appears that I just have to reenter the user/password when making changes to the scheduled jobs( no biggy). Does it prompt me to reenter the credentials, or is this something that I have to remember to do, or the task will not run.
The reason I'm asking is that I dont think I have too much of a choice on the upgrade, unless I tell the boss that it will absolutely not work.
Thanks again for your help.
Right, the issues are related to the security model changes Microsoft made in updating to Task Scheduler 2.0 in Vista and Windows 2008. New jobs are created with the ''Run when user is logged on'' option instead of ''Run whether user is logged on or not". Unfortunately, it's not possible to easily change this security setting through the new API.
So, the primary issue is having to go back to Windows Task Scheduler and set the security on the job so that it runs when the user account is not logged in.
The secondary issue is that on the NCM scheduled Jobs dialog, when user checks/unchecks status option, we had to reprompt for credentials to ensure that the NCM UI and Windows Task Scheduler status remain synched. Again, a security "feature" of the new Windows Scheduler. This prompting should happen automatically.
If you're comfortable with those requirements, then the upgrade is probably okay for you. I just didn't want you to go in blindly and be surprised.
thank you very much Chris,
That's exactly the info I was looking for. I think those issues are easy enough to get around. I'm glad it will prompt for the user/pass in NCM scheduler, that way I dont have to think about it on my own. :-)
