I wish to remove the primary connection broker and replace it with a different connection broker VM. i have a replica connection broker also.
i am running VDM 2.1
what would be the best way to do this.
Stephen
I would use the export config utility to export the Connection broker configuration, shutdown the old connection broker, build a new connection broker, and import the configuration file. Of course you would probably have to use the same name on the new connection broker.
http://www.vmware.com/pdf/vdm_config_data_export_import.pdf
If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points
what i am looking to do is ether promote the replica connection broker to the primary or replace the primary with new system under a diffrent name.
is there a way to do with with out "backing the system up" and restoring it with the same name
Stephen
The following should work, credit goes to markbenson:
C:\WINDOWS\adam><b>dsmgmt</b>
dsmgmt.exe: <b>roles</b>
fsmo maintenance: <b>connections</b>
server connections: <b>connect to server localhost:389</b>
Binding to localhost:389 ...
Connected to localhost:389 using credentials of locally logged on user.
server connections: <b>quit</b>
fsmo maintenance: <b>seize schema master</b>
Attempting safe transfer of schema FSMO before seizure.
FSMO transferred successfully - seizure not required.
Server "localhost:389" knows about 2 roles
Schema - CN=NTDS Settings,CN=MPRYOR-BROKER1$VMwareVDMDS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={ABD5F73C-F0D0-4BA1-9C1E-D1E4DDECAFEB}
Naming Master - CN=NTDS Settings,CN=MPRYOR-BROKER1$VMwareVDMDS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={ABD5F73C-F0D0-4BA1-9C1E-D1E4DDECAFEB}
fsmo maintenance: <b>quit</b>
dsmgmt.exe: <b>quit</b>
C:\WINDOWS\adam>
what i am looking to do is ether promote the replica connection broker to the primary