Installing Administrative Tools on Windows XP

Below are the steps to enable remote administration for Windows Server technologies from a Windows XP.

  1. Go to and download adminpack.exe.
  2. Launch adminpak.exe and have it extract the contents to a common location.
  3. Go to the location where you had the files extracted and run adminpak.msi.
  4. Once you’ve finished installing the adminpak, you can to into the Administrative Tools folder that’s in the Control Panel and see all the available remote administration tools for Windows XP.

Installing Exchange System Manager for Exchange 2003 on Windows XP

In order to administer Exchange attributes for user accounts on Windows XP, you’ll need to install the Exchange System Manager for Exchange 2003. The steps below will guide you through the process.

  1. You must first ensure that you have IIS installed on the Windows XP machine. If it’s not installed then install it by going to Add/Remove programs, Add/Remove Windows Components, check the box for Internet Information Services (IIS), then click Next.
  2. On the Windows XP machine, go to the i386 folder within the source directory for your Exchange 2003 install, and launch Setup.
  3. Once setup has loaded and you’re presented with choosing the components to install, choose Custom for Microsoft Exchange and then Install for Microsoft Exchange System Management Tools.
  4. Once setup has successfully completed, you’ll now have Exchange tabs when looking at user accounts.

Reading WMI Information

When creating task sequences you’ll find yourself using alot of WMI filters to determine if a certain task needs ran on a machine. I’ve found WMI Reader to be an excellent tool to dig through WMI. It can be downloaded for free from softpedia.

Configure Auto Logon for Windows XP


You can configure Windows XP to autologon every time it’s booted up by configuring the following registry values. The registry import assumes that there’s a local account on the XP machine called User, and that account has no password.

Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon]

Managing the dns suffix search order with a script

Recently I ran into an issue where I needed to use a script to change the DNS Suffix search order on multiple Windows XP machines instead of using a GPO (which is the preferred way).

Prior to running the script, this is what you would see when you went to the DNS tab on the Advanced section of the properties for TCP/IP on your network adapter.

Here is what happens after you run the script.
Below is the VBS script. You can easily use ConfigMgr to deploy the script.

On Error Resume NextstrComputer = “.”
arrNewDNSSuffixSearchOrder = Array(“”, “domain2.local”)

Set objWMIService = GetObject(“winmgmts:” _
& “{impersonationLevel=impersonate}!” & strComputer & “rootcimv2”)
Set colNicConfigs = objWMIService.ExecQuery _
(“SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = True”)

For Each objNicConfig In colNicConfigs
strDNSHostName = objNicConfig.DNSHostName

Set objNetworkSettings = _
intSetSuffixes = _

Set colNicConfigs = objWMIService.ExecQuery _
(“SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = True”)
For Each objNicConfig In colNicConfigs Next

Have Windows XP run PnP scan after XP installation

If you ever have the need to have Windows XP do a PnP scan after the Windows XP installation during a task sequence, you can run the following command line.

rundll32.exe Syssetup.dll,UpdatePnpDeviceDrivers

The only thing you should be aware of is if the PnP scan detects hardware and you’re missing all or part of the driver for that hardware, a pop-up asking for the driver location will halt your task sequence until you click Cancel. Or, in the case that the driver in question is your NIC, you task sequence will fail.

Preventing data loss due to USB flash drives

***Not Fully Tested***

So I’ve been thinking lately about data loss due to a recent branch of our company all quiting at the same time and deleting as much data as they could without it being notible. (Luckily we had backups to restore what was deleted.)

So what I’ve come up with won’t prevent users from deleting data off their computers or the network, but it will prevent them from stealing information by copying it to flash drives and such.

Navigate to

then change¬†the dword “WriteProtect” to “00000001”. By making that change whenever a user tries to write data to a external drive they will get a write protect error.


Enabling Remote Desktop remotely

So I ran into the need to enable remote desktop on a computer about 300 miles away this morning. Here is what I did.

First off I logged into my virtual XP machine with a domain admin account. I then launched the registry editor and connected to the registry of the remote machine. I then navigated to the following path on the remote registry: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server

Once in the terminal server key, change the DWORD value for fDenyTSConnections from 1 to 0. (1 = Disabled, 0 = Enabled)

The remote machine won’t automatically start working, so you’ll need to reboot it. You can do this by running the following from command prompt.

shutdown -m remotecontroller -r