Not sure about Project, but for SQL, the syntax to rename the DB and instances
are:
Rename a SQL Server after Restoring Image
--run this first
-- get current SQL Server name\instance name
SELECT @@SERVERNAME
-- get current machine name and instance name
SELECT SERVERPROPERTY('MachineName'), SERVERPROPERTY ('InstanceName')
--get the values from the results of the above script, and then run these two
with the correct values.
sp_dropserver 'old_name'
go
sp_addserver 'new_name', 'local'
go
Restart the Server
From: Jeff Bunting [mailto:[email protected]]
Sent: Monday, August 24, 2009 9:57 AM
To: NT System Admin Issues
Subject: VM cloning advice
Wanted to run this scenario past the list and see what you all think. We have
an MS Project 2007 Server and a separate SQL 2005 backend server being used in
production under VMWare. The developers want to create a test environment to
troubleshoot problems on the production system. I was thinking we could just
clone both VMs, run sysprep, and change the server names and IP addresses.
IIRC, renaming a SQL server isn't a big deal (I think you just have to modify
one of the system tables to reflect it), but I'm not familiar with Project
Server at all. Anyone see any potential pitfalls?
Thanks,
Jeff
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
