Tuesday, December 04, 2012 4:47 PM
I was hoping someone could shed some light on a problem we are having when using the HIDESHELL feature in MDT2012. When we set HIDESHELL = YES, when the task sequence completes and the OS is logged in, there seems to be a delay in the shell or explorer.exe or something being ready to work. The issue we are having is that if we launch a .NET 3.5 executable immediately after the initial completion, we get very strange errors that seem like corruption. However, if we let it sit at the desktop for a minute or two then launch the .NET 3.5 executable, everything works as expected.
What exactly is HIDESHELL doing exactly? Is there a process or service we can watch for to ensure that the shell is fully loaded before trying to run the executable? Has anyone else experienced problems with HIDESHELL and running post-task sequence operations?
Any help would be greatly appreciated!
Thursday, December 06, 2012 11:40 PM
Hideshell simply replaces explorer.exe (your taskbar and start menu) as the default process to run when you log in.
So in your case, the action you want to watch for is explorer.exe
I would actually suggest adding a FINISHACTION=REBOOT as this would solve your problem in a much cleaner manner.
Friday, December 07, 2012 4:01 PMThanks for the reply. Actually the problem is going deeper than that. We are trying to deploy Windows 7 using the new ADK and MDT2012. We are finding a strange issue that when the TS is finished and you are sitting at the desktop, if you try to run a installer (we are using office 2007) it will work fine. However, if you reboot the system any installer (including office 2007) that uses .NET will fail. Office gets a strange IAssemblyCache failure in the event log, basically saying it couldn't load a certain .NET library. Anyone seen this issue? Turns on toggling HIDESHELL on or off makes no difference in this matter. Anyone seen this?
Friday, December 07, 2012 4:50 PMAre you installing applications as a part of the task sequence or using some other method?