ADMS Workgroup 2014 Server Rename Impersonation User Login dialog

[MarkMazour]

We are in the process of upgrading our ADMS 2012 to ADMS 2014 and in the process are moving to new hardware. This is going to require a Server rename after the upgrade process. I have been documenting and testing all steps for the process that will take place over the weekend on the new server. Everything is going well except for the server rename test.

 I renamed the ADMS site using the Command Line Server Console –OsiteRename followed by renaming the Server from EngSrvr1 to EngSrvr1x and restarting. When trying to open ADMS I get a Impersonation User Login dialog prompting for a User Name: and Password: not sure which user and pw this asking for. When using the SQL Server user ‘sa’ and ‘AutodeskVault@26200’ the fields turn read with the warning ‘The username and/or password is invalid. Please provide valid user credentials.’ When using local admin username and password an error of ‘NonmemberSite[200](EngSrvr1x)’

Am I following the correct procedure? What username and password is it asking for?

Edit:

 Here is the logfile entry

11/19/2013 3:59:43 PM -OSiteRename -SNO"EngSrvr1" -SNN"EngSrvr1x" -DBU[username] -DBP[password] -L"C:\Program Files\Autodesk\rename.txt"
11/19/2013 3:59:46 PM Additional sites cannot be enabled in this product edition. If this computer has been recently renamed, please update the site via the server console command line options.

[paul.gunn]

Hi Mark,

The impersonated user is the one the web services run under. This is a windows account - by default the user name is AutodeskVault . So this is indeed different  from the credentials you are entering (sql user admin account).

That said if you are moving to new hardware, I suggest considering a backup / restore procedure to do the move. i.e. do a backup on 2012, install fresh 2014 on the new machine, and restore the backup on the new machine. In this scenario you don't need to worry about machine rename and other factors at all - this is really the simplest way of getting the job done.

Paul

[herrerh]

Paul is right, if you are moving hardware you should do a backup/restore instead of worryign about doing a rename.

In addition to having to update Vault with the new server name if you were to go that route, you would need to update SQL as well with the new computername.

-Hywell

[MarkMazour]

Paul, Herrerh,

That is exactly the process I am using. Tonight after the vault backup.bat runs, on the old server EngServer (ADMS2012), I have a second bat that will copy that vault backup folder set and thousands of other engineering related folders and files to the new server, EngServerA(ADMS2014). On the new server I have a restore.bat that will restore the backup scheduled to fire after the copy.

But the old server, EngServer, will be renamed EngServerOld and the new server EngServerA will be renamed EngServer. There 10+ applications and 100+ desktops that reference that servername EngServer. Thus the need for the rename.

[paul.gunn]

Hi,

Did you retry the process with the correct impersonated user credentials (as described above)?

Paul

[MarkMazour]

What is the password for the default user name AutodeskVault?

[MarkMazour]

Got the password and still have the "NonmemberSite[200](EngSrvr1x)" issue/error.

[paul.gunn]

Hi Mark,

I suggest reversing the order of your actions: rename the computer first and then run the 'siterename' command line. I think there may be issues in 2014 when running the operations in the other order.

Note that you will probably also need to make sure the local SQL server gets correctly renamed. There is a command line -Orenameworkgroup that can be used to accomplish this. It takes the same parameters as the site rename opearation.

Hope this solves your problem,

Paul

[GunnarN]

Can you rename the servers before you restore the backup on the new server instead of doing it afterwards?

[MarkMazour · Accepted solution]

FWIW here are the steps that resulted in a successful server renaming.

1. Rename the computer.

2. Restart the computer.

3. Modify the web.config file - change the userName in the identity tag

(

<identity impersonate="true"userName="EngSrvr1\AutodeskVault"password="secretPassword" />

<identity impersonate="true"userName="EngSrvr\AutodeskVault"password="secretPassword" />

 )

4. Rename the ADMS Server via the Command Line Server Console ( Connectivity.ADMSConsole.exe" -OSiteRename -SNOEngSrvr1 -SNNEngSrvr -DBUsa -DBPotherSecretPassword -L"C:\Program Files\Autodesk\log.txt" )

5. Rename SQL Server. Note: this step requirers Sql Server Management Studio(

sp_dropserver 'EngSrvr1\AUTODESKVAULT'

GO

sp_addserver 'EngSrvr\AUTODESKVAULT','local'

GO

 )

6. Open ADMS

7. Rename Hostname in license file

8. Open Vault Workgroup Client to confirm functionality of FlexLm license manager and license file.

[ndra]

Thank you Mark, I encountered this problem on a similar scenario, but was unable to reproduce the problem. I'll try your solution and post back the results. Nikos

[Anonymous]

Thanks a lot MarkMazour, it works !

[autokoto]

I'm running to this same issue in our vaultserver basic 2016 I've tried the steps but still no luck.

[autokoto]

Hello All, I've tried Mark's solution but still getting the attached error saying nonmember site [200]