If that is a concern for your environment, but you still want the bug fixes and security updates, you might consider sticking with Service Pack 2 and applying Update Rollup 6 instead.
At the time of this writing there are some points in the various release notes that aren't correct or fully updated yet that Microsoft are still working on or that are worth some clarification: You should also plan to update any management tools installations you have on admin workstations or servers, and also check your third party applications that integrate with Exchange in case they also need updated management tools.
But you can spoof Windows updates in order to install retail bits on checked builds and vice versa. Double-click on it and change its value to Checked as shown in following screenshot: If the value is already set to Checked, then change it to Free and click on OK.
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.service Pack 3 to run some applications or due to some other reason but we may be running Service pack 2.I have also come across this situation and then I googled it and found a very simple solution to this problem. When we changed the value of CSD Version from 200 to 300. And thus if you install any program requiring Windows XP service Pack 3 and up then that program will also think that it is Windows XP 3.For example, Windows XP SP3 contains all the fixes that are included in Windows XP Service Pack 2 (SP2).Office XP, Office 2003, Office 2007, Office 2010 and Office 2013 service packs have been cumulative.