How do I uninstall OpenDJ

introduction

This document describes the procedures by which a Cisco TelePresence Management Suite (TMS) database application can be migrated from one server to another by moving the location of the Structured Query Language (SQL) database.

Note: There are no methods for migrating local user accounts from one Microsoft Windows server to another. If you use local Microsoft Windows accounts to access the TMS server, you will need to manually create these accounts on the new server.

requirements

conditions

Cisco recommends that you have knowledge of the following areas:

  • Microsoft SQL Server
  • Cisco TMS

Components used

The information in this document is based on the following software versions:

  • TMS versions 12, 13 and 14
  • TMSPE version 1.0
  • Microsoft SQL Server versions 2005 and 2008

The information in this document was produced by the devices in a specific laboratory environment. All devices used in this document started with an empty (standard) configuration. With your network up and running, make sure you understand the potential implications of a command.

TMS migration

This section describes the processes used to migrate the TMS.

preparation

Note: If you are using older TMS agents, make sure to disable replication on all devices first.

Shut down all TMS Microsoft Windows services:

  • TMS Agent Service
  • TMS database scanner service
  • TMS live service
  • TMS PLCM directory service
  • TMS Scheduler Service
  • TMS Server Diagnostics Service
  • TMS Simple Network Management Protocol (SNMP) service

If you are using TMS Provisioning Extension (tmspe), shut it down as well.

Note: If you are using legacy TMS agents, the FQDN (Fully Qualified Domain Name) configured at the bottom of the TMS Agent Settings page of the TMS (usually the FQDN of the TMS as configured in Microsoft Windows) must be can be resolved to the IP address of the TMS if the Video Communication Server (VCS) carries out a search in the FQDN. Reverse lookups must also be in place.

Back up the SQL database

There are two methods used to back up and restore the SQL database. The CLI is available on all systems that have SQL installed. However, SQL Management Studio can be downloaded from Microsoft and used if necessary.

Using the SQL CLI

If the SQL database is currently on the same server as the TMS server application and you plan to move the database to a new server, either the new Microsoft Windows server hosting TMS or a separate SQL instance, then the database needs to be backed up and restored to the new location.

The commands described in this section are entered at the command prompt on the current TMS server hosting the SQL Express instance with the Tmsng database. These commands are written to allow SQL Server access via the currently logged on Microsoft Windows user. To use SQL credentials, replace -E by -U -P and replace the username and password with the SQL credentials and system administrator rights.

TMS database

Enter the following command to back up the tmsng SQL database using the CLI:

sqlcmd -S (local) \ SQLTMS -E -Q "BACKUP DATABASE tmsng TO DISK = '

If this command is used, replace <path> through the location where you want to save the backup. This location must have enough space for the backup and must be accessible to the SQL service.

TMSPE database(when using TMSPE)

If you are using tmspe, enter this command to back up the tmspe SQL database from the CLI:

sqlcmd -S (local) \ SQLTMS -E -Q "BACKUP DATABASE tmspe TO DISK = '

Copy files to the new server

Copy the backup file (s) to the new location on the SQL server. This can either be a separate SQL server or the new TMS server location running SQL Server Express.

Note: The location where you will copy the backup file requires the SQL service user to have full access.

SQL Management Studio

This section describes the backup process when using SQL Management Studio.

TMS database

On the current SQL server, open SQL Management Studio and navigate to the Tmsng database. Right click the database and navigate to Tasks> Back Up ..:

 

On the backup prompt page, make sure the settings match those shown. A default destination may be specified. If you want to use this location to save the backup, click OKand the backup is sent to the specified location. If no destination location is specified, click Add, click on ... and enter the filename tmsng a. Then click for all three screens OK, and the database backup should take place.

 

Note: If you get a Denied Access message, make sure you are writing to a location that the SQL service user can write to. Usually this includes the backup folder in Microsoft SQL (MSSQL).

TMSPE database (when using TMSPE)

If you are using tmspe follow the steps above but right click on the database tmspe instead of tmsng-Database. Name this fuse tmspe.bak.

Copy files to the new server

Copy the backup file (s) to the new location on the SQL server. This can either be a separate SQL server or the new TMS server location running SQL Server Express.

Note: The location where you will copy the backup file requires the SQL service user to have full access.

TMS agents

If you are using older TMS agents, open Windows Explorer on the old TMS server and navigate to % OPENDS_HOME%> db> userRoot.

Here's an example:

C:> program files> TANDBERG> TMS> deployment> OpenDS-2.0> db> userRoot

Copy the file * .jdb to a temporary location on the new TMS server.

Migration from TMS versions 14 or higher

If the TMS is running version 14 or higher, there is an encryption key that is used to securely store credentials in the tmsng database. This key must be copied from the old server to the new server. To capture this from the old server, open the TMS tools, and choose Encryption key. Copy the key.

Note: This will be used later when installing TMS.

Save the local files

The TMS can contain custom files for end users. These places should be checked. If there are custom files in these locations, be sure to save these files and copy them to the new TMS server location after the reinstallation.

These directories are the standard paths:

  • C:> program files> TANDBERG> TMS> wwwTMS> data> CiscoSettings

  • C:> Programs> TANDBERG> TMS> wwwTMS> Data> CompanyLogo

  • C:> program files> TANDBERG> TMS> wwwTMS> data> ExternalSourceFiles

  • C:> Programs> TANDBERG> TMS> wwwTMS> Data> Image

  • C:> program files> TANDBERG> TMS> wwwTMS> data> language

  • C:> program files> TANDBERG> TMS> wwwTMS> data> logo

  • C:> Programs> TANDBERG> TMS> wwwTMS> Data> Map

  • C:> program files> TANDBERG> TMS> wwwTMS> data> MGCSettings

  • C:> Programs> TANDBERG> TMS> wwwTMS> Data> Software

  • C:> Programs> TANDBERG> TMS> wwwTMS> Data> Sound

  • C:> Programs> TANDBERG> TMS> wwwTMS> Public> Data> SOFTWARE

Restoring the SQL database

There are two methods used to back up and restore the SQL database. The CLI is available on all systems that have SQL installed. However, SQL Management Studio can be downloaded from Microsoft and used if necessary.

SQL CLI usage

This section describes how to use the SQL CLI.

TMS database

Note: An up-to-date copy of SQL Server (version 2005 or 2008) or SQL Server Express (version 2005 or 2008) is required to continue.

If you want to use SQL Express on the new TMS server to house the database, install the TMS and then uninstall it. This will allow you to create the instance of SQL Express needed to restore the database. You do not need to include the release key and option keys during installation, as these data will be overwritten when the database is restored from backup. If you are using a separate SQL server, you do not need to install and uninstall the TMS.

On the server running SQL Server or SQL Server Express, enter the commands in this section to restore the SQL database. These commands are written to allow SQL Server access via the currently logged on Microsoft Windows user.

To use the SQL credentials, replace -E by -U -P and replace the username and password with the SQL credentials and system administrator rights. You also need to make the following replacements:

  • Replace the Server name by the host name of the SQL server.

  • Replace the Instance names by the SQL service instance name.

  • Replace the <pathofbackup> -Variable through the storage location of the backup file (.bak).

  • Replace the <pathofdbfiles> -Variable by the location where the database MDF file (tmsng_data.mdf) and the location where the database LDF file is to be saved (tmsng_log.ldf).

If you need to restore the database to SQL Version 2005, enter the following command:

sqlcmd -S -E -Q "DECLARE @Table TABLE (LogicalName
varchar (128), [PhysicalName] varchar (128), [Type] varchar, [FileGroupName]
varchar (128), [Size] varchar (128), [MaxSize] varchar (128), [FileId] varchar
(128), [CreateLSN] varchar (128), [DropLSN] varchar (128), [UniqueId] varchar
(128), [ReadOnlyLSN] varchar (128), [ReadWriteLSN] varchar (128),
[BackupSizeInBytes] varchar (128), [SourceBlockSize] varchar (128), [FileGroupId]
varchar (128), [LogGroupGUID] varchar (128), [DifferentialBaseLSN] varchar (128),
[DifferentialBaseGUID] varchar (128), [IsReadOnly] varchar (128), [IsPresent]
varchar (128)); DECLARE @Path varchar (1000); SET @ Path = ' \ tmsng.bak'
; DECLARE @LogicalNameData varchar (256), @ LogicalNameLog varchar (256); INSERT
INTO @table EXEC ('RESTORE FILELISTONLY FROM DISK =' '' + @ Path + '' ''); SET
@ LogicalNameData = (SELECT LogicalName FROM @Table WHERE Type = 'D'); SET
@ LogicalNameLog = (SELECT LogicalName FROM @Table WHERE Type = 'L'); RESTORE
DATABASE tmsng FROM DISK = ' \ tmsng.bak' WITH REPLACE, MOVE
@LogicalNameData TO ' \ tmsng_data.mdf', MOVE @LogicalNameLog
TO ' \ tmsng_log.ldf' "

If you need to restore the database to SQL version 2008, enter the following command:

sqlcmd -S -E -Q "DECLARE @Table TABLE (LogicalName
varchar (128), [PhysicalName] varchar (128), [Type] varchar, [FileGroupName]
varchar (128), [Size] varchar (128), [MaxSize] varchar (128), [FileId] varchar
(128), [CreateLSN] varchar (128), [DropLSN] varchar (128), [UniqueId] varchar
(128), [ReadOnlyLSN] varchar (128), [ReadWriteLSN] varchar (128),
[BackupSizeInBytes] varchar (128), [SourceBlockSize] varchar (128), [FileGroupId]
varchar (128), [LogGroupGUID] varchar (128), [DifferentialBaseLSN] varchar (128),
[DifferentialBaseGUID] varchar (128), [IsReadOnly] varchar (128), [IsPresent]
varchar (128), [TDEThumbprint] varchar (128)); DECLARE @Path varchar (1000); SET
@ Path = ' \ tmsng.bak'; DECLARE @LogicalNameData varchar (256),
@LogicalNameLog varchar (256); INSERT INTO @table EXEC ('RESTORE FILELISTONLY
FROM DISK = '' '+ @ Path +' '' '); SET @ LogicalNameData = (SELECT LogicalName FROM
@Table WHERE Type = 'D'); SET @ LogicalNameLog = (SELECT LogicalName FROM @Table
WHERE Type = 'L'); RESTORE DATABASE tmsng FROM DISK = ' \ tmsng.bak'
WITH REPLACE, MOVE @LogicalNameData TO ' \ tmsng_data.mdf',
MOVE @LogicalNameLog TO ' \ tmsng_log.ldf' "

TMSPE database (when using TMSPE)

Enter the following command in the CLI to restore the TM SQL database to SQL version 2005:

sqlcmd -S -E -Q "DECLARE @Table TABLE (LogicalName
varchar (128), [PhysicalName] varchar (128), [Type] varchar, [FileGroupName]
varchar (128), [Size] varchar (128), [MaxSize] varchar (128), [FileId] varchar
(128), [CreateLSN] varchar (128), [DropLSN] varchar (128), [UniqueId] varchar
(128), [ReadOnlyLSN] varchar (128), [ReadWriteLSN] varchar (128),
[BackupSizeInBytes] varchar (128), [SourceBlockSize] varchar (128), [FileGroupId]
varchar (128), [LogGroupGUID] varchar (128), [DifferentialBaseLSN] varchar (128),
[DifferentialBaseGUID] varchar (128), [IsReadOnly] varchar (128), [IsPresent]
varchar (128)); DECLARE @Path varchar (1000); SET @ Path = ' \ tmspe.bak'
; DECLARE @LogicalNameData varchar (256), @ LogicalNameLog varchar (256); INSERT
INTO @table EXEC ('RESTORE FILELISTONLY FROM DISK =' '' + @ Path + '' ''); SET
@ LogicalNameData = (SELECT LogicalName FROM @Table WHERE Type = 'D'); SET
@ LogicalNameLog = (SELECT LogicalName FROM @Table WHERE Type = 'L'); RESTORE
DATABASE tmspe FROM DISK = ' \ tmspe.bak' WITH REPLACE, MOVE
@LogicalNameData TO ' \ tmspe_data.mdf', MOVE @LogicalNameLog
TO ' \ tmspe_log.ldf' "

Enter the following command in the CLI to restore the TM SQL database to SQL version 2008:

sqlcmd -S -E -Q "DECLARE @Table TABLE (LogicalName
varchar (128), [PhysicalName] varchar (128), [Type] varchar, [FileGroupName]
varchar (128), [Size] varchar (128), [MaxSize] varchar (128), [FileId] varchar
(128), [CreateLSN] varchar (128), [DropLSN] varchar (128), [UniqueId] varchar
(128), [ReadOnlyLSN] varchar (128), [ReadWriteLSN] varchar (128),
[BackupSizeInBytes] varchar (128), [SourceBlockSize] varchar (128),
[FileGroupId] varchar (128), [LogGroupGUID] varchar (128), [DifferentialBaseLSN]
varchar (128), [DifferentialBaseGUID] varchar (128), [IsReadOnly] varchar (128),
[IsPresent] varchar (128), [TDEThumbprint] varchar (128)); DECLARE @Path varchar
(1000); SET @ Path = ' \ tmspe.bak'; DECLARE @LogicalNameData varchar
(256), @ LogicalNameLog varchar (256); INSERT INTO @table EXEC ('RESTORE
FILELISTONLY FROM DISK = '' '+ @ Path +' '' '); SET @ LogicalNameData = (SELECT
LogicalName FROM @Table WHERE Type = 'D'); SET @ LogicalNameLog = (SELECT
LogicalName FROM @Table WHERE Type = 'L'); RESTORE DATABASE tmspe FROM DISK =
' \ tmspe.bak' WITH REPLACE, MOVE @LogicalNameData TO
' \ tmspe_data.mdf', MOVE @LogicalNameLog TO
' \ tmspe_log.ldf' "

Using SQL Management Studio

This section describes how to use SQL Management Studio.

TMS database

Open SQL Management Studio on the new SQL server. Right click on Databases, and choose Restore database:

 

Click in the field Recovery source on From device: and specify the location of the file tmsng.bak a. Choose In the Select backup sets to restore field, select the following backup sets: Field, check the box tmsng-Full Database Backup. In the To database: choose tmsng and click on OK. This will restore the tmsng database.

TMSPE database (when using TMSPE)

The process to restore the tmspe database is the same as that used to restore the tmsng database. However, you choose that tmspe-Backup file instead of the tmsngBackup file and select the tmspeDatabase instead of the tmsng database.

Note: On the new database server, make sure that the SQL Browser service is running. If it does not run, the TM installation will fail.

Post-database recovery actions

After restoring the database, do the following:

  1. Reinstall the TMS on the new server to host the TMS server application.

  2. Choose custom installation to point to the new SQL Server location.

Migrations from TMS versions 14 and higher

During installation, enter the encryption key that will be copied from the original TMS server.

Note: Under certain circumstances this field may be grayed out. If so, after the installation is complete, load the TMS Tools and enter the encryption string there. Then restart the TMS server.

TMSPE usage

If you are using TMSPE, reinstall TMSPE on the TMS server and specify the new database location.

Use of TMS agents

If you are using older TMS agents, do the following:

  1. Stop the TMS Agents Microsoft Windows service. This will also stop the OpenDS Windows service.

  2. Navigate to % OPENDS_HOME%> db> userRoot. Here's an example: C: > Programs> TANDBERG> TMS> Provisioning> OpenDS-2.0> db> userRoot.

  3. Delete any files that are in the folder.

  4. Move the .jdb- Files copied from the old TMS server to the folder.

  5. Start the TMSAgentService Microsoft Windows Service.

Attention: Do not currently access the TMS portal.

Using the TMS Tools utility

If the TMS server hostname changes and you are using local user accounts (user accounts that exist on the server hosting the TMS server application, not Active Directory (AD) accounts), you will need to run the TMS Tools utility to get the To change data in the database to ensure that you can log in:

  • Navigate to TMS Tools> Utilities> Change User Domain.

  • Enter the old domain name: <alter TMS-Server-Hostname>.

  • Enter the new domain name: <neuer TMS-Server-Hostname>.

warning: Otherwise access to the TMS portal can be interrupted.

Note: During this migration process, the local user accounts will not be moved to the new server. If you are using local Microsoft Windows accounts, you will need to manually recreate them on the new Microsoft Windows server to which the TMS will be migrated.

After installation

To access the TMS portal from a user account with site administrator rights in TMS, do the following:

  1. Navigate to Administration> Configuration> General Settings.

  2. Make sure the value for the Software FTP directory for reinstalling the server is correct. This value may be incorrect if you installed the TMS with a different drive letter on the new server (compared to the old server) or if you switched from a 32-bit version to a 64-bit version of the Microsoft Windows Server operating system (BS) have switched.

  3. Navigate to Administration> Configuration> Network Settings.

  4. Review the values ​​for the following fields:

    • General network settings>URL for downloading software packages

    • Advanced network settings for systems in the internal LAN> IPv4 address of the TMS server

    • Advanced network settings for systems in the internal LAN> IPv6 address of the TMS server

    • Advanced network settings for systems in the internal LAN> TMS server - fully qualified host name

    • Advanced network settings for systems in the public Internet / behind a firewall> TMS server address (fully qualified host name or IPv4 address)

Use of TMS agents

If you are using older TMS agents, do the following:

  1. Navigate to Administration> Configuration> TMS Agent Settings.

  2. Enter in the section Global> Settings a password for the LDAP configuration password and the LDAP replication password. This ensures that the passwords are synchronized with the data storage location.

  3. Make sure the value for TMS Agent Backup> Backup Directory is correct for the new server installation. This value may be incorrect if you installed the TMS with a different drive letter on the new server (compared to the old server) or if you switched from a 32-bit version to a 64-bit version of the Microsoft Windows Server operating system have switched.

Delete old server

At the bottom of the page in the area TMS server you can monitor several TMS servers. If so, follow the steps below to delete the old server:

  1. Click the computer name and select Delete off.

  2. For the new system, check that the network address is correct (FQDN and IP address). If the network address is incorrect, do the following:

    1. click on To edit (right).

    2. Enter the correct FQDN address for the new TMS server and click To update.

    3. At the top of the page, type in the section Global> Settings a new LDAP configuration set password and LDAP replication password a.

    4. Click at the bottom of the page to save.

Run the TMS Agent Diagnostics.

Navigate to Administration> TMS Agent Diagnostics and run the TMS Agent Diagnostics for the local TMS Agent.

Note: If the TMS Agent diagnostics fail, refer to the manual for more information TMSAgent to Troubleshooting.

Enable TMS agent replication to the VCS

When activating TMS agent replication for the VCS, please note the following important information:

  • If you are using tmspe you will need to reinstall it and provide the current location of the tmspe database.

  • If you are using Analytics Extensions and they were installed on the old TMS server, you will need to reinstall them on the new server.

  • If you are using a TMS extension for Microsoft Exchange, use its configuration tool to specify the new location of the TMS server.

  • If replication fails due to Domain Name System (DNS) lookups, make sure that the FQDN configured at the bottom of the TMSAgent settings page of the TMS (usually the FQDN of the TMS as configured in Microsoft Windows) , can be resolved to the IP address of the TMS when the VCS searches for this FQDN. Reverse lookups must also be in place.

Related information