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!