Because GPOs are stored in the SYSVOL folder on domain controllers and each GPO typically occupies about 2MB of disk space, the more GPOs there were in the environment, the greater the size of the SYSVOL folder was. I also appended ",RequireIntegrity=0,RequirePrivacy=0" (as per this post ) to the keys value, but nothing helped.Prior to Windows Vista and Windows Server 2008, all of the default administrative template files (.adm files) were added to the ADM folder of each Group Policy Object (GPO) on a domain controller. I also created a "\\*\PROFILES" key similar to "\\*\SYSVOL" and "\\*\NETLOGON" above, but again with no result. It works, but only until I try to change the default domain policy (or apply a new domain policy) with the Group Policy Editor (I tried setting password expiration to 42 days): then the errors with the roaming profiles show up again. I successfully joined a Windows 10 Pro (version 1903) VM to the domain (INSIEME), I created a new domain user (alex) with romaing profile (\\\profiles\alex) and I followed your suggestion and created the above registry keys.
I just installed Zenytal 6.0 as a standalone Domain Controller (hostname master, domain insieme.lan) and I had the same problem with roaming profiles. I am certain anyone else using the win 10 creators version and zentyal 5 will be hitting the same issue! The windows 10 version is the latest creators edition. This issue affects all the zentyal 5 setups I have in exactly the same way including a test one. If I then add the user to the admin group the issue goes away. I can browse to and open the gpt.ini with no problems as a standard user. This issue may be transient and could be caused by one or more of the following:Ī) Name Resolution/Network Connectivity to the current domain controller.ī) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).Ĭ) The Distributed File System (DFS) client has been disabled. Group Policy settings may not be applied until this event is resolved.
Windows attempted to read the file \\test.local\sysvol\test.local\Policies\\gpt.ini from a domain controller and was not successful. However on windows 10 PC's unless the users are administrators (members of the admin and schema admin group) neither the roaming profiles or drive maps work and often it logs in with a temp profile.Ī check of the system events shows the following error On windows 7 PC's when regular users log in the roaming profiles and drive maps work perfectly. I use the default domain policy with roaming profiles (the roaming profiles was set in the zentyal admin webpage) and a couple of drive maps. I have three Zentyal 5.1 servers in the field as it were all functioning as DC's.
0 kommentar(er)
