<?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>vmrulz Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>vmrulz Tracker</description>
    <pubDate>Sat, 25 Nov 2023 08:12:15 GMT</pubDate>
    <dc:date>2023-11-25T08:12:15Z</dc:date>
    <item>
      <title>Re: Moving spanned volumes on massive windows 2012r2 to win 2022 server</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2990885#M46267</link>
      <description>&lt;P&gt;Just finished a test of a system with 43 disks and the same scsi mappings and windows vols.&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Shutdown both servers (did not do anything to the source server in terms of offlining disks etc)&lt;/LI&gt;&lt;LI&gt;Remove all disks (except C: and E:) from source in vCenter&lt;/LI&gt;&lt;LI&gt;Assigned disks to new server in the same sequence including SCSI mappings (this was VERY tedious with 43 disks in the UI.. If I did this more I'd powercli it).&lt;/LI&gt;&lt;LI&gt;Powered on new server&lt;/LI&gt;&lt;LI&gt;Onlined all disks&lt;/LI&gt;&lt;LI&gt;Imported foriegn disks (just right click on 1st disk and choose import foriegn disks and this will import all disks and volumes at once)&lt;/LI&gt;&lt;LI&gt;The import checks the health of the disk/vol which is nice before you click OK.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Far more simple than I expected considering this is MS tech! Hopefully production will be a similar experience.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 21:39:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2990885#M46267</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-10-12T21:39:17Z</dc:date>
    </item>
    <item>
      <title>Re: Moving spanned volumes on massive windows 2012r2 to win 2022 server</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2990323#M46248</link>
      <description>&lt;P&gt;This is a mapping of drives I did using one of LUCD's awesome scripts. Can you say ugly?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE width="845"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="90"&gt;SCSIAddress&lt;/TD&gt;&lt;TD width="96"&gt;vmDiskName&lt;/TD&gt;&lt;TD width="103"&gt;vmDiskSizeGB&lt;/TD&gt;&lt;TD width="137"&gt;windowsDiskIndex&lt;/TD&gt;&lt;TD width="267"&gt;vmDiskUuid&lt;/TD&gt;&lt;TD width="152"&gt;windowsDeviceID&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(0:0)&lt;/TD&gt;&lt;TD&gt;Hard disk 1&lt;/TD&gt;&lt;TD&gt;400&lt;/TD&gt;&lt;TD&gt;0&lt;/TD&gt;&lt;TD&gt;6000C2964aea82ff18071b0ac5546b69&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE0&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:6)&lt;/TD&gt;&lt;TD&gt;Hard disk 10&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;34&lt;/TD&gt;&lt;TD&gt;6000C291c1fbb1050f5f1a5eb77a29bb&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE34&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:8)&lt;/TD&gt;&lt;TD&gt;Hard disk 11&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;35&lt;/TD&gt;&lt;TD&gt;6000C29a4cc79d81d470b9886d532181&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE35&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:9)&lt;/TD&gt;&lt;TD&gt;Hard disk 12&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;36&lt;/TD&gt;&lt;TD&gt;6000C2944091ecc95846f269dd2c2457&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE36&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:10)&lt;/TD&gt;&lt;TD&gt;Hard disk 13&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;37&lt;/TD&gt;&lt;TD&gt;6000C2974fe79aeaa067374a12becce7&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE37&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:11)&lt;/TD&gt;&lt;TD&gt;Hard disk 14&lt;/TD&gt;&lt;TD&gt;1024&lt;/TD&gt;&lt;TD&gt;38&lt;/TD&gt;&lt;TD&gt;6000C2910aa709466f6a7d52dd58d70b&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE38&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:12)&lt;/TD&gt;&lt;TD&gt;Hard disk 15&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;39&lt;/TD&gt;&lt;TD&gt;6000C29cd160e93133232d77afe7d976&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE39&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:13)&lt;/TD&gt;&lt;TD&gt;Hard disk 16&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;40&lt;/TD&gt;&lt;TD&gt;6000C29118b306ce025a1918afb4a09e&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE40&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:14)&lt;/TD&gt;&lt;TD&gt;Hard disk 17&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;41&lt;/TD&gt;&lt;TD&gt;6000C29c76d8f657b3ee683f68b51917&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE41&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:15)&lt;/TD&gt;&lt;TD&gt;Hard disk 18&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;42&lt;/TD&gt;&lt;TD&gt;6000C296365dc6ab772871fe344fb9ee&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE42&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:0)&lt;/TD&gt;&lt;TD&gt;Hard disk 19&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;TD&gt;6000C2989e2bb50c40ae2b8ab878810a&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE5&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(0:1)&lt;/TD&gt;&lt;TD&gt;Hard disk 2&lt;/TD&gt;&lt;TD&gt;300&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;6000C293293fd0e586e68b0f35536c74&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:1)&lt;/TD&gt;&lt;TD&gt;Hard disk 20&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;6&lt;/TD&gt;&lt;TD&gt;6000C2984bab312857344c509b1f8fdf&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE6&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:2)&lt;/TD&gt;&lt;TD&gt;Hard disk 21&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;TD&gt;6000C294cf0f4818eddd1c66382041b2&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE7&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:3)&lt;/TD&gt;&lt;TD&gt;Hard disk 22&lt;/TD&gt;&lt;TD&gt;1024&lt;/TD&gt;&lt;TD&gt;8&lt;/TD&gt;&lt;TD&gt;6000C29e7bdc23feef4da1dc94bb8f1f&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE8&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:4)&lt;/TD&gt;&lt;TD&gt;Hard disk 23&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;6000C29a4564825f711efae63988f9ce&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE9&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:5)&lt;/TD&gt;&lt;TD&gt;Hard disk 24&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;10&lt;/TD&gt;&lt;TD&gt;6000C29fbdf6defe5791d63a0b39057d&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE10&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:6)&lt;/TD&gt;&lt;TD&gt;Hard disk 25&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;11&lt;/TD&gt;&lt;TD&gt;6000C29af0a6567f94c1c4d7917d878f&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE11&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:8)&lt;/TD&gt;&lt;TD&gt;Hard disk 26&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;12&lt;/TD&gt;&lt;TD&gt;6000C292ca838d4217c74d6af041d3fb&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE12&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:9)&lt;/TD&gt;&lt;TD&gt;Hard disk 27&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;13&lt;/TD&gt;&lt;TD&gt;6000C292ccc24f69b6693b73dfffefb4&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE13&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:10)&lt;/TD&gt;&lt;TD&gt;Hard disk 28&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;14&lt;/TD&gt;&lt;TD&gt;6000C2975a827a686368f6d8771e7671&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE14&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:11)&lt;/TD&gt;&lt;TD&gt;Hard disk 29&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;15&lt;/TD&gt;&lt;TD&gt;6000C299e217f71a9d68b48a26db0af1&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE15&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(0:2)&lt;/TD&gt;&lt;TD&gt;Hard disk 3&lt;/TD&gt;&lt;TD&gt;1024&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;6000C2929a220407bc91a79387b2c57c&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:12)&lt;/TD&gt;&lt;TD&gt;Hard disk 30&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;16&lt;/TD&gt;&lt;TD&gt;6000C298b22482ebd8bd5e24a697d656&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE16&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:13)&lt;/TD&gt;&lt;TD&gt;Hard disk 31&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;17&lt;/TD&gt;&lt;TD&gt;6000C296b0de59919091cad7d7c359ae&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE17&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:14)&lt;/TD&gt;&lt;TD&gt;Hard disk 32&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;18&lt;/TD&gt;&lt;TD&gt;6000C29ce04eb8cb8776910c214e5bf6&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE18&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(2:15)&lt;/TD&gt;&lt;TD&gt;Hard disk 33&lt;/TD&gt;&lt;TD&gt;10240&lt;/TD&gt;&lt;TD&gt;19&lt;/TD&gt;&lt;TD&gt;6000C29a1d39897192c6cc7cdadd06f7&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE19&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:0)&lt;/TD&gt;&lt;TD&gt;Hard disk 34&lt;/TD&gt;&lt;TD&gt;5120&lt;/TD&gt;&lt;TD&gt;20&lt;/TD&gt;&lt;TD&gt;6000C299e7de093a7e85df47260c99bb&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE20&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:1)&lt;/TD&gt;&lt;TD&gt;Hard disk 35&lt;/TD&gt;&lt;TD&gt;5120&lt;/TD&gt;&lt;TD&gt;21&lt;/TD&gt;&lt;TD&gt;6000C2973101ecfa9534c284f7b76bd8&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE21&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:2)&lt;/TD&gt;&lt;TD&gt;Hard disk 36&lt;/TD&gt;&lt;TD&gt;5120&lt;/TD&gt;&lt;TD&gt;22&lt;/TD&gt;&lt;TD&gt;6000C29570436e88985dcaf17ba5ccfd&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE22&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:3)&lt;/TD&gt;&lt;TD&gt;Hard disk 37&lt;/TD&gt;&lt;TD&gt;5120&lt;/TD&gt;&lt;TD&gt;23&lt;/TD&gt;&lt;TD&gt;6000C297145173bab2aa8a780bd99603&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE23&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:4)&lt;/TD&gt;&lt;TD&gt;Hard disk 38&lt;/TD&gt;&lt;TD&gt;12288&lt;/TD&gt;&lt;TD&gt;24&lt;/TD&gt;&lt;TD&gt;6000C29e1b80166fb45bf488dbc7f65f&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE24&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(0:3)&lt;/TD&gt;&lt;TD&gt;Hard disk 39&lt;/TD&gt;&lt;TD&gt;63488&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;6000C29c8b3618353ccbf330491e62ca&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:0)&lt;/TD&gt;&lt;TD&gt;Hard disk 4&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;28&lt;/TD&gt;&lt;TD&gt;6000C294be38f3f932ca3eeed6143ac2&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE28&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(0:4)&lt;/TD&gt;&lt;TD&gt;Hard disk 40&lt;/TD&gt;&lt;TD&gt;63488&lt;/TD&gt;&lt;TD&gt;4&lt;/TD&gt;&lt;TD&gt;6000C29554a7052eabbfb591a6a25d78&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:5)&lt;/TD&gt;&lt;TD&gt;Hard disk 41&lt;/TD&gt;&lt;TD&gt;63488&lt;/TD&gt;&lt;TD&gt;25&lt;/TD&gt;&lt;TD&gt;6000C29aa913385c071f28a8840c4c88&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE25&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:6)&lt;/TD&gt;&lt;TD&gt;Hard disk 42&lt;/TD&gt;&lt;TD&gt;63488&lt;/TD&gt;&lt;TD&gt;26&lt;/TD&gt;&lt;TD&gt;6000C29b8a13fb1f775fee4268e3365b&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE26&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(3:8)&lt;/TD&gt;&lt;TD&gt;Hard disk 43&lt;/TD&gt;&lt;TD&gt;63488&lt;/TD&gt;&lt;TD&gt;27&lt;/TD&gt;&lt;TD&gt;6000C29ede81e942fec57665c31bacae&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE27&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:1)&lt;/TD&gt;&lt;TD&gt;Hard disk 5&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;29&lt;/TD&gt;&lt;TD&gt;6000C29fc1355d22327fbf5ff5a92890&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE29&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:2)&lt;/TD&gt;&lt;TD&gt;Hard disk 6&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;30&lt;/TD&gt;&lt;TD&gt;6000C2930bd77b0a8f9f4b06667b61eb&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE30&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:3)&lt;/TD&gt;&lt;TD&gt;Hard disk 7&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;31&lt;/TD&gt;&lt;TD&gt;6000C29ada1e3f6767d8a14a7f14fbf5&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE31&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:4)&lt;/TD&gt;&lt;TD&gt;Hard disk 8&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;32&lt;/TD&gt;&lt;TD&gt;6000C29be70d870c85bbb8c17c5cc0d1&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE32&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SCSI(1:5)&lt;/TD&gt;&lt;TD&gt;Hard disk 9&lt;/TD&gt;&lt;TD&gt;2048&lt;/TD&gt;&lt;TD&gt;33&lt;/TD&gt;&lt;TD&gt;6000C295bc69ea0cbc1cf890b4dae664&lt;/TD&gt;&lt;TD&gt;\\.\PHYSICALDRIVE33&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Mon, 09 Oct 2023 21:05:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2990323#M46248</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-10-09T21:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Moving spanned volumes on massive windows 2012r2 to win 2022 server</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2990293#M46247</link>
      <description>&lt;P&gt;Lukas,&lt;/P&gt;&lt;P&gt;thanks for the reply. This is going to be fun.. not!&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 16:04:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2990293#M46247</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-10-09T16:04:17Z</dc:date>
    </item>
    <item>
      <title>Moving spanned volumes on massive windows 2012r2 to win 2022 server</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2989891#M46232</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;It is with great sadness that I'm even posting this question but here's hoping somebody has experienced this pain. As many of us know win2012r2 has ended its life and yet many applications SME's have waited till the bitter end to attempt migration.&lt;/P&gt;&lt;P&gt;We are running vsphere 7.03 backended by Pure flash arrays.&lt;/P&gt;&lt;P&gt;The Win2012r2 vm has evolved (mostly pre-me) to 43 underlying VMDK's of various sizes which are mostly spanned in Windows to several very large volumes (total in use storage is 120T and provisioned is 400T). This server also had a similar activity of moving a spanned volume to it years ago making the disk subsystem even more janky. It is easily one of the top 5 most valuable with the least downtime allowed servers we have. Rubrik backups are a mess because the server is so busy the full Rubrik snaps can kill the server..so we do some by SMB.. point being recovery could be very messy.&lt;/P&gt;&lt;P&gt;Has anybody had luck moving Windows spanned volumes from an older OS to a newer one? Have any reliable references for making it happen?&lt;/P&gt;&lt;P&gt;Appreciate any insight&lt;/P&gt;&lt;P&gt;Fish&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 00:13:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2989891#M46232</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-10-06T00:13:16Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon Instant Clones and Azure MFA - Anybody have a working configuration?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Instant-Clones-and-Azure-MFA-Anybody-have-a-working/m-p/2965739#M99234</link>
      <description>&lt;P&gt;Good to commisserate on this insanity. My project is dead in the water at this point. We have a contingent of people who are full steam ahead with everything Azure but fail time and again when it comes to integration and costs but still we limp forward. I don't have time to attempt to understand how it all works and doesn't work.&amp;nbsp; I think IC technology was created to make our lives simpler and resource efficient but cloud integration and MFA turn IC into a management nightmare. Ultimately we'll probably end up with Azure based VDI which will bring it's own problems with data latency and authentication to on-prem app/data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate all your details and will look into them.&lt;/P&gt;&lt;P&gt;To the cloud and beyond!&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 15:30:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Instant-Clones-and-Azure-MFA-Anybody-have-a-working/m-p/2965739#M99234</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-04-26T15:30:14Z</dc:date>
    </item>
    <item>
      <title>Re: vc_runtimeMinimum_x86 packages missing after removing Hor agent 7.8</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/vc-runtimeMinimum-x86-packages-missing-after-removing-Hor-agent/m-p/2964670#M99152</link>
      <description>&lt;P&gt;Agreed. I didn't note that but we are on 8.7 with our Horizon infra. About 20% of our VM's are these (old agent) VM's that in many cases people have modified over the years and new images will cause ill feelings shall we say. The 7.8 agent is a pain to upgrade in an automated fashion unlike 8.x version agents which can be upgraded in place.&amp;nbsp; We used to be able to manually uninstall and install an 8.x agent until this vc_runtime issue crept in consistiently.&amp;nbsp; There is a lot about these missing c++ libraries on the Internet but no consistently good fixes I've found.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Apr 2023 14:36:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/vc-runtimeMinimum-x86-packages-missing-after-removing-Hor-agent/m-p/2964670#M99152</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-04-19T14:36:15Z</dc:date>
    </item>
    <item>
      <title>vc_runtimeMinimum_x86 packages missing after removing Hor agent 7.8</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/vc-runtimeMinimum-x86-packages-missing-after-removing-Hor-agent/m-p/2964542#M99136</link>
      <description>&lt;P&gt;This has got me stumped. We have a couple hundred Win10 (21h1 - 22H2) static VM's that have the older Horizon 7.8 agent. This agent is problematic in many ways including just upgrading it. You can't do an inplace upgrade. You must uninstall, reboot then attempt to install a newer agent.&lt;/P&gt;&lt;P&gt;This issue seemed to creep in over the last couple months where the uninstall of the agent removes (all?) of the Visual C++ x86 runtime msi packages that are required for newer agent version installs. I've tried updating the runtimes with latest packages from MS but just the install of those is balking about the older MSI's missing. This reminds me of DLL hell of the old days of windows.&lt;/P&gt;&lt;P&gt;The screenshot is when attemping to install the 8.7 agent. If I try to install a slightly older agent it complains about a prior runtime missing. I've tried using the supposed MS wondertool MicrosoftProgram_Install_and_Uninstall.meta app but that doesn't work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anybody have this issue and found a solution?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anybody found a way to repair these libraries?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2023 23:48:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/vc-runtimeMinimum-x86-packages-missing-after-removing-Hor-agent/m-p/2964542#M99136</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-04-18T23:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: High CPU Win10 persistent desktops with no user sessions - scripted reset?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/High-CPU-Win10-persistent-desktops-with-no-user-sessions/m-p/2964536#M99134</link>
      <description>&lt;P&gt;Ultmately I think that is what it is. I just went through a major effort to get all our Win10 stuff up to at least 21h1 enterprise.. Half our stuff was 1809 and older.&amp;nbsp; Thanks for the replies&lt;/P&gt;</description>
      <pubDate>Tue, 18 Apr 2023 23:14:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/High-CPU-Win10-persistent-desktops-with-no-user-sessions/m-p/2964536#M99134</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-04-18T23:14:57Z</dc:date>
    </item>
    <item>
      <title>Re: VMware VDI persistent desktop dump files</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-VDI-persistent-desktop-dump-files/m-p/2963375#M99077</link>
      <description>&lt;P&gt;Upgrade your Horizon infra to 8.x and get rid of all those old agents on VM's. Easier said than done but if you're running newer versions of Win10 VM's (21h2 and 22h2) then you really need to get Horizon upgraded. For us the old 7.8 agents are the only ones causing the huge influx of dump files.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 17:06:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VMware-VDI-persistent-desktop-dump-files/m-p/2963375#M99077</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-04-11T17:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: High CPU Win10 persistent desktops with no user sessions - scripted reset?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/High-CPU-Win10-persistent-desktops-with-no-user-sessions/m-p/2962287#M99028</link>
      <description>&lt;P&gt;I don't disagree other than the machines are so cpu bound that they are impossible to work with in that state. The agents do consume some but its things like system and svchost processes that seem to take most cpu. Those are always fun to figure out what actual service or processes is the cause.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 19:04:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/High-CPU-Win10-persistent-desktops-with-no-user-sessions/m-p/2962287#M99028</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-04-03T19:04:43Z</dc:date>
    </item>
    <item>
      <title>High CPU Win10 persistent desktops with no user sessions - scripted reset?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/High-CPU-Win10-persistent-desktops-with-no-user-sessions/m-p/2962054#M99018</link>
      <description>&lt;P&gt;We have a Horizon 8.7 infra (vSphere 7) serving about a 1000 persistent desktops. Most of these are Win10 21H2 running a typical variety of O365 apps along with a number of security agents and 8.x Horizon agents. We have been finding especially over the last month that a lot of these machines will go into a high CPU state with no user sessions (disconnected or active). These sessions also drive a lot of IOPS which loads up our Pure Flash arrays. I've not been able to isolate any particular process other than SYSTEM which seems to be using majority CPU when I have the time to wait for the UI to respond and look.&lt;/P&gt;&lt;P&gt;This is probably a tall order scripting wise but I'd like to be able to periodically run a script that will reset machines in a high CPU state that also have no active user sessions. Sadly this requires both Horizon and vCenter data to discover this and act on it via Horizon.&lt;/P&gt;&lt;P&gt;Anybody ever seen this and/or know of a script that might work? I guess I could just reset all machines with an available status in Horizon but it would be nice just to reset the offenders.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2023 21:54:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/High-CPU-Win10-persistent-desktops-with-no-user-sessions/m-p/2962054#M99018</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-03-31T21:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 7 admin console web time out??</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-7-admin-console-web-time-out/m-p/2958566#M98846</link>
      <description>&lt;P&gt;Agreed this is the only applicaiton I use that the timeout cannot be managed regardless of what you set it to. VMware doesn't seem to think it is a problem. Doesn't matter whether you connect directly to a connection server or via Load balancer.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are on 2209 now and still experiencing this stupidity.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 18:14:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-7-admin-console-web-time-out/m-p/2958566#M98846</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-03-09T18:14:42Z</dc:date>
    </item>
    <item>
      <title>Horizon Instant Clones and Azure MFA - Anybody have a working configuration?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Instant-Clones-and-Azure-MFA-Anybody-have-a-working/m-p/2958029#M98824</link>
      <description>&lt;P&gt;I've been working with a consultant on producing a viable Win10 IC configuration for several months now. Due to multiple factors surrounding on-prem and Azure AD coupled with OneDrive, o365 and MFA we've thus far created a user experience that is far worse than our static clone Horizon desktops. Essentially we have a user experience that is wrought with authentication/MFA to teams, onedrive (which needs to start with the logon but does not). Every time a user logs off the IC is destroyed (as expected) and the next logon is met with the same frustrating logon experience. We have a small staff working every flavor of IT admin and VDI takes up way too much time. I have come to loath everything about cloud integration.&lt;/P&gt;&lt;P&gt;We have the following pieces in play&lt;/P&gt;&lt;P&gt;vsphere 7 with about 1000 VDI desktops (we want replace with IC and as good or better user experience)&lt;/P&gt;&lt;P&gt;Horizon 8 CS behind F5 internally/externally (via v7 UAG's)&lt;/P&gt;&lt;P&gt;Win10 21h2 images&lt;/P&gt;&lt;P&gt;FSlogix o365 containers storing profiles on CIFS&lt;/P&gt;&lt;P&gt;DEM profiles (for the stuff you can't do with FSlogix)&lt;/P&gt;&lt;P&gt;Onedrive redirection of mydocuments etc&lt;/P&gt;&lt;P&gt;Our logon sessions and IC's objects are on-prem AD which does not match the domain suffix for our AAD/MFA authentication.&lt;/P&gt;&lt;P&gt;Example on prem AD auth is my.company.com and all the AAD stuff authenticates to company.com. This appears to produce the issue with Onedrive not authenticating at logon. MFA tokens aren't being saved one session to the next.&lt;/P&gt;&lt;P&gt;We have been testing with hybrid join of AAD which is met with similar user experience.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Who has time for this insanity? Please just give me back the old days of on-prem everthing!&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2023 20:49:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Instant-Clones-and-Azure-MFA-Anybody-have-a-working/m-p/2958029#M98824</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2023-03-06T20:49:11Z</dc:date>
    </item>
    <item>
      <title>Latest Horizon Admin Console long standing UI issues</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Latest-Horizon-Admin-Console-long-standing-UI-issues/m-p/2937886#M98101</link>
      <description>&lt;P&gt;I find it amazing the VMware cannot fix obvious annoyances with the admin UI (now on 2209) that have been there for years. Specifically not being able to save column settings in Sessions and Machine views and not being able to restart/reset multiple machines in session view. Session view is the only view I know of that shows logon duration. Seems really silly that I can restart multiple VM's in the Machine view but not sessions. Anybody else find this annoying? I pinged my VMware rep and SE about it today.. not holding breath.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vmrulz_0-1668195417274.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/98251iD738A85C98709FF7/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="vmrulz_0-1668195417274.png" alt="vmrulz_0-1668195417274.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Fish&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2022 19:38:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Latest-Horizon-Admin-Console-long-standing-UI-issues/m-p/2937886#M98101</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2022-11-11T19:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon Agent upgrade script(s)?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2913659#M97192</link>
      <description>&lt;P&gt;Hi Fabio,&lt;/P&gt;&lt;P&gt;The SMB share mounts fine locally on Win10 and maps an S drive. I executed the bat file manually and it pops a UAC warning then setup came up in interactive mode.&lt;/P&gt;&lt;P&gt;Contents of bat file&lt;/P&gt;&lt;P&gt;S:\VMware-Horizon-Agent-x86_64-2111-8.4.0-19446757.exe /s /v"/qn REMOVE=ClientDriveRedirection”&lt;/P&gt;&lt;P&gt;Note I get garbage chars at the end of&amp;nbsp;ClientDriveRedirection instead of a quote&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 20:09:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2913659#M97192</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2022-06-10T20:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon Agent upgrade script(s)?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2913364#M97175</link>
      <description>&lt;P&gt;Hi Fabio,&lt;/P&gt;&lt;P&gt;I attempted the script and it ran fine to the point where it uninstalled the agent then rebooted the workstation. Then it hung for 10 minutes waiting for reboot (even though it did reboot as I was watching it in vcenter console session).&lt;/P&gt;&lt;P&gt;I decided to manually reboot it while the script was waiting.. then it progressed to detecting no agent on workstation and asked to disconnect from vcenter.&lt;/P&gt;&lt;P&gt;screenshots with workstation name crossed out.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jun 2022 00:18:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2913364#M97175</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2022-06-09T00:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon Agent upgrade script(s)?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2913310#M97170</link>
      <description>&lt;P&gt;Thank you I will take a look at it.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 16:48:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2913310#M97170</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2022-06-08T16:48:57Z</dc:date>
    </item>
    <item>
      <title>Horizon Agent upgrade script(s)?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2912072#M97109</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;I've got several hundred win10 static VM's that need to be upgraded from agent v 7.08 to 8.x There is no reliable upgrade of this agent so it must be uninstalled.. reboot then new agent installed. Anybody have any methods to share to make this process less pain?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ron&lt;/P&gt;</description>
      <pubDate>Tue, 31 May 2022 23:53:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-Agent-upgrade-script-s/m-p/2912072#M97109</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2022-05-31T23:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon 7 admin console web time out??</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-7-admin-console-web-time-out/m-p/2867622#M94889</link>
      <description>&lt;P&gt;Thank you I think we'll try doing the web-inf file since we don't have want to automatically update our infra.&lt;/P&gt;&lt;P&gt;Ron&lt;/P&gt;</description>
      <pubDate>Mon, 20 Sep 2021 15:45:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-7-admin-console-web-time-out/m-p/2867622#M94889</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2021-09-20T15:45:48Z</dc:date>
    </item>
    <item>
      <title>Horizon 7 admin console web time out??</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-7-admin-console-web-time-out/m-p/2867195#M94857</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have 7.13 connection servers. I'm trying to figure out how to extend the admin web session timeout. I've tried the logical thing by changing my preferences as below but the time out is still less than 5 minutes. Extremely frustrating to use. This occurs for everyone. I assume it is a setting on the connection servers?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vmrulz_0-1631814561804.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/91102i18CBEFE1C7097DED/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="vmrulz_0-1631814561804.png" alt="vmrulz_0-1631814561804.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks Fish!&lt;/P&gt;</description>
      <pubDate>Thu, 16 Sep 2021 17:51:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-7-admin-console-web-time-out/m-p/2867195#M94857</guid>
      <dc:creator>vmrulz</dc:creator>
      <dc:date>2021-09-16T17:51:06Z</dc:date>
    </item>
  </channel>
</rss>

