Duration: 6m 51s
Read more...
ITStuff.ca - ITStaff is all about Windows, VMware, Hyper-V, Virtualization, HP Servers, Blades and other IT Technologies. An invaluable source of Tools and Scripts for IT Network Administrators. A valuable advice, Tips, Tricks and best practices for Net Admins.
Duration: 6m 51s
This video walks through the installation of Hyper-V in Windows Server 2008 R2, and also looks at some of the key changes in this release, such as Processor Compatibility, Core Parking, and more.
Duration: 17m 37s
Microsoft released the SP1 beta at Tech Ed North America in June. Since then, almost 500,000 SP1 mailboxes have gone into production in Technology Adoption Program (TAP) customer environments.
Cached Exchange Mode in a Remote Desktop Session Host environment: planning considerations is a technical whitepaper recently released by Microsoft.
Historically, Microsoft Outlook has only been supported in an RDSH environment when it is deployed in Online Mode and connected to a Microsoft Exchange Server. This is still the recommended configuration for Microsoft Outlook 2010 when it is deployed in an RDSH environment. However, customers who deploy Outlook 2010 now have the supported option of enabling Cached Exchange Mode when Outlook 2010 is installed in a Remote Desktop environment. Cached Exchange Mode might be ideal for deployments in which Outlook is connecting over a high latency connection to an Exchange server that is located remotely. For the relatively few users who access Outlook through a remote desktop, this might be the ideal configuration. However, Online Mode against the Exchange server is still the most scalable and optimized configuration for large deployments.
This white paper covers three major areas that you should consider when you deploy Outlook 2010 with Cached Exchange Mode in a Remote Desktop environment:
The August 2010 edition of the TechNet Magazine is now available for online reading.
The long answer is as follows:
Prior to Window Server 2008 R2 (namely in Windows Server 2008) you could run into a couple of problems. In Windows Server 2008 R2 Microsoft has implemented a Sysprep provider to ensure that everything goes smoothly. This provider does work during two of the phases of Sysprep:
Generalize
The generalize phase of Sysprep is where an installed version of Windows is prepared to be duplicated – and all installation specific information is removed. During this phase Hyper-V makes a couple of key changes:
Specialize
The specialize phase is run after the system image has been deployed to a new computer. Hyper-V makes the following change as part of this phase:
This whitepaper discusses the benefits, configurations and considerations when planning a Microsoft® Windows Server® Remote Desktop Services solution with Microsoft Application Virtualization (App?V®), and while I could probably write up a big long summary and post it here, probably the best way to let you know what's in it is to show the table of contents:
If you run App-V 4.6 on your Remote Desktop Session Host (RD Session Host) servers then you definitely owe it to yourself to check this one out. You can download the whitepaper here.