Event ID 11327 – MsiInstaller. Invalid Drive: h:\
Posted on September 11th, 2008
When trying to install a Windows Installer (msiexec) .msi package, the following error may appear:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11327
Description:
Product: ‘Whatever this product name is’ — Error 1327.Invalid Drive: h:\
Tags: error, event id 1327, eventid 11327, invalid drive, msiexec, msiinstaller, shellfolders, usershellfolders, Windows 2003
Filed under Windows 2003 | No Comments »
Group Policy Editor – Disabling custom.adm template filtering
Posted on September 8th, 2008
When editing a Group Policy in Group Policy Object Editor (gpedit.msc), the settings may be missing from a recently added custom template (.adm).
The adm template may be configured with a filter that hides the settings in it’s default view.
To disable the filter so that all settings can be edited, do the following:
Right click on the relevant user configuration | administrative template and select filtering
Unselect the option to ‘only show policy settings that can be fully managed’
All the settings will now appear and can be managed.
Tags: filter, gpedit, GPO, group policy
Filed under Windows 2003 | No Comments »
What decides the installation directory on Windows 2003 x64
Posted on September 4th, 2008
When an application is installed on Windows 2003 x64 Edition, the installation is made to different directories and registry keys depending on whether it is a 32 or 64 bit application.
Directory location
- c:\program files – (64 bit applications)
- c:\program files (x86) – (32bit applications)
Registry location
- HKLM\software\ – (64 bit applications)
- HKLM\Software\Wow6432Node\ – (32bit applications)
So, what decides where the installation goes?
I have discovered the following from various digging about online.
Tags: 64 bit, install directory, installation location, program files (x86), Wow6432Node, x64
Filed under Windows 2003 | No Comments »
How to show drive letters first in My Computer
Posted on August 26th, 2008
By default, windows explorer and My Computer show the drive description before the drive letter as shown:
This order can be changed so that the drive letter gets shown first, as shown:
To change this order so that the drive letter gets shown first add the following registry key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Explorer
Add a REG_DWORD named: ShowDriveLettersFirst
Set the value to the desired level (4 is best)
- 0 – Show drive letters after description (default)
- 1 – Show network drive letters before description, and local drive letters after description
- 2 – No drive letter is displayed
- 4 – Show drive letters before description
You will need to logout and back in to view the change.
Tags: drive letter, order, reg, ShowDriveLettersFirst
Filed under Scripts/Reg, Windows 2003 | No Comments »
Troubleshooting the Windows logon process
Posted on August 19th, 2008
To troubleshoot the logon process, debug logging can be enabled. This is useful in a Citrix environment as the logon could be slow and the debug log file will show where the pauses occur during the logon.
Microsoft Technet article can be found here: Q221833
Use Registry Editor to add or to modify the following registry entry:
Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Entry: UserEnvDebugLevel
Type: REG_DWORD
Value data: 10002 (Hexadecimal)UserEnvDebugLevel can have the following values:
NONE 0×00000000
NORMAL 0×00000001
VERBOSE 0×00000002
LOGFILE 0×00010000
DEBUGGER 0×00020000The default value is NORMAL|LOGFILE (0×00010001).
Note To disable logging, select NONE (0×00000000).
You can combine these values. For example, you can combine VERBOSE 0×00000002 and LOGFILE 0×00010000 to get 0×00010002. Therefore, if UserEnvDebugLevel is given a value of 0×00010002, LOGFILE and VERBOSE are both turned on. Combining these values is the same as using an OR statement.
0×00010000 OR 0×00000002 = 0×00010002Note If you set UserEnvDebugLevel to 0×00030002, the most verbose details are logged in the Userenv.log file.
The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file. If the Userenv.log file is larger than 300 KB, the file is renamed Userenv.bak, and a new Userenv.log file is created. This action occurs when a user logs on locally or by using Terminal Services, and the Winlogon process starts. However, because the size check only occurs when a user logs on, the Userenv.log file may grow beyond the 300 KB limit.
The 300 KB limit cannot be modified.
Summary
RegKey: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\UserEnvDebugLevel
For full debug logging set to: 30002
Log file: c:\windows\debug\UserMode\userenv.log
Tags: debug, environment, logon, user, UserEnvDebugLevel, Windows 2003
Filed under Windows 2003 | 2 Comments »