Score:0

Local administrator temporary profile after add server to RDS session host group

hm flag

Two weeks ago we have to install a new server (Windows S. 2012R2) as terminal server. There was ServerA ; ServerB; and now ServerC We tried to clone the ServerB to ServerC but because of issue with the Uid we decided to install a brand new system.

After the clean install of windows ready, we:

  • install some application
  • patches
  • put to domain
  • etc..etc..

After this step we put this ServerC to the session host server group. Configure everything as the ServerA and ServerB.

--> Login as domain user, and test...--> Everything fine --> Login as local administrator --> Local administrator get TEMP profile

Rollback an earlier snapshot and test again: --> Login as local administrator --> Local administrator fine!

--> Put server as session host..configure everything --> Login as domain user, and test...--> Everything fine --> Login as local administrator --> Local administrator get TEMP profile

Any idea what the hack is goin'? May i miss something? Why local administrator get Temp profile after add the server as a new RD session host?

Really appreciate any help.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.