Ok here is what I am looking to do. I want to create a UBCD4win custom CD that can be given to remote office locations and the users can boot to the CD, however are not able to access the functionality w/o a password. However, I would also like vnc server to be turned on and fully active, without the user having to put in a password. This would give the home office IT staff the ability to get into the remote system(lets say system downed, OS borked, etc). However, we are trying to avoid giving the user access to what UBCD4win can do unless we absolutely have too. We would also like VNC to use MS login AD authentication.

THIS thread explains how to autostart vnc.

I went over this thread and was able to get VNC to auto start. What I am having trouble with is getting VNC to use ms logon(i udnerstand why that is a challenge), and more importantly some way to lock the user out of the console, yet allowing tech support at the home office to VNC in. The idea is for the user to pop the CD in, boot, and for remote tech support to take over. If support needed the user to be able to access the console, they would provide the user with the password(which ideally would be controlled via active directory).