Upgrade windows 2003 to 2012

You need to raise the functional level to and then run the ADPrep. Then promote a server to a DC and the replication will take place. I am most of the way through a 2k3 to migration currently.

Adding the server side-by-side makes it easy to just promote the new one and remove roles on the old. If anything breaks I had issues with our exchange server you can re-enable the role quickly. As already said, bring the functional level to first. The biggest headache for me has been getting new print drivers loaded. The migration tool wouldn't work in my case. We have older printers and the old server was bit.

I had to find 64 bit drivers with a matching 32bit driver for 5 printer models. I do not have access to a server R2 install disk, I do however have a server install disk. I am operating under the understanding that I need to upgrade to a R2 schema before doing any migration and that is currently impossible for me to do.

You don't need the install disk to change functional levels.. Take a look at this How-To. Are there any other things I have to be informed about while doing it? Attachments: Up to 10 attachments including images can be used with a maximum of 3. In addition to the mentioned fact that there is no direct upgrade path, the fact that you have a custom application running under IIS adds another level of major complexity.

There have been very significant changes made to IIS since You need to test that application on IIS before you even think about attempting to upgrade.

So why not start at the beginning to reach the end? Build a system and install the application to see if it even runs on Do not do an in-place upgrade.

There is no direct upgrade path, it would need to be a multi-step process. The hardware is also unlikely to be supported for such a change. This operating system can be upgraded to Windows Server Enterprise Edition SP2 bit R2 version of Windows Server is available only for bit architectures. The first thing to do is to check if your hardware is compatible with the new operating system , by visiting this link:. Once verified hardware requirements, if the server has Domain Controller role , we must prepare the server for the upgrade.

If not the case, you can skip directly to step 3. In this case you have to force replication with secondary domain controllers or, if not possible, temporarily disable replication. If you see this error after the second adprep command, your domain controller is configured in compatibility mode, or Windows mixed, rather than in Windows Server native mode.

Now you can start the installation by double clicking on the setup. In the first instance, we are asked if we want to download the latest updates from the Internet before proceeding with the upgrade. Another common problem is the presence of Windows PowerShell v1. The error is:. It is located, depending on the architecture, in:.

If you still want to remove this warning, by performing a printers backup for the subsequent recovery on Windows Server after the upgrade, check out this link:. Once solved all the problems, Windows Server upgrade will take place: sit down and relax, waiting for files installation and system configuration, which involves several reboots.