We're in the midst of transitioning our hybrid-joined devices to be fully managed by Intune, with the long-term goal of phasing out our on-premises Active Directory. Currently, we have a DFS server providing shared drives, and I'd like to know the best practices for migrating this setup to a cloud environment that integrates with Intune. I'm particularly looking for ways to maintain a drive mapping in File Explorer with minimal downtime during this process. Although we've considered using SharePoint for this migration, the reliability of drive mapping has been inconsistent, sometimes taking days even with forced checks. I haven't found a comprehensive guide on this, just basic suggestions to explore SharePoint or Azure Files. Any insights on best practices or common pitfalls would be greatly appreciated!
3 Answers
Azure Files provides a more direct 1:1 experience compared to SharePoint, which can require significant changes in how your organization operates. I recommend looking into the drive mapping tools for Intune, like the Intune Drive Mapping Generator. This can simplify the process of scripting your mappings. Some companies even opt for a simple batch file with 'net use' commands to manage their drive maps effectively. If you're migrating a lot of data, both azcopy and the SharePoint Migration Tool work well, but for large amounts, third-party tools like ShareGate are worth considering.
Good point about tying it back to user training. I can see where streamlining access through OneDrive shortcuts might improve user experience!
Drive mapping to SharePoint has its challenges, so I recommend steering clear of it unless you're using third-party solutions like ZeeDrive. Also, if you’re pushing towards SharePoint or Teams, consider utilizing OneDrive shortcuts over traditional drive mappings to ease the transition. The SharePoint Migration Tool can help you seamlessly transition your data. Just be mindful of the larger data volumes—at that point, third-party tools could be advantageous.
Totally agree! Having a reliable shortcut system could alleviate many problems. Plus, I think user education on new access methods is critical to avoid helpdesk loads post-migration.
I’d love to hear more about Azure Files from your experience. How would you say it holds up in real-world usage?
One effective method we've found is using azcopy to transfer data into Azure Files. It can really speed up the migration process. Just keep in mind that if you're considering SharePoint, moving completely away from mapped drives might be the better approach. It tends to create synchronization issues. Instead, utilize the file migration tools available in the SharePoint admin center to handle the transfer efficiently and set up permissions correctly. Also, consider training users on accessing files directly through office apps instead of relying on mappings.
That’s good advice! Just be careful with those older workflows that depend on specific file paths. Transitioning them might require some convincing for teams, especially those that aren't as tech-savvy.
I've experienced that frustration too! Many users cling to that familiar Explorer layout and struggle with adapting to new methods. Education is key!
Using batch files sounds like a simple but effective way to manage things! I appreciate the suggestion about not relying on SharePoint mappings directly.