<?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>lukasrueckerl Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>lukasrueckerl Tracker</description>
    <pubDate>Wed, 15 Nov 2023 13:44:03 GMT</pubDate>
    <dc:date>2023-11-15T13:44:03Z</dc:date>
    <item>
      <title>Re: Reverting vCenter Snap after Certificate Renewal failure</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Reverting-vCenter-Snap-after-Certificate-Renewal-failure/m-p/2995752#M95193</link>
      <description>&lt;P&gt;No, the VMs will keep on running. The vCenter is only needed for management, the actual VMs, the dVS and the HA configuration will keep functioning.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 07:42:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Reverting-vCenter-Snap-after-Certificate-Renewal-failure/m-p/2995752#M95193</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-11-15T07:42:46Z</dc:date>
    </item>
    <item>
      <title>Re: Reverting vCenter Snap after Certificate Renewal failure</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Reverting-vCenter-Snap-after-Certificate-Renewal-failure/m-p/2995749#M95191</link>
      <description>&lt;P&gt;This is taking a snapshot including the VMs RAM contents - if you restore this snapshot the VM will be powered on and running like at the exact time the snapshot was taken.&lt;/P&gt;&lt;P&gt;If you exclude it, the VM will be powered off when restoring, resulting in the VM behaving like it has crashed and rebooted.&lt;/P&gt;&lt;P&gt;The safest option overall though would be to temporarily shut down the vCenter and take an offline snapshot.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 07:38:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Reverting-vCenter-Snap-after-Certificate-Renewal-failure/m-p/2995749#M95191</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-11-15T07:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: Reverting vCenter Snap after Certificate Renewal failure</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Reverting-vCenter-Snap-after-Certificate-Renewal-failure/m-p/2995740#M95188</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;did you take an offline snapshot or did you exclude the VMs memory? Then the vCenter will come up as if it was shut down or crashed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Speaking from my experience with similar infrastructure, you won't have a problem.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ESX servers and the VMs on them are mostly decoupled from the vCenter and will keep running regardless. Regarding the distributed &amp;nbsp;switch - even when the vCenter is lost, the ESX servers will keep working with their running configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 07:10:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Reverting-vCenter-Snap-after-Certificate-Renewal-failure/m-p/2995740#M95188</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-11-15T07:10:40Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN ID not working for port group Standard switching</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VLAN-ID-not-working-for-port-group-Standard-switching/m-p/2995735#M46412</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;do you see any MAC adresses in the address-table of the switch coming from these ports in the desired VLANs?&lt;/P&gt;&lt;P&gt;Could you post the configuration of the switches?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 06:52:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VLAN-ID-not-working-for-port-group-Standard-switching/m-p/2995735#M46412</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-11-15T06:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: Expired Self-signed Certs After Upgrade</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Expired-Self-signed-Certs-After-Upgrade/m-p/2995734#M17078</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;please see this handbook by &lt;A href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2800060" target="_self"&gt;luca19100&lt;/A&gt;&amp;nbsp;for reference:&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/VMware-NSX-Documents/NSX-Certifcates-Management-Cookbook/ta-p/2992832" target="_blank"&gt;https://communities.vmware.com/t5/VMware-NSX-Documents/NSX-Certifcates-Management-Cookbook/ta-p/2992832&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Since NSX-T 4.1 a lot more certificates previously used internally but not visible are now visible in the GUI.&lt;/P&gt;&lt;P&gt;These certificates are important for management and control plane connectivity.&lt;/P&gt;&lt;P&gt;Feel free to reach out to the support team if you need help in replacing these.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 06:49:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Expired-Self-signed-Certs-After-Upgrade/m-p/2995734#M17078</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-11-15T06:49:07Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-T Logs in Log Insight(VMware Aria Operations for Logs)</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Logs-in-Log-Insight-VMware-Aria-Operations-for-Logs/m-p/2995730#M17077</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;the logs coming from NSX-T are all in RFC5424 format, roughly meaning:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;lt;facility + severity code&amp;gt; version timestamp hostname app processid messageid (structured data) message&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In your example it's a log entry of the firewallpkt.log file, meaning it's coming from one of your firewall rules with the logging option enabled.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There's no overall "log reference handbook" - but for the firewallpkt.log, see this KB for reference:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-1D754B94-1523-4C7E-A248-F524B974A66B.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-1D754B94-1523-4C7E-A248-F524B974A66B.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is a general overview of the log format and the log sources in NSX:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-406AF9C3-E8F7-447A-8E3D-92AFB9D5E973.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-406AF9C3-E8F7-447A-8E3D-92AFB9D5E973.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 06:23:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Logs-in-Log-Insight-VMware-Aria-Operations-for-Logs/m-p/2995730#M17077</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-11-15T06:23:55Z</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/2989993#M46236</link>
      <description>&lt;P&gt;Hi Fish,&lt;/P&gt;&lt;P&gt;I had a similar issue once, just not quite this massive of a server.&lt;/P&gt;&lt;P&gt;The steps I performed were just:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Kill all operations on the volume and unmount the volume via removing the drive letter&lt;/LI&gt;&lt;LI&gt;Set all disks offline in disk manager on source&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;Create new SCSI Controller on new VM&lt;/LI&gt;&lt;LI&gt;Detach VMDKs from source&lt;/LI&gt;&lt;LI&gt;Re-attach VMDKs in exact same order with same LUN IDs on the new system&lt;/LI&gt;&lt;LI&gt;Bring disks online on new system&lt;/LI&gt;&lt;LI&gt;You should be able to right-click the first volume and select "Import foreign Disk"&lt;/LI&gt;&lt;LI&gt;Done&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If youre able you could dry-run this process with smaller disks in a test scenario, but it should work.&lt;/P&gt;&lt;P&gt;Nonetheless a full backup would definitely be handy...&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 14:56:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Moving-spanned-volumes-on-massive-windows-2012r2-to-win-2022/m-p/2989993#M46236</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-10-06T14:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Can't add a new compute manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2982043#M16757</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;that's what I've done to get it to work, but this will only be useful in a demo environment or if you have freshly deployed the NSX instance. I have no further information as VMware Support specifically advised contacting them in this case.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 12 Aug 2023 11:50:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2982043#M16757</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-08-12T11:50:47Z</dc:date>
    </item>
    <item>
      <title>Re: Can't add a new compute manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2979916#M16699</link>
      <description>&lt;P&gt;Hi everybody,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I finally got a final statement on this - let me quote directly:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Engineering have confirmed that NSX deployed directly from vCenter would indeed hold a 1:1 relationship with that vCenter, and it was not originally designed to host more than one vCenter.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;However it is possible to detach the NSX instance from vCenter to allow for more than one Compute Manager instance and this can be done either via the way i've mentioned above or with the support team's help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I mentioned that this limitation should be more visible in the official documentation. Let's hope it shows up there some time &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@90D223CDF4C4491D7DFF693BB5C76865/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 05:32:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2979916#M16699</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-07-31T05:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: Can't add a new compute manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2977685#M16626</link>
      <description>&lt;P&gt;Hi everybody,&lt;/P&gt;&lt;P&gt;sorry for the late reply.&lt;/P&gt;&lt;P&gt;The support is still working with VMware engineering on it - but based on the response and the fact that it was forwarding to engineering and is worked on for over two weeks now, i think that this is a bug and should work normally...&lt;/P&gt;&lt;P&gt;I will keep you posted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jul 2023 06:59:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2977685#M16626</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-07-17T06:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: Best Way to Handle a Network Interruption</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Best-Way-to-Handle-a-Network-Interruption/m-p/2975154#M288784</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;TLDR: A live vSAN environment with a total connectivity loss for an extended period of time will almost certainly result in problems. Putting Datastores in Maintenance mode will take it completely out of service and stop all I/O on it.&lt;/P&gt;&lt;P&gt;vSAN handles connectivity loss according to this documentation:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-monitoring-troubleshooting/GUID-DE68730B-B49F-4EA1-A75A-DDE352217806.html" target="_blank"&gt;Network Connectivity Is Lost in the vSAN Cluster (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You will have all Hosts isolated which will most likely result in I/O errors for the VMs. This will most likely lead to reboots of the VMs and could cause some data inconsistency on the OS level.&lt;/P&gt;&lt;P&gt;The best way to resolve a situation like yours would be to replace the network infrastructure step-by-step in parts, so keeping parts of the connectivity alive. If you have over 800VMs which are of such importance, why is there no network redundancy present in your deployment?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 21:04:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Best-Way-to-Handle-a-Network-Interruption/m-p/2975154#M288784</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-29T21:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7 - VM can ping gateway on VLAN interface, but gw cannot ping device</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-VM-can-ping-gateway-on-VLAN-interface-but-gw-cannot-ping/m-p/2975004#M288764</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;any specific reason for the Ubuntu DNS-Server to need multiple NICs on each VLAN?&lt;/P&gt;&lt;P&gt;Having multiple default gateways in your VMs routing table most likely leads to these problems. To check, you could disable all other NICs except the IoT VLAN one and see if the IoT-Machine can ping the DNS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you're using a firewall I would go with a single-NIC DNS-Server, establish Routing and proper Rules and then use the PFSense DNS Forwarder described here:&amp;nbsp;&lt;A href="https://docs.netgate.com/pfsense/en/latest/services/dns/forwarder.html" target="_blank" rel="noopener"&gt;Services — DNS Forwarder | pfSense Documentation (netgate.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 06:27:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-VM-can-ping-gateway-on-VLAN-interface-but-gw-cannot-ping/m-p/2975004#M288764</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-29T06:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Replication</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/vSphere-Replication/m-p/2975003#M3704</link>
      <description>&lt;P&gt;Hi Gordy,&lt;/P&gt;&lt;P&gt;please see the documentation here:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/vSphere-Replication/8.7/com.vmware.vsphere.replication-admin.doc/GUID-FFBF959C-5C05-42C0-A2FE-3688AD55B6EF.html" target="_blank"&gt;Configure vSphere Replication Connections (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Here is also a good blog post, which I have found helpful:&amp;nbsp;&lt;A href="https://www.bdrsuite.com/blog/vmware-vsphere-replication-8-2-step-by-step/" target="_blank"&gt;Configuring VMware vSphere Replication 8.2 step by step (bdrsuite.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jun 2023 05:11:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/vSphere-Replication/m-p/2975003#M3704</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-29T05:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Replication</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/vSphere-Replication/m-p/2974923#M3701</link>
      <description>&lt;P&gt;Hi Gordy,&lt;/P&gt;&lt;P&gt;thats an exact use case for vSphere Replication. What issues are you running into?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 15:01:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/vSphere-Replication/m-p/2974923#M3701</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T15:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: vmware converter 6.4 ssl certificate error</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-ssl-certificate-error/m-p/2974922#M44387</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;the error indicates that the host&amp;nbsp;&lt;SPAN&gt;FT-HV01.ft.local from where you are converting from is serving an incomplete certificate chain (missing issuing and / or root CA). You will have to replace the certificate on the host with a full chain one to get it working in stock configuration.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Otherwise, you could try this KB&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/2020517" target="_blank"&gt;Disabling SSL encryption on VMware Converter Standalone 5.x and 6.0 (2020517)&lt;/A&gt;&amp;nbsp;- although I'm unsure if this "fix" is still viable, as it is only intended for VMware Converter up to version 6.0. This also may increase performance, but will transfer your conversion data unencrypted, which may be a security risk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 14:48:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-ssl-certificate-error/m-p/2974922#M44387</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T14:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: Can't add a new compute manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2974904#M16569</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I had the chance to test this in my demo deployment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please check under System &amp;gt; System Overview in the Capacity tab how many Compute Managers are supported.&amp;nbsp;In my demo it was deployed as Medium and i have a 2 system capacity.&lt;/P&gt;&lt;P&gt;I encountered the same error as you and could only add the second vCenter by deleting the VcLink Computer Manager. After that I added the original vCenter again and could add the second one.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note that this won't work if you already have a existing Transport Node Configuration applied to hosts on this vCenter and after this you won't get the NSX plugin in the vCenter(s).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;My best guess is that NSX is hard-coded and bound to the originating vCenter when deployed directly, based on the fact that in the default state the construct doesn't even use the built-in Service User function.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll open a case with VMware as this is unexpected behaviour and isn't documented properly.&lt;/P&gt;&lt;P&gt;Sorry that I can't help you any further.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 13:42:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2974904#M16569</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T13:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: Can't add a new compute manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2974886#M16566</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;hm... I'm not aware of any other "hard" limits then...&lt;/P&gt;&lt;P&gt;Did you already set up a 3-node Management Cluster or are you running a single Manager setup? I remember it was a limit in NSX-V that a single manager only can manage a single vCenter, although this limit seems not to be present on the configmax website.&amp;nbsp;&lt;/P&gt;&lt;P&gt;There could also be a difference when using the UI directly served by the manager and not via the vSphere plugin.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 11:17:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2974886#M16566</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T11:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: System/keyboard language change into Spanish after each relog</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/System-keyboard-language-change-into-Spanish-after-each-relog/m-p/2974884#M17732</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please see this KB:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-Horizon-Client-for-Mac/2303/horizon-client-mac-installation/GUID-B18F3555-9AB1-4573-AADC-A4462476B8B4.html" target="_blank" rel="noopener"&gt;Keyboard Input Source Language Synchronization (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;From what I understand you will have to control this behaviour agent-side with a GPO or with the registry keys mentioned in this KB under "VDI Registry":&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/88502#:~:text=When%20the%20Keyboard%20locale%20synchronization,is%20also%20restored%20when%20disconnecting." target="_blank" rel="noopener"&gt;When logging on to the Horizon 2103 / 2106 / 2111 VDI in a MultiLingual environment, the Windows input locale is unexpectedly set to English (88502) (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This will result in changes for all users of the VDI though.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't know of any other ways for MacOS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 11:01:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/System-keyboard-language-change-into-Spanish-after-each-relog/m-p/2974884#M17732</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T11:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Where commands saved?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Where-commands-saved/m-p/2974880#M288750</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;please see this KB:&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/2014494" target="_blank"&gt;Viewing the command history in ESX/ESXi (2014494) (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;TLDR: They are in&amp;nbsp;&lt;SPAN&gt;/var/log/shell.log&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 10:32:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Where-commands-saved/m-p/2974880#M288750</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T10:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: Can't add a new compute manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2974878#M16564</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;which form factor did you use when deploying? Note that the medium form factor supports a maximum of 2 Compute Managers per NSX Management Cluster (&lt;A href="https://configmax.esp.vmware.com/guest?vmwareproduct=VMware%20NSX&amp;amp;release=NSX%204.1.0&amp;amp;categories=17-0" target="_blank"&gt;VMware Configuration Maximum tool&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Have you already deployed 2 Compute Managers? The error code on the message indicates a&amp;nbsp;limit has been exceeded...&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lukas&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jun 2023 10:24:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Can-t-add-a-new-compute-manager/m-p/2974878#M16564</guid>
      <dc:creator>lukasrueckerl</dc:creator>
      <dc:date>2023-06-28T10:24:18Z</dc:date>
    </item>
  </channel>
</rss>

