<?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>rodderix Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>rodderix Tracker</description>
    <pubDate>Fri, 24 Nov 2023 04:43:27 GMT</pubDate>
    <dc:date>2023-11-24T04:43:27Z</dc:date>
    <item>
      <title>Freestyle Orchestrator after Enterprise RESET</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Freestyle-Orchestrator-after-Enterprise-RESET/m-p/2985605#M19144</link>
      <description>&lt;P&gt;Hi. We are leveraging a Windows Provisioning Freestyle Orchestrator for first time setup and installation of resources with the order needed and the conditions we need where applicable. It's working pretty fine but the problem comes when we use Enterprise Reset. The workflow doesn't reapply all the resources after the reset and the device remains in a inconsistent state where apps don't get reinstalled even if we force a rerun of the workflow because it says they are already installed.&lt;/P&gt;&lt;P&gt;I know that if i assign the apps directly to the smart group with auto install, they will get automatically reinstalled after an enterprise reset but then we would lose the benefits of using an Orchestrator besides that Vmware doesn't recommend using both assignments.&lt;/P&gt;&lt;P&gt;So, do you know a way to force a complete rerun of the Freestyle Orchestrator after an enterprise reset?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 04:34:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Freestyle-Orchestrator-after-Enterprise-RESET/m-p/2985605#M19144</guid>
      <dc:creator>rodderix</dc:creator>
      <dc:date>2023-09-08T04:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: Find all computers with Unknown bios password and capturing Status codes</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Find-all-computers-with-Unknown-bios-password-and-capturing/m-p/2961670#M18511</link>
      <description>&lt;P&gt;You could use sensors for this. But without&amp;nbsp; Intelligence there is no way to have a report as far as I know.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2023 02:06:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Find-all-computers-with-Unknown-bios-password-and-capturing/m-p/2961670#M18511</guid>
      <dc:creator>rodderix</dc:creator>
      <dc:date>2023-03-30T02:06:01Z</dc:date>
    </item>
    <item>
      <title>Re: Autopilot OOBE Enrollment not working</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Autopilot-OOBE-Enrollment-not-working/m-p/2961508#M18501</link>
      <description>&lt;P&gt;Thanks. We Also opened a support ticket with Vmware but still no news.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2023 09:59:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Autopilot-OOBE-Enrollment-not-working/m-p/2961508#M18501</guid>
      <dc:creator>rodderix</dc:creator>
      <dc:date>2023-03-29T09:59:13Z</dc:date>
    </item>
    <item>
      <title>Autopilot OOBE Enrollment not working</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Autopilot-OOBE-Enrollment-not-working/m-p/2961440#M18493</link>
      <description>&lt;P&gt;Hi. We have a working shared SaaS Environment and already made the AzureAD integration as the documentation says using ONLY the "Airwatch by VMWare" Enterprise APP in the Azure Portal.&lt;/P&gt;&lt;P&gt;We've made all the configurations and pasted the URL's. But when we test, we receive an error "invalid_resource" and Error AADSTS50001 telling&amp;nbsp; that it's not possible to reach the Terms of Use URL. Already double checked the tenant ID, URLs and configurations but to no avail.&lt;/P&gt;&lt;P&gt;Also cannot find a log nowhere in the device as to see the full error message.&lt;/P&gt;&lt;P&gt;Any ideas? Thanks&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rodderix_0-1680038484864.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/100747iEB7D6B9F350E8E14/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="rodderix_0-1680038484864.png" alt="rodderix_0-1680038484864.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2023 02:12:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Autopilot-OOBE-Enrollment-not-working/m-p/2961440#M18493</guid>
      <dc:creator>rodderix</dc:creator>
      <dc:date>2023-03-29T02:12:11Z</dc:date>
    </item>
    <item>
      <title>Onboarding Windows 10 with staging account</title>
      <link>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Onboarding-Windows-10-with-staging-account/m-p/2949961#M18189</link>
      <description>&lt;P&gt;We are trying to enroll existent Windows 10 computers using an staging account with the ASSIGNTOLOGGEDINUSER=Y.&lt;/P&gt;&lt;P&gt;It works fine but if the computer is not conected to the vpn or to the corporate network, the computer remains assigned to the staging user instead of the logged in user.&lt;/P&gt;&lt;P&gt;Is there any way to avoid the need of a vpn/corporate network to be able to switch from the staging user to the logged-in user?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sat, 21 Jan 2023 05:50:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Workspace-ONE-Discussions/Onboarding-Windows-10-with-staging-account/m-p/2949961#M18189</guid>
      <dc:creator>rodderix</dc:creator>
      <dc:date>2023-01-21T05:50:05Z</dc:date>
    </item>
  </channel>
</rss>

