Archive for December, 2010

DFSR failure with Windows Server 2003 R2 and 2008 R2

Tuesday, December 28th, 2010

There is a compatibility issue in the DFSR protocol between Windows Server 2003 R2 and 2008 R2 which causes replication from Windows Server 2008 R2 to 2003 R2 to fail.

Microsoft released a hotfix here under MSKB 2462352

Configuring Remote Desktop licensing settings on Virtualization Host

Thursday, December 16th, 2010

Until Windows Server 2008 R2, in a Virtual Desktop Infrastructure (VDI) deployment, the RD Virtualization Host server was not aware of licensing settings because only the RD Session Host server participated in licensing and performed license validations for the client session/connection requests. But the new licensing model for the Microsoft VDI solution (in Windows Server 2008 R2 SP1) requires that the Remote Desktop licensing mode and the list of Remote Desktop license servers be specified on all RD Session Host servers (configured in virtual machine redirection mode) as well as on all RD Virtualization Host servers (with RemoteFX enabled), because the RD Virtualization Host servers can also participate in VDI licensing.

Here are two important posts from Anki Arora regarding this special centralized licensing feature for VDI coming with Windows Server 2008 R2 Service Pack 1

Centralized Licensing Management for Microsoft VDI

Configuring Remote Desktop licensing settings on a Remote Desktop Virtualization Host server

 

Technical Site Issues and Slowness on LinkedIn

Tuesday, December 14th, 2010

Since a few days the service suffers from technical site issues and slowness.

There is currently an announcement published by LinkedIn:

[…]

We’re sorry, but we’ve identified some site issues that may limit the functionality of certain features or prevent you from accessing your account. We want to get this resolved as quickly as possible, so we have a whole team of experts working to address the problem right now.
At this time, there’s no need to contact LinkedIn Customer Service. Thank you for your patience and please try us again later.

[…]