Autorun keys for new users and/or add registry keys to HKEY_CURRENT_USER

its rather simple, create an entry in the “HKEY_LOCAL_MACHINESOFTWAREMicrosoftActive SetupInstalled Components” key. the entrees in this key is the stuff you se in the upper left hand corner during first log on. (the Personalized Settings box). Most if not all entries in this key will be in the GUID format, but it does not have to be..

Open REGEDIT and follow the instructions below.

image Right click Installed Components and click New KEY, and name the key {Z-UserSetup}. NOTE: The different keys are executed in number and alphabetical order, so to make sure our key is executed last we name it Z-“something” and put it in { }. Everything not in curly braces wile be executed first.
image In the new key create two new String Values (REG_SZ) and name them
StubPath and
Version. StubPath has info on what we want to run, and could be any executable, script, run.dll e.t.c. Version will show in the Installed Components section in CURRENT_USER

(Default) will be the info showed in the Personalized settings box during logon. (can also be sat as @=”info”)

Now just reboot and log on with a different user, and notepad will be executed during logon.

If you want to set this with a script ,then here small one for disabling the Windows Media Player wizard.

Set oShell = CreateObject("WScript.Shell") 

RegPath="HKEY_LOCAL_MACHINESOFTWAREMicrosoftActive SetupInstalled Components{Z-UserSetup}"
oshell.RegWrite Regpath & "Stubpath", "reg.exe add HKCUSOFTWAREMicrosoftMediaPlayerPreferences _
/v AcceptedPrivacyStatement /t REG_DWORD /d 1 /f", "REG_SZ"
oshell.RegWrite Regpath & "Version", "1.00", "REG_SZ"
oshell.RegWrite Regpath & "@", "Accept MP Privacy Statement", "REG_SZ"

you can add as many as you want, just remeber the execution order.

CONFIRMED – Windows 7 RTM, Server 2008, and Office 2010 Beta Leaked

Full details at:

The previously rumored leak has been confirmed.

Wzor has placed the download links to the Windows 7 RTM on their home page, and it definitely the real deal. The build string is:

Windows 7 7600 RTM (x64):
Size: 3,224,717,312 bytes
MD5: E6CE9644D0C7A8E1C950D257A7B2C8A4
SHA-1: 31849B315290EFABFD81F967ED3C553D82925E4C

Windows 7 Server 2008 RTM (x64):
7600.16384.amd64fre.win7_rtm.090710-1945.serverenterprise_en-us_vl. serverenterprise.vhd or
SIZE: 6,857,337,856 bytes
CRC: 2AA7974F
SHA1: EA13B569AD4EA4F34955D1FB8A7ADFF8A30297E6
MD5: EC65EE9F3B18F7A232F8B0073A02216A

Office 2010 Beta (x86):
Size: 798,101,835 bytes
CRC32: 8BE7AB28
MD5: 874AE2B75AD8FAF169784AFEC099B526
SHA-1: E8E13E9DF771314C2B8A615B4952A49DDE3C9117

Office 2010 Beta (x64):
Size: 893,402,501 bytes
MD5: 24A46B000B79520969508CF940D6D581
SHA-1: E22690C6E63ACF0D0BDF9588E8308C5C855A38BC

Windows 7 leaked – official believed-to-be-RTM:

I downloaded this ISO and can confirm its hashes match those of the official believed-to-be-RTM:

File Name: 7600.16384.090710-1945_x64fre_client_en-us_Retail_Ultimate-GRMCULXFRER_EN_DVD.iso CRC32: 1ee7dc6f MD5: e6ce9644d0c7a8e1c950d257a7b2c8a4 SHA1: 31849b315290efabfd81f967ed3c553d82925e4c


Also, here are the properties of the setup.exe:

A fatal error occured while trying to sysprep the machine. Windows 7

I was trying to sysprep a Windows 7 image (build: 7201)

Everytime i started the sysprep process, it was fail with the error: “A fatal error occurred while trying to sysprep the machine.” seems to be a problem with the windows media player. (wmpnscfg.exe) after killing the process, the deployment process ran smoothly.. had to kill it twice once, seems to be starting again after some time… in my case i had to kill the process twice..

Go ahead! Create your own txtsetup.oem…

The txtsetup.oem File Format

During the text-mode setup phase of operating system installation, the Setup program installs drivers for devices that are required to boot the machine. Most of these drivers are included with the operating system. A vendor can enable users to install an additional driver during text-mode setup by supplying a txtsetup.oem file on a floppy disk.

A txtsetup.oem file is a text file that contains the following information:

  • A list of the hardware components supported by the txtsetup.oem file
  • A list of the files to copy from the distribution disk for each component
  • A list of the registry keys and values to create for each component

This section describes the format of a txtsetup.oem file. For additional information, see Installing a Boot Driver.

A txtsetup.oem file consists of several sections that use the following general format:

entry = value1,value2,...

The name of the section is enclosed in square brackets ([ ]). A pound sign (#) or semicolon character (;) at the beginning of a line indicates a comment. Strings with embedded spaces, commas, or hashes must be enclosed in double quotes (” “).

A txtsetup.oem file must include the following sections:

A txtsetup.oem file for a PnP mass storage device must also include the following section:

SCCM PXE/WDS with Remote DHCP Server

SCCM PXE/WDS with Remote DHCP Server

Add the following DHCP Scope Options:

060   PXEClient

066   IP Address of WDS Server



These are required steps if your DHCP Server is on a different subnet than your SCCM/WDS/PXE Server.

Here is a good KB Article on this subject – and

SCCM 2007 OSD Drivers Show as New Hardware Found when you Login

Well funny thing, after OSD deployment the Found New Hardware Wizard shows up… DOH!

Thinking about drivers like KB888111… and strangely enough one Primary IDE Channel…

Pretty simple solution (Like in BDD / SMS 2003 OSD)

rundll32.exe Syssetup.dll,UpdatePnpDeviceDrivers

Before adding this to your task sequence, just run this command on a system that shows new hardware found. You should see in the task bar, new hardware found and when you look at the Device Manager, you should not see any warnings or errors. Remember, you still need to make sure your proper drivers are available.

Thanks to Brian S. Tucker

wpeinit.exe Unable to Locate Component "wdi.dll"

so…. the problem seems to be VM Ware’s VM Server 1.0.4… (ESX/GSX) .. Could give some very “funny” problems when running a cluster with 1.0.3 and 1.0.4 nodes.. DOH!

Download the Intel e1000 drivers from for both XP and Vista. Put them in D:DriversIntel

using Windows AIK command prompt:

1.  In the command window, run copype x86 c:winpe to initialize my WinPE environment.

2.  Run the imagex /mountrw c:winpewinpe.wim 1 c:winpemount command to populate the image folder.

3.  Run the peimg /inf=D:DriversVMWarescsi*.inf /image=c:winpemount for all drivers (e.g. SCSI, NIC,etc.).

4.  Run the peimg /inf=D:DriversIntelPRO2KXP*.inf /image=c:winpemount for the Intel e1000 drivers.

5.  Add the ..WindowsSystem32wdi.dll from a Vista machine to the c:winpemountWindowsSystem32 folder.

6.  Run the imagex /unmount /commit c:winpemount to update the c:winpewinpe.wim.

7.  Run the oscdimg -n -h c:winpeiso c:winpewinpe.iso to generate the boot ISO file.
edit the *.vmx file to add the entry Ethernet0.virtualDev = “e1000” after Ethernet.preset = “TRUE” entry using Notepad.
The configure the VM to use WINPE.iso creating in Step 7.