<?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>mrtharp313 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>mrtharp313 Tracker</description>
    <pubDate>Sat, 25 Nov 2023 11:30:58 GMT</pubDate>
    <dc:date>2023-11-25T11:30:58Z</dc:date>
    <item>
      <title>Browser Based ThinApp (w/ specific Java) ThinApp'd with IE9 fails if IE10 installed.</title>
      <link>https://communities.vmware.com/t5/ThinApp/Browser-Based-ThinApp-w-specific-Java-ThinApp-d-with-IE9-fails/m-p/386077#M771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;I used these instructions on how to make my ThinApp:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://blogs.vmware.com/thinapp/2010/01/step-by-step-instructions-on-how-to-thinapp-newer-java-versions.html" style="font-family: Arial, sans-serif; font-size: 10pt; line-height: 1.5em;" title="http://blogs.vmware.com/thinapp/2010/01/step-by-step-instructions-on-how-to-thinapp-newer-java-versions.html"&gt;Step by Step Instructions on How to ThinApp Newer Java Versions | VMware ThinApp Blog - VMware Blogs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Everything worked fine.&amp;nbsp; This ThinApp needed an older version of Java (1.6 update 18), specific security settings in the IE9 Browser, and certificates imported to the Browser and Java.&amp;nbsp; The users have either IE8 or IE9 installed on their local Win7 x64 workstation.&amp;nbsp; Java 1.6u18 is NOT installed on the user’s computer.&amp;nbsp; Only in the ThinApp.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;I now have a company system requirement to move all users to IE10.&amp;nbsp; The ThinApp never loads once IE10 is installed.&amp;nbsp; It never starts Java and will eventually time out.&amp;nbsp; I've tried configuring the browser with some of the security settings and have installed the needed Java on the local set. Java 1.7u52 is installed which also seems to kill all Java 1.6 and below versions.&amp;nbsp; Uninstalling IE10 allows the ThinApp to work.&amp;nbsp; The ThinApp works with IE8 and IE9 installed locally (I have not tried any other versions).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Has anyone else tried this with different results?&amp;nbsp; I am not trying to ThinApp IE.&amp;nbsp; The purpose of the ThinApp was due to the overwhelming number of browser and java settings that needed to allow this app work and a user community that is spread around the world.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;I'm thinking IE10 is a pre-version killer just like Java 1.7 is.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; font-family: Arial, sans-serif;"&gt;Any assistance would be greatly appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Sep 2014 20:33:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Browser-Based-ThinApp-w-specific-Java-ThinApp-d-with-IE9-fails/m-p/386077#M771</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2014-09-22T20:33:29Z</dc:date>
    </item>
    <item>
      <title>Re: View Composerで作成するリンククローン デスクトップのMACアドレス変更方法</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Composer%E3%81%A7%E4%BD%9C%E6%88%90%E3%81%99%E3%82%8B%E3%83%AA%E3%83%B3%E3%82%AF%E3%82%AF%E3%83%AD%E3%83%BC%E3%83%B3-%E3%83%87%E3%82%B9%E3%82%AF%E3%83%88%E3%83%83%E3%83%97%E3%81%AEMAC%E3%82%A2%E3%83%89%E3%83%AC%E3%82%B9%E5%A4%89%E6%9B%B4%E6%96%B9%E6%B3%95/m-p/310054#M4065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;あなたはMACを割り当てることができますどうかを尋ねるプロフィールの代わりに、各クローンを行うためのアドレスですか？もしそうなら、私がすることができますはないと思う。リンクされたクローンは、親のクローンのMACアドレスを継承します。 VirtualCenterは、自動的にこのような状況を検出し、リンクされたクローンの電源が入っているときに新しいMACアドレスを生成します。&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;してくださいすべての誤翻訳をお許しください。&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Jul 2010 19:26:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Composer%E3%81%A7%E4%BD%9C%E6%88%90%E3%81%99%E3%82%8B%E3%83%AA%E3%83%B3%E3%82%AF%E3%82%AF%E3%83%AD%E3%83%BC%E3%83%B3-%E3%83%87%E3%82%B9%E3%82%AF%E3%83%88%E3%83%83%E3%83%97%E3%81%AEMAC%E3%82%A2%E3%83%89%E3%83%AC%E3%82%B9%E5%A4%89%E6%9B%B4%E6%96%B9%E6%B3%95/m-p/310054#M4065</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-07-15T19:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Composer DiskFault: Selected parent VM is not accessible</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667020#M42599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Composer uninstalled and did not require a reboot.  After re-installing composer, it did require a reboot which I did..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did reboot vCenter before and it didn't not resolve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just heard back from VMware, they are also now reccomending the reinstall of Composer. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jun 2010 15:29:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667020#M42599</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-06-30T15:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Composer DiskFault: Selected parent VM is not accessible</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667018#M42597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That worked for me too.  Now my clones need a tools upgrade from the update 2 install.  So hopefully that won't break anything further.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm keeping my VMware ticket open though so they can find a true fix for this or atleast understand what happened.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks to all for their input! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jun 2010 14:37:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667018#M42597</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-06-30T14:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Composer DiskFault: Selected parent VM is not accessible</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667014#M42593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wow that sounds scary.  Did you uninstall Composter first or did it reinstall/repair over top.  Did it affect any of your existing pools or replicas?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought about trying that, but the fear of the Composer DB getting jacked up and me having to rebuild everything kept me away from that option.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please share the steps you took.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jun 2010 18:03:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667014#M42593</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-06-29T18:03:41Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Composer DiskFault: Selected parent VM is not accessible</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667012#M42591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply, I guess I'm now the lucky one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There was no missing carriage return in /etc/vmware/config&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;restarting the authd service didn't solve the issue&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no mis configurations with HA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VM Tech told me to remove my ESX Hosts from the cluster one at a time and re add them.  He says the problem is the communication between vCetner and the hosts.  Did that manuever last night and no change.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just created about 1GB of log files from vCenter/composer and my primary broker and FTP'd it to VMware.  They are going throug it now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; At this point, I'm wondering if uninstalling all the update2 patches will help, but not having much luck finding out how to do that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The VM Tech did suggest that any time an update comes out, to reinstall the agent on the gold image.  That of coruse didnt resolve my issue either.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I'll update this thread once we get a resolution.  I firmly believe that I'm not the only one with this issue so the more heads on it the better. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Jun 2010 16:50:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667012#M42591</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-06-29T16:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: Desktop Composer DiskFault: Selected parent VM is not accessible</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667010#M42589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was just about to call VMware about this as well and I surmized it came from patching to update2 over the weekend.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So did you restart the authd service on each of your host?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any background how you came to that?  I don't see where that service would cause this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jun 2010 18:44:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Desktop-Composer-DiskFault-Selected-parent-VM-is-not-accessible/m-p/1667010#M42589</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-06-28T18:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: View 4 deployment - am I crazy?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-4-deployment-am-I-crazy/m-p/1174656#M28277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a great document to use.  Start on Page 2 for the Windows side.  Basically you change the shell of the HKCU to a VBS file that calls the View Client.  I use this in my environment.  Keep in mind, only do the registry hack for the USER, not the MACHINE unless you have a boot up registry editor. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.vmware.com/files/pdf/pc_to_thin_desktop.pdf"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; If you are really brave, take on the Linux make your own project. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 19:10:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-4-deployment-am-I-crazy/m-p/1174656#M28277</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-04-09T19:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: Documentation to deploy vmware view?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Documentation-to-deploy-vmware-view/m-p/828126#M18237</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mostly everything can be found here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.vmware.com/support/product-support/view/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you looking for anything specific or general info for now? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 19:03:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Documentation-to-deploy-vmware-view/m-p/828126#M18237</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-04-09T19:03:54Z</dc:date>
    </item>
    <item>
      <title>Re: View 3.1.2 Agent killed my Base VMs</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140666#M27059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You're saying you have the error trying to log into a linked clone or back on your gold image?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've never seen that issue on a linked clone, so that wouldnt make sense  unless there is still a problem with the gold image.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The last View specialist that I talked to about this, suggested the problem in View 3 lies with upgrading teh agent instead of a clean install of it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Feb 2010 18:44:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140666#M27059</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-02-12T18:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Windows XP, VDI and netmeeting</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-XP-VDI-and-netmeeting/m-p/340155#M5761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NetMetting uses the RDP protocol to allow user to connect to other users's PCs.  If you are using RDP for your users to get to their VIew Desktop, then you cannot create another RDP session to do application or screen sharing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fix is in View 4 and the PCoIP protocol.  If your users connect via PCoIP, then RDP will be available for NetMeeting to creating a hosting RDP session for others to peek in. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jan 2010 18:07:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-XP-VDI-and-netmeeting/m-p/340155#M5761</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-19T18:07:17Z</dc:date>
    </item>
    <item>
      <title>Re: Connection Broker Replica FT</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Connection-Broker-Replica-FT/m-p/779525#M15766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not seen that case before.  To Test the load balancer, I did shut down the NIC of my primary Broker to verify users were redirected to Broker #2 and it worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you launch the users desktop by connecting to the replica Brokers IP address directly?  Or from an Admin side, have you ever logged into the View Administrator on the replica Broker?  Sounds like a configuration issue of that the replica Broker is not fully functional.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 20:41:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Connection-Broker-Replica-FT/m-p/779525#M15766</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-11T20:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Broker Connection</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Broker-Connection/m-p/1672646#M43003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've asked the same question to which the answer not really.  If you're good at logs and the DBs that View uses, I'm sure you can figure it out but it could change the next time they log in. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you REALLY want to know, just boot one of the brokers and see who gets kicked out!  (Admin Power :smileygrin:)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 20:37:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Broker-Connection/m-p/1672646#M43003</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-11T20:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Servers and VMWare View</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-Servers-and-VMWare-View/m-p/2511628#M64022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ok, sorry I misunderstood.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think for now you can only serve up Windows XP or Vista desktops with Windows 7 coming due in the next update of View 4 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 20:30:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-Servers-and-VMWare-View/m-p/2511628#M64022</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-11T20:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Connection Broker Replica FT</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Connection-Broker-Replica-FT/m-p/779523#M15764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Correct.  If your Broker dies, the replica won't just pick up those connections or recieve new connections from the crashed broker's IP address. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My VM rep turned me onto the Hercules Load Balancer:  Set him up as a single IP address, and in the config files point to your various Brokers.  The load balancer will redirect the connection requests to a working Broker. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.vmware.com/appliances/directory/300" target="test_blank"&gt;http://www.vmware.com/appliances/directory/300&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 20:02:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Connection-Broker-Replica-FT/m-p/779523#M15764</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-11T20:02:28Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Servers and VMWare View</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-Servers-and-VMWare-View/m-p/2511626#M64020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VIa View Manager?  View Manager is the interface you would use to manage your pools of View Desktops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use the View Client to access a view desktop from a 2003 server (I just tested it using View 3.1.2). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can't use IE to access your View Broker from a Server OS as that version of the browser does not support the OS.  I tried that hitting a View 3.1.2 Broker and a View 4 Broker. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the answer is yes, IF you install the appropriate View Client to connect (based on the test I just made).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jan 2010 19:57:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Windows-Servers-and-VMWare-View/m-p/2511626#M64020</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-11T19:57:06Z</dc:date>
    </item>
    <item>
      <title>View 3.1.1 / 3.1.2 - Failed to set computer name</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-1-3-1-2-Failed-to-set-computer-name/m-p/331139#M5353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using View 3.1.1/.2 in a 37 person call center.  All VMs are in the same pool (starting to think the pool may be corrupt or severly messed up).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We learned in the past if the user got the error "The view desktop assigned to you is unavailable..." we would just reset it via the View Manager on the Desktop Sources tab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I have one that won't fix with the Reset Option.  However, under the Status column (normally says Ready or Connected), it has Error.  The description of the rror is: View Composer agent initialization state error (1): Failed to set computer name &lt;/P&gt;&lt;P&gt;(waited 0 seconds).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Becuase this error exists, the User cannot access her VM via the Broker.  She can however RDP using MS TSC directly to her VM with no problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't find anything helpful to fix this error (some guy had the error but was playing with Win 7).  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I either resolve the error, or get the Broker to clear the error to allow her to access the VM normally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any insight you can provide. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jan 2010 21:43:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-1-3-1-2-Failed-to-set-computer-name/m-p/331139#M5353</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-06T21:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: View 3.1.2 Agent killed my Base VMs</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140664#M27057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That was it.  The damn comma was missing.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry it's been awhile but hell actually froze over and I had a lot of other commitments.  I was playing with the View v4 agent to fix other issues and it happened again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So thanks for the comma find and Thanks Patton for the original path to take! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jan 2010 21:29:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140664#M27057</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2010-01-06T21:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: View 3.1.2 Agent killed my Base VMs</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140662#M27055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No I have not had a chance to open a ticket.  This incident has forced me to redo a lot thus taking all of my time.  I rolled everything back to 3.1.2.  Once I get "time", I was going to try the suggestions made by patten.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Sep 2009 20:09:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140662#M27055</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2009-09-11T20:09:06Z</dc:date>
    </item>
    <item>
      <title>View 3.1.2 Agent killed my Base VMs</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140658#M27051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My upgraded my base VMs with the new View Agent 3.1.2 (from 3.1.1) and let them reboot.  After reboot, I tried to log into the VM and befor the desktop was loaded, I was logged off and sent back to the ctrl-alt-delete screen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I even tried booting up in Safe Mode and the same thing happened.  Tried with a domain acocunt and the local admin account and no change.  Got real creative and did a remote registry to remove the VM tools from the start up &amp;amp; disabled the VM services and still nothing worked.  RDP and Dameware'ing to the VM didn't help either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to get my storage guys to revert the whole volume to last nights snap shot.  Luckily I'm not in production yet so I didn't lose much. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts why this happened?  The only change was the View Agent 3.1.2 upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've upgraded my 2 connection servers to 3.1.2 but have not seen an issue yet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ESX 3.5 update 4, Win XP SP3 Clients, VC 2.5, Composer 1.1.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Sep 2009 17:37:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-3-1-2-Agent-killed-my-Base-VMs/m-p/1140658#M27051</guid>
      <dc:creator>mrtharp313</dc:creator>
      <dc:date>2009-09-09T17:37:40Z</dc:date>
    </item>
  </channel>
</rss>

