imporve backwards compatibility to 2016
it is quite annoying that going through a folder redirection step-by-step instruction found on Microsoft websites it turns out that Windows 2019 does not apply this policy correctly, it keeps me signing in with a temporary profile. Using a Windows 2016 server the policy is applied. Wasted two working days becuase I thought I made it wrong. My AD is nearly untouched AD in 2016 level, the folder redirection is the only GPO object that exists apart from the default domain policy and that has only three settings to stop the screensaver from appearing and weakening the password rules. When going through the gpresult I saw that the policy was not applied on Server 2019 without any result and without event protocol entry being provided as it should be. Windows 2016 reported to me "processed but cannot be applied" in gpresult pls look into event log - and in event protocol of Windows 2016 the information about the missing folder structure. That this structure wasn't created automatically is a bug by itself in 2016 but with reasonalbe error reporting I was abel to fix the root casue. Other redirected folders do create automatically, so why the appdata / roaming folder doesn't?