Here I am complaining that I am NOT seeing errors. This might seems strange, but the expected behaviour, as I understand it, is that I should see errors under this configuration.
We have had roaming profiles set up for a very long time. We PRE-CREATE the folders when the users account is created. Crucially, the owners of the folders are currently NOT set as the user. They are also not set as the "administrator" of the sever where the profiles are stored.
Apparently, there should be an error seen on login according to this article (Note the article relates to 2003, but we never saw the error on 2003 AD either. I assume it still applies to 2008, but I am not sure): Windows Server 2003 checks for pre-created roaming profile folders when you make a roaming user profile
We have the following environment:
- Windows 2008 AD.
- Windows 7 Desktops
- Roaming Profile Path attribute set for all users.
- NTFS permissions are set as described under best practices.
- We DO NOT have the GPo set as described in the above article (Do not check for user Ownership of Roaming Profile Folders). This should mean that we get an error on user login but we do not.
- RSOP and GPEDIT show that there are no GPo settings as described.
Could anyone explain why this is working when it should not?!
When we try this in our virtual environment... I get the expected errors using the same AD, profiles and users. To circumvent the error in the virtual environment, we set the GPo as defined above, and it all works. This seems to suggest that it does still apply to the 2008 AD environment.... so why I am not seeing the issue on all our physical machines?