How to Migrate a WDM Workgroup Server from one server to another (including WDM DB and WDM Repository) - Wyse Device Manager - Wyse Software - Dell Community

How to Migrate a WDM Workgroup Server from one server to another (including WDM DB and WDM Repository)

How to Migrate a WDM Workgroup Server from one server to another (including WDM DB and WDM Repository)

This question has suggested answer(s)

Dear all,

I am searching (but not finding) How to Migrate a WDM Workgroup Server from one server to another.

Because tha actual server is not only used for WDM, I want to move my WDM onto another fresh Windows Server; but I don't want to lost all my devices list, all my sevices settings, ...

So my question is : someone has seen a page about that case ? (I suppose I am not the only one).

I am sure that is not only a WDM DB copy/past and WDM Repository copyt/past.

I will appraciate your help.

Kind regards

All Replies
  • T.Sevin,

    Sorry to say, but WDM Workgroup does not have any migration capabilities built in and since the IP address, the server name and many other parameters are integrated in the database, the only realistic migration option is to re-install. I have not seen any documentation or instructions on migrating a Workgroup server.

    Roger Montalvo

    Here are some helpful links:

  • Moving the Wyse Device Manager Database
    On the Old SQL server
    1. Detach the Database:
    2. Stop the SQL Service
    3. Navigate to folder containing WDM Database files
    a. Default WDM 4.5.x - c:\Program Files\Wyse\WDM\Database
    b. Default Rapport 4.4.x – c:\Program Files\Rapport\Database
    4. Make copy of the Rapport4.mdf and Rapport4.ldf files
    5. Move Rapport4.mdf and Rapport4.ldf files to location accessible by new SQL Server
    On the New SQL server
    1. Attach the Database:
    2. Move a copy of the Rapport4.ldf and Rapport4.mdf files to a directory on the server where for use
    with SQL.
    a. *Default SQL location - c:\Program Files\Microsoft SQL Server\MSSQL\Data
    b. Default WDM 4.5.x - c:\Program Files\Wyse\WDM\Database
    c. Default Rapport 4.4.x – c:\Program Files\Rapport\Database
    3. Open the SQL Enterprise Manager Tool Login as ‘SA’ account (or another account with DB
    Admin rights)
    4. Navigate to the Server or Instance that you are going to install the new Database.
    5. Expand the Database node
    6. Choose the option to “Attach Database” (from right-click or icon)
    7. Browse out to the location of the newly copied Rapport4.mdf/.ldf
    8. Attach the Database name as “RapportDB”
    9. Specify “SA” as the Database Owner
    10. Select OK to attach the database.
    11. Configure the Database User:
    12. Expand the newly attached RapportDB database
    13. Select the Users node under RapportDB
    14. Create new SQL user account “Rapport” (SQL Server Authentication)
    a. Set Password to “ThinMgmt_451”
    b. Set Default Database to “RapportDB”
    c. Uncheck option to Enforce Password Policy if needed
    15. Select Ok to create the new user (confirm password if prompted)
    16. Select the newly Created Rapport user account from the Login name drop-down. (Login name and
    User name should both appear as “Rapport”
    17. Grant db_owner access to the Rapport account by selecting the checkbox
    18. Click OK to finish adding the Rapport account with db_owner access to the RapportDB database.
    19. Update Install Table:
    20. Select the Tables node from under RapportDB
    21. Scroll down to the “Install” table
    22. Right-click on “Install” and choose Open Table > Return all rows
    23. Create\Update the following entries:
    a. Module = Rapport4DB
    b. ServerName = %COMPUTERNAME% of machine including DNS suffix if enabled on
    server (i.e. WDM-server.mycompany.com)
    24. Close “Install” table
    25. Update Server Table:
    26. Open “Server” table
    27. Delete contents of “Server” table
    28. Close “Server” table
    29. Check Stored Procedure Permission
    30. Expand SQL node for Stored Procedures
    31. Locate column for ‘Owner’
    32. Sort by ‘Owner’
    33. Verify all entries for ‘Owner’ are “dbo”
    34. Reset owner on any stored procedure not set to “dbo”
    *The following sample SQL queries can be used to change owner of stored procedure:
    exec sp_changeobjectowner 'rapport.sp_AddUpdateImportClient', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_BlazerHeartBeat', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_createsubnetlevels', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_GetClientValues', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_GetJobRepositoryInfo', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_GetJobStatusInfo', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_OverrideCache', 'dbo'
    exec sp_changeobjectowner 'rapport.sp_UpdateImportClientStatus', 'dbo'
    35. DB Migration Complete