I have a task sequence that is running. It works great. My task sequence does not boot into WIN PE, and does not have the OSDGINA.dll set as the default gina. My task sequence runs a script that renames the computer and adds it to a new domain. After this process, it reboots the machine and runs 2 more application installs, upon reboot. My problem is that I can not tell when the task sequence is running, and when it is finished. So the I have site staff logging on to config the machine, before the 2 applications install. This just causes mass confussion, for site staff. Question: Is there a documented way, on how to lock the User Interface until the 2 applications are done? I am guessing it has something to do with setting the gina chain, but wanted to see if this process has already been created by someone, so that I do not have to recreate the "wheel". thanks

No. Locking the UI is fraught with issues -- specifically recoverability and/or troubleshooting if something goes wrong. What you are doing, although it technically works and many people use it, is a little outside the intended design of ConfigMgr. You could try using ServiceUI.exe from UDI to display a message on the interactive desktop: http://blogs.technet.com/b/cameronk/archive/2011/01/25/can-i-use-serviceui-exe-to-launch-other-programs-besides-the-udi-setup-wizard.aspx. You could also use rpeorting to track task sequence status and provide visibility to the necessary report(s) to do the same.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I am not sure I explained my issue correctly. I currently am not using the OSDgina.dll. I was just wondering, if this was the process that makes the White and Orange, Config Manager OSD background. Example: while in a task sequence. This is what I was wanting to use. I am trying to lock down a task sequence. The easiest example, that I can think of, would be the application install process, after an image has been installed. The machine boots to the OS and installs applications. You get the white and orange background, with the task sequence blue box on top of it. Even though you are no longer booted into WinPE, the UI is locked, and users can not log on. Does this make more sense? Thanks for the help.

No, I understood the spirit, was just offering a different possibility for displaying a message on the desktop when the TS is finished so that you and your Techs know when it is finished. OSDGina.dll is only used for XP installations, there is a special hook in Vista+ that OSD takes advantage of to achieve a simlar result. To my knowledge, OSDGina.dll just automatically logs the system in as the local SYSTEM account w/o user input. The actual "locking" behavior though is the result of the system being logged in as local SYSTEM and explorer not being the default shell -- it's not really locked at all as you can still push F8 and do whatever you want although a normal user would be at a loss to do anything on the system. There is no built-in way to achieve a similar result. But you could use ServiceUI.exe to display a message scaring people away, not equivalent, but it may achieve your desired goal. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks Jason I will take your advice and see how I can get the serviceui.exe to work for us.