First it was the IIS box serving this site, but now it's going to be the whole network that's moving to Windows Server 2008. I'm attempting to go with a complete new forest installation, which will force migrating everything over from the old Server 2003 forest, so that should be interesting. And now, onto the first notes about that experience!

So...here's what's happening: installing a "new" server using Windows Server 2008, making it the first DC in the domain, and then installing Virtual Server 2005 R2 SP1 Enterprise (okay, can that name get any longer?!) without installing IIS. And it's the Core version of Server 2008, so everything is via the command line. After having worked on it for the better part of today, I'm now sitting here wondering why the heck anyone would use Core. I mean, if I wanted a command line only interface, I'd just use BSD or Linux!

For future reference here are a couple of things:

Useful commands:

pnputil -i -a <inf> (install device drivers (I think...I haven't confirmed if this actually installed them yet))

cscript %systemroot%\system32\scregedit.wsf /au 4 (Enable automatic updates)

cscript %systemroot%\system32\scregedit.wsf /ar 0 (Enable Terminal Services)

cscript %systemroot%\system32\scregedit.wsf /im 1 (Enable remote IPSec management)

netsh interface ipv4 show interface (get the list of names for use in other netsh commands)

Feldspar:

netsh interface ipv4 set address name=2 source=static address=10.0.1.9 mask=255.0.0.0 gateway=10.0.0.1

netsh interface ipv4 set address name=3 source=static address=10.0.1.10 mask=255.0.0.0 gateway=10.0.0.1

netsh interface ipv4 add dnsserver name=2 address=10.0.1.9 index=1

netsh interface ipv4 add dnsserver name=3 address=10.0.1.10 index=1

Useful links:

http://blogs.technet.com/shinsley/archive/2007/04/19/windows-server-longhorn-server-core.aspx

http://blogs.technet.com/server_core/archive/2008/04/16/reducing-the-server-core-disk-footprint.aspx

http://support.microsoft.com/kb/890893/en-us