Retire those legacy farms and sites. SharePoint on-premise locking, unlocking and no access sites

I had to retire an old SharePoint 2013 on-premise farm following a successful migration project. Since this wasn't a wholesale migration, there was a small level of uncertainty whether we moved all the relevant content over. I removed locked all the sites in the farm as read-only and parsed the IIS logs to monitor access. When I was satisfied that I had redirected all the users to the new locations, I removed access to all sites and will leave it like that for a couple months before retiring the servers.


This works much better than shutting down the servers. If you've ever had to turn on a server that has been offline for an extended period you have no doubt experienced domain membership issues, patching compliance issues, outdated anti-virus signatures, etc.


If someone needs access to content in their My Site or something, I can unlock it by using the PowerShell command:


set-spsite -identity https://mysite/username -LockState "Unlock"

Unlock all sites in a farm:

Get-SPWebApplication | get-spsite -limit all | set-spsite -LockState "Unlock"


Lock all sites in a farm:

Get-SPWebApplication | get-spsite -limit all | set-spsite -LockState "ReadOnly"


Disable access to all sites in the farm:

Get-SPWebApplication | get-spsite -limit all | set-spsite -LockState "NoAccess"

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