Questions and Answers
Q: Can I use a Public CA for internal Lync servers?
Although an internal enterprise certification authority (CA) is recommended for internal servers, you can also use a public CA. For a list of public CAs that provide certificates that comply with specific requirements for unified communications (UC) certificates and have partnered with Microsoft to ensure they work with the Lync Server Certificate Wizard, see article Microsoft Knowledge Base 929395, "Unified Communications Certificate Partners for Exchange Server and for Communications Server," at http://go.microsoft.com/fwlink/p/?linkId=202834.
Q: Are wildcard entries on certificates supported for Lync Server?
Wildcard entry as the subject name (also referred to as the common name or CN) are not supported for any role. The following server roles are supported when using wildcard entries in the SAN:
Reverse proxy - Wildcard SAN entry is supported for simple URL publishing certificate.
Director - Wildcard SAN entry is supported for simple URLs in Director web components.
Front End Server (SE) and Front End pool (EE) - Wildcard SAN entry is supported for simple URLs in Front End web components. Exchange Unified Messaging (UM) - The server does not use SAN entries when deployed as a stand-alone server.
Microsoft Exchange Server Client Access server - Wildcard entries in the SAN are supported for internal and external clients.
Exchange Unified Messaging (UM) and Microsoft Exchange Server Client Access server on same server - Wildcard SAN entries is supported.
Q: Can I integrate Lync Server 2010 with Exchange 2010 SP1 OWA (en-US)?
Lync Server 2010 can be integrated with Exchange 2010 SP1, so that Exchange Outlook Web App can also act as a Lync web client. Once integrated, users will automatically log into Lync when they log into OWA. http://technet.microsoft.com/en-us/library/gg420962(v=exchg.141).aspx http://social.technet.microsoft.com/wiki/contents/articles/5305.how-to-integrate-lync-server-2010-with-exchange-2010-sp1-owa-en-us.aspx http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/
Q: Can I use one public certificate for two edge servers and Reverse Proxy servers?
Yes it works but usually not recommended to share certificates between servers unless they are in a load balanced configuration.
Q: Is Office Communicator 2007 R2 compatible with Lync Server 2013?
Yes, but conferencing features are not. Office Communicator 2007 R2 is suitable for presence and IM interoperability, but users should use Lync Web App 2013 to join Lync Server 2013 meetings. The presence and IM features in Office Communicator 2007 R2 are compatible with Lync Server 2013, but conferencing features are not. During migration from Office Communications Server 2007 R2, Office Communicator 2007 R2 is suitable for presence and IM interoperability, but users should use Lync Web App 2013 to join Lync Server 2013 meetings.
Q: What format should I use to store phone numbers in Active Directory?
You should save every number in E.164 format. E.164 is an internationally recognized standard for phone numbers. The standard is:
+<CountryCode><City/AreaCode><LocalNumber>;ext=<ext>
Q. When would a Edge Server be needed?
- Your organization’s own users can use Lync Server functionality, if they are working from home or are out on the road.
- Your users can invite outside users to participate in meetings.
- If you have a partner, vendor or customer organization that also uses Lync Server, you can form a "federated relationship" with that organization. Your Lync Server deployment would then recognize users from that federated organization, leading to better collaboration.
- Your users can exchange instant messages with users of public IM services, including any or all of the following: Windows Live, AOL, Yahoo!, and Google Talk. A separate license might be required for public IM connectivity with these services.
Q. We would like to assign a particular conference ID to a user, is it possible?
It is not possible to assign custom conference ID to Lync users. Conference ID’s are randomly generated and cannot be manually assigned.
Q: I have noticed that Office communication server 2007 created groups named RTC and when we installed Lync 2010 and updated AD it created CS named groups. If we don’t have OCS2007 any longer do we still need the RTC groups?
The RTC groups still are needed in the Lync Server, so you should keep all of the RTC groups as they are used to grant permissions even in Lync. However, from a day to day admin perspective you should be assigning users to the CS groups. So for example, for a Lync admin account you should assign it to the CSAdministrator group and not the RTCUniversalServerAdmins group. In previous versions of Office Communications Server, administrative rights were defined very broadly, and users with administrative access for a server running Lync Server could make many types of changes. With RBAC, access and authorization is based more precisely on a user’s Lync Server role. This enables greater use of the security practice of "least privilege," granting administrators and users only the rights that are necessary for their job.
http://technet.microsoft.com/en-us/library/gg425917.aspx
Q. Using the move users command how many hours would it take to move 50000 from OCS2007R2 to Lync?
The general rule I use is that it takes about one hour to move approximately 4000 users, give or take couple hundred. So 50000 would take roughly 12hrs.
Q. Does Lync supports non- DID #'s?
Lync Server 2010/2013 supports E.164 numbers and non-Direct Inward Dialing (DID) numbers. Non-DID numbers can be represented in the format <E.164>;ext=<extension> or as a string of digits, with the requirement that the private extension is unique across the enterprise. For example, a private number of 1001 can be represented as +1425550100;ext=1001, or as 1001. When represented as 1001, the expectation is that this private number is unique across the enterprise.
Q. Why can’t I use NAT with Hardware Load Balancer HLB)?
On the Edge server external
interfaces, Microsoft supports one NAT and one NAT only. A HLB counts as a NAT
device. Therefore you must use public IP address so you don’t violate the one
NAT rule.
Q. Does Lync uses SIP diversion header?
Lync uses 'SIP diversion header ' for forwarding calls to UM mailbox extensions in Lync -UM integration setup where diversion header will have UM voice mail extension as destination.
