mark100 Posted December 13, 2023 Posted December 13, 2023 Hi This has got us scratching our heads..... when a new AD user is created and they logging for the first time, a user folder gets created on a file server via a gpo \\fileserver\studentdocuments$\intake 2023\%username%. But since around mid November this seems to have stopped working. The weird bit is, if we log them on with a computer that hasn't been turned on for a few weeks, that folder does get created and the drive mapped no problem. Looked at rolling back windows updates, if there have been any changes to GPO, but cant find anything that would be restricting the folder creation. Permissions haven't changed since September when 1000+ account were created without issue. Anyone seen anything similar?
altecsole Posted December 13, 2023 Posted December 13, 2023 Not an answer to your question, but a way to create the folders in advance, if required, using Powershell: $homeRoot = "\\server\share_path" $userFile = Get-Content -Path D:\ListOfNewUsers.txt foreach ($name in $userFile){ Write-Host $name new-item -Path "$homeRoot\$name" -ItemType Directory -Force $Acl = Get-Acl "$homeRoot\$name" $Ar = New-Object system.security.accesscontrol.filesystemaccessrule($name,"FullControl","ContainerInherit, ObjectInherit","None","Allow") $Acl.SetAccessRule($Ar) Set-Acl "$homeRoot\$name" $Acl } 1
mavhc Posted December 13, 2023 Posted December 13, 2023 They should be auto created when the user is created https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/automatic-creation-of-user-folders-for-home-roaming-profile-and/ba-p/395527 1
PotNoodleTech Posted December 14, 2023 Posted December 14, 2023 I've had a lot of weird file system permission errors lately since about mid November which coincidentally was the same time a MS patch went on. I initially blamed the LA for fiddling in the AD but now I am not so sure.
Davit2005 Posted December 14, 2023 Posted December 14, 2023 My experience with the folder creations certainly for the Home Drive was that as long as you stuck to the standard and did not use hidden folders it was no problem doing in the users AD object i.e. \\[share_Server]\[shared_Folder]\%username% . and could even update multiple AD objects at the same time if needing to move to a new server.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now