Even if you’ve planned your SharePoint project properly, or it might be years later, you need to rename your SharePoint 2010 server. This quick tip covers this on SharePoint 2010 which is a much cleaner experience than it was in 2007. There is an STSADM switch that can handle it, but for 2010, there is a certain procedure to yield best results. I was able to do this on a single SharePoint server earlier and it worked great! This was a single SharePoint server with SQL on another server.
For 2010, there’s a new PowerShell cmdlet for this very thing, Rename-SPServer. This is this article on TechNet covering the procedure. It has you renaming the server itself first, then fixing up SharePoint. However I’ve heard of issues with that, and I had better results by doing it in reverse. That is, running the PowerShell to fix up SharePoint then renaming the server. Here is what I did:
1: Rename-SPServer –identity “old_server_name” –name “new_server_name”
That’s it! Of course if you like, you could write a quick little PowerShell script that would do all this for you. If you need to do STSADM, you would run the following (assuming its in your system path):
1: stsadm -o renameserver -oldservername <oldServerName> -newservername <newServerName>
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.