<?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>curtistcreps Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>curtistcreps Tracker</description>
    <pubDate>Sat, 25 Nov 2023 07:29:47 GMT</pubDate>
    <dc:date>2023-11-25T07:29:47Z</dc:date>
    <item>
      <title>Re: App Volumes Slow Initial Application Launch</title>
      <link>https://communities.vmware.com/t5/App-Volumes/App-Volumes-Slow-Initial-Application-Launch/m-p/2932148#M9030</link>
      <description>&lt;P&gt;I know this thread is a bit old, but did you ever get this resolved? I have also been dealing with this issue.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 19:30:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/App-Volumes-Slow-Initial-Application-Launch/m-p/2932148#M9030</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2022-10-05T19:30:05Z</dc:date>
    </item>
    <item>
      <title>Re: Horizon PowerCLI filtering Session ID's</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-PowerCLI-filtering-Session-ID-s/m-p/2913066#M97163</link>
      <description>&lt;P&gt;Jumped the gun too quick:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Modified the Write-Host line from:&lt;/P&gt;&lt;P&gt;Write-Host "$SessionUserName is logged into $MachineName, SessionID is $SessionId"&lt;/P&gt;&lt;P&gt;To:&lt;/P&gt;&lt;P&gt;Write-Host "$SessionUserName is logged into $MachineName, SessionID is" $SessionId.Id&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Worked like a charm!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 12:31:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-PowerCLI-filtering-Session-ID-s/m-p/2913066#M97163</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2022-06-07T12:31:48Z</dc:date>
    </item>
    <item>
      <title>Horizon PowerCLI filtering Session ID's</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-PowerCLI-filtering-Session-ID-s/m-p/2913064#M97162</link>
      <description>&lt;P&gt;I've searched all over the place trying to figure out why this doesn't work correctly. I am trying to display the list of Session IDs associated with each user with the Vmware.Hv.Helper module in PowerCLI. Syntax:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;$SessionSummaries = Get-HVLocalsession&lt;/P&gt;&lt;P&gt;ForEach($SessionSummary in $SessionSummaries)&lt;BR /&gt;{&lt;BR /&gt;$DesktopName= $sessionSummary.NamesData.DesktopName&lt;BR /&gt;$sessionID=$sessionSummary.ID&lt;BR /&gt;$MachineName=$SessionSummary.NamesData.MachineOrRDSServerDNS&lt;BR /&gt;$SessionUserName=$SessionSummary.NamesData.UserName -creplace '^[^\\]*\\', ''&lt;BR /&gt;Write-Host "$SessionUserName is logged into $MachineName, SessionID is $SessionId"&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;This is what it is returning:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_0-1654604320535.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95712iA02958F5C6C53A8A/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_0-1654604320535.png" alt="curtistcreps_0-1654604320535.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Based off what I have above in $SessionID = $SessionSummary.ID, I would expect to see the actual string of the IDs like what you would return by running (Get-HVLocalSession).ID:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_1-1654604511076.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95713i899DC52AC2D77BD4/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_1-1654604511076.png" alt="curtistcreps_1-1654604511076.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea what I'm missing? Seems that just printing the contents of the $SessionID variable returns the appropriate string that I am expecting, but the second it is fed to the array, it no longer works...&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>Tue, 07 Jun 2022 12:29:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Horizon-PowerCLI-filtering-Session-ID-s/m-p/2913064#M97162</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2022-06-07T12:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: App Volumes 2111 - Apps on demand</title>
      <link>https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/m-p/2908226#M8897</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/3120093"&gt;@julatoski&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you so much for your quick response on this. Luckily I just upgraded our AppVolumes instance to 2203, so I was able to follow your recommendations and get this working!&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 12:59:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/m-p/2908226#M8897</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2022-05-10T12:59:16Z</dc:date>
    </item>
    <item>
      <title>Re: App Volumes 2111 - Apps on demand</title>
      <link>https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/m-p/2908029#M8889</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2964843"&gt;@Micheal_A&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is exactly what I found in testing. Unfortunately, we have DEM rules that apply shortcuts to the users' desktops (depending on AD security group membership) with the runOnceSpecial parameter. Reason for that is that our users throw a fit when they can't customize their desktop shortcuts to their liking. When creating the AppVol package, I manually removed the desktop icon but made sure to copy the path and the arguments in the shortcut as you have shown above. I then created a new DEM shortcut rule for the desired application with those parameters. When logging in, DEM applies the shortcut, and the on-demand app launches fine with no issues. The problem is presented when users close the application and attempt to use the same desktop shortcut to launch the application again:&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="curtistcreps_0-1652104630826.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95172i693706B7CA8DCECD/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_0-1652104630826.png" alt="curtistcreps_0-1652104630826.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that once the volume is attached, the agent cannot run the specified shortcut parameters again. However, launching from the start menu still works fine. Not necessarily a deal-breaker, but it does unfortunately cause the end user to lose some control over their desktop shortcuts since the on-demand apps will always require the shortcut to be provisioned by the AppVolumes package rather than a separate DEM configuration.&lt;/P&gt;&lt;P&gt;Still really enjoying apps on-demand. There are plenty of use cases for it in our environment, but it would be nice to see some flexibility for those of us who want to dynamically assign shortcuts in a future update. In my ideal environment, I would just force the same shortcuts for every user at every login, making this a non issue. But unfortunately, as stated before, our end users “require” the ability to modify the shortcuts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 14:09:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/App-Volumes-2111-Apps-on-demand/m-p/2908029#M8889</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2022-05-09T14:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: DEM folder structure changes under "Personalization"</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/DEM-folder-structure-changes-under-quot-Personalization-quot/m-p/2896283#M96437</link>
      <description>&lt;P&gt;Quick follow up to this:&lt;/P&gt;&lt;P&gt;I ended up doing the exact thing that I mentioned in the article. I ended up creating the new folder structure and duplicating the existing configuration files. Only catch was, I had to disable DirectFlex on the new ones since you can't have the same set of executables enabled for DirectFlex on two configuration files (otherwise when you validate DirectFlex config in DEM it will show conflicts and the rules wont run right). Only drawback doing it this way was that while I waited for about a week for users to log in / out to have the new configuration structure generated in their profiles, the logon times were increased by a fair amount due to the new configuration files importing data at logon. After everyone had generated the new configurations, I changed the new ones back to use DirectFlex and reitred the old ones.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I still think VMware needs a more streamlined solution to make things like this easier. I reached out to support to inquire if there was a better way of accomplishing this, but they did not know of anyway natively to accomplish this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Mar 2022 14:26:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/DEM-folder-structure-changes-under-quot-Personalization-quot/m-p/2896283#M96437</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2022-03-02T14:26:57Z</dc:date>
    </item>
    <item>
      <title>DEM folder structure changes under "Personalization"</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/DEM-folder-structure-changes-under-quot-Personalization-quot/m-p/2883852#M95715</link>
      <description>&lt;P&gt;I've been managing a Horizon environment for about the past three years at my organization. That includes managing DEM. When I first became the primary "VDI guy", I had to build off of what had already been put in place. With that said, DEM (though still needing some work) has been something I've focused in on a lot more lately in trying to better understand / polish up to better fit our organizations needs. It also is a bit unorganized partially due to the last person who managed it. I would like to re-organize some of the items in the "Personalization" section.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using a mix of DirectFlex and rules that are processed at logon and logoff (I would argue 70% DirectFlex). Knowing how the DEM agent on the VM reads the data from the DEM Config location on the DEM server and processes the rules, I decided to do a small test to see if changing the directory structure would affect the export of user data that already had an active session running when I changed the rules. It appears that it did...&lt;/P&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_1-1639651545511.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/92647i389FABEF68BB1269/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_1-1639651545511.png" alt="curtistcreps_1-1639651545511.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My Adobe Reader configuration is DirectFlex enabled (data is exported at logoff). I want to move it to the "Adobe" folder I created as shown above. I have a test user that is currently logged into a non persistent session at the time I move the configuration for Adobe Reader to that new folder. I open Adobe Reader as the test user, and all of the customizations I set are imported via DirectFlex as expected. After logging off, the data is exported still to the original path above \\DEM_User_Archive_Path\Applications\Standard\Adobe Reader.ini. The problem is, the next time I log on as that test user, since the folder path for the Adobe Reader configuration has been changed, DirectFlex no longer imports from&amp;nbsp;\\DEM_User_Archive_Path\Applications\Standard\Adobe Reader.ini, but rather attempts to import from the new path&amp;nbsp;\\DEM_User_Archive_Path\Applications\Standard\Adobe\Adobe Reader.ini. Since the new path does not contain any of the test users data, it does not import the settings.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this expected behavior of DirectFlex? My thought is that if were to make a configuration change while users were already logged in that once they logged off, the DEM agent would be able to read the changes and export the DirectFlex data to the new location, but it doesn't seem to be the case...It just seems odd that rule changes like that would require the user to log out completely and back in again to process the changes. You can see why this is problematic though. I've got nearly 40 users that use these configurations. It would be a disaster to re-organize the folder structure, only to have users logout and still have DirectFlex export the data to the old paths. Next time they log in, any customizations via DirectFlex would be gone and would have to be moved manually in their Profile Archive. Not to mention it would bombard the helpdesk with calls...&lt;/P&gt;&lt;P&gt;Does anyone know a way to be able to re-organize the folder structure without causing such problems? My only thought is create the folders, duplicate the rules into those folders and wait a few days for users to log in / out to generate the DirectFlex data. Then after several days just retire the old rules.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&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, 16 Dec 2021 10:59:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/DEM-folder-structure-changes-under-quot-Personalization-quot/m-p/2883852#M95715</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-12-16T10:59:55Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Hybrid Join...</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Azure-Hybrid-Join/m-p/2873467#M95163</link>
      <description>&lt;P&gt;I know it's been a little over a year, but I wanted to follow up on this with the permanent solution that I have working in our environment. Most of what solved the issue was related to the new Computer Environment Startup and Shutdown tasks settings in DEM 2106. Though I know not everyone uses DEM as a profile manager, in the event you do it should help you out.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Originally, I was relying on normal group policy to ensure successful AAD joins. I accomplished this by using startup and logon scripts that utilized the dsregcmd /join command. After upgrading DEM to version 2106, I started to utilize the Computer Environment ADMX settings to move away from normal GPOs where I could (logon times were still not nearly as good as they could have been). In the process of doing so, I discovered the Startup and Shutdown tasks. I created a Startup task that includes dsregcmd /join and a Shutdown task that inlcudes dsregcmd /leave. I also for good measure still have a &lt;EM&gt;&lt;STRONG&gt;logon&lt;/STRONG&gt;&lt;/EM&gt; task that runs the /join command,&amp;nbsp;&lt;/P&gt;&lt;P&gt;After implementing these rules, I would clear out a large number of instant clone VMs at once from a test pool whilst simultaneously checking the Devices section of our Azure tenant. Sure enough, once the VM's were deleted, so were the devices in Azure. Once the VM's started to start up, they all were registered again with a valid timestamp and ID. No duplicates neither! I could confirm when logging in / out of VMs with a test account that each time dsregcmd /status showed that the machine was AAD joined. The only thing that still seems a bit off at times (but not near enough for it be a major issue), is that there are times where the machine is registered but the PRT for the user does not roam at logon correctly, which occasionally invokes a logon to Office 365 / Teams.&amp;nbsp;&lt;/P&gt;&lt;P&gt;As I mentioned before, this isn't really helpful for those not using DEM as their profile manager in Horizon. But if you are, I strongly suggest giving this a try. Much more reliable, no more duplicated Azure objects, random non AAD joined logins, etc.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2021 13:29:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Azure-Hybrid-Join/m-p/2873467#M95163</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-10-21T13:29:18Z</dc:date>
    </item>
    <item>
      <title>Office 365 (x86) Preview Handler issue in AppVolumes 4.1 (2006)</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Office-365-x86-Preview-Handler-issue-in-AppVolumes-4-1-2006/m-p/2873453#M8639</link>
      <description>&lt;P&gt;I've been struggling with an issue with the preview handlers for the 32bit version of Office 365 when provisioned in AppVolumes 4.1 (2006). It seems that the provisioning process works fine as expected. All of the applications in the suite launch without issue, but users have pointed out that the preview handlers are completely broken in Outlook. When a user attempts to preview any sort of Office related attached file in the previewer (Word, Excel, PowerPoint, etc) they get this error:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_0-1634814925274.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/91648i81618FE8A773A760/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_0-1634814925274.png" alt="curtistcreps_0-1634814925274.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;To further complicate it, if they attempt to open the attached file in Outlook the following occurs (just used an attached word doc in an email as an example):&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_2-1634815112399.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/91650iAD0421C14B4B4543/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_2-1634815112399.png" alt="curtistcreps_2-1634815112399.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&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="curtistcreps_1-1634815079035.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/91649i6E8491B30347C0CF/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_1-1634815079035.png" alt="curtistcreps_1-1634815079035.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've read around a lot this week. Most of these issues when searched return results for older solutions that involved versions of AppVolumes below 2.12 before provisioning Office365 products in Writables or Appstacks was supported. So far I have done the following:&lt;/P&gt;&lt;P&gt;* Updated the provisioning VM to the latest build of Windows 10&lt;/P&gt;&lt;P&gt;* Attempted to re-provision the Appstack several different times&lt;/P&gt;&lt;P&gt;* Created GPO that disables Office 365 updates completely and disables the functionality to update for the end user&lt;/P&gt;&lt;P&gt;* Deployed the most recent version of Office 365 (x86) in the Appstack&lt;/P&gt;&lt;P&gt;* Ensured appropriate .NET and vcredist libraries are installed on the golden image needed for Office 365&lt;/P&gt;&lt;P&gt;* Confirmed that the preview handlers are properly set in the registry&lt;/P&gt;&lt;P&gt;&amp;nbsp;Originally, I had Office installed on the golden image. I installed it the same way I am provisioning it in the Appstack (ClicktoRun with an xml configured for shared licensing). The preview handlers seemed to work fine when installed directly on the golden image. The primary reason I am forced to move Office to an Appstack is due to the specific licensing needs of our organization. We are planning a hybrid of Cloud mail in Azure and on Premise Exchange depending on the licensing needs per user. Some need an E3, while others only need access to on prem exchange. For on prem, I will be creating an Appstack with Office 2016 Standard (x86). So having appstacks that work are my only option. It's worth noting that we are also required to use a 32bit version due to some Macros developed internally that are not supported yet with 64bit.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen anything like this? So far, this is the only issue that has been reported to me by users after provisioning the Appstack to them. The temporary work around is just to copy any Office related attachment locally and open it that way. Strange enough, the preview handlers seem to work fine for other products like Adobe Reader?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2021 11:40:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Office-365-x86-Preview-Handler-issue-in-AppVolumes-4-1-2006/m-p/2873453#M8639</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-10-21T11:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: Adobe Acrobat DC Pro 2017 Licensing in AppVolumes 4</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Adobe-Acrobat-DC-Pro-2017-Licensing-in-AppVolumes-4/m-p/2869294#M8617</link>
      <description>&lt;P&gt;Thanks for the response.&lt;/P&gt;&lt;P&gt;This issue ended up resolving itself in the end. We actually switched to named licensing for all Adobe products in our organization. We had so many different versions out there that management agreed it was time to make the switch. As for this, I will test it out, as I don't think I have the HKLM keys you listed below set the way you do.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Sep 2021 11:50:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Adobe-Acrobat-DC-Pro-2017-Licensing-in-AppVolumes-4/m-p/2869294#M8617</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-09-29T11:50:36Z</dc:date>
    </item>
    <item>
      <title>Adobe Acrobat DC Pro 2017 Licensing in AppVolumes 4</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Adobe-Acrobat-DC-Pro-2017-Licensing-in-AppVolumes-4/m-p/2859571#M8560</link>
      <description>&lt;P&gt;I've been spinning my wheels for a while on this and have read around quite a bit to get an idea of other people's experience with it. I figured for the sake of it, I would post in communities. Our company has a paid volume license of Adobe Acrobat 2017 Pro DC that we originally used with AppVolumes 4 on a Windows 10 1809 floating pool. The serialize deployment article is what we originally used to accomplish this and everything worked as expected:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.adobe.com/devnet-docs/acrobatetk/tools/VirtualizationGuide/vmware.html" target="_blank"&gt;https://www.adobe.com/devnet-docs/acrobatetk/tools/VirtualizationGuide/vmware.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Roughly a year later, I am working on getting users moved over to a 1909 floating pool. When doing so, the users entitled to the Adobe AppVolume started calling regarding an error every time they would launch it:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_0-1627417343779.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/90331i3CE30DB59557187A/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_0-1627417343779.png" alt="curtistcreps_0-1627417343779.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I thought I would re-create the Appvolume on a new 1909 VM for good measure using the same process documented in the Adobe article. However, the result was still the same. Same error each time a user tries to launch Adobe.&amp;nbsp;&lt;/P&gt;&lt;P&gt;From what I have read, it seems that some serial deployments are being phased out, and it seems that with older versions of Adobe that use volume licensing are starting to run into this problem. Can anyone confirm this? If so, I assume that this is more of a push towards named licensing on Adobe's end.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help is appreciated!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 20:25:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Adobe-Acrobat-DC-Pro-2017-Licensing-in-AppVolumes-4/m-p/2859571#M8560</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-07-27T20:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCLI script to send message to all desktops in a specific pool</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/PowerCLI-script-to-send-message-to-all-desktops-in-a-specific/m-p/2845198#M93866</link>
      <description>&lt;P&gt;Thanks for the quick response.&lt;/P&gt;&lt;P&gt;Still no luck. I can confirm that I am on v. 5.1.17763.1007 of PS. Seems that v7 is not plausible (at least from the last time I tried it with PowerCLI due to .NET incompatibilities):&lt;/P&gt;&lt;P&gt;Now I'm seeing this:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="curtistcreps_0-1620054200061.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/88584i5D43A7AF01A1DF25/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_0-1620054200061.png" alt="curtistcreps_0-1620054200061.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you recall what version of PS you used at the time of writing this article?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 15:04:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/PowerCLI-script-to-send-message-to-all-desktops-in-a-specific/m-p/2845198#M93866</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-05-03T15:04:09Z</dc:date>
    </item>
    <item>
      <title>PowerCLI script to send message to all desktops in a specific pool</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/PowerCLI-script-to-send-message-to-all-desktops-in-a-specific/m-p/2845189#M93864</link>
      <description>&lt;P&gt;I am working on a PowerCLI script that will filter all sessions within a specific Horizon pool, send a warning message to those filtered sessions via the Session_SendMessage API call, then wait a certain amount of time before logging them off. The filtering and logging off portion does not seem to be the issue, but rather the Session_SendMessage portion. Here is what I have so far:&amp;nbsp;&lt;/P&gt;&lt;P&gt;Connect-HVServer &amp;lt;server&amp;gt;&lt;BR /&gt;$Services1 = $Global:DefaultHVServers.ExtensionData&lt;BR /&gt;$Sessions = (Get-HVLocalSession).NamesData&lt;BR /&gt;ForEach ($Session in $Sessions) {&lt;BR /&gt;IF ($Session.DesktopName -eq "TEST") {&lt;BR /&gt;Write-Host `n "Connection to TEST found" $Session.Username }&lt;BR /&gt;$Services1.Session.Session_SendMessage($session.id, "INFO", "Your session will be logged out in 10 minutes for maintenance. Please save your work!")&lt;BR /&gt;}&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order to confirm that $Sessions variable was working correctly I threw in the the Write-Host portion. In the TEST pool I have specified, I do get a return (there is only one session logged into that pool at the moment). The problem is what follows after the API call:&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="curtistcreps_0-1620052410293.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/88582iD3629A1214858849/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="curtistcreps_0-1620052410293.png" alt="curtistcreps_0-1620052410293.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not entirely sure what I'm doing wrong...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 14:39:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/PowerCLI-script-to-send-message-to-all-desktops-in-a-specific/m-p/2845189#M93864</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2021-05-03T14:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Hybrid Join...</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Azure-Hybrid-Join/m-p/2301214#M61055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have struggled with this for the last couple of months as well. vBritinUSA is right when they say that it isn't supported. "Technically" not supported, rather. I do have it working in my environment. The problem is consistency with the instant clone VM's being registered. Sometimes when a user logs into a floating pool, they might be assigned a VM that didn't successfully join AzureAD. This obviously causes a ton of problems with Outlook due to the fact that a proper license token cannot be acquired if the machine is not AzureAD joined. In our case, it also causes issues with Teams. By policy, we don't allow non company assets to log into anything 365 related. So if the instant clone VM is not AzureAD joined, Teams will fail to login and tell the user that "Personal devices are not permitted". Only way I have found to remedy the issue is have the user log out and back in in hopes of getting a VM that registered successfully when vCenter provisioned it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In terms of "how" I got it to work, the key is to make sure your Golden Image VM is not already AzureAD Joined. I have always published my Golden Image snapshots to a pool while they were domain joined. As a byproduct of that, the Golden Image was also AzureAD joined. This led me to start experimenting with leaving my Golden Image non domain joined when provisioning to a pool. I found collectively, there are less problems (in my case) in general doing it this way. I know people will debate back and forth whether a non-domain joined vs domain joined Golden Image is the "right way", but in this specific instance where AzureAD comes into play, it seems to be a requirement that your Golden Image VM is non-domain joined and not already AzureAD joined.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's also important to note that I also had to do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Created a &lt;STRONG&gt;startup&lt;/STRONG&gt; task that runs "dsregcmd /join" on the Golden Image VM&lt;/P&gt;&lt;P&gt;- Created a &lt;STRONG&gt;logon&lt;/STRONG&gt; task in DEM that runs the same command at logon of the VM (Not sure if this is actually required but I have it for good measure)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This guide directly from Microsoft regarding this topic was helpful:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.microsoft.com/en-us/azure/active-directory/devices/howto-device-identity-virtual-desktop-infrastructure" title="https://docs.microsoft.com/en-us/azure/active-directory/devices/howto-device-identity-virtual-desktop-infrastructure"&gt;Device identity and desktop virtualization - Azure Active Directory | Microsoft Docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As previously stated, with all of this in place, I seem to get about 70% consistency with my instant clone VM's being AzureAD joined. The other 30% of the time end users call claiming "Outlook says it isn't activated" or "Teams says it can't sign in". And of course every time the culprit is always the VM not being AzureAD joined. Like most people, I search these forums all the time and have seen several instances of people claiming they've got it working perfectly in their environment. Not sure how, but I hope Microsoft comes up with a more reliable solution in the near future, as this does get tedious and tends to annoy the end users with the issues it causes...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Sep 2020 11:26:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Azure-Hybrid-Join/m-p/2301214#M61055</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2020-09-16T11:26:27Z</dc:date>
    </item>
    <item>
      <title>AzureAD Hybrid in Non Persistent Desktop Environment</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/AzureAD-Hybrid-in-Non-Persistent-Desktop-Environment/m-p/2295478#M89479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just wanting to get opinions on this. I've got a domain environment that is setup as an AzureAD Hybrid. We are also using instant clone technology in Horizon. I have not been able to reliably get instant clones to register with the AzureAD domain since we switched to it. This obviously causes a ton of problems with users on Office 365 and Microsoft Teams, specifically because our Azure policies prevent users from signing into those applications with their domain accounts if the machine is not AzureAD registered. Arguably about 70% of the time we see users get a joined VM when logging into Horizon. The other 30% users end up calling due to Office 365 needing activated or Teams not wanting to sign in due to the non domain status. I have configured group policy and a startup task on my golden image to implement the "dsregcmd /join" command, but it still doesn't seem consistent. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else found a way to reliably get VMs to register with an AzureAD domain when vCenter provisions them to a pool?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Sep 2020 21:33:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/AzureAD-Hybrid-in-Non-Persistent-Desktop-Environment/m-p/2295478#M89479</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2020-09-03T21:33:05Z</dc:date>
    </item>
    <item>
      <title>Microsoft Teams in Non Persistent environment with AzureAD Hybrid</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Teams-in-Non-Persistent-environment-with-AzureAD/m-p/2291851#M89349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As of now, I have successfully been able to get Microsoft Teams provisioned via two methods. AppVolumes Application and installed on the golden image. Along with DEM, I am able to persist settings correctly. All seems to work well. The only issue I am still experiencing and have been struggling with since day one with Teams is the known issues revolving around AzureAD Hybrid environments and instant clone VM's not registering correctly. This causes the following error more often than not when users log in and try to launch Teams:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Capture.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/22662i9411E652DFC7C43B/image-size/large?v=v2&amp;amp;px=999" role="button" title="Capture.PNG" alt="Capture.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've read around online and found a few good resources, but have still not been able to get any consistency out of Teams when it comes to this issue. So far, my golden image has never been joined to the AzureAD domain. I have also implemented some startup / logoff scripts that implement the "dsregcmd /leave" and "dsregcmd /join" commands as recommended by several different articles I've come across, but I am still having no luck. Has anyone else using an AzureAD Hybrid setup experienced this? If so, is there any solution, or will I have to wait until Horizon 8 releases and "officially supports" Teams?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help is appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Aug 2020 15:48:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Microsoft-Teams-in-Non-Persistent-environment-with-AzureAD/m-p/2291851#M89349</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2020-08-31T15:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: Writable Volumes for Outlook Indexing</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Writable-Volumes-for-Outlook-Indexing/m-p/2283114#M1557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;An update: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I ended up transitioning over to the FSLogix route as many other people reported success with it. In all my testing I did with writable volumes, I just found that they were unreliable more so whenever PST's are attached in a mail profile and the search index needs to be roamed. We use very small mailbox sizes in our environment, 2GB for all users running Exchange 2010 (Migrating to 365 later this year). Naturally PST's are the only remedy for storing email for the end users and can't be avoided. We allocate enough storage per user (each has their own home drive) that they are able to store PST's on. Problem is, PST's that are referenced on UNC locations also cause indexing issues. I couldn't justify spending more time trying to figure out why writable volumes would cause the search index to rebuild at every log on, take massive amounts of time per user depending on the size of those PST's for Outlook to finish indexing and also prevent users from searching in Outlook at all while they waited for indexing to finish. FSLogix works well so far, as we have been using it for about three weeks now with no reported issues yet. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Mar 2020 19:50:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Writable-Volumes-for-Outlook-Indexing/m-p/2283114#M1557</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2020-03-11T19:50:52Z</dc:date>
    </item>
    <item>
      <title>Writable Volumes for Outlook Indexing</title>
      <link>https://communities.vmware.com/t5/App-Volumes/Writable-Volumes-for-Outlook-Indexing/m-p/2283111#M1554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Per the following article, I have successfully configured a writable app volume that captures a user's OST and indexing upon logon: &lt;A href="https://kb.vmware.com/s/article/2149799" title="https://kb.vmware.com/s/article/2149799"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I performed the following steps as instructed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Configure the writable per the above article&lt;/P&gt;&lt;P&gt;2. Assign users to writable&lt;/P&gt;&lt;P&gt;3. Log in and re-create Outlook profile&lt;/P&gt;&lt;P&gt;4. Begin indexing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can confirm that I am seeing the OST in the default path of the writable (as specified in DEM: C:\Snapvolumestemp\) And from what I can tell, any PSTs being indexed are also being written to that location. The issue I am seeing now is that whenever a user logs back in, Outlook begins indexing again even though the data still exists in C:\Snapvolumestemp and I am also able to confirm that the writable has status "attached" in the AppVolumes manager. I can also verify that the the same path in the Outlook Indexing options exists even after indexing starts again on logon:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/17635i8453EE2A53430B59/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else seen this behavior before? Is there something that I'm not configuring correctly in Outlook that is causing it to re-index? We are using non-persistent desktops in our environment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Feb 2020 16:21:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/Writable-Volumes-for-Outlook-Indexing/m-p/2283111#M1554</guid>
      <dc:creator>curtistcreps</dc:creator>
      <dc:date>2020-02-24T16:21:25Z</dc:date>
    </item>
  </channel>
</rss>

