Windows Server: Remote Desktop Error: The task you are trying to do can’t be completed because Remote Desktop Services is currently busy

Hi everyone

Today I will talk about a tip to kill / reset any RDP session when it’s locked out and that give the error “The task you are trying to do can’t be completed because Remote Desktop Services is currently busy”


You will see some printscreen with the ica-rdp’s description, but I’am using the Windows Server built-in tool to reset the session, and the RDP’s session manager was in error too for that session. (ica is built over rdp)

From that MMC you see an active session, but no application run.

When that happen you will have those symptoms:

  • In taskmgr you will see no application under the useraccount in error
  • In the RDP’s MMC you will not see the user logged, even if you see everyone else logged.
  • The user profile is lock. (IE, you can’t delete it)
  • The winlogon process seem to never finish for that session


From the MMC you can’t kill the session or reset it as it does not offer the choice to do it.

The first thing to do is a query session in command shell to validate. There we can see the real status, it’s still in Connecting.


After you can issue a reset session <session-name>.


Now relax and enjoy, you just saved yourselft a server restart for a hung connection 🙂

In my case the culprit was a bad GPO for that user.


Dell | Wyse Terminal badly support VLAN tagging and DHCP’s problem

Hi, today I will talk about a issue I found today.

The Wyse Xenith & CL0 serie brougth a lot of headache for the DHCP’s request, as it seem to spam before the network port open. The STP kill the DHCP’s attemp. So, the fix is quite easy, port-fast for each port.

Today I felt on a bigger problem. After some upgrade in my park, I found myselft with the re-surfacing DHCP’s problem. I was there, why ???

I wireshark’ed the network traffic, and after some test I found that tagged VLAN’s traffic is just not an option with those Wyse.

I was in the default VLAN’s ID (1), and the port set as access or trunk or any other type just didn’t work. I even see other DHCP offer, wich was really strange… (DHCP offer from the VLAN 50)

Thus, now I tested it with a old dummy switch, and no more problem ….


The moral of the story :


User HAPPY on DELL Client = port-fast + no VLAN

Windows 7 VDI and ESX 5.1 – BSOD or PVS slowliness !!

Hi everyone !


Did you have a Citrix Provisionning Server to stream some Windows 7 machine ? and they are hosted on Windows & ??


To be ok, you need a private KB, and to do that;


– Make your golden image.

– Be sure it’s a VMXNET3 NIC. Not  a E1000.

– Install the KB :

“0x0000007B” Stop error after you replace an identical iSCSI network adapter in Windows Server 2008 R2 SP1 or in Windows 7 SP1

 Ghost NIC seen on Windows 7/Windows 2008 R2 machines built from VMWare Templates when the Template uses a Synthetic NIC (VMXNET3)

– Follow those step (Starting a Target Device Displays a Blue Screen on vSphere), thus making etherne## the same in the virtual machine and the template.

– From there, you need a last change, on your ESX’s host you need to set that at false.

esxcli system settings kernel set -s netNetqueueEnabled -v FALSE



From there your VDI should boot ok, and be speedy !




Directory Service: NETLOGON missing after a restore


SYSVOL empty but share existant. NETLOGON share non-existant GPO’s console list all old GPO, but can’t display any detail on all GPO.


First DC (DC#1) in Windows 2003
Second DC (DC#2) in Windows 2008R2
Each are Global Catalogue.
DC#1 is old, no longer in the backup schedule. DC#2 got all FSMO’s role and is the primary DC.
The datastore die. We restore the the system-state from DC#2, and we find ourselft faced with the FAQ that the SYSVOL is empty.
From the tape we found that the SYSVOL was not replicating, so it seem an issue that the SYSVOL does not replicating when you have a 2003 and you DCPROMO an 2008’s DC.

How to

First step done is that;

To complete an authoritative restore, stop the FRS service, configure the BurFlags registry key, and then restart the FRS service. To do so:
 1.Click Start, and then click Run.
2.In the Open box, type cmd and then press ENTER.
3.In the Command box, type net stop ntfrs.
4.Click Start, and then click Run.
5.In the Open box, type regedit and then press ENTER.
6.Locate the following subkey in the registry:
Backup/RestoreProcess at Startup
7.In the right pane, double click BurFlags.
8.In the Edit DWORD Value dialog box, type D4 and then click OK.
9.Quit Registry Editor, and then switch to the Command box.
10.In the Command box, type net start ntfrs.
11.Quit the Command box.
When the FRS service is restarted, the following actions occur:
•The value for the BurFlags registry key is set back to 0.
•An event 13566 is logged to signal that an authoritative restore is started.
•Files in the reinitialized FRS replicated directories remain unchanged and become authoritative on direct replication. Additionally, the files become indirect replication partners through transitive replication.
•The FRS database is rebuilt based on current file inventory.
•When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.


After that test, the folder was still empty.
So the final test was simple.
I created the scripts folder in the c:windowsSYSVOLSYSVOLdomain.nameSCRIPTS and shared it to NETLOGON and runned : DCGPOFIX
That reset/recreate the default domain policy, and after you just need to erase all old GPO that are still empty in your console.


Thanks everyone !


nb; Article published in the TNWiki there too :