aarond

Anyone know if this is still the case? About to migrate NCM/NPM to 2008 R2 64-bit and need to know if 32-bit IIS limitation is still the case.

Thanks Jiri. Is there a document that provides details on this? Also, is it poossible to use a Windows share for Config Archive Folder Locations setting so multiple NCM pollers can backup to the same location? I can change the path to a UNC format but how do you authenticate?

Thanks for the input guys. I was able to collocate the Config-Archives to a single share, which is nice. Looks like all I need to do is copy the following directories to the new polling engine. <install area>\Orion\NCM\DeviceTypes\*.* <install area>\Orion\NCM\Scripts\*.* <install area>\Orion\NCM\Reports\*.* <install…

Thank you!

Jiri, thank you. I may be interested once I spend some time with it. Now that we have a second polling engine I have to use the web console to view everything from the same place. Also, isn't there some items I need to copy from the primary NCM to the secondary poller with version 7.3.2? I've seen mention of this on Thwack…

10-4, thanks for the assistance.

Thanks for the run down. Perhaps I should bring NCM and NPM to the latest releases before adding the additional polling engine.

Has the NCM additional polling engine changed that much from 7.2 to 7.3? Running 10.5 NPM and 4.1 VNQM as well.

Does it have to be IIS 6.0 or will 7.0 run in 32-bit mode? Is there official documentation on how to set IIS to 32-bit mode? Thanks in advance.

Sigh...I'm sure you are correct. Hopefully the old console will live on. Doing everything from the web with NCM is too slow.

Is there a grace period once the licenses are deactivated or the minute I do this on old server our SolarWinds will stop working?

Thanks Richard! I'm going to be upgrading to the latest versions of NCM and NPM before adding the second polling engine.

Yes. We actually migrated NPM/NCM to a new server when upgrading and we didn't move the jobs from the old server, just recreated since it changed to a web based interface. The current job list shows only one nightly job enabled.

Are there any nodes backing up over the WAN? If so, Windows isn't updating the file sizes on the SFTP transfers until the file is complete. If it takes longer than 15 minutes to grab a single file (like a subscriber node TFTP for example), then DRS will timeout. I had to schedule a task that runs a dir /R every 5 minutes…

Disregard my previous post. Using the built-in admin account instead of a domain account with admin privileges did the trick.

I have the exact same issue. A reboot of the primary server didn't change the result. Any ideas on how to fix this? Thanks in advance.