Hyper-V, the virtualization capability comes with Windows Server 2008, is just finally released. The final version number is 18016. This is the complete Hyper-V RTM package for Windows Server 2008 x64. It includes the Hyper-V Server components for Full and Core installations. In addition, is contains the Windows Server 2008 Hyper-V Management components for Full installations. Notice once installed, this package is permanent and cannot be uninstalled.
If upgrading from Hyper-V RC0, RC1 Escrow, RC1 or RTM Escrow, you will not need to recreate your virtual machines or network settings. All virtual machine information will simply persist once the upgrade is complete. However, saved-state files and online snapshots are not supported during the upgrade. Integration Components are specific to the build of Hyper-V. New Integration Components (ICs) must be installed for your supported guest operating systems. Hyper-V RTM Integration Components for all supported Windows Operating Systems are provided using the ‘Action’ à ‘Insert Integration Services Setup Disk’ action.
New customers and partners can download Hyper-V at http://www.microsoft.com/hyper-v. Customers who have deployed Windows Server 2008 should receive Hyper-V from Windows Update beginning July 8. Here are some essential bookmarks on Hyper-V:
· Microsoft Virtualization web site
· Microsoft Virtualization Team Blogs
· Windows Server 2008 and Virtualization
Microsoft Assessment and Planning (MAP) Toolkit 3.1 is to help accelerate planning and deployment of virtualization solutions. More information is available at http://www.microsoft.com/map. The logo-qualified hardware and software for Windows Server 2008 and Hyper-V are available at http://www.windowsservercatalog.com.
Do the following steps in your target Windows Server 2008 x64 box.
To get the sidebar,
Now to get the Aero, assuming your graphic card is sufficient
Then spend the next hour to add/remove all the gadgets you like/dislike, which is the fun part. After all is done, here's what a Windows Server 2008 desktop may look like.
Finally I got some time to finish documenting the screen flow of Groove Server 2007 Relay installation. It is now published and the one for Groove Server 2007 Manager is also available here. Let me know, if you notice any correction is needed.
Windows Server 2008 has Rights Management Services (RMS, which is a server add-on feature) as an installable role and seamlessly integrated into the OS. Further Information Rights Management (IRM, which is the client ability to comply with what is set to be enforced by RMS) can be enabled in SharePoint Central Admin (after installing RMS client on the SharePoint box) by pointing SharePoint to a RMS server in Central Admin Operations and also granting IIS App Pool ID and AD RMS Service Group access right to server certificate web services on the CA box required by RMS. The operations are straightforward as discussed in my webcast.
When adding a SharePoint file tool in a Groove workspace, the documents downloaded from an IRM-enabled SharePoint document library are still embedded with set usage policies. Groove does not translate SharePoint permissions, nor the usage policy embedded in an IRM-enabled document regardless it is from SharePoint or not. As far as documents in a Groove workspace are concerned, Groove is a secure transport. As far as Groove is concerned, all documents are bits and bytes. It is up to the file system at an end point to, as appropriate, invoke an associated application to open a file. The transition of a file from Groove to a local file system is transparent to a user. With RMS-aware application like Office 2007, IRM will kick in and the usage policy is for sure enforced at file opening time based on individual’s license acquired form RMS server.
The net is IRM is transparent to Groove. IRM is enforced at file opening time regardless where it is from or if it is placed in Groove or not.
June, 2008 - Yung Chou on Hybrid Cloud - Site Home - TechNet Blogs