'User profile' versus 'Remote Desktop Services Profile' for Remote-Desktop-only user roaming profiles
Hi Experts!
In our hosted solution users only log on via terminal services, that is setup with Roaming Profiles (users only log on via remote desktop services).
For as long as I've been in the company, Roaming profiles are setup in AD via the 'Profile' tab and I've never questioned that because it has never failed to work.
It's not that I haven't noticed the 'Remote Desktop Services Profile' tab but I just never dug into it.
Now that I am preparing Google Chrome in a roaming profiles scenarium I read this article saying that
Changing this would require a lot of preparation, so I hope to see strong arguments.
Thank you!
Anders
In our hosted solution users only log on via terminal services, that is setup with Roaming Profiles (users only log on via remote desktop services).
For as long as I've been in the company, Roaming profiles are setup in AD via the 'Profile' tab and I've never questioned that because it has never failed to work.
It's not that I haven't noticed the 'Remote Desktop Services Profile' tab but I just never dug into it.
Now that I am preparing Google Chrome in a roaming profiles scenarium I read this article saying that
You should assign a separate profile for Remote Desktop Services sessions because many of the common options that are stored in profiles, such as screen savers and animated menu affects, are not desirable when using Remote Desktop ServicesWould you recommend changing our user configuration and why/why not?
Changing this would require a lot of preparation, so I hope to see strong arguments.
Thank you!
Anders
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So just to be certain - you don't see the techinalities mentioned in the TechNet article "[..] such as screen savers and animated menu affects [..]" as a problem in any aspect (space required/functionality reduced/slight malfunctioning etc.)?No, because I disable these settings through Group Policy anyway. You can still have these settings enabled in a Remote Desktop Services environment, that TechNet article is just saying that it may not desirable when you have users logging into both regular Desktops as well as RD servers which is often the case.
There's also the fact that RD servers and desktop/laptops may have completely different versions of Windows installed along with different applications. Take Office versions for example, you may run into problems with settings not roaming correctly, etc.
ASKER
Thanks for your explanation - spot on!
ASKER
I also found that I would have to use ADSI insted of native PowerShell CMDlets to create users if I was to migrate settings to the Remote Desktop Services Profile tab, so I would definately rather stay with the current setting.
So just to be certain - you don't see the techinalities mentioned in the TechNet article "[..] such as screen savers and animated menu affects [..]" as a problem in any aspect (space required/functionality reduced/slight malfunctioning etc.)?