FWIW I recorded a video about using FSLogix Profile Containers (which are simply UPD on steroids) to shunt profiles into an Azure Storage Account.
https://www.youtube.com/watch?v=7s_o1O8dBQQ&t=2s <end flagrant self-promo> From: [email protected] [mailto:[email protected]] On Behalf Of Melvin Backus Sent: 03 July 2017 16:38 To: [email protected] Subject: [NTSysADM] RE: Folder redirection issues The problem with DFS and profiles is when they switch replicas. It has the possibility to leave files out of sync and can cause all manner of weirdness because of it. As long as they can't access any other replicas (read-only, etc.) it works OK. I don't know that it's unsupported, but it does have a big warning on it. Never played with UPD, may have to take a look. -- There are 10 kinds of people in the world... those who understand binary and those who don't. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of James Rankin Sent: Monday, July 3, 2017 10:22 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Folder redirection issues Didn't I read somewhere DFS for profiles is not supported? Why not use User Profile Disks instead? You can use UPD on Windows 10 with a bit of tinkering as well. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Melvin Backus Sent: 03 July 2017 15:12 To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: Folder redirection issues DFS for profiles? It's possible but NEVER, repeat NEVER, allow multiple replicas to be active if you do. We recently migrated all our user profiles to a new server. The new server is accessed via the DFS name but there is only one replica. You might confirm results with DNS domainname versus NETBIOS domainname to see if that helps. -- There are 10 kinds of people in the world... those who understand binary and those who don't. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dan Bartley Sent: Friday, June 30, 2017 3:20 PM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [NTSysADM] Folder redirection issues I have a couple of issues with folder redirection and GPO. I have been using it for years. I am currently migrating everyone to a new file server. I use DFS for the drive mappings, so that part is easy. We are still on a 2003 Functional level domain (yes, I know but the CTO does not see the value in IT related matters until it hits him personally). Folder redirection has always been set to the literal \\server\share<file://server/share> name with Basic setting. If I simply update the server name in GPO almost no one actually changes in their Document settings, even with a gpupdate. Some Win 10 machines do, but none of the Win 7 machines update for the Documents location. They are receiving the GPO as it shows in RSOP and won't allow manually changing the location. I have to turn it off altogether, go change them manually-after the tedious step of making the new share available offline for Win 7, then set the GPO to the same thing. This is only for existing users, any new users pick up the new location fine. Am I Missing something here? I can't get it to reliably update. A thought I had for future proofing this was start changing people to the DFS link, then going forward I don't have to change anything for Folder redirection, just the DFS. HOWEVER, I set my PC to the DFS path for the new User\Documents share, did a gpupdate and upon logging back in it completely deleted everything I had in the Documents network share. Yes, I had a backup right before testing so I was able to restore it all, but I don't know why it did that and can't afford to have a bunch of users suddenly get everything deleted. I can restore, but they will fill my office with panic attacks until it is done. Any thoughts on this part? Thanks in advance for any expertise on these. Best Regards, Dan Bartley CONFIDENTIALITY NOTICE***The information contained in this message may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or any employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.
