Home
  •  

The Terminal Services User Home Directory was not set because the path specified does not exist or not accessible

Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.EventCollection.1060 (Rule)

Knowledge Base article:

Resolutions

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

The Terminal Services home folder name for a user is incorrect

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

Note: If the terminal server is not a member of an Active Directory domain, use Local Users and Groups (lusrmgr.msc) to change the Terminal 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 terminal 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 Terminal Services home folder configuration for a user account:

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

If the Terminal 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 terminal 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 terminal server and the home folder server:

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

The user does not have sufficient permissions to the home folder

If the Terminal 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:

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

Specify the correct Terminal Services home folder location by using Active Directory Users and Computers

Note:  If the terminal server is not a member of an Active Directory domain, use Local Users and Groups (lusrmgr.msc) to change the Terminal Services profile path on a user account. To use Local Users and Groups, you must have membership in the local Administrators group on the terminal 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 specify the correct Terminal Services home folder location:

Note:  You can also specify the Terminal Services home folder location by using Group Policy.

Identify and fix network connectivity issues

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.

If you can successfully ping the home folder server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.

If you cannot successfully ping the home folder server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:

Assign sufficient permissions to the home folder

To resolve this issue, assign the appropriate 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 assign permissions to the home folder:

Note:  The share permissions might also need to be changed. To change the share permissons for the folder, in the user account Properties dialog box, on the Sharing tab, click Advanced Sharing. For more information about share and file permissions, in the Advanced Security Settings dialog box, click Managing permission entries.

Element properties:

TargetMicrosoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer
CategoryEventCollection
EnabledFalse
Event_ID1060
Event SourceMicrosoft-Windows-TerminalServices-RemoteConnectionManager
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
The Terminal Services User Home Directory was not set because the path specified does not exist or not accessible
{0}
Event LogSystem

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
Alert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.EventCollection.1060" Enabled="false" Target="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>System</LogName>

      <Expression>

        <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>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertName/>

      <AlertDescription/>

      <AlertOwner/>

      <AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.EventCollection.1060.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/LoggingComputer$</SuppressionValue>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

  </WriteActions>

</Rule>