<Update 8/1/2011>Just added some more links and notes… Looks like there is more to this…</Update>

I'm getting a little frustrated after feeling a little strong armed into updating to the June CU update. While I LOVE being an early adopter and LOVE being on the latest and greatest, I haven't been so happy with the latest update. Microsoft has been anxious to get people on SP1, and for valid reasons… the message of sharing SP1 they really encouraged people to install the June CU and most recently the update to the update, but should we have one more update to that one? So yeah, we were doing an upgrade and were told we'd have a better experience if we were running it, so we considered it, and figured if we had any support issues with just SP1, the PFEs and CSS Customer support reps would say our issues might be fixed in the latest update. Now I'm feeling a little foolish. Spence and Todd Carter (June CU Regression) had the right idea, while Spence has now been convinced that we should be pushing June CU. I still agree with the mantra: "Don't install the CUs it if you don't need them." Here's more information about the June CU re-release.

Here are the issues that we're experiencing that haven't been fully flushed out, but definitely appear to be regressions.

1. SP1 + June CU update: "Security validation for this page is invalid" – You get this error message when you have a people picker on the form: The security Validation for this page is invalid. Click back in your Web Browser, refresh the page and try your operation again. It happens when switching to or from a view that contains a people picker field. Workaround: Turning off security validation. It also appears to be happening on a postback for an attachments field on an Infopath form.

More details:

• Giles' Project and SharePoint Blog: Security Validation Issue – Form Services issue with SP1+June 2011 CU (Release 2) #in #SP2010 #SharePoint #MSProject #ProjectServer
• After June 2011 CU custom Application Pages produce exceptions (more info on the people picker)

Noticed that since the June CU some security coding practices are being enforced more often… See "Security Validation and Making Posts to Update Data"

For reasons of security, by default, Microsoft SharePoint Foundation does not allow you to make posts from a Web application to modify the contents of the database unless you include security validation on the page making the request.

TechNet: Security validation for this page is invalid" After SP1 on infopath browser forms

I was able to fix this error by adding this code to the bottom of layouts/dialog.master (this isn't in the page before the update either):

<asp:ContentPlaceHolder ID="PlaceHolderFormDigest" runat="server">

<SharePoint:FormDigest ID="FormDigest1" runat="server" />

</asp:ContentPlaceHolder>

1. Project Server PWA – Project Web Access provisioning fails… to provision site.

• Project Server 2010: SP1 and June 2011 CU–FormatException when trying to provision a PWA site
• Recording that mentions this in relation to Project and PWA provisioning in June CU update.
• @NaupliusTrevor: #SharePoint Workaround for June CU and PWA provisioning; delete and retype admin name before clicking OK bit.ly/qTaHcj

1. Another issue we ran into post June CU was our Profile customization where we would make sure you agree to the policy before updating your profile photo broke. Appears to be by design that we can no longer inspect to make sure the user is authorized and upload the photo on behalf of the user.

User Profile Administrators can no longer upload a picture for a User Profile in the UPA as of June 2011 Cumulative Update