Good Morning AskPerf Nation! Our Launch Series is at Day Seventeen. There are only five more days to go! Today we’re continuing on with Remote Desktop Services, with a look at Remote Desktop Services Virtualization (or RDS-V, for short). You may also hear RDS-V referred to as Virtual Desktop Infrastructure (VDI). RDS-V provides remote desktop access to managed desktop environments hosted in Hyper-V on Windows Server 2008 R2. OK, there are way too many technical buzzwords in that last sentence, aren’t

Welcome back to our Launch Series. Today is Day Thirteen – only a few more days to go! Today we’re continuing on with Remote Desktop Services with a look at the architecture. Here we go: There have been some design changes in RDS (remote desktop services) and in RDC (remote desktop client). Let’s start by discussing the legacy RDP. RDP is a layered binary-encoded protocol that runs on a lossless connection-oriented transport. Some of RDP’s layers originated in code derived from the NetMeeting project,

Raymond beats me to the punch (mine was going to be rant-i-er, but five times * as funny), on how the HKEY_USERS\.Default , despite having the word "Default" in the key name, isn't "The Default User" from which all others are initially spawned. It's possibly the most frequent misconception I've hit in the user profiles space (which I don't really work in any more, but did quite a bit for a while there). I even argue with colleagues about it from time to time; the most reliable way to win the argument

It's been ages since I touched on anything wibbles-related , but I realized I'd neglected a very common query: If one of my applications is under load, will Network Load Balancing route/move/transfer all the additional load to the other server? No . As long as the box still lives (or more specifically, the NLB driver is able to send heartbeats and receive incoming IP traffic), NLB will keep on allowing connections. The load rules are used to govern the rough percentages of connections, but any web

Well Parky, you asked , so I'm going to try to answer! The way I think about PAE is that it kinda works a bit like a stonking great in-memory pagefile might. It doesn't change the game for 32-bit applications, but it does give the OS more headroom to manage them. Without PAE, any memory over 4GB can't be "seen" by the OS itself, so it can't be used. With PAE, the memory manager can see all the installed memory, but it doesn't change the per-process or kernel limits. So if, for example, you ran 3

Via TonySo : http://www.microsoft.com/technet/security/advisory/904797.mspx Our initial investigation has revealed that a denial of service vulnerability exists that could allow an attacker to send a specially crafted Remote Desktop Protocol (RDP) request to an affected system. Our investigation has determined that this is limited to a denial of service, and therefore an attacker could not use this vulnerability to take complete control of a system. Services that utilize the Remote Desktop Protocol

Like XPSP2 before it, Windows Server 2003 Service Pack 1 is going to be distributed via Automatic Updates. The start date for automatic updates is July 26, 2005 . If you'd rather move at your own pace over the next year, you'll want to look at the Blocking Toolkit , and the following information: http://www.microsoft.com/WindowsServer2003/evaluation/news/bulletins/ws03sp1blockertool.mspx FAQ: http://www.microsoft.com/windowsserver2003/evaluation/news/bulletins/ws03sp1blockertoolfaq.mspx The blocking

Versions of Microsoft Windows for AMD64 and EM64T are now available: Windows Server 2003: http://www.microsoft.com/windowsserver2003/evaluation/trial/default.mspx MSDN Subscriber Downloads have both versions available now, under Windows Server 2003 and under Windows XP Professional (not the SP2 branch) respectively. X64 versions are built from the same code base as the 32-bit Windows Server 2003 SP1.

http://www.microsoft.com/downloads/details.aspx?FamilyId=22CFC239-337C-4D81-8354-72593B1C1F43 If you've been waiting for this - it's finally baked!

Release Candidate 2 for Windows Server 2003 SP1 is available to test from microsoft.com, which means RTM can't be that far away! A new feature in SP1 (at least, present in the RC2 build of SP1) that's been causing some confusion is RDP over SSL - a new option for Terminal Services that should provide server authentication for TS sessions, preventing MITM (man in the middle) attacks while providing a new option for encryption. Up front - RDP over SSL is not a firewall traversal technology . It doesn't