<?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>article How to troubleshoot Location Based Printing in Horizon Documents</title>
    <link>https://communities.vmware.com/t5/Horizon-Documents/How-to-troubleshoot-Location-Based-Printing/ta-p/2796921</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H1&gt;&lt;SPAN style="font-size: 10pt;"&gt;I'll update this document as people ask more questions about it but this is the beginning of how you troubleshoot LBP and ThinPrint issues.&lt;/SPAN&gt;&lt;/H1&gt;&lt;H1&gt;Troubleshooting&lt;/H1&gt;&lt;P class="MsoNormal"&gt;Open a command prompt and go to this directory: C:\Program Files\VMWare\VMWare Tools\&lt;/P&gt;&lt;P class="MsoNormal"&gt;From within that directory run these commands:&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;STRONG&gt;tpautoconnect.exe –d all&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;This will delete all printers created by ThinPrint&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;&lt;STRONG&gt;tpautoconnect.exe –v –i vmware –a COM1 –F 30&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;This command is the same command that is run by the TP process, the only difference is that instead of running the process with the quiet flag (-q) we want to run it in verbose mode (-v).&amp;nbsp; This will help us see if there are any errors.&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Common Errors&lt;/H2&gt;&lt;P class="MsoNormal"&gt;“Can’t get Client Name” – This error most likely means that the Group Policy is not taking affect.&lt;/P&gt;&lt;P class="MsoNormal"&gt;“No suitable client protocol found.” – This error can be ignored, following this error you should see your printers map.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jan 2012 15:49:38 GMT</pubDate>
    <dc:creator>gunnarb</dc:creator>
    <dc:date>2012-01-11T15:49:38Z</dc:date>
    <item>
      <title>How to troubleshoot Location Based Printing</title>
      <link>https://communities.vmware.com/t5/Horizon-Documents/How-to-troubleshoot-Location-Based-Printing/ta-p/2796921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H1&gt;&lt;SPAN style="font-size: 10pt;"&gt;I'll update this document as people ask more questions about it but this is the beginning of how you troubleshoot LBP and ThinPrint issues.&lt;/SPAN&gt;&lt;/H1&gt;&lt;H1&gt;Troubleshooting&lt;/H1&gt;&lt;P class="MsoNormal"&gt;Open a command prompt and go to this directory: C:\Program Files\VMWare\VMWare Tools\&lt;/P&gt;&lt;P class="MsoNormal"&gt;From within that directory run these commands:&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;STRONG&gt;tpautoconnect.exe –d all&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;This will delete all printers created by ThinPrint&lt;/LI&gt;&lt;/UL&gt;&lt;P class="MsoNormal"&gt;&lt;STRONG&gt;tpautoconnect.exe –v –i vmware –a COM1 –F 30&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;This command is the same command that is run by the TP process, the only difference is that instead of running the process with the quiet flag (-q) we want to run it in verbose mode (-v).&amp;nbsp; This will help us see if there are any errors.&lt;/LI&gt;&lt;/UL&gt;&lt;H2&gt;Common Errors&lt;/H2&gt;&lt;P class="MsoNormal"&gt;“Can’t get Client Name” – This error most likely means that the Group Policy is not taking affect.&lt;/P&gt;&lt;P class="MsoNormal"&gt;“No suitable client protocol found.” – This error can be ignored, following this error you should see your printers map.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2012 15:49:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Documents/How-to-troubleshoot-Location-Based-Printing/ta-p/2796921</guid>
      <dc:creator>gunnarb</dc:creator>
      <dc:date>2012-01-11T15:49:38Z</dc:date>
    </item>
  </channel>
</rss>

