I have a running sharepoint 2007 instance set up the way we need it, and have made a virtual clone ond placed it on a VMWare Virtual Server. I have chenged the server name to be sharepointtest, and issued a new IP address. How do I make the new sharepoint environment point to this server rather than the old server for everything - just use the new local server name, and get central admin to come up? The services can start, and the database starts (embedded SQL), but trying to start central admin by default points to teh old physical server, not the new server name. If I try to go to that server by IE browsing, it gives a 404 error - web page cannot be found. I am new to sharepoint, and the fellow who set up this environment is no longer available. I am just trying to set up a test environmant, so we can made tests and evals, without disturbing production, and can do snapshots of the complete working environment as needed. Thanks Dennis_A

Hi Suppose the link for the Central Admin was http://oldservername:8080. What happens when you try "http://ip of the new server:8080"? Also if you go to the IIS manager in the new server, can you see the IIS website for central admin. What happens when you right click on it and select browse? Thanks, Soumya

Hi Suppose the link for the Central Admin was http://oldservername:8080. What happens when you try "http://ip of the new server:8080"? Also if you go to the IIS manager in the new server, can you see the IIS website for central admin. What happens when you right click on it and select browse? Thanks, Soumya

I was on the server itself, and cannot open any of the web pages, either by using the IP adress, or right-clicking the web site in IIS manager. I verified the services, and they are running. Sharepoint Services : Administration Search Timer Tracing and World Wide Web Publishing Service Thanks for your suggestion. Dennis

Take the site collection backup of your production site. then enumerate all the solutions deployed on your production site by either stsadm or central administration. Download all the packages posted at your production site. List down all the activated features on your production site as well. You can utilize an extended stsadm command built by Gary Lapointe (http://blog.falchionconsulting.com) Create the web application on your new VM and restore the sitecollection backup of your production site. Then deploy the solutions previously located at production and then activate the features as per the list of activated features you have noted down on the previous set of instructions. This is just to get you started, your production site may have multiple site collections, SSP, resources files, etc..

Hi, According to your description, I suggest you should use PowerShell to set up a test environment. Please refer to this link: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=199 Have a try. In addition, check this thread about setting up environment with new SharePoint install: http://www.eggheadcafe.com/software/aspnet/35248855/set-up-test-environment-with-new-sharepoint-install.aspx I hope it can help you a little. Best regards, David Hu

Hi, According to your description, I suggest you should use PowerShell to set up a test environment. Please refer to this link: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=199 Have a try. In addition, check this thread about setting up environment with new SharePoint install: http://www.eggheadcafe.com/software/aspnet/35248855/set-up-test-environment-with-new-sharepoint-install.aspx I hope it can help you a little. Best regards, David Hu