Installing MOSS SP1

Installing MOSS SP1 isn't difficult, but there is at least one area I found to be a head scratcher due to the text in the Configuration Wizard notification window.



I'll save the steps that several others have already catalogued. Here is a decent blog that highlights the steps involved in deploying the service pack:

http://msmvps.com/blogs/shane/archive/2007/12/14/how-to-install-wss-and-moss-sp1.aspx



I received this message after installing the MOSS SP1: You must run setup to install new binary files for every server in your farm. If you have multiple servers in your farm, run setup and the configuration wizard on the other servers now, and then return to this server and click OK to continue.

What? Okay, here's what this means. You don't actually run the configuration wizard on every server first. Start with the server that hosts central admin and run the WSS 3.0 SP1 and MOSS sp1. Don't click OK. Go to each front end server and run the binaries on each of those servers. THEN come back and click OK which will start the configuration wizard on the first server. Go around and click OK on all the other servers after the Configuration Wizard completes.

It wouldn't hurt to perform and IISRESET, but I didn't do the reset and it seemed to function fine. I will test more tomorrow and update this post if I find anything useful.


Comments

Post a Comment

Popular posts from this blog

Robocopy Error 31 A device attached to the system is not functioning

I was migrating Windows file shares to NetApp CIFS shares using Robocopy. I was unable to copy owner information or NTFS Security (/COPY:DATSOU) without getting this Error: ERROR 31 (0x0000001F) Copying NTFS Security to Destination Directory F:\PATH A device attached to the system is not functioning. I thought it may be the zone information on may of these files. I used the Sysintenals Streams utility to remove that information. It did not help. In the end, I was forced to copy without NTFS information (/COPY:DATU) When I viewed the properties of any share, folder, or file, the length of time to enumerate and display the permissions was exceedingly slow. I tried disabling anti-virus, etc. In the end, I had to manually re-create the permissions after the initial data copy. File ownership information was lost. UPDATE: I ran a CHKDSK /F and following a reboot this robocopy functioned fine.
Read more

"The following factors also affect the level of access for" user with excess permissions

Image
I have a user that had access to site settings, all content, etc. I double checked her access and it was read only but the permissions check tool showed a panel beneath the site permissions that showed Allow for many categories. She had full control. "The following factors also affect the level of access for" She was added as a Site Collection Administrator. I don't know who would have added her there, but someone had. If you find this type of issue, that should be the first thing you check. You can also check the Web Application User Policy in Central Admin. That's the other area I find people or groups with elevated permissions.
Read more

Unknown server tag 'AdminControls:MigrationToolPromotionTip'. in Central Admin after installing SharePoint 2013 security update KB4482464

I installed KB4482464 on my sandbox server without issue so I moved to my development farm. Following the patch, Central Admin (CA) had an error: Unknown server tag 'AdminControls:MigrationToolPromotionTip'. I noticed that the sandbox environment CA had this banner: You can now use the SharePoint Migration Tool to migrate to OneDrive and SharePoint Online. It looks like that failed in the Dev farm. The Configuration Wizard GUI failed to successfully run. Solution: I ran PSCONFIG with these options on my primary APP server: psconfig.exe -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent -install -cmd upgrade -inplace b2b -force -wait I ran PSCONFIG with these options on my remaining app, search and WFE servers: psconfig.exe -cmd upgrade -inplace b2b -wait -force I will exclude this update from my deployment on SCCM and run it manually.
Read more