The quickest and simplest ways to check the patch level of SharePoint

There are two ways to get the most accurate patch level and quickly:




  1. Central Admin - System Settings - Servers in farm
  2. PowerShell SharePoint Management Shell: (Get-SPFarm).BuildVersion

Comments

Post a Comment

Popular posts from this blog

"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

Renaming a SharePoint server

Image
How to change the server computer name with MOSS These instructions relate specifically to my VM configuration. I found many references on the internet for doing this and most omitted a step or included other steps. It was extremely frustrating spending the time doing this to have it fail. Finally I discovered another reference that indicated “stsadm updatefarmcredentials” was required. This was missing in other recipes. In addition, this recipe includes changing IIS identities, very possibly the problem that was occurring before. The error I was getting after unsuccessful attempts: “some or all identity references could not be translated”. This occurred when navigating to the operations page, for example. Old server name: SHAREPNTSERVER New server name: OMITTED User name: administrator Password: password Server name change steps 1. Change alternate access mappings Go to Operations in Central Administration. Select Alternate access mappings. Change them all to referen...
Read more

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