Migration DHCP Server from 2003 to 2008 or 2008 R2

Based on the Microsoft Windows DHCP Team Blog a migration of DHCP Server from 2003 to 2008 (or 2008 R2) is quiet easy actually.

On 2003:

• netsh dhcp server export c:\dhcpdatabase.dat all
• if DHCP Server hasn’t been unauthorized automatically, unauthorize DHCP Server

On 2008 (and 2008 R2):

• copy the dhcpdatabase.dat to the local disk
• netsh dhcp server import c:\dhcpdatabase.dat all
• authorize DHCP Server

When all is done with success, you can uninstall DHCP Server from the 2003 server. Make sure that if you have firewall(s) or other devices relaying towards the DHCP Server to adapt their configuration and if applicable firewall access rules.

Location of log files: C:\WINDOWS\system32\dhcp

Migration of DHCP Server from Windows Server 2003 Windows Server 2008
http://blogs.technet.com/b/teamdhcp/archive/2009/02/18/migration-of-dhcp-server-from-windows-server-2003-to-windows-server-2008.aspx

Windows Server DNS root hints

Thanks to the integrated Best Practices Analyzer tools in Windows Server 2008 R2 I recently discovered that some DNS servers didn’t have the correct root hints configured. Found 2 excellent references regarding this, and this again proves the use of those BPA tools!

First link expains the warning reported by the BPA and documents the default list of root hints.

DNS: Root hint server <IP address> must respond to NS queries for the root zone
http://technet.microsoft.com/en-us/library/ff807382%28WS.10%29.aspx

An updated list of root hints
ftp://ftp.rs.internic.net/domain/db.cache

Windows Server 2008 R2 DNS breaks WPAD

When you introduce a Windows Server 2008 R2 DNS server in your network and you use WPAD based on a DNS entry, it will be blocked by default.

To check the settings:

dnscmd [<ServerName>] /info /globalqueryblocklist

example:
dnscmd 192.168.1.1 /info /globalqueryblocklist

To change the settings:

dnscmd [<ServerName>] /config /globalqueryblocklist [<name> [<name>]…]

example:
dnscmd 192.168.1.1 /config /globalqueryblocklist isatap

 

Windows Server 2008 R2 Breaks WPAD
http://www.bohack.com/2011/02/windows-server-2008-r2-breaks-wpad/

Symantec Backup Exec reports warning regarding lsi_sas.sys after V2V conversion

Noticed this detail when I migrated some machines between a stand-alone ESXi 5.0 host and a cluster (no shared storage or anything) using vConverter 5.0 for Windows Server 2008 R2 machines: after the V2V conversion Symantec Backup Exec 2010 R3 reported a warning "Backup- \\SERVER.vanwellen.be\System?StateVSS Snapshot warning. File c:\windows\\systemroot\system32\drivers\lsi_sas.sys is not present on the snapshot."

What actually happens is that the following registry has been altered, reconfigure the key with the original (and correct) value solves the warning! No restart needed.

HKLM\SYSTEM\CurrentControlSet\services\LSI_SAS\ImagePath

Bad value (after V2V): \SystemRoot\system32\drivers\lsi_sas.sys

Good value (original): system32\drivers\lsi_sas.sys

Active Directory default Tombstone lifetime

Great post by Joe regarding Active Directory default Tombstone lifetime, a must read article!

Default Tombstone Lifetime yet again… Alternate working title: TechNet why do you hate tombstoneLifetime and correct information?

Upgrade edition in-place are possible as from Windows 7 and 2008 R2

As from Windows 7 and 2008 R2 it is possible to upgrade edition in-place using the DISM utility. However you can’t downgrade, it’s 1 way only.

Possible upgrade paths are:

- Windows Server 2008 R2 Standard -> Windows Server 2008 R2 Enterprise -> Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Standard Server Core -> Windows Server 2008 R2 Enterprise Server Core -> Windows Server 2008 R2 Datacenter Server Core
- Windows Server 2008 R2 Foundation -> Windows Server 2008 R2 Standard

You can’t perform the operation on a DC, to accomplish this on a DC, you need to transfer FSMO roles (if applicable), demote it, reboot, upgrade, reboot, promote it, reboot.

To determine the installed edition, run:
DISM /online /Get-CurrentEdition

To check the possible target editions, run:
DISM /online /Get-TargetEditions

Finally, to initiate an upgrade, run:
DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Reboot at the end to activate the change.

 

EDIT 24-03-2012: I recently had the problem that the command returned "1605" error stating that the product key entered wasn’t correct, however the key was valid. Solution was: upgrade using a KMS key (see Microsoft website for those) and afterwards change product key to the final key.

 

TechNet Blogs – Server Core : Upgrading Windows Server 2008 R2 without media

Microsoft TechNet : Windows Edition-Servicing Command-Line Options

Create WPAD/PAC files the easy way…

A very basic but flexible WPAD/PAC file with which you can start:

function FindProxyForURL(url, host) {
    //check for local domains
    if (dnsDomainIs(host,"fqdnA.internal.domain"))   {return "DIRECT";}

    //check for local IP addresses
    if ((shExpMatch(host,"127.0.0.1"))
        || (shExpMatch(host,"10.*.*.*"))  // Enter you local IP subnets
        ) {return "DIRECT";}

    //check for short host names
    if (isPlainHostName(host)) {return "DIRECT";}
   
    //else return proxy
    return "PROXY proxyA.internal.domain:8080";
}

 

McAfee KnowledgeBase – Web Gateway: Using PAC files with Web Gateway

Microsoft BPA’s on Windows Server 2008 R2

They are now installed when you add a role to a Windows Server 2008 R2 installation, updates are released through MU. Use them to have a check on your configuration settings!!

Best Practices Analyzer
http://technet.microsoft.com/en-us/library/dd759260.aspx

Running and Filtering Scans in Best Practices Analyzer
http://technet.microsoft.com/en-us/library/dd759206.aspx

Reclaim disk space after service pack installation on Windows Server 2008 & R2 / Vista / 7

After installing a service pack you will notice that the used disk space is increased. This because of uninstall files. You can free up disk space by making the service pack permanent, meaning you can’t uninstall it anymore… This also counts for Vista and 7 installations.

Windows Vista SP1: vsp1cln.exe /verbose

Windows Server 2008 SP2: COMPCLN.exe /verbose

Windows Server 2008 R2 SP1: dism /online /cleanup-image /spsuperseded

More information in the deployment guides.

Windows Server 2008 SP2 Deployment Guide
http://technet.microsoft.com/en-us/library/dd351467%28WS.10%29.aspx

Deployment Guide for Windows Server 2008 R2 with SP1 and Windows 7 with SP1
http://technet.microsoft.com/en-us/library/ff817650%28WS.10%29.aspx

How to reclaim space after applying Windows 7/2008 R2 Service Pack 1
http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-reclaim-space-after-applying-service-pack-1.aspx

FSMO roles…

You want to know about FSMO roles? Then read this! (and the links in that great blog post)

The Impact Of FSMO Roles Not Being Available
http://blogs.dirteam.com/blogs/jorge/archive/2011/07/11/the-impact-of-fsmo-roles-not-being-available.aspx