Here's the situation:
We have a large (5,000+ user) organization that is currently using folder redirection to manage the windows desktop icons. This folder is redirected to a network share where we can centrally manage the different sites and such. When a user tries to use a computer when the network is not available, they are unable to use any shortcuts in the Public folder. We only redirect the C:\Users\%username%\Desktop folder.
Does anyone have any suggestions of how to go about managing desktop icons? We still want a central location to manage these items, but find a way to keep the system working when the network is unavailable.
As a point of clarification, the network rarely goes down. We do have instances where a few computers do not have a network connection. Usually, something is simply unplugged. Since we have multiple sites, the line from a branch to the central office has gone down a few times. This is more of an attempt to maintain a positive end user experience when disconnected from the network.
I think I see this problem differently to @Daniel. I don't approve of sneaky batch scripts to do that kind of thing.
Fix your goddamn network. If you've got 5000 users, and the network is unavailable, that's 5000 people unable to work. Potentially, very costly. It shouldn't be too difficult to use that as justification for some time, hardware (if required), and manpower to fix the network and make it more resillient to failures.
I'd say that should be prioritised higher than scripting a solution to hack around the real problem.
One of the other techs in our organizations came across something called Group Policy Preferences. It is new to Server 2008 and it seems really powerful. Here's a link for more information:
http://support.microsoft.com/kb/943729
Inside this new feature is a "Shortcuts Preference extension". This allows you to mange shortcuts on the client machines using group policy. Since you are copying a file object to the local machine, you don't depend on an available network connection. The system is technically caching files locally, but it does so without the need for folder redirection and offline files.
I realize that I shouldn't answer my own questions, but this seems to be the best solution available. I'll try it out and update this answer if it doesn't work out.
I think the best solution is write a batch script that run as task on all clients and sync the networkshare to a local folder. Than change the Path in the folder redirection to the local folder. Nice tool to sync is robocopy.