<?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>szafa Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>szafa Tracker</description>
    <pubDate>Wed, 15 Nov 2023 09:41:30 GMT</pubDate>
    <dc:date>2023-11-15T09:41:30Z</dc:date>
    <item>
      <title>Re: storage allocation issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2989585#M25359</link>
      <description>&lt;P&gt;changing placement policy on project level didn't help. We spoke with VMware TAM and they recommend just one storage policy and select any datastore but it didn't help so far. Will try tags now but looks like because storage is always selected first might be not possible to use aria operation advance placement without workflow and we'd like to avoid it. Will keep you update if we get some progress. If anyone have any suggestion please post it :).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 10:02:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2989585#M25359</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-10-04T10:02:22Z</dc:date>
    </item>
    <item>
      <title>Re: storage allocation issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2987813#M25316</link>
      <description>&lt;P&gt;already tried that but then we limiting deployment just to Cluster1 but I'd like to automatically deploy e&lt;SPAN class=""&gt;qually on both clusters &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2023 13:52:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2987813#M25316</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-09-22T13:52:33Z</dc:date>
    </item>
    <item>
      <title>Re: storage allocation issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2987810#M25314</link>
      <description>&lt;P&gt;Thanks for answer&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5640015"&gt;@eduardosuarez&lt;/a&gt;. I have already check that KB but we have different scenario, two cluster with own storage each with same tag. Each time same data store is selected so all VM's are deployed in Cluster1. As I mentioned before the best would be that compute is selected first based on Aria Operation recommendation and storage that is available on selected cluster with tag storage:DB&amp;nbsp;&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="UntitledD.png" style="width: 601px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/103631i2FA399491802FEEC/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="UntitledD.png" alt="UntitledD.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;YAMAL :&lt;/P&gt;&lt;P&gt;***&lt;/P&gt;&lt;P&gt;Cloud_vSphere_Machine_1:&lt;BR /&gt;type: Cloud.vSphere.Machine&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;storage:&lt;BR /&gt;constraints:&lt;BR /&gt;- tag: Storage:DB&lt;/P&gt;&lt;P&gt;Cloud_vSphere_Disk_1:&lt;BR /&gt;type: Cloud.vSphere.Disk&lt;BR /&gt;properties:&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;constraints:&lt;BR /&gt;- tag: Storage:DB&lt;/P&gt;&lt;P&gt;***&lt;/P&gt;&lt;P&gt;Error that we get&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="host.png" style="width: 589px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/103632i1335CA13F7D8157D/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="host.png" alt="host.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I understand that datastoreB is allocated and then Aria Operation recommends host in cluster1 (which has no access to datastoreB) and VM is deployed on cluster2. First question why each time same datastore is selected and how to workaround that issue?&lt;/P&gt;&lt;P&gt;I hope that is clear now &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2023 13:44:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2987810#M25314</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-09-22T13:44:58Z</dc:date>
    </item>
    <item>
      <title>storage allocation issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2987785#M25312</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;I'am new to aria automation and got nice task to troubleshoot issue in existing setup :). In short customer decided to test advanced workload placement using VMware Aria Operations recommendation. The integration is done but it is keep placing all new VM's on same cluster,look like storage is selected before compute, more details below.&lt;/P&gt;&lt;P&gt;Goal : use Advanced workload placement using VMware Aria Operations&lt;/P&gt;&lt;P&gt;Scenario : One vCenter with 4 cluster located in on DC and 4 cluster in other DC, each DC has own storage&lt;BR /&gt;Aria Automation integrated with Aria Operation&lt;BR /&gt;- one cloud zone (Placement policy : ADVANCED)&lt;BR /&gt;- storage profile for each cluster with tag for example : Storage:DB&lt;BR /&gt;- because we have two DC each with own storage in result we have two storage profile with tag Storage:DB&lt;/P&gt;&lt;P&gt;Now when we request VM that should be placed on data store with tag Storage:DB Aria Automation have two option :&lt;BR /&gt;data store on DC1 or data store on DC2 and always chose DC1. Then compute allocation starts (Advanced workload placement using VMware Aria Operations) and DC2 is recommended (because there is more available resources) but it will fail because datastore on DC1 was already selected :). In result all VM's get deployed to DC1.&lt;/P&gt;&lt;P&gt;It would work if the compute was selected first and then storage &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;P&gt;Let me know if any one have idea how resolve that problem and how the storage allocation happen (cluster with more free space?)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2023 11:30:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation-Tools/storage-allocation-issue/m-p/2987785#M25312</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-09-22T11:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: vlcm vrops upgrade issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/vlcm-vrops-upgrade-issue/m-p/2973048#M273</link>
      <description>&lt;P&gt;&lt;U&gt;Hi Harry&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;This is reoccurring&amp;nbsp;issue so like to fix LCM (VMware already open PR)&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Inventory sync is working fine all the time. I even tried to remove vrops product and add it again, removed witness from vcenter inventory and registered&amp;nbsp;it again. Still no joy :(.&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;U&gt;Thanks&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 12:29:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/vlcm-vrops-upgrade-issue/m-p/2973048#M273</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-06-14T12:29:17Z</dc:date>
    </item>
    <item>
      <title>vlcm vrops upgrade issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/vlcm-vrops-upgrade-issue/m-p/2970286#M271</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;vLCM ver :&amp;nbsp;8.12.0.7 and vROPs 8.10 CA (with witness node) keep failing to upgrade with below error&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="css"&gt;com.vmware.vrealize.lcm.drivers.commonplugin.exceptions.NodeVmidException: Unable to find vMoid for host DE00VOVP001-Witness	at com.vmware.vrealize.lcm.drivers.commonplugin.task.GetVMidWithMachineNameTask.execute(GetVMidWithMachineNameTask.java:150)	at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:63)	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)	at java.base/java.lang.Thread.run(Unknown Source)&lt;/LI-CODE&gt;&lt;P&gt;vmware_vrlcm.log&lt;/P&gt;&lt;LI-CODE lang="css"&gt;2023-05-25 14:07:45.359 INFO  [pool-3-thread-31] c.v.v.l.d.v.v.u.CoreUtility -  -- Not able to find the VM with IP address : 10.224.20.201
2023-05-25 14:07:45.365 INFO  [pool-3-thread-31] c.v.v.l.p.a.s.Task -  -- Injecting task failure event. Error Code : 'LCMCOMMON80084', Retry : 'true', Causing Properties : '{ CAUSE ::  }'
com.vmware.vrealize.lcm.drivers.commonplugin.exceptions.NodeVmidException: Unable to find vMoid for host DE00VOVP001-Witness
        at com.vmware.vrealize.lcm.drivers.commonplugin.task.GetVMidWithMachineNameTask.execute(GetVMidWithMachineNameTask.java:150) [vmlcm-commonplugin-core-8.12.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:63) [vmlcm-engineservice-core-8.12.0-SNAPSHOT.jar!/:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
        at java.lang.Thread.run(Unknown Source) [?:?]
2023-05-25 14:07:45.842 INFO  [scheduling-1] c.v.v.l.r.c.RequestProcessor -  -- Updating the Environment request status to FAILED for request ID : 214cccb8-15af-4154-bf3a-64b4cc4ca210 with request type : UPGRADE_PRODUCT.&lt;/LI-CODE&gt;&lt;P&gt;Already tried to remove vROPs product from LCM env and add it back but it didn't help at all (SR with VMware open as well but no update so far)&lt;/P&gt;&lt;P&gt;Let me know if anyone experienced same issue and have some fix.&lt;/P&gt;&lt;P&gt;Thanks in advance&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 May 2023 14:11:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/vlcm-vrops-upgrade-issue/m-p/2970286#M271</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-05-25T14:11:57Z</dc:date>
    </item>
    <item>
      <title>vIDM error /hc/error/</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/vIDM-error-hc-error/m-p/2961121#M18483</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;One ESXi node crash and looks like IDM nodes were HA and since then I'm not able to login with AD creds. When I change domain for my AD I get redirect to url =&amp;gt;&amp;nbsp;&lt;A href="https://my_idm001.siedhc14.next/hc/error/" target="_blank"&gt;https://my_idm001.siedhc14.next/hc/error/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="szafa_0-1679917715113.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/100725iBD2F890E96E7FD00/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="szafa_0-1679917715113.png" alt="szafa_0-1679917715113.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When I check logs&amp;nbsp;/opt/vmware/horizon/workspace/logs/connector.log I see below error, any idea what could be wrong and how to fix it.&lt;/P&gt;&lt;P&gt;I can login as admin and new users from AD are sync.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2023-03-27T11:42:52,519 INFO  (Thread-12798) [;;;] com.vmware.horizon.connector.utils.TenantStateIdUtils - No tenantStateId found for tenant="FTH03IDM002" and connId="3002".
2023-03-27T11:42:52,521 INFO  (Thread-12798) [unknown;-;139.22.66.22;] com.vmware.horizon.connector.utils.TenantStateIdUtils - No tenantStateId found for tenant="FTH03IDM002" and connId="3002".
2023-03-27T11:42:52,521 INFO  (Thread-12798) [unknown;-;139.22.66.22;] com.vmware.horizon.connector.mvc.ControllerInterceptor - Unauthorized to access /hc/3002/authenticate/ :: com.vmware.horizon.connector.controller.AdapterLoginController
2023-03-27T11:42:52,521 ERROR (Thread-12798) [unknown;-;139.22.66.22;] com.vmware.horizon.connector.mvc.C2ExceptionResolver - Exception caught in C2ExceptionResolver. (com.vmware.horizon.connector.exception.UnauthorizedException )
com.vmware.horizon.connector.exception.UnauthorizedException: Unauthorized to access /hc/3002/authenticate/
        at com.vmware.horizon.connector.mvc.ControllerInterceptor.preHandle(ControllerInterceptor.java:111) ~[classes/:3.3.5.0 Build 18049997]
        at org.springframework.web.servlet.HandlerExecutionChain.applyPreHandle(HandlerExecutionChain.java:151) ~[kdc-kerberos-auth-adapter-0.1.jar:3.3.5.0 Build 18049997]
        at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1035) [kdc-kerberos-auth-adapter-0.1.jar:3.3.5.0 Build 18049997]
        at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) [kdc-kerberos-auth-adapter-0.1.jar:3.3.5.0 Build 18049997]
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) [kdc-kerberos-auth-adapter-0.1.jar:3.3.5.0 Build 18049997]
        at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) [kdc-kerberos-auth-adapter-0.1.jar:3.3.5.0 Build 18049997]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:626) [servlet-api.jar:?]
        at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) [kdc-kerberos-auth-adapter-0.1.jar:3.3.5.0 Build 18049997]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) [servlet-api.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [catalina.jar:8.5.63]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.63]
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat-websocket.jar:8.5.63]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;VMware Identity Manager™ 3.3.5.0 Build 18049997&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:50:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/vIDM-error-hc-error/m-p/2961121#M18483</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-03-27T11:50:44Z</dc:date>
    </item>
    <item>
      <title>OS disk queue issue</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/OS-disk-queue-issue/m-p/2956437#M19313</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;What metric can help to find out VM's (windows os) that having issue with disk performance on OS level because of high disk queue (usually cased by low disk queue depth of the LSI Logic SAS driver).&lt;/P&gt;&lt;P&gt;Recently customer complained about but disk performance on Windows SQL server so we changed LSI Logic SAS driver with PVSCSI and performance on OS is much better but can't see big difference on VM metrics after that change.&lt;/P&gt;&lt;P&gt;Just would like to monitor metric that would be good indicator of OS driver queue depth issue.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2023 07:37:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/OS-disk-queue-issue/m-p/2956437#M19313</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2023-02-24T07:37:13Z</dc:date>
    </item>
    <item>
      <title>vIDM source connection test failed.</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vIDM-source-connection-test-failed/m-p/2931667#M19195</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;After upgrade of IDM (3.3.5.0 Build 18049997) and vROPs (Version: 8.5.0 (18255622)) can't add IDM as&amp;nbsp;Authentication Sources, error "vIDM source connection test faile"&amp;nbsp;&lt;/P&gt;&lt;P&gt;/storage/vcops/log/web.log&lt;/P&gt;&lt;P&gt;2022-10-03T10:43:21,984+0000 ERROR [ajp-nio-127.0.0.1-8009-exec-8] com.vmware.vcops.ui.util.PreResultInterceptor.beforeResult - functionName = testVidm, succeededPartially = false, errorMessage = vIDM source connec&lt;BR /&gt;tion test failed.&lt;/P&gt;&lt;P&gt;Everything worked before upgrade.&lt;/P&gt;&lt;P&gt;Any idea what can be wrong and what logs to check?&lt;/P&gt;&lt;P&gt;Thanks&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;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 10:56:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vIDM-source-connection-test-failed/m-p/2931667#M19195</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-10-03T10:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: Telegraf Agent Install Failed to connect to vCenter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Telegraf-Agent-Install-Failed-to-connect-to-vCenter/m-p/2927027#M19173</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1985286"&gt;@chadc1979&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had strange issue with agent installation and removing all ARC adapters help (they are then recreated automatically) but not sure how this will affect existing agent as I had none.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2022 07:01:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Telegraf-Agent-Install-Failed-to-connect-to-vCenter/m-p/2927027#M19173</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-09-02T07:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: vROPs alerts being sent from alerts with no notification set</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROPs-alerts-being-sent-from-alerts-with-no-notification-set/m-p/2927026#M19172</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1327673"&gt;@billdossett&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you able choose&amp;nbsp; between notification that you set? I can't see them and seams that vrops use just one of those rule to trigger alerts.&lt;/P&gt;&lt;P&gt;I have created 3 notifications rule but when I go to alert definition it say "You have no notification rules with notification&lt;BR /&gt;triggers defined by alert definition.". Alerts are sent so one of the rule is used&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="szafa_0-1662101624770.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/97024i3AACC92D3055313C/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="szafa_0-1662101624770.png" alt="szafa_0-1662101624770.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="szafa_1-1662101643532.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/97025i69CC02BA9BE4AFD1/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="szafa_1-1662101643532.png" alt="szafa_1-1662101643532.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I'm going to open VMware case&lt;/P&gt;&lt;P&gt;Will update you if I'll get any update on it&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;&lt;P&gt;&amp;nbsp;&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;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2022 06:57:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROPs-alerts-being-sent-from-alerts-with-no-notification-set/m-p/2927026#M19172</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-09-02T06:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: vROps 7.5 app remote collector agent install fails</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-7-5-app-remote-collector-agent-install-fails/m-p/2911291#M19106</link>
      <description>&lt;P&gt;I manage to resolve that issue by removing the ARC adapter from VMware vRealize Application Manager Pack. The adapter was added the automatically and now I can install agent from UI.&lt;/P&gt;&lt;P&gt;Hope that this will help someone with similar problem&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 13:34:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-7-5-app-remote-collector-agent-install-fails/m-p/2911291#M19106</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-05-26T13:34:44Z</dc:date>
    </item>
    <item>
      <title>Re: Optimization Report - Oversized Virtual Machines filter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Optimization-Report-Oversized-Virtual-Machines-filter/m-p/2911278#M19105</link>
      <description>&lt;P&gt;I have solution for my problem. The metric that can be used to display just objects with enough collection points =&amp;gt;&amp;nbsp;&amp;nbsp;„vRealize Operations Generated|Availability” then filter sum is greater than 25000 which is about 90days. Maybe some one can benefit from that &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 12:45:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Optimization-Report-Oversized-Virtual-Machines-filter/m-p/2911278#M19105</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-05-26T12:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: vROps 7.5 app remote collector agent install fails</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-7-5-app-remote-collector-agent-install-fails/m-p/2909230#M19090</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;This is old thread but I have same issue with vROPs 8.6.2 and so far GSS don't know what is the resolution. They going to open PR now.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm suspecting that reinstalling proxy will fix issue but maybe someone has simple permanent solution for that issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2022 12:05:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-7-5-app-remote-collector-agent-install-fails/m-p/2909230#M19090</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-05-16T12:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: Optimization Report - Oversized Virtual Machines filter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Optimization-Report-Oversized-Virtual-Machines-filter/m-p/2909229#M19089</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5502585"&gt;@pashnal&lt;/a&gt;&amp;nbsp;but would like to automate it and schedule on monthly basis.&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2022 12:01:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Optimization-Report-Oversized-Virtual-Machines-filter/m-p/2909229#M19089</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-05-16T12:01:32Z</dc:date>
    </item>
    <item>
      <title>Optimization Report - Oversized Virtual Machines filter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Optimization-Report-Oversized-Virtual-Machines-filter/m-p/2908183#M19081</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;Just looking for quick and simple way to exclude VM's that have less that 3 months collected data from&amp;nbsp; "Optimization Report - Oversized Virtual Machines". Is there any property that I can use? Already tried "creation date" but it show when vm was created in vCenter not when vROps started monitoring it.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 10:03:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Optimization-Report-Oversized-Virtual-Machines-filter/m-p/2908183#M19081</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-05-10T10:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: vROps activate automated accions</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-activate-automated-accions/m-p/2893437#M18978</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5539267"&gt;@Davturo999&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;Maybe your action actions is not supported for automation =&amp;gt;&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-vRealize-Operations-Cloud/services/config-guide/GUID-8838DA32-0055-4BD2-9C0F-51A182857F51.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-vRealize-Operations-Cloud/services/config-guide/GUID-8838DA32-0055-4BD2-9C0F-51A182857F51.html&lt;/A&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;Reg.&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;Michał&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 14 Feb 2022 12:45:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROps-activate-automated-accions/m-p/2893437#M18978</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-02-14T12:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Proxies status offline after chaining vROPs certificates</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Cloud-Proxies-status-offline-after-chaining-vROPs-certificates/m-p/2893431#M18977</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/4464864"&gt;@crodpwc&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have checked my proxy in lab and cert location is below, but I'd recommend to open case with vmware to check why the procedure from KB83698 didn't work first.&amp;nbsp;&lt;/P&gt;&lt;P&gt;/etc/pki/tls/certs/ca-bundle.crt&lt;/P&gt;&lt;P&gt;Reg.&lt;/P&gt;&lt;P&gt;Michał&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 12:36:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Cloud-Proxies-status-offline-after-chaining-vROPs-certificates/m-p/2893431#M18977</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-02-14T12:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: vROPS 8.x and 2 Data Centers question</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROPS-8-x-and-2-Data-Centers-question/m-p/2893021#M18972</link>
      <description>&lt;P&gt;I can see 2 options :&lt;/P&gt;&lt;P&gt;- go back to HA cluster&lt;/P&gt;&lt;P&gt;- deploy witness node on VMware certified cloud provider (it is the cheapest option to have such setup if security will allow fort that &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; )&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that will help you.&lt;/P&gt;&lt;P&gt;I tested vROps CI in my test env without 3rd site for witness and that didn't go well when we lost one site and support was not able to recovery that cluster so it is clear for me that 3rd site for witness is a must&lt;/P&gt;&lt;P&gt;Hope that will help you make some good decisions for future.&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>Thu, 10 Feb 2022 16:26:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROPS-8-x-and-2-Data-Centers-question/m-p/2893021#M18972</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-02-10T16:26:34Z</dc:date>
    </item>
    <item>
      <title>Re: vROPS 8.x and 2 Data Centers question</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vROPS-8-x-and-2-Data-Centers-question/m-p/2893009#M18970</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/4268491"&gt;@jdheltneHPE&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had same requirements and after discussion with our VMware TAM the vROPs CI required 3rd site to work and cover all DR scenarios other wise you might encounter serious issues when you lose site with witness. You can find more details =&amp;gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;A href="https://docs.vmware.com/en/vRealize-Operations/8.6/com.vmware.vcom.refarch.doc/GUID-73E81793-74AF-4609-B75B-F7389492F61E.html" target="_blank"&gt;https://docs.vmware.com/en/vRealize-Operations/8.6/com.vmware.vcom.refarch.doc/GUID-73E81793-74AF-4609-B75B-F7389492F61E.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Reg.&lt;/P&gt;&lt;P&gt;Michał&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>Thu, 10 Feb 2022 15:26:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vROPS-8-x-and-2-Data-Centers-question/m-p/2893009#M18970</guid>
      <dc:creator>szafa</dc:creator>
      <dc:date>2022-02-10T15:26:06Z</dc:date>
    </item>
  </channel>
</rss>

