Avatar of Pau Lo
Pau Lo
 asked on

file share move - impact

We are soon being requested to migrate our team data from one file share to another, albeit on the same windows 2012 file server. The drive mappings for users will stay the same (Y:\) as part of the login script, and our infrastructure team claim the migration if data will be 'effortless' with no impact on end users!

Currently, our area on the file server It is essentially a team directory full of office documents, e.g. docx, xlsx, and a few access databases. I need to try and assess everything that could break with such a move of all our data from one share to another. I know in some of the teams word documents are hyperlinks to other documents, which use UNC paths, so whereas a hyperlink e.g. \\server\currentshare\team\dir1\word.docx will break when we move the data to \\server\newshare\team\dir1\word.docx - hyperlinks was just one area I had thought of as a possible trouble spot. Can you think of any more that we need to factor into plans.
Windows 10Windows OSWindows Server 2012Windows Server 2008Windows 7

Avatar of undefined
Last Comment

8/22/2022 - Mon
William Fulks

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Anything using a UNC path can break. Linked Office documents are the biggest concern, but people can also have shortcuts to documents or directories on their desktop, in Favorites, most recently used, etc.

It seems weird that you would need to be moved to a new share. Normally an entire share would get moved at once, which can be done when moving to different storage, and that can be seamless as the UNC can stay the same. Otherwise, I map everything to DFS Namespace so that I can move folders/shares between servers all day long and keep the UNC path the same. Hopefully your infrastructure team is already using DFS Namespace. It's easy to tell. Just look for a DFS tab under Properties for a network directory. If they're not using DFS Namespace, ask them why not. They wouldn't neven need to modify login scripts. Hey why are they using login scripts and not drive mappings as part of group policy preferences? Are they stuck in 2005?

Showing DFS tab

Also consider. Bat files, PowerShell scripts
Your help has saved me hundreds of hours of internet surfing.