We all knew it was coming shortly after Hyper-V RTM’d a while back. MS had been hinting around at releasing an update to their support policy for virtualizing Exchange and they finally delivered.
"Today Microsoft announced some significant changes to its licensing and support policies for applications in hardware virtualization environments. There are two key parts of the announcement worth highlighting for Exchange customers:
- Microsoft now supports Exchange Server 2007 SP1 running Hyper-V or hypervisors validated under the Microsoft Server Virtualization Validation Program (SVVP).
- Microsoft is waiving its 90-day license reassignment policy to enable customers who virtualize Exchange to move their licenses between servers within a data farm as often as necessary."
Highlights for Exchange 2007
- The guest is running Exchange Server 2007 SP1
- The Exchange server is deployed on Windows Server 2008 OS (This is a big one)
- The Exchange server does not have the Unified Messaging server role installed
- No dynamically expanding disks (fixed disks only)
It is highly recommended to read the Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments found on the Exchange TechNet library if you plan on or are even thinking about virtualizing Exchange.
Click here to read the entire article…
This is one utility that I just can’t live without anymore. A recommended utility for any IT geek. Available in both 32-bit and 64-bit along with a nice white paper for your reading enjoyment.
SyncToy helps you copy, move, rename, and delete files between folders and computers quickly and easily.
Click here to download SyncToy…
Click here to get the white paper…
An update to the OCS BPA was released over the weekend.
The Microsoft Office Communications Server 2007 Best Practices Analyzer is designed for administrators who want to determine the overall health of their Office Communications Server 2007 servers and topology.
Click here to download the update…
This little gem has been floating around the Internet for some time now but I’m still going to add it here. Jeffery Snover over on the Powershell team blog came up with the basis for this trick. The guys over at the MSExchange team seized the opportunity to apply it to EMS and dropped a little post about it a few days back.
Basically, if you’ve ever started up the Exchange shell you know that it always takes a bit to get up and running. Now if you are making a lab or your Exchange server isn’t very powerful those few seconds will multiply quickly.
So as usual never one to reinvent the wheel check out the MSExchange team’s post and see for yourself.
"So how does speeding up PowerShell help Exchange?
The Shell is built on Windows PowerShell technology, and under the hood, the Exchange Management Console also executes PowerShell cmdlets. If you’re running Exchange Server 2007 on Windows Server 2003, you’re likely to see performance gains in shell start-up times after running this script. On one of my Exchange 2007 servers, EMS now starts up in as little as 2-3 seconds. Disclaimer: Your mileage may vary"
Click here to read the rest of the post…