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.

Hits: 215

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.

Hits: 69

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.

Hits: 46

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]

Hits: 58

Customize Windows 7 OEM Information

The following will show you how to customize the Windows 7 (and Windows Vista) OEM information to display information more specific to your environment. You’ll be able to add information like Manufacturer information, Support hours, Support phone number, and a Support website. (Oh yea, and add a custom logo image.)

The first thing you want to do (assuming you want to have your own logo image) is to create a 120 pixel by 120 pixel 24-bit bitmap image file. You’ll then need to place this file somewhere on the the local disk of the PC. I suggest creating a folder called OEM under the System32 folder and placing the image there with the name of OEMLogo.bmp. (C:WindowsSystem32OEM)

Now you need to open up the registry editor and go to HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionOEMInformation.

To add your custom logo, go tothe OEMInformation key create a new Reg_Z string value and name it Logo and give it a value of the path to the folder in which you put your image file.

To add a manufacturer name, create a Reg_Z string and name it Manufacturer and give it a value of whatever you would like the manufacturer to be.

To add support hours, create a Reg_Z string and name it SupportHours and give it a value of whatever you want your support hours to be.

To add a support phone number, create a Reg_Z string and name it SupportPhone and give it a value of whatever you want your support number to be.

To add a support website, create a Reg_Z string and name it SupportURL and give it a value of whatever your website is.

Look at the example image below if you’re not getting anywhere with the instructions above.

Here’s a quick registry import to.

Windows Registry Editor Version 5.00

“Manufacturer”=”Company Name”
“SupportPhone”=”1-800-888-8888 ″

Hits: 527

Run As funcationality in Windows 7

By doing the following you’ll be able to get the “Run As” functionality back when you right click a shortcut or executable in Windows 7.

First obtain ShellRunAs from Windows Sysinternals. (Quick link here)

Next from the following command through command prompt.

shellrunas.exe /accepteula /reg /quiet

All done. You should now be able to right click shortcuts and executable’s and easily get a Run As prompt.

Hits: 115

Installing Exchange System Manager for Exchange 2003 on Windows 7

This morning my colleague decided that he wanted to upgrade his XP machine to Windows 7. Other than myself, no one else on the support team had Windows 7, so the need to have Exchange 2003 tools integrated into Windows 7 wasn’t there until this morning. ( I always remoted into a Windows XP machine or into the server.)

So after looking into how to get Exchange 2003 tools on a Windows 7 machine, I came up with this.

  1. Download the “Exchange System Manager for Windows Vista”
  2. On the Windows 7 machine, go to Control Panel -> Programs and Features -> Turn Windows features on or off -> Expand Internet Information Services -> Expand Web Management Tools and then install all of the IIS 6 Management Compatibility tools.
  3. Open Command Prompt on the Windows 7 machine as an Administrator and navigate to where you stored ESMVISTA.msi.
  4. Run “ESMVISTA.msi /q”
  5. You should now be able to open up the properties on a user account through the ADUC and see your exchange tabs.

Hits: 178

Deploying Server 2008 R2 Std via SCCM

I was asked to create a deployment for Server 2008 R2 today. I figured it would be easy as hell, however that wasn’t the case. The task sequence kept throwing an error on the “Setup Windows and ConfigMgr task. Ends up it was due to the product key. After messing around with the TS over and over again, I found that if I removed the product key the TS would finish successfully. I ended up finding out that the copy of Server 2008 R2 that I got off my companies licensing site doesn’t allow for a MAK key to be entered during setup. After some more searching online however I found a way to input the MAK key another way so that when the OS went to automatically activate itself it wouldn’t throw an error.

What you need to do is add a Run Command Line task to your TS that comes after the OS is already installed. Put in the command line “SLMGR.VBS -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX” and then tell it to start in %system root%system32.

By doing that you’re specifying a product key to be used during automatic activation.

Hits: 243