W2K3 to W2K8 Active Directory Upgrade Considerations

I have collected some upgrade considerations from a couple colleagues of mine and have been sharing them on our internal technical DLs as the question comes up.  I have gotten positive feedback on the notes and have been encouraged to post them.  So, here they are.  Though, the real thanks go out to my colleages Tom and Arren.

Here are some of the problems customers run into when upgrading W2K3 DCs to W2K8

A very comprehensive list of solutions to problems people run into when upgrading from a Windows 2003 domain to a Windows 2008 domain.  Thank you Glenn LeCheminant.

Don’t even waste time on it.

Oh, I’m sure you COULD get it to work, but I would not bother.

Update 29 July:
It is not compatible as SMS 2003 hooks into IIS.  And that is not possible with Windows Server 2008.

THIS IS A WORK IN PROGRESS

1. Install Windows 2008 Server Core
2. When finished, logon to console with Administrator / <no password>
   You will be prompted to change the password.
3. Install the RealTek network driver, with the command
   pnputil -i -a <path to extracted driver files>netrtx32.inf
4. Configure a (static) IP address
5. Enable Remote Firewall Management.  This will allow you to manage the firewall from a client PC
   netsh advfirewall set currentprofile settings remotemanagement enable
6. Enable Remote Desktop Access, by typing the following commands on the Server 2008 Core console
   cscript C:\Windows\System32\Scregedit.wsf /ar 0
   netsh advfirewall firewall set rule group=”Remote Desktop” new enable=yes
7. Apply any patches from Windows Update
   Fermin Sanchez Central – How to patch Windows Server 2008 Core

Ingredients

• Windows 2008 Server DVD
• Realtek network driver, extracted to a USB stick.
• Download the Microsoft Remote Server Administration Tools for Windows Vista Service Pack 1 32-bit
• Install RSAT on a client PC, and then enable it.

References

• Managing Windows 2008 Server Core Local Settings
• Server Core Installation Option of Windows Server 2008 Step-By-Step Guide
• The things that are better left unspoken – Remotely managing your Server Core using RSAT
• Keith Combs’ Blahg – Windows Server 2008 Core screencast
• Fermin Sanchez Central – How to patch Windows Server 2008 Core
• Smart-X Core Configurator
• Upgrading the RAM on Eee Box
• My Core box. How to turn a near obsolete PC into a Lab Domain Controller.
• http://www.coreconfigurator.com/

TO DO

Installing PHP / MYSQL / WordPress

Some sort of free Proxy software

Microsoft releases Windows Server 2008 to manufacturing, and it’s already at SP1!

WTF!?!

Yeah.  At first glance you may think it strange that a first version of a product would already be at SP1 level.  So I thought I would throw out a couple of reasons why Windows Server 2008 is at SP1 already.  NOTE: Only ONE of the following reasons is correct:

A.  We call it Service Pack 1 because we want to have something to say to the customer who is always “waiting for SP1″.  “Here you go!”

B.  We call it Service Pack 1 because it sounds like it’s of a higher quality.

C.  We call it Service Pack 1 because it IS of a higher quality.

The correct answer is C.  Windows Server 2008 is indeed of a higher quality,

- Why is Windows Server 2008 at SP1 already-

Microsoft (Kevin Remde) claims C.  To my mind, it’s marketing BS.  Listening to my cynical heart, the REAL answer is A.
I’m sure the market will decide whether to wait until SP2 before adopting.  I’d be tempted to adopt it now for WDS Multicasting.