For some reason, the June build of Office 365 (2013) update won't let 95% of my users open any office application. I have been in the process of deploying it in a side by side with the existing Office 2007 version.
There were a few hiccups with some add-ins (adobe, ozlink and shoretel) and a Office is busy message. So I decided that I should get the June build to see how well it worked. Well I don't know what happened because it screwed pretty much everyone that pulled it down.
I immediately deleted the office directory on my local server to prevent further damage and then created the configuration.xml file for the previous build and ran setup /download to grab it.
The build just completed the download but since they deprecated the force downgrade option for the configuration.xml, I am a little lost on how I tell the clients on my...