Windows
Configure 2008 Server Core Networking
Dec 3rd
So you’ve installed Windows Server 2008 Core, you don’t use DHCP and you want to get the thing on the network. I keep forgetting how to do this so I thought I’d create this post to help me remember!
I’m assuming that you’ve got as far as changing the administrator password and logging in. The next step is as easy as typing a few commands into the plain black window you see in front of you. For this example, let’s assume that we want the server to have the following network configuration:
HOSTNAME: win2008core
IP ADDRESS: 10.1.5.16
SUBNET MASK: 255.255.255.128
DEFAULT GATEWAY: 10.1.5.126
DNS SERVER: 10.10.20.6
DNS SERVER: 10.20.4.3
We first have to extract two pieces of information from the server. The current hostname and the index of the NIC that we want to configure.
The hostname can be acquired simply by entering the command:
hostname
This will return something like “WIN-87abac8chasa87″ or something random like that. Make a note of the name returned as we’ll need it later.
Next enter the following command:
netsh interface ipv4 show interfaces
This will return an output a bit like the one below. The important thing though is getting the index (Idx) value for the interface that you’re interested in (3 in this case). By default this will probably be called “Local Area Connection”.
To setup the IP details for the interface just enter the following command:
netsh interface ipv4 set address name="3" source=static address=10.1.5.16 mask=255.255.255.128 gateway=10.1.5.126
To add the DNS servers to this interface, use the following commands:
netsh interface ipv4 add dnsserver name="3" address=10.10.20.6 index=1 netsh interface ipv4 add dnsserver name="3" address=10.20.4.3 index=2
Note that we incremented the index value in the second command.
That was quite easy really. All that remains is to rename the server. This is done with another simple command using the value that we obtained earlier:
netdom renamecomputer WIN-87abac8chasa87 /NewName:win2008core
All that you then need to do is reboot the server:
shutdown /r /t 0
SIDs in Windows VMs
Nov 3rd
Today sysinternals retired the NewSID tool from their suite of utilities. Mark Russinovich (one of the writers of NewSID – the other being Bryce Cogswell) explains in his blog how the decision to retire the utility came about and it’s probably a surprise to many.
It has been a long held belief by man in IT that all Windows Servers and Desktops must have a unique SID. Certainly I recall having SID duplication issues back in the heady days of Windows NT but it’s not something that I have encountered as an issue since. Like many I just assumed that Windows uses SIDs still and so they must be unique still. But, as Mark explains, the way that Windows operating systems use SIDs is not the way that most people think it is and it is ok to have machines with identical SIDs.
From a VM perspective this is good news as it means that cloning VMs just got a tad bit easier. Although deploying a Windows VM from a template will require customisation and the use of sysprep (there is more than just the SID changed by sysprep) the process will probably only get easier. I hope.
Read Mark’s full blog post here.
Windows VM MAC Address Change
Oct 29th
Sometimes moving a server into a Virtual Infrastructure is not straightforward. Consider a server that has software on it that is licensed based on a MAC address for instance. MAC addresses start with a vendor ID and the rest of the address is made up with hexadecimal numbers to make each MAC address unique. VMware’s vendor ID is 00:50:56, all VM NICs will have MAC addresses starting with it.
So, suppose you have a piece of software installed on a Windows server that is licensed to a MAC address of 00:0B:CD:6D:17:D9. How do you P2V that server and still have the software work? More >
Non-Present Devices in XP / Vista
Jun 20th
My boot up time was increasing on my XP desktop and I knew this was in part to lots of drivers for hardware that I no longer have. So how do you identify and remove such drivers then?
These instrcutions are sort of XP based but will work on Vista too.
If this is a one off activity, open Device Manager using the following command line:
Devmgmt.msc set DEVMGR_SHOW_NONPRESENT_DEVICES=1
Then from the View menu select “Show hidden devices”. Hardware that was connected to your computer but no longer is will appear with a faded icon. You can right click and select to uninstall it.
Another way to accomplish this is to add “DEVMGR_SHOW_NONPRESENT_DEVICES” with a value of 1 as a system or user environment variable. Any time Device Manager is run, you can just select “Show hidden devices”.
The Arc – Microsoft Architecture Magazine
May 7th
I haven’t read it yet (not enough hours in the day) but I came across The Arc Magazine yesterday. Described by Microsoft as “a multi-part publication showcasing the Microsoft ‘Software + Services’ strategy from an architectural perspective” it’s availble to download from Microsoft’s MSDN website.



