aschmitt

This is pretty cool, I plan on implementing this tomorrow in our environment at work thanks for this post!

If that's the case then I would transfer what I have and perform the upgrade on the new environment then you can decom the old one sooner rather than later and the upgrade will take less time on the new system assuming the amount of upgrading you do. Hope that helps!

I would recommend upgrading the NPM version and comparing the performance increase from what you were running to the newest version on your old box. The upgrade process is very simple and strait forward and has very little downtime (less than 1 hour), that way you can see exactly how your old system can handle it. If…

Yes, from what I've seen it's actually recommended to move the database to a separate server when using NTA 4.0 etc, from my understanding all you should have to do is make a backup of the current database (compress it so it's not that large of a file). and load it onto the new server that you want to host the database on.…

try this: Remote to whatever server Orion is installed on and go to Orion Service Manager, turn everything off and back on. I didn't have the IIS issue but I did get the engine issue, make sure you let your team know (if you work with a team) that you'll be shutting down the services on that server so potentially you won't…