Windows Server

GPO – Auto Disconnect Idle Remote Desktop Sessions

Working in a geographically distributed Windows Server environment I often found that most servers have a number of idle RDP connection. As Windows Server only allows for two concurrent Remote Desktop connections for administration you are sometimes faces with the choice of disconnecting other user blindly or in the case of Windows Server 2003 not to be able to connect at all. The same applies also to some Virtual Client machine hosting legacy application that a frequently used by different users, who would not have administrator right to force a disconnect.

The obvious way to address this issue is to use a Group Policy do disconnect any idle session after a given time period. The are few more settings that can be set in this regards like as to whether to keep application running or not when disconnecting (Microsoft Technet Article).

We want to set a time-out limit for an active RDP session when this has been reached for all computer in a giving OU. To do this open the Group Policy Management Editor and go to …

Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits

… and enable “Set time for active Remote Desktop Services sessions” and “End session when time limits are reached”. When done apply GPO and test.

Error determining whether the target server is already a domain controller: The target server is already a Domain Controller.

I was trying to add a new Windows 2012R2 Domain controller to an existing Domain. I was using the GUI tools, may be I should do this with PowerShell the next time. After adding the AD and DNS role I went through the DCPROMO wizard and kicked off the promotion. After a manual reboot I checked and all of DNS and AD seems to be working fine including replication. However, I’m still being prompted in the Server Manager to promote the server. When I do the following messages is displayed – “Error determining whether the target server is already a domain controller: The target server is already a Domain Controller.” After some research it looks like I’m not the only one, check out these posts. First thing always, run DCDIAG. The output only confirms that everything seems to be working. The solution seems to be to just disable/acknowledge the notification by clicking the “x” beside the task. Even after a reboot the notification doesn’t come up anymore.

[codesyntax lang=”text” lines=”fancy”]

Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   Home Server = SRV-ADC-01

   * Identified AD Forest. 
   Done gathering initial info.


Doing initial required tests

   
   Testing server: IEGW\SRV-ADC-01

      Starting test: Connectivity

         ......................... SRV-ADC-01 passed test Connectivity



Doing primary tests

   
   Testing server: IEGW\SRV-ADC-01

      Starting test: Advertising

         ......................... SRV-ADC-01 passed test Advertising

      Starting test: FrsEvent

         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems. 
         ......................... SRV-ADC-01 passed test FrsEvent

      Starting test: DFSREvent

         ......................... SRV-ADC-01 passed test DFSREvent

      Starting test: SysVolCheck

         ......................... SRV-ADC-01 passed test SysVolCheck

      Starting test: KccEvent

         ......................... SRV-ADC-01 passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... SRV-ADC-01 passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... SRV-ADC-01 passed test MachineAccount

      Starting test: NCSecDesc

         ......................... SRV-ADC-01 passed test NCSecDesc

      Starting test: NetLogons

         ......................... SRV-ADC-01 passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... SRV-ADC-01 passed test ObjectsReplicated

      Starting test: Replications

         ......................... SRV-ADC-01 passed test Replications

      Starting test: RidManager

         ......................... SRV-ADC-01 passed test RidManager

      Starting test: Services

         ......................... SRV-ADC-01 passed test Services

      Starting test: SystemLog

         ......................... SRV-ADC-01 passed test SystemLog

      Starting test: VerifyReferences

         ......................... SRV-ADC-01 passed test VerifyReferences

   
   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : Schema

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

   
   Running partition tests on : Configuration

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

   
   Running partition tests on : DOMAIN

      Starting test: CheckSDRefDom

         ......................... DOMAIN passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DOMAIN passed test CrossRefValidation

   
   Running enterprise tests on : DOMAIN.INC

      Starting test: LocatorCheck

         ......................... DOMAIN.INC passed test LocatorCheck

      Starting test: Intersite

         ......................... DOMAIN.INC passed test Intersite

[/codesyntax]