I'm in an running Virtual images for development and demos that are stand along PerformancePoint Servers.
They are running Windows Server 2003, SQLServer 2005, SharePoint Services 3.0, and PerformancePoint Server.
I have a development environment and a DMZ environment that can each run 5 instances of the Virtual image.
To make this setup easier, we created a "gold" image that we will use as our baseline image for each of the environments.
If you try to do this, what you will quickly find out is that all hell breaks loose when you go to rename the server. SharePoint hates it. PerformancePoint hates it. It's just a bad seen. fortunately, I'm managed to figure this out. And fortunately, I managed to document (most of it). I have to repeat this process several more times, so I will update this post when I find things that I failed to document.
How to rename a server running SharePoint Services 3.0.
Prior to renaming the server, you need to run a command line exe called stsadm.exe.
- To do this, go to start=>run=>cmd
- Navigate to c:\program files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
- Type the following command
- Stsadm.exe -o renameserver -oldservername <oldServerName> -newservername <newServerName>
Now you can go to My Computer => Properties and rename the server.
Obviously you need to reboot after this.
Now that you are up and running, open a browser and go to your SharePoint site.
Change administrator name
Click the down arrow next to Welcome …. My Settings
Modify the account name (currently has local box\name)
How to rename a server running PerformancePoint
There are multiple places that you need to change to update the server name. If you are in a position like I am with the demo boxes where everything runs local, I am setting everything to "localhost" instead of the server name. This only works well an environment like mine where these are dev boxes and everything runs stand alone on the same box. Otherwise you want to update it with the new server name. Here's a list of the places I wrote down. I'll update this if I find any that I'm missing.
- Navigate to c:\inetpub\wwwroot\wss\virtualdirectories\80
- Open web.config
- Find and replace the old server name with the new (or localhost in my case)
- Navigate to c:\program files\microsoft office performancepoint server\3.0\monitoring\ppsmonitoring_1\webservice
- Open web.config
- Find and replace the old server name with the new (or localhost in my case)
- Navigate to c:\Program Files\Microsoft Office PerformancePoint Server\3.0\Monitoring\Preview
- Open web.config
- Find and replace the old server name with the new (or localhost in my case)
- Navigate to c:\Program Files\Microsoft Office PerformancePoint Server\3.0\Tools\MonitoringConfiguration
- Open monitoringConfig.xml
- Find and replace the old server name with the new (or localhost in my case)
Like I said, with this many changes, it likely that I forgot to writedown one, but hopefully this gets you started.
The next step is to go through and update all of our datasources in PerformancePoint to point to the new server name (or localhost if appropriate)