<?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>mittim12 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>mittim12 Tracker</description>
    <pubDate>Sat, 25 Nov 2023 08:43:51 GMT</pubDate>
    <dc:date>2023-11-25T08:43:51Z</dc:date>
    <item>
      <title>Re: Machines are deleted after provisioning</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Machines-are-deleted-after-provisioning/m-p/1375634#M81596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume you are using quickprep when creating the pool.&amp;nbsp;&amp;nbsp; Does the account you specified when setting that up have the correct permissions so that can join to the domain and move objects into the specified OU? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Feb 2017 19:52:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Machines-are-deleted-after-provisioning/m-p/1375634#M81596</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2017-02-01T19:52:07Z</dc:date>
    </item>
    <item>
      <title>Re: Machines are deleted after provisioning</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Machines-are-deleted-after-provisioning/m-p/1375632#M81594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is logged in View administrator?&amp;nbsp;&amp;nbsp;&amp;nbsp; What version are the host running the environment? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Feb 2017 13:32:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Machines-are-deleted-after-provisioning/m-p/1375632#M81594</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2017-02-01T13:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: VMware horizon 7 desktop pool machine reconfigure</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-horizon-7-desktop-pool-machine-reconfigure/m-p/1412838#M37950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have anything enabled in that pool that may not be enabled in any of the other pools.&amp;nbsp;&amp;nbsp; Something like storage accelerator?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Nov 2016 19:14:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-horizon-7-desktop-pool-machine-reconfigure/m-p/1412838#M37950</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-11-29T19:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: View desktops will not allow a "space" as the first character of a user password</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-desktops-will-not-allow-a-quot-space-quot-as-the-first/m-p/2736522#M74386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just tested this through HTML access on version 6.2.1 build-3284346 and it worked fine. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Nov 2016 19:05:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-desktops-will-not-allow-a-quot-space-quot-as-the-first/m-p/2736522#M74386</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-11-29T19:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: Client Drive Redirection also for PCoIP? And how can we disable/manage that?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Client-Drive-Redirection-also-for-PCoIP-And-how-can-we-disable/m-p/472724#M11298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm fairly certain you can use a GPO&amp;nbsp; to disable CDR.&amp;nbsp;&amp;nbsp;&amp;nbsp; Do a search on client redirection on the documentation and it should give you the location of the GPO. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/support/pubs/view_pubs.html" title="https://www.vmware.com/support/pubs/view_pubs.html"&gt;Documentation for VMware Horizon 7&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2016 13:54:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Client-Drive-Redirection-also-for-PCoIP-And-how-can-we-disable/m-p/472724#M11298</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-11-17T13:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: AGENT_PENDING_EXPIRED - VDI Disconnect - Urgent Help!!!</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/AGENT-PENDING-EXPIRED-VDI-Disconnect-Urgent-Help/m-p/940513#M79128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to the event viewer you should check the PCOIP and other agent logs.&amp;nbsp; Here is a KB that goes over collecting View logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/kb/1017939" title="https://kb.vmware.com/kb/1017939"&gt;Collecting VMware Horizon View logs and diagnostic information (1017939) | VMware KB&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Nov 2016 19:12:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/AGENT-PENDING-EXPIRED-VDI-Disconnect-Urgent-Help/m-p/940513#M79128</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-11-02T19:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: Please help understand Horizon Products</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Please-help-understand-Horizon-Products/m-p/921673#M78931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The product provides a means of deploying, managing, and providing connectivity for virtual desktops.&amp;nbsp;&amp;nbsp; As far as the components, I think they have already been listed and explained in a previous post on this thread.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; There are many more post about this subject if you want to search through the forums. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2016 12:57:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Please-help-understand-Horizon-Products/m-p/921673#M78931</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-09-08T12:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: operation of  snapshot and replica file</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/operation-of-snapshot-and-replica-file/m-p/1380825#M80111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1:&amp;nbsp; The replica is a read only copy of the snapshot that the linked clones will be based on.&amp;nbsp;&amp;nbsp; If it fails to create then you will not be able to provision any linked clones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2:&amp;nbsp; The snapshot is what the replica is based on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3:&amp;nbsp;&amp;nbsp; The clones use the replica as their primary source of information and then write the changes back into their disk.&amp;nbsp;&amp;nbsp;&amp;nbsp; So they may start out as 20 GB but the longer they are around the more changes will be made and the more they will grow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4:&amp;nbsp; They will just continue to grow.&amp;nbsp;&amp;nbsp; It's always best practice to have some kind of refresh schedule.&amp;nbsp; When you refresh a linked clone it resets it back to the replica.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2016 12:51:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/operation-of-snapshot-and-replica-file/m-p/1380825#M80111</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-09-08T12:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: operation of  snapshot and replica file</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/operation-of-snapshot-and-replica-file/m-p/1380823#M80109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The snapshot is what the replica is based on and then the linked clones are built from the replica.&amp;nbsp;&amp;nbsp; You could in theory store 100GB of data on each clone but that would end up negating the space saving features of composer and linked clones.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2016 04:17:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/operation-of-snapshot-and-replica-file/m-p/1380823#M80109</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-09-08T04:17:10Z</dc:date>
    </item>
    <item>
      <title>Re: View 4.6 view client certificate</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-4-6-view-client-certificate/m-p/1773129#M48136</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you verified that the 4.6 client is support for use on Windows 10? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jul 2016 13:01:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-4-6-view-client-certificate/m-p/1773129#M48136</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-07-26T13:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: Lowering the number of spare machines on an existing pool</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Lowering-the-number-of-spare-machines-on-an-existing-pool/m-p/1773497#M48153</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If I'm not mistaken the spare number only controls how many machines are built and ready at all times.&amp;nbsp;&amp;nbsp;&amp;nbsp; The power policy would be the one to control the status of available vs provisioned.&amp;nbsp;&amp;nbsp; If you are using "ensure machines are powered on" then every machine in the pool will be up and running vs "power off" which breaks machines online and offline based on demand. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jul 2016 14:48:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Lowering-the-number-of-spare-machines-on-an-existing-pool/m-p/1773497#M48153</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-07-20T14:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: Dekstopo pool vCenter linked clone size after vm deletion</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Dekstopo-pool-vCenter-linked-clone-size-after-vm-deletion/m-p/495042#M11597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As the other poster mentioned the linked clones are based off a replica machine that is made from your parent snapshot.&amp;nbsp; They start off very small at the datastore level and will grow over time.&amp;nbsp;&amp;nbsp;&amp;nbsp; Even though the Windows OS may say it's a 60GB drive its still, in most scenarios, only taking up a small portion of that on the vSphere datastore.&amp;nbsp;&amp;nbsp; This would explain why you didn't see a 120 GB size increase upon removal of these machiens. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 May 2016 13:04:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Dekstopo-pool-vCenter-linked-clone-size-after-vm-deletion/m-p/495042#M11597</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-05-25T13:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: Move non-persistent Linked clones from one host to another.</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Move-non-persistent-Linked-clones-from-one-host-to-another/m-p/2738217#M74415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In that case you would need to edit the desktop pool storage options, select the local storage of the new host and de select the local storage of the old host.&amp;nbsp;&amp;nbsp; You would then have to perform a recompose on the machines which should rebuild them on the new storage located on the new host.&amp;nbsp;&amp;nbsp;&amp;nbsp; I would try the recompose on a single VM first to make sure the process goes smoothly.&amp;nbsp;&amp;nbsp;&amp;nbsp; When you do a recompose the VM is set back to default of the parent VM so hopefully your using roaming profiles or one of the persistent disk modes to cover that. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 May 2016 13:29:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Move-non-persistent-Linked-clones-from-one-host-to-another/m-p/2738217#M74415</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-05-16T13:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Move non-persistent Linked clones from one host to another.</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Move-non-persistent-Linked-clones-from-one-host-to-another/m-p/2738214#M74412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If they are on shared storage you could simply vmotion them to the other host provided that host can also see the storage.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 May 2016 13:19:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Move-non-persistent-Linked-clones-from-one-host-to-another/m-p/2738214#M74412</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-05-16T13:19:36Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade 6.1 to 6.2.2 or 7?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Upgrade-6-1-to-6-2-2-or-7/m-p/2726885#M91730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;2:&amp;nbsp;&amp;nbsp; You can build out new servers as version 6, add them as replica partners to the view pod,&amp;nbsp; remove the old servers from the environment, and then upgrade the new servers to version 7.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; That would allow you to move to new servers while retaining all of your View information and settings. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Apr 2016 18:23:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Upgrade-6-1-to-6-2-2-or-7/m-p/2726885#M91730</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-04-18T18:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: Open console on a VM already connected with Horizon client</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Open-console-on-a-VM-already-connected-with-Horizon-client/m-p/953685#M23916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try the registry key in this article.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.thatsmyview.net/2011/04/29/using-the-vcenter-console-for-mirroring-a-pcoip-session/" title="http://www.thatsmyview.net/2011/04/29/using-the-vcenter-console-for-mirroring-a-pcoip-session/"&gt;Using the vCenter console for mirroring a PCoIP session at That's my View&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Apr 2016 15:04:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Open-console-on-a-VM-already-connected-with-Horizon-client/m-p/953685#M23916</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-04-11T15:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: system disposable disk full</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/system-disposable-disk-full/m-p/2720346#M73879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What if you go into options and view hidden files, system files, etc?&amp;nbsp;&amp;nbsp; The page file and other things get redirected to the disposable disk they could easily be using up the space. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2016 19:28:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/system-disposable-disk-full/m-p/2720346#M73879</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-04-08T19:28:27Z</dc:date>
    </item>
    <item>
      <title>Re: How many replicas should be present?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/How-many-replicas-should-be-present/m-p/2721021#M73916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correct.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If that were not the case you would have to create a new replica every time you made a graphics change to the pool.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 14:51:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/How-many-replicas-should-be-present/m-p/2721021#M73916</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-04-07T14:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: How many replicas should be present?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/How-many-replicas-should-be-present/m-p/2721019#M73914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you using a dedicated replica datastore in the pool settings.&amp;nbsp; If so you would have, I believe, 2 replicas with one for each unique snapshot.&amp;nbsp;&amp;nbsp; If not, I think you would have 8 which would be 1 for each unique snapshot on each datastore.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 14:36:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/How-many-replicas-should-be-present/m-p/2721019#M73914</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-04-07T14:36:29Z</dc:date>
    </item>
    <item>
      <title>Re: The display protocol for this desktop is currently not available BLAST</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/The-display-protocol-for-this-desktop-is-currently-not-available/m-p/2719596#M73843</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is anything load balanced?&amp;nbsp;&amp;nbsp; Just curious because you said after a few tries they can connect.&amp;nbsp; I wanted to make sure there wasn't multiple brokers that could be possibly handling the traffic. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 13:41:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/The-display-protocol-for-this-desktop-is-currently-not-available/m-p/2719596#M73843</guid>
      <dc:creator>mittim12</dc:creator>
      <dc:date>2016-04-07T13:41:51Z</dc:date>
    </item>
  </channel>
</rss>

