SharePoint

How to rename a server (continued)... With Proclarity

John Workman — Fri, 29 Feb 2008 03:06:55 GMT

As I wrote about yesterday, I am in the process of building out virtual images with PerformancePoint. I figured out how to rename the server and have both SharePoint Services and PerformancePoint work (see yesterday's post.)

Today, while working with the server, I realized that none of my Proclarity views were working. I tried several things and finally I gave up, uninstalled the Proclarity Analytics Server and re-installed it. This worked great in getting it up and running. Only took about 10 minutes. Once that was taken care of, the Proclarity reports still didn't work. I thought I had a great idea and I set everything up as http://localhost instead of the server name. So I went through every report on my server and pointed them from the older server to localhost. This was a slow process, but once it was done everything worked great.... FROM my machine. As soon as I ran the dashboard from another box, it failed. The moral of the story is, DO NOT use localhost as the server name in Proclarity reports. I thought I was saving myself some effort if I clone the VS. I then had to go back and reset them all to the new server name. This is a pain because I did it all by hand. Soon I will document the steps to save this off as a BSWX file and modify the xml to change the urls. This is a much more efficient way to go, especially if you have to do it twice.

Once this was done, everything worked great. If I find a better way to handle Proclarity, I'll re-post. In the meantime, this works, so give it a try.

How to rename a server running SharePoint and PerformancePoint

John Workman — Thu, 28 Feb 2008 04:22:43 GMT

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)

New Year with PerformancePoint Server

John Workman — Thu, 17 Jan 2008 04:44:57 GMT

One of my new year's resolutions was to start blogging on a more regular basis, and here I am on January 16th with my first post of the year. It's amazing to look back over the past year and see how much technology has changed, at least in my little world. I have been an xml geek for the better part of this century (sounds more impressive that way than saying around 8 years). I still love xml, but begun exploring several other paths over the past 12 months (ESBs, Ajax, Silverlight, Orcas, etc.) before landing in my new technology home of PerformancePoint Server and SharePoint. The sad part about deep diving into some many areas is it doesn’t leave much time to blog about it, but now that I am settling in on PPS and SP, I’m planning to focus most of my on-line rambling on these areas. I want to start out by saying PerformancePoint Rocks! Working with this product makes you look like a rock star. People can’t believe how well it performs, how great it looks, and how powerful it is. That said, none of it would be possible without the awesome cube designs by my buddy James. It’s still a new product with a lot of room to grow. But even in its infancy, it’s still better than anything else on the market. Thanks Microsoft. You guys have hit a home run with this one. Lastly, I love all the new work Jeff has added to GeeksWithBlogs. I’ve got to study up and get my tags right. I appreciate the tutorials you've started on the blog. I'm going to look them over soon. Belated Happy New Year to all.

Test drive Sharepoint Server 2007

John Workman — Thu, 26 Jul 2007 02:39:06 GMT

There's been a lot of chatter about SharePoint lately, so I thought I would share this information. Microsoft's VHD (virtual hard drive) program is offering the chance to evaluate SharePoint Server 2007. It's a 30 day trial to get your feet wet. I have an older version of SharePoint, so I'm looking forward to trying out some of the new features. Check it out here.