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.