Chatta subito con l'assistenza
Chat con il supporto

Unified Communications Diagnostics 8.6.3 - Deployment Guide

Installing and upgrading Unified Communications Diagnostics Technical Information for UC Diagnostics for Exchange Technical Information for Office 365 Technical Information for UC Diagnostics for BlackBerry Technical Information for UC Diagnostics for OCS Technical Information for UC Diagnostics for Lync/Skype for Business Troubleshooting

Manually upgrading the Management Console database

If you installed the database manually, you must upgrade it manually incrementally per minor release. For example, if you are upgrading from version 7.0, you must first upgrade from 7.0 to 7.1, then from 7.1 to 7.2, and so on.

You can manually upgrade your database using the Upgrade Scripts from the Install tab of the Autorun dialog box.

To manually upgrade your database
1
Stop your Diagnostic Services.
2
Open Microsoft SQL Server Management Studio (or similar application to open SQL scripts).
3
Click File | Open | File.
4
Depending on the version from which you are upgrading, install the two or more of the following scripts in the following order:
•
UpgradeSchema1.sql
•
UpgradeSchema2.sql
•
UpgradeData.sql
•
UpgradeData2.sql
5
Select Query | Execute.

The Diagnostic Services restart once the upgrade of the Diagnostic Services is complete.

Configuring existing UC Diagnostics to work with SQL Always On

If you recently configured SQL Server Always On and have an existing UC Diagnostics deployment, you must make some changes in SQL and in UC Diagnostics to support the new configuration.

•
In SQL server, you must create an availability group listener that connects to the primary replica. Suppose that you have created a listener called UCDAGListener.
•
For the UC Diagnostics Management Console, you must change the SQL server name used for the SQL server connection to use the availability group listener name by editing the registry.
•
For Web Reports, you must edit the WebReports.udl file used to connect to Web Reports to the SQL server and modify the SQL server name to the availability group listener name.
To edit the registry for the Management Console
1
Stop the Diagnostic Services.
2
From the Registry Editor, go to HKEY_LOCAL_MACHINE | SOFTWARE | Quest | Spotlight Management Framework | Diagnostic Services.
3
Double-click DatabaseConnectionString.
4
Modify the Data Source to specify the availability group listener name that you created in SQL, such as tcp: UCDAGListener.
5
Modify the SqlServer to use the availability group listener name that you created in SQL.
6
Click OK.
7
Restart the Diagnostic Services.
To modify the UDL (Universal Data Link) file for Web Reports
1
Locate and open the WebReports.udl file ( …\Quest\UC Diagnostics\Web Reports).
The file is located where you have Web Reports installed. Once open, the Data Link Properties dialog box is displayed.
2
Click the Connection tab.
3
Modify the SQL server name to be the availability group listener name such as tcp: UCDAGListener.
4
Enter the account and password that must be used for SQL authentication.
* 
NOTE: SQL authentication must be used for Web Reports if you have implemented SQL Always On.
5
Select the Allow saving password check box and click OK.

Backing up and restoring UC Diagnostics

Use the following sections to back up and to restore the database and information settings for the Management Console and for the Diagnostic Console.

Backing up and restoring the settings and database for the Management Console
To back up the settings and database for the Management Console
1
Backup your SQL database using Microsoft’s best practices.
2
To back up your topology and MMC customizations, back up the UC Diagnostics.msc file.
The .msc file is located at %userprofile%\Application Data\Microsoft\MMC.

You can also export your topology layout to a file to backup your topology settings.

To restore the settings and database for the Management Console
1
Restore the SQL database.
2
Install UC Diagnostics.
3
At the SQL Server dialog box during installation, click Yes to use the existing database.
4
Add the UC Diagnostics.msc file back to %userprofile%\Application Data\Microsoft\MMC.
If you have exported your topology layout, re-import it.
Backing up and restoring the Diagnostic Console information
To back up the connection, configuration, and template information
•
Save each connection as a template file.
To restore the connection, configuration, and template information
1
Install UC Diagnostics.
2
Create a connection using the backed up template files.

Moving UC Diagnostics to a another server

To move UC Diagnostics to another server
1
Follow the steps for Backing up and restoring the settings and database for the Management Console .
2
Copy the MMC settings to the new server.
All the Management Console settings are stored in the .msc file. If you are using the default shortcut, that file is cached to %userprofile%\Application Data\Microsoft\MMC.
3
Follow the steps for Backing up and restoring the Diagnostic Console information .
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione