Solved

MicroSoft, SQL Server, 2005, Large Domain, SharePoint Servers (NLB), one SQL Server, forced server(s) name change

Posted on 2008-06-19
5
201 Views
Last Modified: 2010-04-21
We have set up a development SharePointServer 2007, connected to a stand alone SQL server, which we are running in a AD Domain. Everything has been setup and is working properly. We were just advised we need to change the name of all the servers, URL's etc. , to accomodate an organizational name change.  I am only responsible for the SQL side, another team has the MOSS 2007 side. I do not have to change the names of the individual databases - those can remain the same.

The reseach I have done so far, indicates I should be able to rename the server with a stand-alone instance of SQL Server 2005. I have found information on renaming the report server. Backups are performed using LiteSpeed for SQL, and I should be able to modifiy those jobs. Am I missing anything? What else needs to be considered? Will I need to detach the databases from the old server, and reattach on the new? Is there a better way?

I would appreciate what ever help I can get. I am completely at a loss with this one.

0
Comment
Question by:chapmancd
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 38

Accepted Solution

by:
Jim P. earned 500 total points
ID: 21827253
If you are doing a completely new server/instance a couple of things I do/use to do cutovers/moves.

1. Beyond Compare from www.scootersoftware.com. At the cost -- it has given us something like 5000 times the payback. That is how I copy the mdf/ldf files.

2. Don't detach the databases, just take them offline (best from a QA window with Alter database DBName set offline with immediate rollback)  That way your backoff is much quicker if you would have to do it.

3. Get the sp_help_revlogin (http://support.microsoft.com/kb/918992) to transfer userids between the servers.

4. Make sure you keep the BOL (books online) handy.

5. I have these KB articles memorized:
http://support.microsoft.com/kb/314546
http://support.microsoft.com/kb/224071
Good to bookmark them and refer to them. They are actually quite well written.

0
 

Author Comment

by:chapmancd
ID: 21828999
jimpen,
Thanks for the assistance. Will review the recommended documents today. Looking to do move over the next week to ten days (hope closer to the ten day mark). Will comment on line again before I leave for the day with any additional questions, comments, concerns. Thanks again,

Cory
0
 

Author Comment

by:chapmancd
ID: 21951804
JIMPEN, Sorry it took so long to get back - things changed in our setup almost before I was done with my last entry. I was able to use the information you provided, but on a different issue.

With my original problem, we used stsadm.exe to invoke the "renameserver" command option on the MOSS 2007 servers (frontends, index and search servers) to rename all of the servers in the SPS farm, based on information found in the following two links:

http://msdn.microsoft.com/en-us/library/ms178083.aspx

http://technet.microsoft.com/en-us/library/cc263117(TechNet.10).aspx

The process looked like this:
1) Take a backup of the SQL Database before performing the following operations.
2) Rename the SQL Server from My Computer > Properties > Computer Name > Change
3) Reboot the Server when prompted to do so.
4) After reboot of the SQL Server is complete > Open a Remote connection to the
SharePoint Server.
5) Start > Run > Cmd
6) Change to the Directory C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\12\BIN 
7) Run the command Stsadm -o renameServer -oldservername
Old_Database_Server_Name -newservername New_Database_Server_Name 
8) After the command completes successfully > Reboot the SharePoint Server (Even if
not prompted for the reboot)
9) Once the server has rebooted > Browse to the SharePoint Central admin page and
check if the SQL Server shows up with the new name on the home page.

The only problem I was left with, I had to go back and modifiy all of my backups to accomodate the servers new names.

Thanks again for the assistance. Points have been awarded.

Cory
0
 

Author Closing Comment

by:chapmancd
ID: 31468861
The information you gave was on spot. We just changed direction mid-stream. Thanks for the assistance.
0
 
LVL 38

Expert Comment

by:Jim P.
ID: 21954064
Glad to be of assistance. May all your days get brighter and brighter.
0

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this blog post, we’ll look at how ClickHouse performs in a general analytical workload using the star schema benchmark test.
This article shows how to get a list of available printers for display in a drop-down list, and then to use the selected printer to print an Access report or a Word document filled with Access data, using different syntax as needed for working with …
Using examples as well as descriptions, and references to Books Online, show the documentation available for date manipulation functions and by using a select few of these functions, show how date based data can be manipulated with these functions.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

631 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question