RDS 2012: Profile Disks and Temp Profiles


The huge pain with using Profile Disks in Windows Server 2012 RDS is to dealing with TEMP profiles. When the user’s profile corrupts and started creating TEMP user profiles, Admins has to deal with fixing the issue and it’s NOT easy. But if you want to know how to fix it, here it is.

1. Delete User’s profile disk (.VHDX). To find the user’s correct profile disk, you have to check the NTFS security tab in properties of the xxxxx.vhdx file.

image

2. Check all Remote Desktop Session Host servers C:\Users folder to check which server has the corrupt user profile. (hint: check \\sessionhost\c$\users from your computer)

3. Once you find the server, Remote desktop to that server. You will see the following event log message on that server in System Logs.

Remote Desktop Services could not apply a user desktop for a user account with a SID of <GUID>. A temporary profile was enforced for the user. Verify that the user profile disk settings are correct. The error code is 0x800700AA.0

4. Open REGEDIT and expand to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

5. Click each sub key section and watch ProfileImagePath value. This value will say username in the path.

6. Once you find the correct key, Delete it.

7. Have user logon again to the RemoteApp or VDI. RDS will create new profile disk.

Hope that fixed your issue. If so, please leave me a thanks note.

Advertisements

10 thoughts on “RDS 2012: Profile Disks and Temp Profiles

  1. This is indeed an option. What I also found why users have currently a temporary profile, is that the profile disk has been locked by de RDS session host. Just don’t know for what reason.

    1. That’s just what I’m facing right now. UPD’s are locked and users receive temp profiles.
      I found a way to eject them from Disk Management, but this whole UPD hell is totally unacceptable.

    1. You have to identify the disk that is stuck in diskpart. With “list disk” you see all the disks. With “select disk n” and “detail disk” you have to find which one is the stuck disk. Then you can right click that certain disk in disk management console and select “eject”. That’s it.

  2. Hello,

    though late, I was in a similar situation. Problem is not a bug, but that the design of RDS in 2012 is another one.

    What’s wrong: DNS round robin by farm name on each host.
    What’s right: use Web feed or RDGateway.

    What the fu **? … Yes I know. There is a solution which makes it possible to use a self generated RDP file to connect cleanly. It is called “Connection Broker Redirection”.
    Dissolve the DNS RR and created a DNS record with the farm name, which points to the broker.
    On the broker you create a registry entry:
    Path: HKLM \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ Cluster Settings
    Type: REG_SZ
    Content:
    ⇒ For desktop collection: TSV: // MS Terminal Services Plugin.1.Name
    ⇒ For VDI: TSV: //VMResource.1.Name

    Result is that the broker is always the redirection server and not one of the RDS hosts (old 2008R2 style), which can lead to these temp profiles.

    Slightly more detail here: http://it-gotsch.com/rds2012-upd/ (but in German)

    MfG

  3. Some tips before any clean up

    Close any session open before rebooting any terminal server.
    Easy command:
    query session
    logoff *ID*

    Make sure there any VHDX file open before login back in. Login to you VHDX location serveur under comptuter management then under Shared folders look into files open.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s