Discover your system state, generate requirements, and validate the target environment.
Microsoft will end support for Windows Server 2003 on July 14, 2015. If you are running one of the 24 million instances–half of which are still on physical servers–that means it's time to start planning your migration. There are already vulnerabilities like Jasbug that will not be patched for Server 2003. If your boss thinks that Server 2003 doesn't need fixing because it still works, well, he or she is an idiot.
Even if you want to move, migrations aren't easy. That's where we come in. GuardRail provides a straightforward platform to discover your existing system state, document requirements, and test configurations after making the shift.
GuardRail starts by scanning all your servers and telling you what's really on them. It's probably been awhile since these 2003s were built and the documentation might have some holes. We'll tell you exactly what is on every machine right now.
GuardRail enables you to compare two or more servers to detect differences. Especially in older hardware like Server 2003 there is likely to be configuration drift. GuardRail differencing compares thousands of configuration items so you have machine-readable documentation of the desired state.
GuardRail is platform agnostic, so whatever OS you choose to target, GuardRail can validate that the new instance matches the requirements generated during discovery and assessment.
GuardRail can make your life easier by generating PowerShell DSC files based on existing configuration items. Scan a node, pick the configurations you want to declare in PowerShell, and GuardRail does the rest. Most importantly, the requirements gathered in the Discovery and Assessment phases can be executed as tests inside GuardRail, removing the effort of generating test scripts and the possibility of human error.
We've used GuardRail to perform enterprise scale migrations before. Download our white paper on data center migrations to start planning your strategy for July.