Offline Files with mapping network Drives

I've encountered a problem with offline files that I can not find a clear resolution to.  The user in question has a laptop which he takes home or on travel frequently.  The setup once worked on his system, but he has since gotten a new laptop and we had problems getting the setup to work.  He puts his My Documents on his network drive (maps automatically with a login script) and then points his my documents folder to there.  This works fine when the machine is hooked to the network.  The Offline Files feature also seems to be working fine because we can unplug the network line and he can still access files and they will syncronize and whatnot.  The problem is when he logs in and the computer is not attached to the domain.  The P drive will not map automatically.  When he tries to open his my documents, it throws up an error saying that the drive could not be reached.  Changing the login script is not really an option due to the vast amount of users it affects.  there has to be a simple solution to this, yet I've wasted too much time trying to find it.

Thanks in advance.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robert Sutton JrSenior Network ManagerCommented:
You should sync your files before going offline therefore the files are accessible whether connected or not.
If the drive mapping was "persistent" everything should work fine. So, I am assuming it is not persistent and part his Logon script looks something like this:

net use p: "\\serverABC\homedirectory\%username%" /persistent:no

If this is true you could work around by mapping an different drive to his network location and select "Reconnect at Logon" and then point his My Documents to the other drive.   Make the new drive available offline instead of the P drive

net use h: "\\serverABC\homedirectory\%username%" /persistent:yes

Basically he would now have two drives mapped to the same place, however the new one will will work when he logs on offline.

Note:  You will get errors on certain file types such as MDB and PST.  You are not able to syc these files.
clark-jaAuthor Commented:
changing the login script isn't really an option, as it is complex enough as is.  this setup USED to work for this user on a previous machine.  also one of our guys has a machine that the setup works with fine.  So when he unplugs his network, logs in (none of his network drives will map), he can still open his my documents.  My system got the same error.  I ended up formatting my system, just to get rid of all previous offline files settings that might cause a conflict and got the same error again after I set it back up.  is this something simple i'm missing that I can avoid remapping the same drive manually?
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Are you telling it to show your P drive offline as well as My Documents?  Try with just making My Documents available offline.

How do you have My documents mapped?  

 P:\homedirectory  or \\serverABC\homedirectory

Try mapping My Documents to \\serverABC\homedirectory, then make My Documents available offline rather than making the P drive available offline.   If the system is trying to map P: during logon even when not connected to the network I think it will be an issue with offline files if you choose P: to be available offline.  
I have a number clients who use offline files when away from the corporate network.  Works great, but their P: drive  and other drives are mapped persistent (not each time they log on) so they all work great offline and syc like they are supposed to.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
clark-jaAuthor Commented:
mapping as \\server\homedirectory as opposed to the non persistent P drive resolved the issue.  Thanks alot.  I wasted alot of time on such a simple problem.
clark-jaAuthor Commented:
mapping the mydocuments as \\server\share as opposed to using the non-persistent P mapping resolved this issue.  Thanks folks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.