This can also be used if you can’t/don’t want to specify the user profile location for each user seperatly. If you would like to have a special user profile for the RD Session Host(s), you can define a location. Just like the home directory, there are several ways to configure the location of the user profile. Profiles – Set Path for Remote Desktop Services Roaming User Profile Currently I advise not to use a mandatory profile anymore, but a local profile combined with a profile management solution, for more information see my article The alternatives for mandatory profiles. When you enable this setting you need to define the location of the mandatory profile at “Set Path for Remote Desktop Services Roaming User Profile”. To simply arrange the configuration of a Mandatory Profile MS added this policy setting. Profiles – Use Mandatory Profiles on the RD Session Host Serverįor a long time mandatory profiles were the profiles advised to use on an RD Session Host. If you would like to have another location for the RD Session Host or don’t want to specify the User Home directory on a per user basis, you can use this setting to define the home directory that will be mapped into the RD session. One is to specify those on the user object within AD. If you would like to specify a home directory for the user there are several methods. Profiles – Set Remote Desktop Services User Home Directory These are not that much more on the RD Session Host actually. The policy mentions that this only applies to roaming profiles. You define a monitor interval and the maximum size allowed. With this setting you can specify how large all the user profiles together are allowed to grow on the local RD Session Host. Profiles – Limit the size of the entire roaming profile cache
I already discussed these settings in detail in the article How to configure Microsoft RDS Universal Printing, earlier published on .įigure 2: Remote Desktop Session Host – Profiles With this setting you can define which type (per user or per device) the RD Session Host will support. Each RD Session Host can issue one of the two types. Which you use depends on the situation (do you have more users than devices or more devices than users).
Microsoft has two types of RDS licenses, per user or per device. Licensing – Set the Remote Desktop licensing mode
If you don’t want such users to be notified about license issues you can enable this policy (but I don’t recommend that). Licensing – Hide notifications about RD Licensing problems that affect the RD Session Host serverĪn RD Session Host will mention license issues when a user defined in the local administrator logs on to the RD Session Host. If you would like to overrule this process you can define the RDS License Server names in this policy setting. If this policy is not configured, an auto discover process will start which will look for RD License Servers published in AD, followed by looking for RD License Servers installed on a Domain Controller. Licensing – Use the specified Remote Desktop license servers Machine Configurationįigure 1: Remote Desktop Session Host – Licensing In part two we started describing the settings available on the computer configuration level for the RD Session Host. We continued describing the policy locations both available within the machine- and user configuration.
In Part 1 of the article series MS RDS Policies explained, we started with describing how RDS settings can be configured and that the policies always win. Microsoft RDS Policies explained (Part 4).Microsoft RDS Policies explained (Part 2).Microsoft RDS Policies explained (Part 1).Over.If you would like to read the other parts in this article series please go to Summer has faded more and the march towards fall is nearly