Skype for Business, Lync and Exchange Web Services EWS and different DNS Domains Exchange crawling e. This Blog is dedicated to UC VoIP deployment utilising Lync, OCS and Exchange with some interop tech i. Asterisk, Trixbox and Skype. Categorized lists of links to downloads and updates for Lync 2010, Lync 2013, and OCS 2007 R2 products, including server and client software, tools, devicebased. Polycom Cx700 Software Update' title='Polycom Cx700 Software Update' />We have three product lines besides many other devices that looks like a phone and work like a phone. Those are Aastra 6721ip and Aastra 6725ip Polycom CX700 and. Polycom UC Software 5. Download Polycom UC Software 5. Software Downloads. Polycom has now made the VVX series phones as Lync Server Compatible. The latest firmware version 5. Supports more Lync features such as PIN Authentication and. This article shows how to setup basic centralized provisioning of Polycom SIP Phones by utilizing an FTP server. Also covered as an example is how to use this server. Skype for Business, Lync and Exchange Web Services EWS and different DNS Domains Exchange crawling e. Hi all,This is an updated version 2. This blog entry is valid for Lync 2. Lync 2. 01. 3 and Skype for Business Server. Generally, Ill write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2. Server. Once this written, I post the link here. Lync is crawling Exchange Web Services EWS. Generally it is necessary to understand how DNS must be implemented Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync Exchange deployments an issue, where the Lync configuration show up with empty EWS Internal URLEWS External URLand. EWS Information EWS not deployed. Pages2/4793/c8916296-5066-e411-93eb-0025907e4a45/page_files/img_01.png' alt='Polycom Cx700 Software Update' title='Polycom Cx700 Software Update' />Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e. Horizontal Foundation Cracks Above Grade more. Presence Information based on your Outlook Calendar. The feature depending on EWS are Unified Contact Store. High Resolution Photos. Meeting tab. Contact Information. Presence based on Calendar Information. Conversation History. Missed Conversations. Missed Calls. Voice Mail Playback. Exchange Setup DNS You need PER SMTP Domain 3 DNS Record, internally Split DNS and on the external DNS Server, 2x for Autodiscover and 1x for EWSautodiscover. CNAME exchangeserverCASautodiscover. SRV 0 0 4. 43 exchangeserverCASewsurl. A exchangeserver CASif you use internally another domain, e. Active Directory domain, sure you can have internally another EWS published, but Autodiscover use by Lync identifies still the xml file via the users SIPDOMAIN. So split DNS is recommended at least for AutodiscoverNOTE As its never really proper discussed Autodiscover will never use the internal. URL and external. URL. in Exchange 2. Exchange 2. 01. 3 they are even documented in Tech. Net, but they simply dont exist anymore. Youll receive an error if you specify the URLs. The correct discovery process is like OUTLOOK SCP lookup only if client is domain joinedHTTPS root domain query. HTTPS Autodiscover domain query. HTTP redirect method. SRV record query. Local XML filecached URL in the Outlook profile new for Outlook 2. The correct discovery process is like LYNC internal, Autodiscover is identified by DNS entry. Autodiscover is identified by DNS entry. Additionally you need to check Autodiscovery Virtual Directory Setup the internal and external URL, including HTTPS and Basic Authentication. Set Autodiscover. Virtual. Directory Identity autodiscover default Web site External. URL https ews. Internal. URL https ews. Basic. Authentication true. Note The Autodiscover. Virtual. Directoy URL are supposed for Microsofts optional use only. Therefore it is not necessary and not Best Practise defining them If you set the URLs, it will NOT HAVE AN IMPACT. Meaning, if they are defined or not, it will not change the Autodiscover behavior, since they are NOT USED within Exchange. What is IMPORTANT, is the Authentication, you must set it the Basic Authentication, so the SSL configuration will take part. It would be enough is you configure simply Set Autodiscover. Virtual. Directory. Identity autodiscover default Web site. Basic. Authentication true. But If you define them, you have a reminder what is configured, more like a comment. Web Services Virtual Directory Setup the internal and external URL, including HTTPSand Basic Authentication. Set Web. Services. Virtual. Directory Identity SERVER0. EWSdefault Web site External. Url https ews. EWSexchange. Internal. Url https ews. EWSexchange. asmx Basic. Authentication true. The EWS Services are responsible for the Lync integration, especially for Calendar Information and The Conversation History. Therefore this is the most essential configuration. Publishing EWS service via Reverse Proxy Autodiscover and EWS service do NOT support FBA form based authentication. The client need the XML file straight and without authentication webpage, than access the EWS URL need to be authenticated at the Exchange CAS server. Authentication must be NTLM over HTTPS. So do not use http, the password would be submitted in clear text. The NTLM authentication is hard coded in Lync Client. Lync Setup First the good new, there is nothing which we have to consider for Lync Server. The Feature is a Client Integration Feature, therefor we have nothing to configure. There is only one exception, this is the CWA integration for Exchange OWA. During setup and integration of CWA features, truly the EWS configuration must meet the requirements identically with the Lync Client Configuration. One last thing necessary to consider and plan proper are the Certificates Since all communication is based on HTTPS and TLS, which includes the encryption. Certificates are used for trans coding. What is now complicated is the DNS Setup, SMTPSIP Domains and the SAN Names in this involved certificates. Lync in this case is straight forward, you simply have to include all SIP Domains in your SAN. But however Exchange now requires another possible way make sure you have configured the CAS Server Certificates including all SAN Names for all SMTP and SIP domainsmake us of IIS based redirection web pages. If you chose this configuration, it is possible minimizing the required SAN configuration. But still in both configurations you need to consider your DNS Zone setup. If possible and I personally prefer DNS Splitting, for internal and external resolving. This makes your deployment more supportable. Note if you consult a customer and you are propose DNS Splitting, make sure you fully validate other Web base services, which depends on DNS names tooHow Lync discover the EWS service via autodiscover As illustrated, it is essential for best user experiences having the Lync SIP Domain identically with the default Exchange EMail Domain. Lync is using the smtp domain for the autodiscovery process. This is especially important if you are not inside your corporate network LAN. Lync is never able to use SCP, only DNS A and SRV Records. DNS resolution occurs first have look into the Autodiscover. DNS provided thereusing autodiscover. Access now the Autodiscover. Exchange environment in the following order. One more remarks If you didnt deploy EWS correctly from the very beginning, you might encounter other Client issues. Therefore it is recommended you delete the following file userprofileApp. DataLocalMicrosoftOutlookautodiscover. This file is ONLY created by Outlook, Lync do not write this file it only uses the web services. Troubleshooting You should try and access Autodiscover via web browse using a link provided above. You must be asked for your credential it requires you are having a Exchange Mailbox. Exchange will than show you this XML lt UTF 8 lt Autodiscover xmlnshttp schemas. Response lt Error Id2. Time1. 2 5. 5 5. Error. Code 6. Error. Code lt Message Invalid Requestlt Message lt Debug. Data lt Error lt Response lt Autodiscover If you see this message, Autodiscover is reachable and ok. Next check access to https EWSURLewsexchange. EWSURLewsServices. Verify also on the client, where Outlook is installed HKCUSoftwareMicrosoftx. OutlookAutodiscoverRedirect. Configure Polycom VVX series phones to work with Lync Server 2. Polycom has now made the VVX series phones as Lync Server Compatible. The latest firmware version 5. Supports more Lync features such as PIN Authentication and update the device using Lync Server device update platform like the rest of the CX series. Polycom has introduced the new BTo. E Better Together over Ethernet application to support VVX series to integrate tightly with the Lync Client. The user experience of this is same as the CX Series tether via the USB cable but in this case, it use the Ethernet connection. This article highlights the standard deployment process of a VVX Series phone and sign in to the device using Lync Enterprise Voice enabled account. Im using a VVX 5. Then the device first plugged in to the Po. E connection, It comes up with the generic Profile. Get the devices IP Address from the display menu. Unlike the CX series, VVX can be configured with both manual IP configuration and DHCP. Connect to the devices main web page using IE. The standard Admin password for VVX Series is 4. Login as an Admin. In Home page, itll show you what is the current Firmware configured and information such as the IP and the MAC ID. If the current configured Firmware is not 5. Utilities and select Software Upgrades. To upgrade the Firmware, verify that the device has access to the Internet and Check for UpdatesOnce the Firmware is sorted, navigate in to Simple Setup. Set the correct time Zone and select the Base Profile as Lync. The device will restart upon confirmation. Once the device comes up, navigate to the Features using the Menu and notice that two new options appeared. This would be Microsoft Lync and BTOEIn Microsoft Lync option, there will be two sign in methods. User Credentials and PIN Authentication. As usual, to use the PIN Authentication, the DHCP Options must be configured in DHCP server Option 4. You can use any EV enabled account with the Extension and the PIN to sign in to the device like the CX series. In User Credentials, you can use the Lync Sign In address and domain login credentials to sign in to the device. The on screen keyboard is. Now to play around with the BTo. E application. Download and install the Polycom BTo. E application from http support. Polycom. ServicesupportussupporteulaucsUCagreementBTo. E. html and install. Connect the PCs Ethernet cable to the devices PC port and run the BTo. E application. Verify that the BTo. E is enabled on devices using the menu. By default its enabled. If thats the case, then itll show in the task bar as BTo. E Activated Just like when you Tether a CX series using USB, a log in menu will come up to sign in to the device. Enter sign in credentials and sign in to the device. The BTo. E status will now change from Activated to Paired. At this point, you can make calls from Lync Client and the device will dial the call out. Notice that the green icon on top right side of the display indicating the paring status. The sign in process is successfully completed and no alerts coming up. Still the Exchange integration need to be configured. Unlike the CX Series, the VVX series does not automatically detect the EWS URL to connect to Exchange Server. Go back to the admin page of the device and select Settings, In Settings, drop down the Exchange Application configuration. Exchange Server URL with the EWS URL. This should be https autodiscover. Enable the Exchange Calendar and apply the configuration change. The device will restart upon confirmation. A basic troubleshooting can be done on the device using Diagnostics Logs. Its not much but can get an idea of what might be going on in there. Overall, the VVX Series is way better and more feature rich compared to CX Series. But it has its own downfalls. One would be manual configuration of EWS which i feel will not be feasible in mass deployments.