Renaming a Standalone SharePoint 2010 Server

October 23, 2011 by Joel Jeffery

OK. You never create standalone servers. I know. But, let’s just say you *did* have one, maybe for development or test, and let’s say you had such an environment on your laptop, and also let’s say your machine had an embarrassing name that you needed to change before you next demoed SharePoint stuff on it… OK, you get the picture. Smile

The Microsoft recommended steps are:

Rename your PC using Computer properties:
Reboot.
Run the PowerShell Command “Rename-SPServer”

There is only one problem with this suggested method: it’s a steaming pile of nonsense.

The correct procedure would be:

Rename your server using “Rename-SPServer”
Rename the PC using Computer properties
Reboot
Rename your SQL instances
Restart SQL
iisreset /noforce

If you are unlucky enough to have tried to follow the official guidelines and renamed the PC before executing Rename-SPServer, you would get a message like this when trying to launch the SharePoint Management Shell:

Then the correct recovery would be:

Rename the server using “stsadm -o renameserver”
iisreset /noforce
Rename your SQL instances.
Restart SQL
iisreset /noforce

Best of luck!

#spthingaday

#spthingaday 003 - Information Architecture. Folde

#spthingaday 003 - Information Architecture. Folders are evil. Use metadata. #SharePoint, #Office365..
On a fileshare, all you have is path and filename. That's the only axis by which you can classify your stuff. So you nest folders, within folders, within folders. Then you pack the filename with extra bits of information - like the initials of the last editor, or the version number.
You don't need to do this in SharePoint. Use metadata.
Add columns to your libraries. Text columns, number columns, choice columns, managed metadata columns. Each file can have several of these values simultaneously. But a file can only live in one folder at a time.
Use metadata.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

#spthingaday 003 - Information Architecture. Folders are evil. Use metadata. #SharePoint, #Office365..
On a fileshare, all you have is path and filename. That's the only axis by which you can classify your stuff. So you nest folders, within folders, within folders. Then you pack the filename with extra bits of information - like the initials of the last editor, or the version number.
You don't need to do this in SharePoint. Use metadata.
Add columns to your libraries. Text columns, number columns, choice columns, managed metadata columns. Each file can have several of these values simultaneously. But a file can only live in one folder at a time.
Use metadata.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

14 0

#spthingaday 001 - Governance. Avoid death by file

#spthingaday 001 - Governance. Avoid death by fileshare #SharePoint, Teams, Planner and #Office365 projects need executive sponsorship.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

#spthingaday 001 - Governance. Avoid death by fileshare #SharePoint, Teams, Planner and #Office365 projects need executive sponsorship.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

15 0

#spthingaday 060 - SharePoint Search. Changing the

#spthingaday 060 - SharePoint Search. Changing the Search Topology. #SharePoint, #SharePointSearch.. The Search Service in SharePoint on-premise is made up of six components.

Crawl, Content Processing, Index, Analytics, Query and Administration.

Each of these components can be placed on one or more servers in your Farm.

To make any one Search component support high availability, you need to make sure there are at least two servers in your Farm running it.

SharePoint Server 2010 had only 3 types of component, and Microsoft let you manage their placement via Central Admin, in the browser.

From SharePoint 2013 onwards, this was deemed too difficult to express graphically.

For SharePoint 2013 and 2016, topology changes need to be made via PowerShell.

Tomorrow, we'll look at just what PowerShell cmd-lets you need to use.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

#spthingaday 060 - SharePoint Search. Changing the Search Topology. #SharePoint, #SharePointSearch.. The Search Service in SharePoint on-premise is made up of six components.

Crawl, Content Processing, Index, Analytics, Query and Administration.

Each of these components can be placed on one or more servers in your Farm.

To make any one Search component support high availability, you need to make sure there are at least two servers in your Farm running it.

SharePoint Server 2010 had only 3 types of component, and Microsoft let you manage their placement via Central Admin, in the browser.

From SharePoint 2013 onwards, this was deemed too difficult to express graphically.

For SharePoint 2013 and 2016, topology changes need to be made via PowerShell.

Tomorrow, we'll look at just what PowerShell cmd-lets you need to use.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

12 0