Remove-CsManagementConnection [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]

Parameters

Configuration data for Microsoft Communications Server 2010 is stored in the Central Management Database; as you might expect, computers running Communications Server services or server roles need to be able to locate this database. When you install Microsoft Communications Server 2010, a service control point is created in Active Directory that provides location information for this database. Typically, computers rely on this service control point in order to connect to the management database. If you want to know the details behind this connection (that is, if you want to know which computer the database is running on, as well information about the SQL Server connection to that database) all you have to do is run the Get-CsManagementConnection cmdlet.

Get-CsManagementConnection is useful because it provides information about the actual connection to the management database; it does not simply retrieve information from the service control point. That’s important, because it’s possible to temporarily change your management connection, in which case the service control point is no longer valid. For example, in a case of hardware or software failure (or maintenance) you might want to temporarily use a different computer or a different instance of SQL Server as your management database. Likewise, Communications Server even lets you use the file system, and a set of XML files, as the management database. (This is usually done for testing purposes only.) If you change the management connection (which is done using the Set-CsManagementConnection cmdlet) Get-CsManagementConnection will return information about the new location. (Incidentally, computers running Communications Server use this cmdlet to retrieve connection information rather than directly retrieving that information from Active Directory.)

When you are once again ready to use the default management database, all you need to do is run the Remove-CsManagementConnection cmdlet. When you run this cmdlet, it erases the current connection information and replaces it with the connection information stored in the service control point. This means you do not have to recreate the original connection information; Remove-CsManagementConnection will essentially do that for you.

In case you are wondering, no problems will occur if call this cmdlet while using the default connection information. When the cmdlet finishes running, you will not be left without a connection; instead, you will still be using the default connection information stored in Active Directory.

Remove-CsManagementConnection deletes instances of the Microsoft.Rtc.Management.Xds.ManagementConnection object.

Add code example

	Copy Code
Remove-CsManagementConnection

The command shown in Example 1 removes the existing management connection information and replaces it with the default connection information that is stored in Active Directory.