Remote Desktop Session Host User Configuration

Microsoft.Windows.Server.RemoteDesktopServices.2012.NewUnitMonitor_25 (UnitMonitor)

This object monitors the configuration of the Remote Desktop users.

Knowledge Base article:

Summary

The properties of a user account can be configured to provide a Remote Desktop Services-specific profile and home folder. This profile and home folder will only be used when a user establishes a remote session with an RD Session Host server. A separate profile for RD Session Host sessions should be assigned to a user 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 Services.

Resolutions

To resolve this issue, check the event ID, and then view the troubleshooting information for that event in the sections below.

Resolution steps for the following event ID: 1046

To resolve this issue, specify a new location for the Remote Desktop Services profile path, ensuring that the path does not exceed 256 characters.

Note: When calculating the length of a user’s Remote Desktop Services profile path, Username.Domain is appended to the profile path.

Specify the Remote Desktop Services profile path by using Active Directory Users and Computers

Note: If the RD Session Host server is not a member of an Active Directory domain, use Local Users and Groups (lusrmgr.msc) to change the Remote Desktop Services profile path on a user account. To use Local Users and Groups, you must have membership in the local Administrators group on the RD Session Host server, or you must have been delegated the appropriate authority.

To perform this procedure, you must have membership in the Account Operators group in the domain, or you must have been delegated the appropriate authority.

To change the Remote Desktop Services profile path for a user account:

1. Open Active Directory Users and Computers. To open Active Directory Users and Computers, log on to a computer where Active Directory Users and Computers has been installed, click Start, click Run, type dsa.msc, and then click OK.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

3. Locate the user account whose profile settings you want to change, right-click the user account, and then click Properties.

4. Click the Remote Desktop Services Profile tab.

5. In the Profile Path box, enter the new location.

6. Click Apply, and then click OK.

Note: You can also specify the Remote Desktop Services profile path by using Group Policy.

Resolution steps for the following event ID: 1060

This error might be caused by one of the following conditions:

The Remote Desktop Services home folder name for a user is incorrect

To determine the Remote Desktop Services home folder name for a user in an Active Directory domain, use Active Directory Users and Computers.

Note: If the RD Session Host server is not a member of an Active Directory domain, use Local Users and Groups (lusrmgr.msc) to change the Remote Desktop Services profile path on a user account. If you use Local Users and Groups, you must have membership in the local Administrators group on the RD Session Host server, or you must have been delegated the appropriate authority.

To perform this procedure, you must have membership in the Account Operators group in the domain, or you must have been delegated the appropriate authority.

To check the Remote Desktop Services home folder configuration for a user account:

1. Open Active Directory Users and Computers. To open Active Directory Users and Computers, log on to a computer where Active Directory Users and Computers has been installed, click Start, click Run, type dsa.msc, and then click OK.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

3. Locate the user account whose profile settings you want to change, right-click the user account, and then click Properties.

4. Click the Remote Desktop Services Profile tab.

5. In Remote Desktop Services Home Folder, if the folder location that is specified is not correct, see the section titled "Specify the correct Remote Desktop Services home folder location."

The computer on which the home folder is located is not accessible

If the Remote Desktop Services home folder is correctly specified, check that the computer on which the home folder is located is accessible from the network.

To determine if there is a network connectivity problem between the RD Session Host server and the home folder server, use the ping command.

Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To determine if there is a network connectivity problem between the RD Session Host server and the home folder server:

1. On the RD Session Host server, click Start, click Run, type cmd, and then click OK.

2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the home folder server (for example, server1.contoso.com), and then press ENTER.

If the ping was successful, you will receive a reply similar to the following:

Reply from IP_address: bytes=32 time=3ms TTL=59

Reply from IP_address: bytes=32 time=20ms TTL=59

Reply from IP_address: bytes=32 time=3ms TTL=59

Reply from IP_address: bytes=32 time=6ms TTL=59

3. At the command prompt, type ping IP_address, where IP_address is the IP address of the home folder server, and then press ENTER.

If you cannot successfully ping the home folder server by IP address or by FQDN, see the section titled "Identify and fix network connectivity issues."

The user does not have sufficient permissions to the home folder

If the Remote Desktop Services home folder is correctly specified, and the computer on which the home folder is located is accessible, check that the user has sufficient permissions to the home folder.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To check the permissions on the home folder:

1. On the computer on which the home folder is located, use Windows Explorer to find the folder location.

2. Right-click the folder, and then click Properties.

3. On the Security tab, click Advanced.

4. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

5. If the Permission column for the user account does not display Full control and the Apply To column does not display This folder, subfolders and files, see the section titled "Assign sufficient permissions to the home folder."

Note: Incorrect share permissions might also be causing this problem. In the user account Properties dialog box, on the Sharing tab, click Advanced Sharing to view the share permissions for the folder. For more information about share and file permissions, in the Advanced Security Settings dialog box, click Managing permission entries.

Element properties:

TargetMicrosoft.Windows.Server.2012.RemoteDesktopServicesRole.Service.RDSessionHost
Parent MonitorSystem.Health.ConfigurationState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityHigh
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLogManualReset3StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Remote Desktop Session Host User Configuration Alert
Event ID: {0} -- Description: {1}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.RemoteDesktopServices.2012.NewUnitMonitor_25" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.Server.2012.RemoteDesktopServicesRole.Service.RDSessionHost" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.RemoteDesktopServices.2012.NewUnitMonitor_25_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDisplayNumber$</AlertParameter1>
<AlertParameter2>$Data/Context/EventDescription$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId57d43e7fb99146d6bd225caa013980d5" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIda1f2fabd2d4f4c78a5ef2d6c63621960" MonitorTypeStateID="SecondEventRaised" HealthState="Warning"/>
<OperationalState ID="UIGeneratedOpStateId9280ab51ca594a64ae5e69f8cd5a6148" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FirstComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>System</FirstLogName>
<FirstExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">1046</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-TerminalServices-RemoteConnectionManager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</FirstExpression>
<SecondComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>System</SecondLogName>
<SecondExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">1060</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-TerminalServices-RemoteConnectionManager</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</SecondExpression>
</Configuration>
</UnitMonitor>