SBM powered by Microsoft Lync Administrator's Guide 2010-11

2-30
Complete the Setup Wizard
Initiate the Installation Process
SBM Not Added to the Topology. For the replication to complete success-
fully, the data center engineers must have:
 Added your branch to the topology:
• Defined the branch site within a site with an existing Lync server pool
• Defined a survivable branch server for the branch site, specifying the
SBM’s FQDN for the survivable branch server and PSTN gateway
 Published and enabled the new topology
In addition, the domain administrator must have specified the SBM’s SPN as
its FQDN, or the topology does not publish successfully.
If you see an error message such as “export failed” or “specified part does not
exist,” verify that the data center engineers have completed these tasks. If not,
wait until they have before proceeding with the installation.
Also verify that the SBM’s name matches the FQDN that the data center
engineers have specified for the SBM in the branch site of the Lync Server
topology. You can check the hostname by accessing the system properties in
the Remote Desktop. If the name is wrong, you must follow a precise proce-
dure for changing it. See “Change an HP SBM’s Name” on page 3-33 of
Chapter 3: “Manage and Monitor the HP SBM Locally.”
When you are ready, you can click Restart Automated Replication Process.
Insufficient Privileges. This step might have failed because you do not
have permission to complete all of the necessary tasks.
Note Typically, you should be a member of the RTCUniversalSBATechnicians
group. (By default, when the SBM joins the domain, this group and the Domain
Admins group are added to the SBM local Administrators.)
If you need to log in as a different user or as a user with refreshed rights, you
must close the browser, reopen it, and then navigate back to the SBM’s FQDN.
If you launched the browser from the Remote Desktop, you must log out of
the desktop and log back in with the correct domain user credentials.
When you are ready, you can click Restart Automated Replication Process.
Failed Network Connection. If you see a “network related or instance-
specific” error, the SBM’s link to the server at the data center that stores the
topology might have failed. Test this theory by pinging that server from a
command prompt via RDP or from the SBM OS CLI. If the link has failed, you
can either: