Microsoft has released Service Pack 3 for Exchange Server 2010.
This is a significant release that delivers some key functionality to customers such as support for Windows Server 2012, support for co-existence with Exchange Server 2013 CU1, and general bug fixes and security updates.
nice install SP1 and you get new features and it is SP1 greats new stuff for your Hyper-V server. there is a work around with a * If you have the errors above and you are trying to logon to your server it is pending for uninstalling the Service pack and stays there forever. Well you can boot in safe mode or get the ownership of the and rename it. Just poweroff the server start in safe mode and reboot. This server is fried I have not found a solution to fix this or to recreate this issue.
these are the errors and the errors are not fixable !
Breakdown of all changes to date: Windows 7 Information Changelog.
I cannot possibly test all configurations extensively (meaning, each persons specific computer needs), but what I can offer is what “works for me” and the obstacles I have came across so you do not have to discover them on your own.
For Client Access servers that are in a CAS Array you should remove some of the servers (eg half of them) from the load balancer configuration, upgrade them, re-add them to the load balancer, then repeat the process with the remaining Client Access servers in that load balanced array.Before adjusting your service settings, ensure that your system has already installed all updates by “checking now” for any available updates via Windows Update.At this time, it is best for you to ensure that all services are set to the default values before updating your system.If you have an AD forest topology with multiple domains, or process restrictions that require schema updates to be managed a certain way, you can apply the Exchange 2010 SP3 schema update on a 64-bit domain controller that is in the same AD site as the Schema Master, using an account with Schema Admins and Enterprise Admins rights.Otherwise the schema update will be applied when you upgrade the first Exchange server.