Hello, maybe someone can help me. I've been searching the net for the last couple of days for a solution. We map our network drives via the group policy settings (using the create option). Now when a laptop is not connected to the corporate network the client takes some minutes to show the desktop after entering the credentials. A balloon tip pops up stating the network drives could not be restored. As far as I can tell you don't have the persistent option in the gp settings but it behaves like it is persistent. Other tips to use a logoff script sound bad because there should be a solution to this. Does anyone have a hint/solution? regards Marcel

mg79 wrote: Hello, maybe someone can help me. I've been searching the net for the last couple of days for a solution. We map our network drives via the group policy settings (using the create option). Now when a laptop is not connected to the corporate network the client takes some minutes to show the desktop after entering the credentials. A balloon tip pops up stating the network drives could not be restored. As far as I can tell you don't have the persistent option in the gp settings but it behaves like it is persistent. Other tips to use a logoff script sound bad because there should be a solution to this. Does anyone have a hint/solution? regards Marcel Are your laptops joined to the domain ? If yes, they will always try to reach the domain and that has to timeout before it resorts to local logon. I had no problems if drives are mapped via a logon script set by a group policy. The other options seem to be persistent to a certain extent. regards Wolfgang

Hi, If you use GPO to push a script which launch when startup. It would run every time after you logon the client. As a work around you could write a script to determine whether the computer is connected to the corporate network before you map the network drive. If not, exit the script. For more information about script you may access Scripting Guys Forum: http://social.technet.microsoft.com/Forums/en-US/ITCG/threads However, I would try to write script and test is on my side. If there is any progress, I would post here. Hope that helps Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The laptops are joined in a domain. Strangely they behaved the same when we used a traditional logon on script with persistent:no. I think this behavior started when we updated the domain to a 2008 R2 functional level.

I think you are right. I will also look into it at the weekend and will post my results.