Hi, Is there anyway to make the domain user's home share drive persistent? Reason is, VPN users log on the machine without any connection, then start VPN After VPN is connected the home share drive can be only mapped manually I need an automatic way, without modifing things (AD, GP and etc) too much, is it possible? Thanks Andy

Here is an answer from another thread for W2K8 R2 (author Gunner999) You must do it manually via a the reconnect at logon drive mapping option in windows explorer or the /persistent:yes optoin in the net use command. A logon to active directory (allowing the Home Folder setting to be used) can only occur when the ctrl-alt-del logon box is used to initiate the logon. Therefore a logon via VPN does not meet this requirement, because a VPN client is used to perform the authentication, not the ctrl-alt-del. The back in the day, you could use the logon via dial-up connection check box on the clt-alt-del logon box to work around this limitation, but most VPN clients do not offer this option. Regards Milos

Hope this helps if Milos answer does not. Mine is more of a work-around than a fix We have to use a script that maps the drive. Our engineers could not figure it out either so we created this script for the user in question and then put it in their startup folder on the PC itself. Example **********************Map F & Y drives on SBMO Windows server ************************* @echo off net use F: \\servername\bankdata net use Y: \\servername\home\%userName%

This is not exactly what you need but it may help in an alternative way to reach shared resouces with clean "rollback". I have used simple workaround for simple access to share. It is in the form of script that "sits" on desktop. There are two lines in this script (say my_share.bat) explorer.exe \\server\share pause This works even for subfolder explorer.exe \\server\share\any_subfolder pause This opens Windows Explorer (WE) and the "lifetime" of open in given by user's hitting Enter. I could avoid various hangs and failed mappings. Even less skilled users have adopted this procedure without complaining. Of course the use is limited to simple file management and is not suitable for the case when any application expect shared drive character, say t: Regards Milos