Jamin

I recently ran into this issue but the solution posted here (upgrading to CU3) did not fix it for me. However, as this was the first (and only) site I came across with this error message, and as I have now resolved the issue, I thought I'd post the fix here for others to find. The problem in my case was Windows Updates. Specifically FEP updates. I'd created a nice little automated deployment rule to approve FEP updates, add them to a software update group, and then assign that update group to All Systems. Unfortunately on the automatic deployment rule I'd set the setting to "Create a new Software Update Group" each time the task runs. Over the past 7 months this rule had created in excess of 700 FEP update groups that were all assigned to every PC that was being built. Although I'm not 100% sure of the inner workings of SCCM 2012, my guess is that after the client is installed in the OSD it goes back to the server to find out what deployments it needs to run. This information is then returned in the form of an XML document that the client interprets. The 700+ deployments must have created an XML file that was too big for the client to handle and this caused the build to fail. To resolve the problem I went in to the Software Update Groups section and deleted all but the most recent update group. I then changed my automated deployment rule to "Add to an existing Software Update Group". This resolved the maxXMLsize size constraint violated error. So if you do get this error, check the number of mandatory deployments on All Systems, or any other collection that your computer is a member of.