This hotfix rollup resolves the following issues:
- You cannot protect the Microsoft Exchange Database Availability Group (DAG) on a secondary DPM 2010 server.
- You are prompted to restart a client computer after you install an agent on the client.
- DPM services crash, and you receive the error, “Unable to connect to the database because of a fatal database error.”
- MSDPM crashes, and event ID 945 is logged in the event log.
- When you change a Protection Group, add a very large database, change the disk allocation, and then commit the Protection Group, DPM 2010 does not honor the user intent, and instead, DPM 2010 sets the sizes of replica and shadow copy volumes to the default sizes.
- The Management tab does not link to information about the latest Microsoft Knowledge Base article for DPM 2010.
- You receive the message, “Computers not synchronized,” when you try to replicate DPM 2010 databases to a System Center Operations Manager.
Get it here http://support.microsoft.com/kb/2250444