The RDC 7.0 client can be used to connect to legacy terminal servers or to remote desktops as before. However, the new features that are mentioned in this article are available only when the client connects to a remote computer that is running Windows 7 or Windows Server 2008 R2
Web Single Sign-On (SSO) and Web forms-based authentication
For security, Web SSO requires remote applications to be signed using a certificate from a trusted issuer.
Access to personal virtual desktops by using RD Connection Broker
Access to virtual desktop pools by using RD Connection Broker
Status & disconnect system tray icon
RD Gateway-based device redirection enforcement
RD Gateway system and logon messages
RD Gateway background authorization & authentication
RD Gateway idle & session time-outs
NAP remediation with RD Gateway
Windows Media Player redirection
Multiple monitor support
Note For connections with multiple monitor support enabled, AeroGlass support is currently not supported and will be turned off.
Enhanced video playback
Functionality available only when connecting from Windows 7 to Windows 2008 R2
Language Bar docking
RemoteApp allows users to use their docked Language Bar with their RemoteApp applications just as they do with the local applications.
This productive functionality was previously unavailable. Instead, users had to use the floating Language bar.
Remote application task scheduler
Remote application task scheduler functionality automatically starts remote applications on the Remote Desktop client required by the user. The client computer must have Windows 7 installed to use this feature.
Aero Glass support
Terminal Services in Windows Server 2008 did not support Aero Glass remoting for sessions. This is now supported in Windows Server 2008 R2 Remote Desktop Services, but is incompatible with multi-monitor support.
Start applications and desktops from ‘RemoteApp and Desktop Connections
Users can subscribe to all of their RemoteApp programs and desktops which are then listed in their local Start menu. The list is automatically updated as items are added or deleted
Update for Windows Vista, x86-based versions
Update for Windows Vista, x64-based versions
Update for Windows XP, x86-based versions
Here are the Release Notes from the RC that discusses this issue. It’s about half way down under the System Preparation Tool section
SCVMM takes care of applying sysprep.
But you most likely want the "Deployment Toolkit"
Hotfix needed to move R2 differencing disk to Windows Server 2008
In Windows Server 2008 R2 there was a minor change to the format of differencing virtual hard disks. As a result you will need to apply an update to Windows Server 2008 if you want to move differencing disks from Windows Server 2008 R2 to Windows Server 2008.
You can download this update from here:
Note that this applies to Windows Server 2008 and Windows Server 2008 SP2 (not to Windows Server 2008 R2). If you do not have this update installed and you try to use a differencing disk created with Windows Server 2008 R2 you will receive an error message that states that the virtual hard disk is corrupted or unreadable.
Posted by Ben ( Virtual PC Guy )
In a server-based computing environment, all application execution and data processing occur on the server.
- Virtual PC supports a maximum virtual disk size of 127GB. If you create a VHD from a larger disk it will not be accessible from a Virtual PC VM.
- Do not attach to VHDs on the same system on which you created them if you plan on booting from them. If you do so, Windows will assign the VHD a new disk signature to avoid a collision with the signature of the VHD’s source disk. Windows references disks in the boot configuration database (BCD) by disk signature, so when that happens Windows booted in a VM will fail to locate the boot disk.
If the Directory Service event log reports Event ID 2095. Here is how to fix the issue:
Shut down the domain controller virtual machine that recorded the error, and ensure that it does not restart.
Determine whether a snapshot of the domain controller was recently used as a restore mechanism. If so, this is most probably the source of the error.
Attempt to determine whether any changes originated from this domain controller and propagated to other domain controllers. If the event was a result of a snapshot or copy of a virtual machine being started, try to determine the time the USN rollback occurred. You can then check the replication partners of that domain controller to determine whether replication occurred since then.
You can use the Repadmin tool to make this determination. For information about how to use Repadmin, see Monitoring and Troubleshooting Active Directory Replication Using Repadmin (http://go.microsoft.com/fwlink/?LinkId=122830). If you are not able to determine this yourself, contact Microsoft Customer Service and Support (http://go.microsoft.com/fwlink/?LinkID=102491) for assistance.
Forcefully demote the domain controller. This involves cleaning up the domain controller’s metadata and seizing the operations master (also known as flexible single master operations or FSMO) roles. For more information, see the “Recovering from USN rollback” section of article 875495 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=137182).
Delete all former VHD files for the domain controller.