<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cisco Jabber for Windows 9.6.1  - Installer switches in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603772#M36874</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am attempting to use the _cisco-uds SRV record to auto discover services in Jabber for Windows 9.6.1 using CUCM/IM&amp;amp;P 9.1.1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Our internal DNS servers are on a internal AD domain (example.local) which is different to our SIP (sipdomain.com.au) or Email domain (company.com.au) Based on the Cisco Jabber for Windows 9.6 installation and configuration documentation, I believe I should be using the SERVICES_DOMAIN installer switch&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;EM&gt;"Use the SERVICES_DOMAIN installer switch to specify the value of the domain where DNS records reside if you wish users to bypass the email screen during the first login of a fresh installation".&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I uninstalled a previous Cisco Jabber for Windows 9.2.4 on the PC, therefore I used the "CLEAR" installer switch to remove any previous bootstrap information that might have been on the PC&lt;/P&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;&lt;EM&gt;"CLEAR=1&lt;/EM&gt;&lt;P&gt;&lt;EM&gt;&lt;EM&gt;Specifies if the client override&lt;/EM&gt;s any existing bootstrap file from previous installations. The client saves the arguments and values you set during installation to a bootstrapfile.The client then loads settings from the bootstrap file at startup"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"If you do not specify CLEAR, the client checks for existing bootstrap files during installation&lt;/EM&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;If no bootstrap file exists, the client creates a bootstrap fileduring installation&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;If a bootstrap file exists,the client does not override that bootstrap file and preserves the existing settings".&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Opened a command prompt&lt;/P&gt;&lt;P&gt;Changed the prompt to the location of the jabber msi file and performed the following command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 SERVICES_DOMAIN=example.local&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After installation and launch of Jabber for Windows, I receive "Cannot communicate with the server" on the Jabber for Windows client&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran wireshark during the launch of Jabber for Windows and I see ONLY the following DNS queries to the name server:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;_cisco-uds._tcp.sipdomain.com.au&lt;/LI&gt;&lt;LI&gt;_cisco-uds._tcp.cisco-internal.sipdomain.com.au&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The SIP domain, which I suspect is cached from the previous install is being used instead of the SERVICES domain.&lt;/P&gt;&lt;P&gt;Am I doing something wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any assistance is appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NSlookup seems to show the SRV is setup correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt; &amp;gt;nslookup&lt;BR /&gt;Default Server:&amp;nbsp; nameserver.example.local&lt;BR /&gt;Address:&amp;nbsp; 10.1.1.10&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;gt; set type=srv&lt;BR /&gt;&amp;gt; _cisco-uds._tcp.example.local&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;_cisco-uds._tcp.example.local&amp;nbsp; SRV service location:&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 1&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; weight&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 5&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 8443&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; svr hostname&amp;nbsp;&amp;nbsp; = cucm2.example.local&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;_cisco-uds._tcp.internal.local&amp;nbsp; SRV service location:&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 2&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; weight&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 20&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 8443&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; svr hostname&amp;nbsp;&amp;nbsp; = cucm3.example.local&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;_cisco-uds._tcp.internal.local&amp;nbsp; SRV service location:&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 6&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; weight&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 30&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 8443&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; svr hostname&amp;nbsp;&amp;nbsp; = cucm1.example.local&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 17 Mar 2019 22:58:20 GMT</pubDate>
    <dc:creator>hanlykent</dc:creator>
    <dc:date>2019-03-17T22:58:20Z</dc:date>
    <item>
      <title>Cisco Jabber for Windows 9.6.1  - Installer switches</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603772#M36874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am attempting to use the _cisco-uds SRV record to auto discover services in Jabber for Windows 9.6.1 using CUCM/IM&amp;amp;P 9.1.1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Our internal DNS servers are on a internal AD domain (example.local) which is different to our SIP (sipdomain.com.au) or Email domain (company.com.au) Based on the Cisco Jabber for Windows 9.6 installation and configuration documentation, I believe I should be using the SERVICES_DOMAIN installer switch&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;EM&gt;"Use the SERVICES_DOMAIN installer switch to specify the value of the domain where DNS records reside if you wish users to bypass the email screen during the first login of a fresh installation".&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I uninstalled a previous Cisco Jabber for Windows 9.2.4 on the PC, therefore I used the "CLEAR" installer switch to remove any previous bootstrap information that might have been on the PC&lt;/P&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;&lt;EM&gt;"CLEAR=1&lt;/EM&gt;&lt;P&gt;&lt;EM&gt;&lt;EM&gt;Specifies if the client override&lt;/EM&gt;s any existing bootstrap file from previous installations. The client saves the arguments and values you set during installation to a bootstrapfile.The client then loads settings from the bootstrap file at startup"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"If you do not specify CLEAR, the client checks for existing bootstrap files during installation&lt;/EM&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;If no bootstrap file exists, the client creates a bootstrap fileduring installation&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;If a bootstrap file exists,the client does not override that bootstrap file and preserves the existing settings".&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Opened a command prompt&lt;/P&gt;&lt;P&gt;Changed the prompt to the location of the jabber msi file and performed the following command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;msiexec.exe /i CiscoJabberSetup.msi CLEAR=1 SERVICES_DOMAIN=example.local&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After installation and launch of Jabber for Windows, I receive "Cannot communicate with the server" on the Jabber for Windows client&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ran wireshark during the launch of Jabber for Windows and I see ONLY the following DNS queries to the name server:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;_cisco-uds._tcp.sipdomain.com.au&lt;/LI&gt;&lt;LI&gt;_cisco-uds._tcp.cisco-internal.sipdomain.com.au&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The SIP domain, which I suspect is cached from the previous install is being used instead of the SERVICES domain.&lt;/P&gt;&lt;P&gt;Am I doing something wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any assistance is appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NSlookup seems to show the SRV is setup correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt; &amp;gt;nslookup&lt;BR /&gt;Default Server:&amp;nbsp; nameserver.example.local&lt;BR /&gt;Address:&amp;nbsp; 10.1.1.10&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;gt; set type=srv&lt;BR /&gt;&amp;gt; _cisco-uds._tcp.example.local&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;_cisco-uds._tcp.example.local&amp;nbsp; SRV service location:&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 1&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; weight&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 5&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 8443&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; svr hostname&amp;nbsp;&amp;nbsp; = cucm2.example.local&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;_cisco-uds._tcp.internal.local&amp;nbsp; SRV service location:&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 2&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; weight&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 20&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 8443&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; svr hostname&amp;nbsp;&amp;nbsp; = cucm3.example.local&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;_cisco-uds._tcp.internal.local&amp;nbsp; SRV service location:&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 6&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; weight&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 30&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 8443&lt;/P&gt;&lt;P style="padding-left: 60px;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; svr hostname&amp;nbsp;&amp;nbsp; = cucm1.example.local&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Mar 2019 22:58:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603772#M36874</guid>
      <dc:creator>hanlykent</dc:creator>
      <dc:date>2019-03-17T22:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber for Windows 9.6.1  - Installer switches</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603773#M36875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;Kent,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;This community does not provide technical &lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;support&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt; and is not staffed with technical &lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;support&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt; experts. I recommend you post this and future technical&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt; support q&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;uestions to the Cisco&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt; Support C&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;ommunity (&lt;/SPAN&gt;&lt;A href="https://supportforums.cisco.com/index.jspa" style="color: #0000cc; font-family: arial, sans-serif; font-size: 12.800000190734863px;" target="_blank"&gt;https://supportforums.cisco.com/index.jspa&lt;/A&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;) where our Cisco technica&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;l support ex&lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;perts provide assistance. Another option is to open a ticket with the Cisco Technical Assistance Center (&lt;/SPAN&gt;&lt;A href="http://www.cisco.com/go/support" style="color: #0000cc; font-family: arial, sans-serif; font-size: 12.800000190734863px;" target="_blank"&gt;www.cisco.com/go/&lt;SPAN style="color: #222222;"&gt;support&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;) &lt;/SPAN&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;to get expert debugging assistance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;We do encourage you to participate in the Cisco Collaboration Community and to also join our Cisco Collaboration User Group program!&amp;nbsp; In the community, we encourage your discussion/sharing around collaboration topics and Cisco Collaboration Solutions, including business and IT requirements, industry trends, process, culture/organization issues, how collaboration can be used to transform businesses, vendor selection, adoption, training, architecture, licensing, and product features/functionality. If you are a customer or partner, you can also join the user group program to be eligible for member-only events and influence product direction.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;We hope to hear from you again.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;Kelli Glass&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #222222; font-family: arial, sans-serif; font-size: 12.800000190734863px;"&gt;Moderator for the Cisco Collaboration Community&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Feb 2014 19:54:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603773#M36875</guid>
      <dc:creator>keglass</dc:creator>
      <dc:date>2014-02-25T19:54:12Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Jabber for Windows 9.6.1  - Installer switches</title>
      <link>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603774#M36876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have just used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 AUTHENTICATOR=CUP CUP_ADDRESS=cup-server-name SERVICES_DOMAIN=example.local&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To install the 9.6.1 client which has worked to install Jabber and when logging in it has worked using just username and password.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Feb 2014 11:23:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/cisco-jabber-for-windows-9-6-1-installer-switches/m-p/3603774#M36876</guid>
      <dc:creator>Stephen Harrison</dc:creator>
      <dc:date>2014-02-27T11:23:08Z</dc:date>
    </item>
  </channel>
</rss>

