Windows 2012 Terminal Servers temporary profile issues
We have 3 windows 2012 terminal servers. There are setup in a farm. We have an issue that appears to be random. users logon and they get the temporary windows profile. We logon to that server and delete the profile and the associated registry entries and the user logs back on fine. We are use roaming profiles and redirected folders. I have read this can happen when the roaming profile is not available or "in use". that appears not to be the case here.
To troubleshoot is there a log or some event that will tell us why the temporary profile was loaded and then perhaps once we have this we can work towards a resolution.
To troubleshoot is there a log or some event that will tell us why the temporary profile was loaded and then perhaps once we have this we can work towards a resolution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Perhaps an app is hanging the session's log off process?
ASKER
Yes that is possible bringing me back to how to find the reason for the temp profile in the event logs. So far we are not able to find any events associated with it. Example unable to open file or file locked.... etc,,.
A report from each session host indicating which profiles are active just prior to the hard log off event would be a place to start.
From there, what apps are running at the time.
From there, what apps are running at the time.
ASKER
Sorry you lost me on that one. Currently all we know is when a user calls with the issue. What we don't know or cannot find the cause of the issue. So how would we back track that users to see why the temp file was loaded?
Here is one PowerShell logged-on users script that can be scheduled to run on the session hosts.
This one uses the native Get-UserSession PowerShell.
This one uses the native Get-UserSession PowerShell.
ASKER
in the end using profile disks was our best choice.
ASKER
Thanks