0

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.

holian
  • 227
  • 1
  • 8
  • 14

0 Answers0