I have a laptop connected to my domain runing windows 7. Everything works great until the laptop is no longer connected to my windows domain network. Once the laptop has been disconnected from the domain network i cannot run programs that relie on explorer.exe to run i get Server Execution Failed error. I have tried adding NT AUTHORITY\LOCAL SERVICE to the user group Administrator, this has done nothing.

Update:The user has Administrative privileges, I did a test with a regular domain user and they have no problem.

I am using a desktop and get the same error. It is something to do with the Desktop. If I launch any application from the start menu I don't get any problem. I need a solution please.

The problem has to do with having a shell folder (like Documents/Pictures/Music/Videos/etc) mapped to a network location, and that location is (temporarily or permanently) unmapped. For example: In my environment, I map P: to \\server\users\username so that I can use Group Policy to map their Documents/etc shell folder to P:\Documents (etc). This usually works GREAT, except that for laptop users that take their computers home and haven't connected to the domain via VPN or other method, the P:\ drive doesn't get mapped when the domain is unavailable at login. This triggers the error, and the proof is that when I temporarily map the P:\ drive to, let's say, \\computername\c$ the issue immediate goes away. I view this as a significant bug for corporate users and administrators, because I now have to either wait for a fix before deploying Windows 7 in my environment OR drastically change how my mobile users store their documents so that they're always accessible to them. I'm in the process this week of evaluating viable work-arounds, so I'll bookmark this and post my findings here in the hopes it will help others.

*BUMP*I'm having the same issue with notebooks on our SBS 2008 domain. Interestingly enough I don't have the problem with my home desktop running Windows 7 64 bit RC. But on two different notebooks, both running Windows 7 64 bit RC, and NOW one of them with Win 7 64 bit Ultimate RTM the problem remains.When I connect via VPN the issue goes away for the remainder of the session.I've also noticed, (and it may be unrelated) that when I try and play Fallout 3 on the home system, I cannot run it properly until I've connected to the VPN at least once. (Fallout 3 saves its save games in a My Documents subdirectory, which is mapped to the server redirected folder share.)Please advise, as this issue is crippling to notebook users, and we are having to postpone a number of planned Windows 7 rollouts for corporate clients until this is resolved.

The problem has to do with having a shell folder (like Documents/Pictures/Music/Videos/etc) mapped to a network location, and that location is (temporarily or permanently) unmapped. For example: In my environment, I map P: to \\server\users\username so that I can use Group Policy to map their Documents/etc shell folder to P:\Documents (etc). This usually works GREAT, except that for laptop users that take their computers home and haven't connected to the domain via VPN or other method, the P:\ drive doesn't get mapped when the domain is unavailable at login. This triggers the error, and the proof is that when I temporarily map the P:\ drive to, let's say, \\computername\c$ the issue immediate goes away. I view this as a significant bug for corporate users and administrators, because I now have to either wait for a fix before deploying Windows 7 in my environment OR drastically change how my mobile users store their documents so that they're always accessible to them. I'm in the process this week of evaluating viable work-arounds, so I'll bookmark this and post my findings here in the hopes it will help others. I've spent quite a bit of time on this and can confirm that it is an issue based on the summary I made above. The issue seems to be that it's annoyed that the user's critical shell folders are unavailable. The easiest solution is to use Group Policy to redirect any profile folders to UNC paths instead of static mapped drive paths (ie. \\server\share\user\Documents instead of P:\Documents). Then, enable Offline files synchronization if you need the files to be available while the network is not available.

Try this:Click "Start"Type "Folder Options" wait a moment, and press Enter.Go to "View," "Advanced Settings," "Launch Folder Windows in a Seperate Process."Is it Checked? As a matter of course on a new install, I always enable this. Through process of elimination I nailed that as the cource of my problem. I Unchecked that, and the problem went away on all machines I had it set on.Does this work for you guys?Good Luck!Stephen

This worked for me. Thank you!

I've had this problem for a few weeks now - and I've been searching up and down the Internet for a solution. Sure enough - the "LAUNCH FOLDER WINDOWS IN A SEPERATE PROCESS" was checked (old habit) and was causing this exact problem for me on a notebook outside of the domain. When I unchecked that - problem went away!BUT - now all my offline files / folders (Documents) went away as well... Group Policies that we use DO map a bunch of network drives (and those ARE available offline, where they should be) - but the SBS2008 policy of redirecting folders DOES map to a UNC path (\\servername\RedirectedFolders\%USERNAME%\My Documents) does NOT work.Funny - when the notebook returns to the network - all works again. This one seems like a bug for sure.Checking the OFFLINE FILES SYNC partnership - I see that the above URL "IS" setup to sync (and it does successfully). I can't explain why it's not there. Anyone know of any other work arounds??