Lync 101:1 Edge installation failure

When installing the Lync Edge server it can fail on step 2 and say:

Host name: tssrvlync003
WARNING! Host not found in topology. All roles will be uninstalled.
Disabling unused roles…

Make sure to configure a DNS suffix, since the computer is not a member of the domain it will look for itself as only the computer name and not with the FQDN.

Configure the DNS Suffix for Edge Servers

1. On the Edge Server computer, click Start, right-click Computer, and then click Properties.

2. Under Computer name, domain, and workgroup settings, click Change settings.

3. On the Computer Name tab, click Change.

4. In the Computer Name/Domain Changes dialog box, click More.

5. In the DNS Suffix and NetBIOS Computer Name dialog box, in Primary DNS suffix of this computer, type contoso.net and then click OK three times.

6. Restart the computer.

Learn OCS & Lync Server 2010, 3 days Lab–Stockholm 2010-10-19

image

Take the chance and be the first to learn Lync server 2010 at labcenter in Stockholm.

A three days lab where we deep dive in OCS 2007 R2, look at what’s new in Lync, learn how to upgrade to Lync Server 2010, integrate it all with Exchange 2010 UM, SIP trunking, PBX´s, playing with loads of cool gadgets and a lot of more…

Date: 2010-10-19

For more details, info and signup go to http://labcenter.se/Lab/2055 (in Swedish but send me a message or give me a call for details in English)

Troubleshooting 101:6 The Unified Messaging Troubleshooting Tool

There is a new tool currently in beta just out from Microsoft. The Exchange UM Troubleshooting Tool.

The Exchange 2010 UM Troubleshooting Tool is an Exchange Management Shell cmdlet that you can use to diagnose configuration errors specific to call answering scenarios and to test whether voice mail is functioning correctly in both on-premises and cross-premises UM deployments. You can use this cmdlet in deployments with Microsoft Office Communications Server 2007 R2 or Microsoft Communications Server "14" or in UM deployments with IP gateways or IP PBXs.
This cmdlet emulates calls and runs a series of diagnostic tests that help on-premises administrators to identify misconfigurations in telephony equipment, Exchange Server 2010 SP1 Unified Messaging settings, and connectivity issues between on-premises and cross-premises deployment of Exchange 2010 SP1 Unified Messaging.
When you run the cmdlet, it states the reason and possible solutions for issues that have been detected. It also outputs general audio quality metrics for diagnosing audio quality issues related to network connectivity such as jitter and average packet loss.

Download here