My work was compromised due to it so Today i Decided to write a post on how to activate it to let go of that annoying message “windows is not activated and blah blah blah” So here are the foolproof steps There are many ways on the net to activate windows 7 ultimate but only a few work out– this is one of the working one’s as i have tested it myself 1.
If you know your windows is not an bought one then i recommend you to use this software called windows loader.
However for an Exchange 2010 Database Availability Group the upgrade process can be performed with no downtime following the normal process of moving active databases off DAG members while they are being updated.
You can use the standard process as demonstrated here: However, be aware that once a database has been made active on an Exchange 2010 SP3 member of the DAG, it can't be made active on a pre-SP3 DAG member again.
[this is optional if you still have trial apearring on system properties or the not genuine message] First download this registry tweaker and double click it and press ok for every thing it asks 3a.
Download this: file For 32bit OS –Download(do not do anything with this file now) Go to system32en-US folder and delete the file “mui” 7.
For example if you have two Hub Transport servers in a site, upgrade them one at a time.
The upgrades steps are very straightforward and easy to follow. When the splash dialog appears click Install Microsoft Exchange Server upgrade. Warnings will not prevent you from proceeding, but you should pay attention to them anyway as they are often important.
fit=610,381" class="alignleft wp-image-1618" style="border-style: initial; border-color: initial;" alt="" src="https://i0com/Client Access servers are the first server role to update, and you should begin with the internet-facing site if you have multiple sites in your organization.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.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.