Wednesday, June 4, 2008

Outlook: "Empty the Deleted Items Folder Upon Exiting"

Unchecked - dword:00000000
Checked - dword:00000001

Windows Registry Editor Version 5.00


Tuesday, June 3, 2008

Network Timeout bug in Windows PE 2.1 causes MDT 2008 Lite Touch to fail

Network Timeout bug in Windows PE 2.1 causes MDT 2008 Lite Touch to fail.

You get the following error message in MDT 2008 Lite Touch Deployment even though you have the correct nic drivers in Windows PE and the correct bootstrap.ini settings. "A connection to the deployment share \\Server\Distribution$ could not be made. The Deployment will not proceed"

A network initializion timeout issue in wpeinit.exe in Windows PE 2.1 causes MDT 2008 Lite Touch Deployments to fail.

Give WIndows PE 2.1 a few more seconds by editing startnet.cmd on your LiteTouch_x86.wim (or iso) to look like below


wpeutil InitializeNetwork
ping localhost

If you want the Deployment Workbench to include the updated startnet.cmd every time you update the Deployment Point just follow the below steps

Configure MDT to use the updated startnet.cmd

  1. Create a folder named D:\ExtraFiles\Windows\System32 and copy the updated startnet.cmd to it.
  2. In the Deployment Workbench, right-click the Deployment Point and select Properties.
  3. In the Windows PE Tab, in the Extra directory to add textbox, type in D:\ExtraFiles
  4. Click OK

Monday, June 2, 2008

HP Network Configuration Utility - Unable to create team

You receive an error message: "Unable to create team" (or similar) even after rebooting.

Also, HP Network Configuration Utility (NCU) does not appear as an uninstallable option in Add/Remove Programs.

Cause: Generally a corruption in cpqnic.xml

1. Rename "C:\Program Files\HP\NCU" to "C:\Program Files\HP\NCU.old"
2. Re-run the Proliant Support Pack (PSP) setup.exe
3. HP Smart Update Manager will advise "Installation Not Needed" for NCU
4. Locate NCU in the list, and select "Installation Options"
5. Select "Force Install"
6. Follow prompts and restart server.
7. Recreate the team as required.

VBScript: Error : An invalid dn syntax has been specified

You receive this error message when manipulating AD objects that contain characters including:

Reserved character Description Hex value

space or # character at the beginning of a string

space character at the end of a string
, comma 0x2C
+ plus sign 0x2B
" double quote 0x22
\ backslash 0x5C
< left angle bracket 0x3C
> right angle bracket 0x3E
; semicolon 0x3B
LF line feed 0x0A
CR carriage return 0x0D
= equals sign 0x3D
/ forwards slash 0x2F

Working with AD accounts and groups with reserved characters

For most reserved characters, you can use them in binding strings simply by placing a backslash (\) in front of the characters. This script will successfully bind to the !TestGroup group and report back the user’s CN:
Set objGroup = GetObject("LDAP://CN=\!TestGroup,OU=Accounting,DC=fabrikam,DC=com")
Wscript.Echo objGroup.CN

Related articles