Microsoft Tech.Ed Online Link : http://www.msteched.com/online/home.aspx
Here are the top 3 reasons you should join me at Tech·Ed 2010.
More networking, more knowledge – Tech·Ed is an intensive learning experience and a great opportunity to expand our network of IT contacts.
Practical skills – Together, we can cover more ground by going to more sessions and more labs. Then we can start applying our new skills right away to build, deploy, secure, mobilize and manage solutions.
Competitive Advantage – Tech·Ed can give us all the chance to experience emerging technologies and share ideas. That’s the perfect way for all of us to get a competitive edge in the future.
Sound good? Let’s do it! To learn all about Tech·Ed 2010, just click here
Live migration is integrated with Windows Server 2008® R2 Hyper-V™ and Microsoft® Hyper-V™ Server 2008 R2. With Hyper-V™ live migration, you can move running VMs from one Hyper-V™ physical host to another without any disruption of service or perceived downtime.
Hyper-V™ live migration has very similar requirements to Hyper-V™ Quick Migration. For organizations already using quick migration, the shift to using live migration should be simple. The physical hosts that will participate in live migration must be configured with Microsoft Failover Clustering Services as a Failover Cluster and must use shared storage. In addition, the physical hosts must use the same processor type. For example, to use live migration to move a VM from one Hyper-V™ physical host to another, both physical hosts must use processor(s) from the same manufacturer. It should be noted that there are no differences in storage requirements between Quick Migration and live migration.
For Articles and White paper from Microsoft click here
New and Updated Features in Windows Server 2008 R2..click here
Below is a complete list of the requirements for Hyper-V™ live migration:
Hyper-V™ live migration is supported on the following editions of Windows Server 2008 R2:
- Windows Server 2008 R2 x64 Enterprise Edition
- Windows Server 2008 R2 x64 Datacenter Edition
- Live migration is also supported on Microsoft® Hyper-V™ Server 2008 R2.
- Microsoft Failover Clustering must be configured on all physical hosts that will use live migration
- Failover Clustering supports up to 16 nodes per cluster
- The cluster should be configured with a dedicated network for the live migration traffic
- Physical host servers must use a processor or processors from the same manufacturer
- Physical hosts must be configured on the same TCP/IP subnet
- Physical hosts must have access to shared storage
Recommendations and Notes:
- A clustered shared volume is recommended for VM storage in a cluster where live migration will be used.
- One live migration can be active between any two cluster nodes at any time. This means that a cluster will support number_of_nodes/2 simultaneous live migrations. For example, a 16-node cluster will support 8 simultaneous live migrations with no more than one live migration session active from every node of the cluster.
- A dedicated 1 Gigabit Ethernet connection is recommended for the live migration network between cluster nodes to transfer the large number of memory pages typical for a virtual machine.
The cluster configurations that have been validated by vendors can be found through the listings in the FCCP program under the heading of The Microsoft Support Policy for Windows Server 2008 Failover Clusters ..click here
Stop printing and use digital technology
SAVE OUR EARTH
IT’S A FIRST FOR THE MIDDLE EAST. DON’T MISS OUT..REGISTER NOW! You can’t afford to miss out on the very first Tech·Ed in the Middle East. Worldwide Telephone: +971 4 293 0117, Worldwide Fax: +971 4 501 5777, E-mail: email@example.com, MSN Support: firstname.lastname@example.org
The Windows Activation Technologies Update for Windows 7, the Windows Genuine patch is designed to detect more than 70 known and potentially dangerous activation hacks, according to a February 11 post about the update on the Windows Team blog. They are planning to push the update first to Windows 7 Home Premium, Professional, Ultimate and Enterprise users via Windows Update later this month, and also plans to make the update available for download via the http://www.microsoft.com/genuine site starting February 16 and on the Microsoft Download Center as of February 17.
A good tool…
Microsoft Exchange Server 2010 introduces the Exchange Deployment Assistant or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment.
You can use ExDeploy for the following scenarios:
- Upgrade from Exchange Server 2003
- Upgrade from Exchange 2007
- Upgrade from mixed Exchange 2003 and Exchange Server 2007
- New installation of Exchange 2010
For more info click here
Dumpster is essentially a view stored per folder. Items in the dumpster stay in the folder where they were soft-deleted (shift-delete or delete from Deleted Items) and are stamped with the ptagDeletedOnFlag flag. These items are special-cased in the store to be excluded from normal Outlook views and quotas. In addition, data with this flag cannot be searched or indexed.
Key architectural changes in Exchange 2010 must meet these requirements
- Exchange has to ensure that dumpster data moves with the mailbox.
- Dumpster data must be indexed and discoverable.
- Dumpster must have a quota.
- Exchange has to prevent purging of data from dumpster.
- Exchange has to track edits of certain content.
- Dumpster should be per mailbox and not per folder.
To facilitate these requirements, Dumpster was re-architected, Dumpster 2.0 is no longer simply a view…Dumpster in Exchange 2010 is implemented as a folder called the Recoverable Items and is located within the Non-IPM subtree of the user’s mailbox (note that this is a hidden section of the mailbox and is not exposed to the end user through any client interface). The folder has three sub-folders:
Dumpster data is now indexed and discoverable, can now be moved with the mailbox, and is now stored on a per-mailbox basis rather than a per folder basis. Exchange 2010 includes capability for each mailbox to also maintain an archive mailbox as well. There is a dumpster for both the primary mailbox and the archive mailbox. Data deleted in the primary mailbox is placed in the primary mailbox dumpster, while data deleted in the archive mailbox is placed in the archive mailbox dumpster. Unlike previous exchange server, Exchange 2010 automatically purges items from dumpster 14 days by default and 120 days for calendar items..you can set this up..
Exchange 2010 includes the ability to ensure that data within the mailbox is preserved for a period of time…short term or long term. This feature can be enabled enabled on a per mailbox basis by running the following cmdlet: Set-Mailbox <identity> -SingleItemRecoveryEnabled $true