windows server 2012 remote desktop timeout setting

In this demo, we’ll configure user profile disks for the collection later so that we don’t have to manually set NTFS file and share permissions. The virtual disk is only accessible in the given collection, so if a user is a member of a different collection, they will have different settings and app data. Each collection can be directed to a file share that stores a virtual disk for each user, and contains application data and settings. Microsoft has gone some way to solve the problem by creating user profile disks in RDS, starting in Windows Server 2012. Roaming profiles are not always an effective solution and in RDS environments can prove even more problematic. When you’re done selecting groups, click Next.

By default, all domain users get access, but you can change this using the Add and Remove buttons. And obviously this also works on an ordinary PC if you keep receiving the login screen whenever you.

Now you can remain idle on the remote desktop connection as long as you want and you won’t be locked out. Uncheck On Resume, display logon screen and click OK.

On the Specify user groups screen, add the domain users that can access this collection. Right click Desktop and select Personalize.

For more information on working with Server Manager, see Managing Windows Server 2012 with Server Manager on the Petri IT Knowledgebase. To add RD Session Hosts to the collection, they must be members of the Server Pool. Note that the server I’m logged into is a member of Server Manager’s Server Pool, and it happens to be the only RD Session Host server in my RDS deployment. A RD Session Host servers to a collection (Image Credit: Russell Smith)

Windows server 2012 remote desktop timeout setting