TFS Server Move: stsadm renameserver does not work

Question

I'm following the guide How to: Restore Data for Team Foundation Server to a Different Server, 

and at the step "Reconnect the Administration and Configuration Databases" I try to run:

stsadm –o renameserver –oldservername OriginalDataTierServerName -newserver NewDataTierServerName

from the location "%PROGRAMFILES%\common files\microsoft shared\web server extensions\12\bin"

First of all, STSADM.EXE is not located in ..\12\bin\stsadm.exe, I found my program in ..\60\bin\stsadm.exe.

Trying to run stsadm with the renameserver option, it seems that the option is not supported, instead I get the error: 

"...

Command line error.

Usage:

           stsadm.exe -o <operation> [<parameters>]

           stsadm.exe -help [<operation>]

Operations:

           ...

           migrateuser

           recalculatestorageused

           removedrservice

           renameweb

           restore

           setadminport

           ...

"

Maybe I run the wrong stsadm? How can I then get the correct version that supports the renameserver option?

Can I go ahead with the migration and do this step later on?

Best regards 

Anders

---

Anders

Answer 1

Hey AndersA,

It appears you are moving a TFS 2005 instance (WSS 2.0's STSadm.exe is stored in the ..\60\bin folder), but following the TFS 2008 guide (which has instructions for configuring WSS3.0 which has stsadm.exe stored in ..\12\bin).

Reverse whatever steps you've done, ensure that the server is back to operation status, create a backup of all databases and then follow this guide: http://msdn.microsoft.com/en-us/library/ms404869(VS.80).aspx

Regards,
Maxim

Answer 2

Hi Maxim and thanks for your answer!

Our TFS is a TFS 2008 instance (upgraded from 2005), but with sharepoint services 2.0, so I now understand why the stsadm.exe does not work.

I guess I should still follow the TFS 2008 guide, but perhaps follow the sharepoint section (Restore Team Project Web Sites) in the 2005 guide?

Regards,

Anders

---

Anders

Answer 3

Hmm, That's an odd scenario. I guess you could try that, but It will probably introduce issues down the road (and I'm not sure it is even supported - some of the MS folks would shed some light on this). Any chance you could upgrade the WSS instance from 2.0 to 3.0 ?

Cheers,
Max

Answer 4

Hi again,
When I did the upgrade to 2008, upgrading from sharepoint services 2 to 3 was optional, if I remeber correctly. It might be possible to upgrade now, but I think I solved the move for my current configuration.

Instead of running the stsadm script, I used SharePoint Central Administration to change the database. Inspired by the steps in Restore Team Project Web Sites for TFS 2005 and sharepoint 2, I changed the content database, deleted the old virtual configuration database and then created a new one (described in a previous post).

It now seems to work, so I gues it is a solution after all..

Best regards,
Anders

---

Anders