<?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>Bruticusmaximus Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Bruticusmaximus Tracker</description>
    <pubDate>Wed, 15 Nov 2023 09:13:20 GMT</pubDate>
    <dc:date>2023-11-15T09:13:20Z</dc:date>
    <item>
      <title>Query to see what ID powered off a VM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Query-to-see-what-ID-powered-off-a-VM/m-p/2982716#M2889</link>
      <description>&lt;P&gt;Is there a log insight query I can use to see who shut down a VM? I don't use Log Insight a lot.&amp;nbsp; We have a VM that keeps shutting down.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Aug 2023 14:11:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Query-to-see-what-ID-powered-off-a-VM/m-p/2982716#M2889</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2023-08-17T14:11:46Z</dc:date>
    </item>
    <item>
      <title>Does vSphere Replication pre-allocate disk space for replicated VMs?</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/Does-vSphere-Replication-pre-allocate-disk-space-for-replicated/m-p/2936892#M3639</link>
      <description>&lt;P&gt;Does vSphere Replication pre-allocate disk space for replicated VMs?&lt;BR /&gt;&lt;BR /&gt;Here's my scenario.&amp;nbsp; I'm setting up replication for a VM that is 6TB.&amp;nbsp; At the recovery site I see datastore A has 8TB free,&amp;nbsp; I choose that datastore. VSR is happy.&lt;BR /&gt;&lt;BR /&gt;Someone else comes along a few minutes later and sets up replication for another VM that is 4TB.&amp;nbsp; They see datastore A has 8TB and they choose that. VSR is also happy. VSR doesn't seem to say "Hey, I have this 6TB replicating so you can't stick your 4TB VM there" when you setup replication for the second VM.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Now, throw on top of this DRS.&amp;nbsp; Before the 6TB VM finishes the initial sync, DRS comes along and throws a few TB of other VMs on datastore A so now, the 6TB replication fails.&lt;BR /&gt;&lt;BR /&gt;Am I doing something wrong?&amp;nbsp; Does VSR not communicate with DRS? If you're replicating a 6TB VM, shouldn't VSR set aside that space so other VMs don't end up on that datastore before replication finishes?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Nov 2022 18:39:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/Does-vSphere-Replication-pre-allocate-disk-space-for-replicated/m-p/2936892#M3639</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2022-11-04T18:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: RVTools - Run against a specific data center</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/RVTools-Run-against-a-specific-data-center/m-p/2892441#M105220</link>
      <description>&lt;P&gt;I'm using that command too.&amp;nbsp; I have a spreadsheet for 3 different virtual centers. The&amp;nbsp;&lt;SPAN&gt;"RVToolsMergeExcelFiles" works great to put them all into one spreadsheet.&amp;nbsp; It's just getting rid of unneeded columns that I'm having an issue with.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Feb 2022 16:15:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/RVTools-Run-against-a-specific-data-center/m-p/2892441#M105220</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2022-02-07T16:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: RVTools - Run against a specific data center</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/RVTools-Run-against-a-specific-data-center/m-p/2892440#M105219</link>
      <description>&lt;P&gt;That's actually one of the blogs that I was using.&amp;nbsp; My problem is that as soon as&amp;nbsp; I try to do Import-excel, it fails because the spreadsheet RvTools generates had duplicate headers.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Feb 2022 16:13:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/RVTools-Run-against-a-specific-data-center/m-p/2892440#M105219</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2022-02-07T16:13:48Z</dc:date>
    </item>
    <item>
      <title>RVTools - Run against a specific data center</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/RVTools-Run-against-a-specific-data-center/m-p/2891707#M105152</link>
      <description>&lt;P&gt;Is there a way to run RVTools against a specific data center within Virtual Center?&lt;/P&gt;&lt;P&gt;Also, is there a way to export just specific data to Excel?&lt;/P&gt;&lt;P&gt;I basically need about 20 columns from the million that RVTools spits out.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've also tried using Powershell to extract just the columns I need but, RVTools creates Excel files with two row 1's.&amp;nbsp; So I get "Duplicate Header" errors whenever I try to manipulate things with Powershell.&amp;nbsp; It's more like there's 2 copies of the whole spreadsheet. If you unfreeze the top row, when you expand it, it's two spreadsheets. (See screenshot)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 00:42:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/RVTools-Run-against-a-specific-data-center/m-p/2891707#M105152</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2022-02-03T00:42:29Z</dc:date>
    </item>
    <item>
      <title>Create email alert when VM is created with user name included</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Create-email-alert-when-VM-is-created-with-user-name-included/m-p/2891202#M2765</link>
      <description>&lt;P&gt;I had an old installation of Loginsight where I would get an email every time a VM was created or deleted. It gave me all of the info like VM name, host, cluster etc.&amp;nbsp; I also used to give me the user name of the person that created it.&lt;BR /&gt;&lt;BR /&gt;I'm trying to re-create this alert in our new environment.&amp;nbsp; It's working except, I don't get the user name in the email alert.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do I customize was info is sent in the emailed alert?&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2022 21:26:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Create-email-alert-when-VM-is-created-with-user-name-included/m-p/2891202#M2765</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2022-01-31T21:26:16Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to run tasks against VC from vRops</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Unable-to-run-tasks-against-VC-from-vRops/m-p/2878854#M18858</link>
      <description>&lt;P&gt;I managed to get this to work. There IS another ID for automated tasks buried in there in the new version.&amp;nbsp; None of the documentation mentions it. Even our Vmware TAM didn't know about it. Once I added the ID, everything worked fine. If I can find where you enter it again, I'll post a screenshot here.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 19:43:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Unable-to-run-tasks-against-VC-from-vRops/m-p/2878854#M18858</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-11-18T19:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Calling a powershell script from SRM appliance</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Calling-a-powershell-script-from-SRM-appliance/m-p/2873818#M13943</link>
      <description>&lt;P&gt;I tried running a bash script on the SRM appliance that would call a Powershell script on a utility VM but, couldn't get it to go.&amp;nbsp; I was investing too much time into it and just gave up.&amp;nbsp; The simple solution is to just go back to the Windows version of SRM.&amp;nbsp; So our DR test is automated now except for one manual step.&amp;nbsp;It would have been cool to have it completely automated like it used to be before upgrading SRM.&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@D5E6B168D16C1011E835DECBE0488360/emoticons/2639.png" alt=":frowning_face:" title=":frowning_face:" /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;I submitted a feature request so, we'll see how that goes.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Oct 2021 14:25:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Calling-a-powershell-script-from-SRM-appliance/m-p/2873818#M13943</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-10-22T14:25:47Z</dc:date>
    </item>
    <item>
      <title>Re: Automated snapshot deletion after x number of days</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Automated-snapshot-deletion-after-x-number-of-days/m-p/2873813#M40520</link>
      <description>&lt;P&gt;This VM is 2TB. It would be down all day trying to restore it from backup if we needed to.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Oct 2021 14:17:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Automated-snapshot-deletion-after-x-number-of-days/m-p/2873813#M40520</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-10-22T14:17:22Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Template to VM to Template after Patching</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Convert-Template-to-VM-to-Template-after-Patching/m-p/2873805#M103873</link>
      <description>&lt;P&gt;We have a static IP address on all our templates.&amp;nbsp; Changing the IP is part of the deployment of a VM.&lt;BR /&gt;&lt;BR /&gt;We time the convert from template to VM and power on with our patch window.&amp;nbsp; When SCCM or Satellite pushes patches, the VM is up and running. Then, power off and convert back to a template.&amp;nbsp; When things don't work correctly, it's usually on the SCCM or Satellite side.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Oct 2021 14:09:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Convert-Template-to-VM-to-Template-after-Patching/m-p/2873805#M103873</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-10-22T14:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to run tasks against VC from vRops</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Unable-to-run-tasks-against-VC-from-vRops/m-p/2873793#M18796</link>
      <description>&lt;P&gt;I've gotten a little further.&amp;nbsp; I removed the ID it was using from VC then, re-added it.&amp;nbsp; Now, in vRops, the task goes into a "Starting" state for about 5 minutes before it fails with the same error.&amp;nbsp; Before, it would fail within seconds.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Oct 2021 13:52:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Unable-to-run-tasks-against-VC-from-vRops/m-p/2873793#M18796</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-10-22T13:52:59Z</dc:date>
    </item>
    <item>
      <title>Unable to run tasks against VC from vRops</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Unable-to-run-tasks-against-VC-from-vRops/m-p/2873786#M18795</link>
      <description>&lt;P&gt;I've just started playing around with some of the tasks in vRops. Delete old snapshots, right size VM, etc.&amp;nbsp; The tasks fail right away with&amp;nbsp;"Unable to establish VC connection. Cannot complete login due to an incorrect user name or password".&amp;nbsp;&lt;/P&gt;&lt;P&gt;vRops is collecting data from VC fine.&amp;nbsp; The ID we use for that is an administrator of everything.&amp;nbsp; Is there a different ID buried in there somewhere that vRops uses for tasks?&amp;nbsp; The error message isn't all that helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Oct 2021 13:36:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Unable-to-run-tasks-against-VC-from-vRops/m-p/2873786#M18795</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-10-22T13:36:06Z</dc:date>
    </item>
    <item>
      <title>Automated snapshot deletion after x number of days</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Automated-snapshot-deletion-after-x-number-of-days/m-p/2860073#M39832</link>
      <description>&lt;P&gt;Is there a way to automatically delete a scheduled snapshot after x number of days.&amp;nbsp; There's a VM that has issues and, we're constantly restoring it from backup.&amp;nbsp; I can schedule a daily snapshot of the VM but, I have to also remember to delete it every single day. Sure, i could do a power CLI script and schedule it to run with some scheduler but, I'd still have to check it every once in a while to make sure it's still running.&lt;BR /&gt;&lt;BR /&gt;I've put in a feature request to add "Delete snapshot after x days" when you schedule a snapshot.&lt;BR /&gt;&lt;BR /&gt;Way back, maybe 10 years ago when Vmware owned Shavlik for patching, you could apply Windows updates through Vmware Update Manager.&amp;nbsp; It worked great.&amp;nbsp; You could schedule it to take a snapshot of the VM before applying patches then, automatically delete the snapshot x number of days later.&amp;nbsp; We usually did it 2 days later. So I know the hooks are in there somewhere to do this.&amp;nbsp; Am I just missing something?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2021 13:17:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Automated-snapshot-deletion-after-x-number-of-days/m-p/2860073#M39832</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-07-30T13:17:22Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a simple way of doing a snapshot on a VM after recovery?</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Is-there-a-simple-way-of-doing-a-snapshot-on-a-VM-after-recovery/m-p/2860070#M13891</link>
      <description>&lt;P&gt;Unfortunately, we're not using vSphere Replication.&amp;nbsp; We're using Recover Point.&amp;nbsp; It lets you do the same point in time snapshots but, it's of a whole volume and not at the VM level.&amp;nbsp; We'd have to revert about a dozen VMs at once.&amp;nbsp; We could do it but, it's a pain.&lt;BR /&gt;&lt;BR /&gt;My solution for now was to put a message in the recovery plan that pauses and says "Hey, go take a snapshot of xxx".&amp;nbsp; Not as elegant as I would have liked but, it works.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2021 13:07:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Is-there-a-simple-way-of-doing-a-snapshot-on-a-VM-after-recovery/m-p/2860070#M13891</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-07-30T13:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating to new hardware without shared storage</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Migrating-to-new-hardware-without-shared-storage/m-p/2850568#M276349</link>
      <description>&lt;P&gt;How many VMs do you need to move?&amp;nbsp; A down and dirty way to do it is to use the Vmware Converter P2V tool.&amp;nbsp; The one benefit of this is that you still have the original VM powered off in the old environment if something goes drastically wrong.&amp;nbsp; If you need to move 100 VMs, this might not be the best solution.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 20:07:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Migrating-to-new-hardware-without-shared-storage/m-p/2850568#M276349</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-06-02T20:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: Does Syslog get wiped out each time a host is rebooted?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Does-Syslog-get-wiped-out-each-time-a-host-is-rebooted/m-p/2850564#M276348</link>
      <description>&lt;P&gt;That's the thing though, our SD cards are 32GB.&amp;nbsp; I would have thought that was large enough to put the logs on. But it seems that Vmware sees it's an SD card and doesn't even bother.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 19:57:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Does-Syslog-get-wiped-out-each-time-a-host-is-rebooted/m-p/2850564#M276348</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-06-02T19:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: Does Syslog get wiped out each time a host is rebooted?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Does-Syslog-get-wiped-out-each-time-a-host-is-rebooted/m-p/2845596#M275845</link>
      <description>&lt;P&gt;Is it different if I were booting from HD?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 May 2021 17:58:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Does-Syslog-get-wiped-out-each-time-a-host-is-rebooted/m-p/2845596#M275845</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-05-05T17:58:34Z</dc:date>
    </item>
    <item>
      <title>Does Syslog get wiped out each time a host is rebooted?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Does-Syslog-get-wiped-out-each-time-a-host-is-rebooted/m-p/2844091#M275739</link>
      <description>&lt;P&gt;I guess we've been fortunate and haven't had to pull logs for Vmware tickets in a while.&amp;nbsp; We had an issue over the weekend where we had to hard boot hosts to resolve.&amp;nbsp; Afterwards, we pulled logs for a vendor to look at but, they only went back to the reboot.&lt;/P&gt;&lt;P&gt;It's been a while but, I seem to recall the syslogs just overwriting based on how much space was available regardless of reboots.&amp;nbsp; Has that changed?&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;One thing that we have changed is booting our hosts from SD cards rather than local disk or SAN.&amp;nbsp; Could this make a difference?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Apr 2021 14:20:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Does-Syslog-get-wiped-out-each-time-a-host-is-rebooted/m-p/2844091#M275739</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-04-27T14:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: scratch partition and syslog</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/scratch-partition-and-syslog/m-p/2844086#M275738</link>
      <description>&lt;P&gt;Is the Syslog always in Ramdisk?&amp;nbsp; Does it always get wiped out when a host is rebooted?&amp;nbsp; Or, does that only happen when yo boot from SD cards?&lt;/P&gt;&lt;P&gt;Years ago, we used to boot from a local HD.&amp;nbsp; I seem to recall the Syslogs not getting wiped out on reboots.&amp;nbsp; Now that we're on SD cards, they seem to get wiped out.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Apr 2021 14:08:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/scratch-partition-and-syslog/m-p/2844086#M275738</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-04-27T14:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a simple way of doing a snapshot on a VM after recovery?</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Is-there-a-simple-way-of-doing-a-snapshot-on-a-VM-after-recovery/m-p/2844082#M13829</link>
      <description>&lt;P&gt;I understand that and I have recovery plan setup with the primary data node powering on first.&amp;nbsp; The problem is, the node that is primary can switch and I would never know it until I try to recover them at the DR site. Node 1 is primary right now and everything should work fine but, if node 2 becomes the primary down the road and we run the recovery plan, it's going to power on the wrong node first.&lt;BR /&gt;&lt;BR /&gt;I guess the other option would be to somehow have the app send an alert that triggers a script to edit the recovery plan each time the nodes fail over but, that seems like a lot more work than just creating a snapshot in the unlikely event we ever have to recover these VMs during a disaster.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Apr 2021 13:59:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Is-there-a-simple-way-of-doing-a-snapshot-on-a-VM-after-recovery/m-p/2844082#M13829</guid>
      <dc:creator>Bruticusmaximus</dc:creator>
      <dc:date>2021-04-27T13:59:04Z</dc:date>
    </item>
  </channel>
</rss>

