<?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>rrizzi3821 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>rrizzi3821 Tracker</description>
    <pubDate>Sat, 25 Nov 2023 11:47:25 GMT</pubDate>
    <dc:date>2023-11-25T11:47:25Z</dc:date>
    <item>
      <title>Re: UEM not backing up Office products</title>
      <link>https://communities.vmware.com/t5/Dynamic-Environment-Manager/UEM-not-backing-up-Office-products/m-p/2943307#M7863</link>
      <description>&lt;P&gt;I just spent about six hours debugging something I believe occurs quite often with DEM versions 2203 through 2209 (they are the only versions I have checked so far) for new administrators, that will really cause you some frustration if you run into the issues I have run into while performing a POC for DEM with App Volumes 4.x and VMware Horizon 8 with non-persistent desktops.&lt;/P&gt;&lt;P&gt;This is related to most of this thread, &lt;STRONG&gt;and&lt;/STRONG&gt; the documentation beginning on or around p. 70 titled "&lt;U&gt;&lt;EM&gt;VMware Dynamic Environment&lt;/EM&gt;&lt;/U&gt;&lt;BR /&gt;&lt;U&gt;&lt;EM&gt;Manager Administration Guide&lt;/EM&gt;&lt;/U&gt;" retrieved on December 11, 2022 from &lt;A title="VMware Dynamic Environment Manager Administration Guide VMware Dynamic Environment Manager 2103" href="https://docs.vmware.com/en/VMware-Dynamic-Environment-Manager/2103/dynamic-environment-manager2103-adminguide.pdf" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-Dynamic-Environment-Manager/2103/dynamic-environment-manager2103-adminguide.pdf&lt;/A&gt;. I checked the docs for DEM 2203, 2206 and 2209 as of this writing and they are all the same (not sure about the page numbers though).&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Using 32-Bit Path to Program Files on 64-Bit Systems&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;You can convert a 32-bit Program Files folder path to be used on a 64-bit system.&lt;/SPAN&gt;&lt;SPAN class=""&gt; Several conditions refer to paths in the Program Files folder. If you specify a path starting with&lt;/SPAN&gt;&lt;SPAN class=""&gt; C:\Program Files&lt;/SPAN&gt;&lt;SPAN class=""&gt;,&lt;/SPAN&gt;&lt;SPAN class=""&gt; C:\Program Files (x86)&lt;/SPAN&gt;&lt;SPAN class=""&gt;, or a localized equivalent, a button appears in front of the path. If you click it, you can convert the start of the path to&lt;/SPAN&gt;&lt;SPAN class=""&gt; %ProgramFiles%&lt;/SPAN&gt;&lt;SPAN class=""&gt; and resolve that variable to the 32-bit Program Files folder on 64-bit systems.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;What puzzles me about the above documentation is that you would think the path-expansion by the FlexEngine would be automatic, but it does not appear to be the case. I have only worked with 64-bit apps thus far on 64-bit Windows 10 Enterprise desktops.&lt;/P&gt;&lt;P&gt;What they do not tell you is &lt;STRONG&gt;if&lt;/STRONG&gt; you use an environment variable in the path, &lt;STRONG&gt;then&lt;/STRONG&gt; you &lt;STRONG&gt;must&lt;/STRONG&gt; verify if your application is stored in c:&lt;FONT face="courier new,courier"&gt;\Program Files (x86)\&lt;/FONT&gt; (32-bit app on a 64-bit system), or if it was installed into c:&lt;FONT face="courier new,courier"&gt;\Program files\&lt;/FONT&gt; (64-bit app on a 64-bit system). The reason is that your exports &lt;EM&gt;will never occur&lt;/EM&gt; if the FlexConfig engine cannot find the app in that path shown. The three different settings for "Export Moment" on the DirectFlex tab make not difference here either.&lt;/P&gt;&lt;P&gt;In other words, the trigger to facilitate the export operation(s) will never happen as evidenced in the [DEBUG] version of the logs. I profiled Notepad++ and even though it is rather simple as to what the export (&lt;FONT face="courier new,courier"&gt;[IncludeFolderTrees] of &amp;lt;AppData&amp;gt;\Notepad++&lt;/FONT&gt;) , I could not find any source that clearly indicates that I had to disable the check mark that seems to appear by DEFAULT in DEM 2203, to tell the FlexEngine that the 64-bit version was installed and profiled. This 32 bit versus 64 bit option is somewhat buried under the DirectFlex tab, in the Executables Frame near the middle half of the dialog box. If you see "32" and then &lt;FONT face="courier new,courier"&gt;%ProgramFiles%&lt;/FONT&gt; and your app is 64-bit, then this is very likely to be at least ONE of the issues preventing the FlexEngine from exporting your configured settings to capture upon log off or application close, etc.&lt;/P&gt;&lt;P&gt;This seems very counterintuitive when profiling applications using the DEM profiling tool, since it absolutely should know which path the application was installed into. Please correct my post here if I am wrong about this and I will EDIT this post to be correct. I've gone back and forth for over six hours to track this issue down and it was affecting all my profiles, and I'm only one week into learning DEM soup to nuts, so that might explain some things here.&lt;/P&gt;&lt;P&gt;I hope this helps someone save some time, and I hope that VMware decides to add some wording to the documentation to point this out.&lt;/P&gt;</description>
      <pubDate>Sun, 11 Dec 2022 21:06:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Dynamic-Environment-Manager/UEM-not-backing-up-Office-products/m-p/2943307#M7863</guid>
      <dc:creator>rrizzi3821</dc:creator>
      <dc:date>2022-12-11T21:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: vcenter 7 appliance is running low on memory (12GB)</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vcenter-7-appliance-is-running-low-on-memory-12GB/m-p/2899797#M92930</link>
      <description>&lt;P data-unlink="true"&gt;Reply to &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;schudakov&lt;/SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;This worked for me too. A Default 7.03 vcsa produced the same error within just a few hours and remained for 7 weeks. I even added 2 GB of vRAM before making the changes (and waiting), and still "low on memory." Within 3 minutes of making the changes above, problem solved.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It appears to be an allocation problem, and these commands above reserve/allocate more RAM to these two services.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Mar 2022 22:46:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vcenter-7-appliance-is-running-low-on-memory-12GB/m-p/2899797#M92930</guid>
      <dc:creator>rrizzi3821</dc:creator>
      <dc:date>2022-03-21T22:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Different brands of PCIe SSDs</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Different-brands-of-PCIe-SSDs/m-p/400767#M116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check &lt;A href="http://partnerweb.vmware.com/comp_guide2/search.php?action=base&amp;amp;deviceCategory=san" title="http://partnerweb.vmware.com/comp_guide2/search.php?action=base&amp;amp;deviceCategory=san"&gt;VMware Compatibility Guide: Storage/SAN Search&lt;/A&gt; where Partner Name = "Fusion-io, Inc." and Product Release Version = "ESXi 5.5 U1" as that is the only version of ESXi that works properly with VSAN 5.5. We might be using exactly the same PCIe SSD cards you have, since they sound about the same size and they work perfectly (plus they are on the HCL).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-- Robert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Oct 2014 04:27:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Different-brands-of-PCIe-SSDs/m-p/400767#M116</guid>
      <dc:creator>rrizzi3821</dc:creator>
      <dc:date>2014-10-26T04:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot change font size View 4.5 client</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Cannot-change-font-size-View-4-5-client/m-p/1223707#M30055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just went through all of this today with a clean, 2008 R2 AD, Win 7 Pro x86, View 5.2.0 and still cannot adjust the font size. I followed your suggestion, and what is interesting about it is that the &lt;EM&gt;User Configuration/Policies/Administrative Templates/Control Panel/Personalization/Prohibit selection of visual font size&lt;/EM&gt; setting only applies to "Windows Server 2003, Windows XP, and Windows 2000 operating systems only" according to the Group Policy Editor in Windows Server 2008 R2. I confirmed this when I modeled the effect of the policy setting against a Windows 7 target computer, because it will not apply it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore, there must be something else you did, or some "other" policy settings that makes this work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 19:39:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Cannot-change-font-size-View-4-5-client/m-p/1223707#M30055</guid>
      <dc:creator>rrizzi3821</dc:creator>
      <dc:date>2013-06-12T19:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: View, Windows 7, PCoIP can't change font size</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Windows-7-PCoIP-can-t-change-font-size/m-p/892087#M21490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are having the same issue (extremely similar), and have added additional information here &lt;A href="https://communities.vmware.com/message/2251284"&gt;Cannot Change Font Size on Linked Clones Running Windows 7 x86 View 5.2.0&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 19:34:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/View-Windows-7-PCoIP-can-t-change-font-size/m-p/892087#M21490</guid>
      <dc:creator>rrizzi3821</dc:creator>
      <dc:date>2013-06-12T19:34:12Z</dc:date>
    </item>
    <item>
      <title>Cannot Change Font Size on Linked Clones Running Windows 7 x86 View 5.2.0</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Cannot-Change-Font-Size-on-Linked-Clones-Running-Windows-7-x86/m-p/1752545#M47377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a follow up to &lt;A _jive_internal="true" href="https://communities.vmware.com/message/1642640#1642640"&gt;http://communities.vmware.com/message/1642640#1642640&lt;/A&gt; (&lt;EM&gt;Cannot change font size View 4.5 client, November 8, 2010&lt;/EM&gt;). The posting is obsolete at this point, is a bit confusing and doesn't seem to apply to Windows 7 desktops at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cross-Post Update : Just found an unanswered similar post at &lt;A href="https://communities.vmware.com/message/2136591"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using VMware Horizon View 5.2 with WYSE P25 Zero Clients (PCoIP) and I am able to reproduce the same problem while connecting to the View Connection Server with the standard VMware View Client, version 5.2. The virtual desktop is a member of a Windows 2008 R2 Active Directory Domain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have painstakingly made sure that both GPO's shown below are actually being applied to the desired user and computer at the View Virtual machine in question and it still will not allow the user to modify the "Appearance and Personalization-&amp;gt;Display" settings from Smaller - 100% (default) to Medium or Larger because they are all grayed-out. I am sure there is a policy setting buried somewhere, or another policy setting that I need to Enable/Disable, but I cannot find it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="6-12-2013 12-25-02 PM.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/45510iEC2D4AC836355B69/image-size/large?v=v2&amp;amp;px=999" role="button" title="6-12-2013 12-25-02 PM.png" alt="6-12-2013 12-25-02 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The logged in user for the Virtual Desktop is also a member of the Local Administrators Group, and I modeled the Group as shown above to make sure the policies were being applied correctly. Lastly, there is a claim/reference in the post (&lt;EM&gt;Cannot change font size View 4.5 client, November 8, 2010&lt;/EM&gt;)&lt;EM&gt; &lt;/EM&gt;mentioned above that claims the solution is to Disable the GPO found at "User Configuration/Policies/Administrative Templates/Control Panel/Personalization/Prohibit Selection of Visual Font Size". This policy does not seem to apply to Windows 7 machines, so naturally it does not show up above (even though I defined it).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For more information about managing Windows 7 GPO see &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://technet.microsoft.com/en-us/library/ee617164%28v=ws.10%29.aspx"&gt;http://technet.microsoft.com/en-us/library/ee617164%28v=ws.10%29.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Robert Rizzi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 16:36:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Cannot-Change-Font-Size-on-Linked-Clones-Running-Windows-7-x86/m-p/1752545#M47377</guid>
      <dc:creator>rrizzi3821</dc:creator>
      <dc:date>2013-06-12T16:36:24Z</dc:date>
    </item>
  </channel>
</rss>

