I have experienced this issue with IE7 and the Run-Once customization hanging. Not sure exactly why this occurs, but it seems most often on clean systems that have had files and settings transferred over using the USMT. Most recommendations are to disable the run-once customization from coming up, even Microsoft has a knowledge base article that instructs users on how to do so. But this is a workaround and it doesn't resolve the issue. In fact if you use the work around you may notice that when you try to add or change default search providers that it doesn't work.
The solution is to change the key found in:
HKEY_CLASSES_ROOT\TypeLib\{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}\1.1\0\win32
Most likely if you are experiencing this issue the default key will have the following value:
C:\WINDOWS\system32\shdocvw.dll
(Note if you are using a 64-bit O/S the value may start with C:\Windows\SysWOW64\shdocvw.dll)
Change the value to:
C:\WINDOWS\system32\ieframe.dll
(Note if you are using a 64-bit O/S the value will be C:\Windows\SysWOW64\ieframe.dll)
Restart your browser and this should resolve the issue.
Wednesday, March 31, 2010
Friday, March 5, 2010
Configuring Services Startup Type from the Command Line
After installing a custom image using MDT2010 I noticed that aero was not enabled for my theme. In my task sequence I added the following command to run the Windows System Assessment Tool (Winsat)
winsat formal
This did not work and Aero still was not enabled.
To resolve the issue I found that the Desktop Window Manager service was not started and was set to manual. After starting the service, Aero was there in all its transparent beauty!
To have this happen during the build I added the following commands to the task sequence which start the service and set the service startup to automatic.
net start uxsms
Net can be used to start and stop a service but not to change the startup type of a service. To do so you must use the following command:
sc configstart=
The values that can be used for mode are
auto: Automatically start the service
boot: Start service as a device driver loaded by the boot loader
demand: Manually start the service
disabled: Disable the service from running
system: Start a service during kernel initialization
For example,
sc config uxsms start= auto
winsat formal
This did not work and Aero still was not enabled.
To resolve the issue I found that the Desktop Window Manager service was not started and was set to manual. After starting the service, Aero was there in all its transparent beauty!
To have this happen during the build I added the following commands to the task sequence which start the service and set the service startup to automatic.
net start uxsms
Net can be used to start and stop a service but not to change the startup type of a service. To do so you must use the following command:
sc config
The values that can be used for mode are
auto: Automatically start the service
boot: Start service as a device driver loaded by the boot loader
demand: Manually start the service
disabled: Disable the service from running
system: Start a service during kernel initialization
For example,
sc config uxsms start= auto
Subscribe to:
Posts (Atom)