Guest Triage Posted January 30, 2008 Posted January 30, 2008 I have a share on a server that has reached EOL. I have been robocopying the share files to an alternate machine. What is the best way (most transparent to users) to allow the share name to remain the same but redirect the users to the new storage space? -- "I enjoyed my youth so much that I decided to bring it along with me." -G.C.
Guest Pegasus \(MVP\) Posted January 30, 2008 Posted January 30, 2008 Re: File Redirection? "Triage" <Triage@discussions.microsoft.com> wrote in message news:E6BC5EB9-50DB-4405-8EC1-C98709B80C79@microsoft.com... >I have a share on a server that has reached EOL. I have been robocopying >the > share files to an alternate machine. What is the best way (most > transparent > to users) to allow the share name to remain the same but redirect the > users > to the new storage space? > -- > "I enjoyed my youth so much that I decided to bring it along with me." > -G.C. This is often done by modifying the logon script.
Guest Lanwench [MVP - Exchange] Posted January 30, 2008 Posted January 30, 2008 Re: File Redirection? Triage <Triage@discussions.microsoft.com> wrote: > I have a share on a server that has reached EOL. I have been > robocopying the share files to an alternate machine. What is the best > way (most transparent to users) to allow the share name to remain the > same but redirect the users to the new storage space? Ideally, you're using a login script and users access the drive letter, not the UNC path (I always prefer that). If so, change your login script so that the drive letter now points at the new server name and share. If not, the share name isn't the sole issue - you've also got a different server name.I would start using the login script & drive letter method now when you make this change, so you never ever have to deal with the problem again.
Recommended Posts