That's a weird one- I don't see any updated files that it'd install from PATCH_CAB and in !_StringData, it says "For Testing Purposes Only". It'll be interesting to see what the KB article says, when available (or if the update will even remain available publicly). Good find though Burf!
The KB article is avaible but I can't post the link...yet I don't have the required 20 posts) Issue that this update fixes When you install Office 2010 SP1, SharePoint Workspace 2010 is installed. However, SharePoint Workspace 2010 is not included in the original Office Professional Plus 2010 installation and should not be installed. In certain situations, Microsoft Office Groove 2007 is upgraded to SharePoint Workspace 2010 when you install Office SP1. For more information about this issue, click the following article number to view the article in Microsoft Knowledge Base: 2612800 Office 2010 SP1 installs SharePoint Workspace So allegedly it fix the god damn SharePoint Workspace issue when SP1 is slipstreamed! It is about time MS do something about it! Looks like they heard us!
Burf, you ask some good questions- maybe others know the answers. I'm not 100% sure how the update works at this point.. Yeah, it seems like this should've been an issue that was fixed a week or two after SP1 was released, instead of taking 8 months to do it. But, good timing, considering we were just talking about the issue here last week!
Yes, but it did answer the question I asked earlier on. The update must be applied before Service Pack 1.
This is however a bit of a problem if you intend to integrate them... or well maybe installer is smart enough and installs this update 1st
Here's what I've seen with this patch: I installed it after Office, SP1 and updates were installed: the patch applies but does nothing (as expected) except to add a messy entry in Installed Updates. Sharepoint Workspace remained installed. Added the patch's .msp in the \Updates folder (slipstreamed) with default name and did a fresh install: SP1 was installed 1st, the patch was installed 35th (out of 48 updates applied). Sharepoint Workspace remained installed. Added the patch's .msp in the \Updates folder, added "1_" to filename in hopes of installing first, then did a fresh install: SP1 was installed first, the patch was installed 13th (out of 48 updates). Sharepoint Workspace remained installed. So this patch is useless for slipstreaming (unless somebody knows of a script to get it installed before SP1). In my case, slipstreaming everything (without this patch) and then manually uninstalling Sharepoint Workspace is the way I'll continue (personal install; not a corporate deployment environment). I'm sure SP2 will fix the issue correctly, but that's probably at least another eight months out.
In that case, it must be detecting the sp1 files (by the sp1 at the end of the first part of the filename) and installing them first. Possible solution: Rename rmaddlocal-x-none.msp to rmaddlocalsp1-en-us.msp (for example) to mimic a SP1 file, and place it in the updates folder along with the rest of the updates. Make have to add a '1' or an 'a' to the beginning of the filename to ensure it installs first.
Burf, good suggestion, but no luck- I just tried renaming the file to "1_rmaddlocalsp1-en-us.msp" and then did a fresh install. The patch was again the 13th one installed- well after SP1 and again ineffective. I predict a v2 release of this patch soon, considering how messy its Installed Updates entry is..
So, they are spying on us in this thread? File Version of msp: pre_rmaddlocal-x-none.msp extracted from Office2010-kb2598245-fullfile-x64-glb.exe, downloaded from Microsoft Download center: 14.0.6117.5002 rmaddlocal-x-none.msp from burfadel's link: 14.0.6119.5000 @burfadel Where did you obtain the newer msp?
My prediction was right- the update was replaced. Burf is also correct- I downloaded the patch .exe from that KB page (right after it was posted) and the extracted .msp was the same one he uploaded (the newer ver). They must've replaced it just last night. The patch now has that older version number, but a later build date (by 6 days). The entry in Installed Updates is now fixed. Before, the entry said "14.0.6119.5000 x-none\rmaddlocal.msp (For Testing Purposes Only)". With the latest ver installed, the correct info is shown. I'll need to re-run the tests I did earlier with this latest patch.
I added the latest ver of the patch's .msp to the \Updates folder, renaming it with a "1_" at the beginning of the filename (all other patches using their default names) and then did a fresh install. The only difference I see is that the entry in Installed Updates is fixed. Sharepoint Workspace is still installed (even though it was not selected during install). So this patch is not effective in integrated (slipstreamed) installs, unless someone can figure out a script to get it installed before SP1. I didn't test it, but I'm sure the patch is effective for non-integrated installs- first install Office, then apply this patch, then install SP1, then apply updates. But that method adds so much time to the install process that it's quicker to just manually uninstall Sharepoint Workspace after an integrated install is complete.
hi mcrip, question: why are the runtimes in folder, it used to be in 7zip. any idea, when it will be in 7zip again? thanx for updates and your hardwork
My bad; I'm doing it now. It will take a couple of hours total to download , compress, upload-1:30 Eastern Standard Time. Also, I'm uploading the new Microsoft Express Deployment Tool 1.2 for those that want it. Handy for seamless deployment of Office 2010 with Windows 7
Out of curiosity, I tested the patch in non-integrated installations today. I first did a fresh Office install (no SP1), then applied the patch using its full .exe, then installed SP1. I also repeated the procedure using the patch's extracted .msp. Both times it was effective- Sharepoint Workspace was not installed after SP1 was applied. But since most users will be doing an integrated install (via the \Updates folder) or will have SP1 already installed, I don't see much value in this patch. SoLoR- you still have version 14.0.6119.5000 of this patch in the repo. You should swap that one out for the version currently available from the KB page (14.0.6117.5002). Even though it's an older version number, the build date is newer and it fixes a problem that the version in the repo currently has (sloppy entry in Installed Updates). Thanks to akf for noticing the patch had been updated yesterday.