The Logon Type field indicates the kind of logon that was requested.
This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Subject fields indicate the account on the local system which requested the logon. This event is generated when a logon request fails. Source: Microsoft-Windows-Security-Auditingįailure Reason: An Error occured during Logon.
NOTE: The Server Manager\Remote Desktop Services\Servers screen in Windows Server 2012 shows Event Log information but it appears that it doesn't show everything relevant, because this error didn’t appear there so we chased our tails for a long time before actually finding this error in the Security Event Log. Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.Īfter a lot of time trying to work out why this single user could not connect we found an error in the Security Event Log looking similar to that shown below. Remote Desktop can't connect to the remote computer for one of these reasons:ġ) Remote access to the server if not enabledģ) The remote computer is not available on the network The error message the user was receiving was as follows (however as seems to be the case with RD Gateway sometimes a different connection failure would be randomly returned): The user was able to access the RDWeb page for the server, but launching any applications failed, as did launching them from RemoteApp RDP files. This will reduce the likelihood that UPDs will remain connected if the server is restarted or loses power.Īdditionally, ensure all user sessions are logged off and do not allow new connections to hosts before performing maintenance and/or restarts.Having just built a nice new shiny Window Server 2012 VM with Remote Desktop Gateway Services installed we encountered a problem where one user was not able to start RemoteApp applications from their home PC even though they were able to launch them from the 2008 R2 server we were using previously. Set GPO policy to log off disconnected sessions after X minutes.
How to prevent temporary profiles issues (i.e., mitigation): Finally, manually delete any temporary profiles located in c:\users\, for example:.Use this string value to easily identify individual users, for example: N.B., each objectSID profile has an expandable string value called ProfileImagePath. Identify and delete any objectSIDs that have a. Profiles are listed using objectSIDs, for example: HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\ProfileList Delete any temporary use profiles from the ProfileList in Regedit.Go to Control Panel → System → Advanced System Properties → Advanced → User Profiles → Settings.ĭelete any profiles with Typeset as TEMP. Attempt to delete the temporary profile from Advanced System Properties:.Do not allow users to log on while troubleshooting. Users will receive temporary profiles if their UPD was attached to the RDS server when it was restarted. Although the user is not connected their sessions continue to run in the server background -therefore their UPD remains attached to the RDS server. The problem usually occurs when the user session state is disconnected. Changes you make to this profile will be lost when you log off."īackground: RDS server is configured with User Profile Disks (UPD). Possible errors may read, "Windows cannot find the local profile and is logging you on with a temporary profile. The problem is not uniform and may only occur for individual users.
Problem: Users receive temporary profiles each time they log onto the Remote Desktop Server.