almostIT's Posts

Figured out the problem.  I was using Windows Ent 1809 which is not supported by the current Intelligent Hub version.  Updated to Windows 22H2 and the scripts worked.  It is kind of interesting th... See more...
Figured out the problem.  I was using Windows Ent 1809 which is not supported by the current Intelligent Hub version.  Updated to Windows 22H2 and the scripts worked.  It is kind of interesting that the Intelligent Hub application has such a high OS requirement, considering there are a lot of features and configurations within WS1 for OLDER Windows versions, like 1809.  Moral of the story. Use the latest OS of Windows, if possible, along with the latest Intelligent Hub version. Less problems. 
I did add an exit code 0 to the script, but it made no difference. Per this little gem: https://techzone.vmware.com/getting-started-freestyle-orchestrator#scripts  
How is this not talked about more? I can't find a single working example of this feature and to me it seems this would be very useful for most admins.  When I try to run even basic PowerShell comman... See more...
How is this not talked about more? I can't find a single working example of this feature and to me it seems this would be very useful for most admins.  When I try to run even basic PowerShell commands against a Windows device with this it does not work.  Additionally, devices > scripts shows me zero. I have no indication of why it does not work.  Reddit user with the same issue, no solution: https://www.reddit.com/r/WorkspaceOne/comments/q8s5b1/scripting_in_ws1/ I've tried the suggestions in that post, but what is weird is that there is no indication anywhere if the script even ran or not.  YouTube video showing the feature itself, but with no working example and comments turned off: https://www.youtube.com/watch?v=kNAZN0RpyV4 He never shows the success of the deployment, or any indication of such, it's just a GUI walkthrough.  VMware's own, vague and very basic, documentation: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/Windows_Desktop_Device_Management/GUID-uemWindeskScripts.html  Which again, is just a walkthrough.  Am I going crazy here or is it just me?   
Alright. I'm onto something. Apparently when I'm on the login screen for cn700.awmdm.com, I can't use just my email. I have to add in my domain name as well. my.domain.com\my.adminaccount@my.domain... See more...
Alright. I'm onto something. Apparently when I'm on the login screen for cn700.awmdm.com, I can't use just my email. I have to add in my domain name as well. my.domain.com\my.adminaccount@my.domain.com <--like this This works, I even got the 2fa prompts. Not what I expected. But it's something. After login I do get a, "The 'objectGUID' attribute, which is required to securely authenticate administrators into the Console, is missing from your Identity Provider SAML response." Suppose I'll have to fix that. I'll update with the final configuration if I find one that works FLAWLESSLY.  
psiwi1 - I already had that checked. My on premise AD is replicating an "admins" group to Azure. Which is then synced with WS1 UEM. The same "admins" group is set within UEM for that role. The logi... See more...
psiwi1 - I already had that checked. My on premise AD is replicating an "admins" group to Azure. Which is then synced with WS1 UEM. The same "admins" group is set within UEM for that role. The login behavior for an admin is inconsistent. Sometimes it will be short, and only prompt me for a username and password, then fail. Other times it'll go through the entire 2 factor authentication process (which is more the expectation) but in the end fails to login. I keep clearing the browser cache to see if that's messing with the login process, but it doesn't make a difference. Other accounts work fine. The enrollment part works fine for users. I just cannot seem to get the admin users to login this way, it's really bizarre. I would have thought if enrollment works, the admin part would work too, so long as the user/groups were set within UEM for the "admin role", but it's just not the case.
SaaS UEM version 22.9.0.0 (2209)  We have integrated on-premise AD and SAML enabled for enrollment, admins.  However; when I try to use an AD account for admin access, and not a "Cloud Services Adm... See more...
SaaS UEM version 22.9.0.0 (2209)  We have integrated on-premise AD and SAML enabled for enrollment, admins.  However; when I try to use an AD account for admin access, and not a "Cloud Services Admin" account, it fails and says... "Your Workspace ONE UEM account has been locked. Please reset your password to unlock your account or contact your IT Administrator." It's not locked.  The cloud services accounts work fine, but I'd like to have admins, without those accounts, work in sub-organizational groups and those users come from integrated AD.  I get the feeling VMware doesn't want AD accounts used for admins.  "This tenant is enabled with Workspace ONE Cloud Admin Hub. Administrators created in UEM will only have access to UEM. Add the administrator in Cloud Services to enable access to Workspace ONE services."
22.06 and no app catalog. It was there on a previous version, not sure which, but now it's nowhere to be seen. There used to be a link for it in the start-menu by default. That is also gone. I've bee... See more...
22.06 and no app catalog. It was there on a previous version, not sure which, but now it's nowhere to be seen. There used to be a link for it in the start-menu by default. That is also gone. I've been trying all day to figure out where it went. 
I would use a new machine to capture Chrome. Don't use a machine that might have had old Chrome. Also, don't update an application stack with old Chrome in it, like a collection of web browsers, if t... See more...
I would use a new machine to capture Chrome. Don't use a machine that might have had old Chrome. Also, don't update an application stack with old Chrome in it, like a collection of web browsers, if that's what you're trying to do. Start with a brand new app stack instance. If you work with an app stack instance that had old Chrome installed then it may be next to impossible to remove - you'll just have to rebuild the stack. I had one with Chrome, Edge, and Firefox and just rebuilt it instead of trying to mess with removing pieces of old Chrome.  The only other thing you might try is: on the app stack with old Chrome installed already, download the latest MSI for Chrome, install new Chrome, then uninstall new Chrome, then re-install new Chrome. That might remove all the old Chrome artifacts. I think that worked for at least one instance where old Chrome was installed on a separate application stack by accident.  Good luck. 
Running App Volumes 4.7.0.64 on a Windows Server 2019 instance. Over time the ruby interpreters overwhelm the memory on the server. We have only a single, very small, app volume package running on ab... See more...
Running App Volumes 4.7.0.64 on a Windows Server 2019 instance. Over time the ruby interpreters overwhelm the memory on the server. We have only a single, very small, app volume package running on about 10-12 VMs with this particular instance. This is the second time it's happened in about two months. Restarting the service doesn't help. Ending the processes doesn't help. It only goes back to "normal" after I reboot the machine. Dynamic Environment Manager also runs off this machine for the 10-12 VMs. See attached images. Server 2019 1809 17763.3532, 4vcpu 8gb ram Very low utilization of DEM and App Volumes so I'm surprised to see this issue.  
Okay, if I don't update the OS it works (with the newer versions of agents). 
Printer redirection does not work if I update the gold image tools and view agent.  On the working gold image and corresponding snapshots:  Tools: 10.3.5 View Agent: 7.11 DEM: 9.10.0.921 App Vol... See more...
Printer redirection does not work if I update the gold image tools and view agent.  On the working gold image and corresponding snapshots:  Tools: 10.3.5 View Agent: 7.11 DEM: 9.10.0.921 App Volumes Agent: 4.1.0.57 OS: 17763.1577 On the updated gold image and corresponding snapshots where printer redirection does not work:  Tools: 12.1.0.x View Agent: 7.13.1 (matches our version of Horizon)  OS: 1809, 17763.3532 Note: did not update App Volumes/DEM agents, just reinstalled them as part of testing. Didn't matter because printer direction still does not work when I update just the tools and view agent. I tried testing updating only one at a time and it made no difference.  Could it be the the OS update? Am I missing something I need to do after an update? It doesn't seem to matter if I use older or newer versions of the Horizon Client to connect, I get the same behavior. It works in the old instance, but not the new instance. I've tried on Windows 10/11 desktops.  I do have another environment running the latest version of Horizon DaaS and, using the same desktops to make connections, the printer redirection works. It seems like either a Windows update or agent update is breaking the printer redirection.  Also, the OS and versions are old (inherited environment).  I saw a post where someone had a similar issue with printer redirection not working after an update to 7.12 and there was no resolution. I would really like to update these images and not have to rebuilt them from scratch.  
When a user opens Chrome it launches, but then exits abruptly. A small command prompt screen appears for a split second then disappears. Version of Chrome is 106.x, 32bit or 64bit.  appwiz.cpl show... See more...
When a user opens Chrome it launches, but then exits abruptly. A small command prompt screen appears for a split second then disappears. Version of Chrome is 106.x, 32bit or 64bit.  appwiz.cpl shows the wrong version of Chrome, 85.x. C;\Program Files(x86)\Google\Application\Chrome\ shows TWO version of the application. I'm adding this in case it happens to someone else. SOLUTION: There is an older instance of Chrome (or similar application) installed by accident in an app stack. Check your app stack(s) for the culprit. Narrow it down by date of installation and applications a user has access. Uninstall the older application version from the app stack or rebuild the entire stack. Hope this never happens to someone else.  
Try this: https://virtuallyunboxed.wordpress.com/2019/11/14/windows-updates-and-osot/ The script I attached (it's a PowerShell script in Text format, just convert to .ps1) does what is described in ... See more...
Try this: https://virtuallyunboxed.wordpress.com/2019/11/14/windows-updates-and-osot/ The script I attached (it's a PowerShell script in Text format, just convert to .ps1) does what is described in this post, but "automatically". Hope it works for you, it worked for me. 
I had the same issue. Try a more recent Windows Update. 
Nah, same issues. Every time I try to update Windows with the OSOT tools it doesn't work. It just breaks Windows Updates. I've tried the most recent version of the OSOT tool and still does the same t... See more...
Nah, same issues. Every time I try to update Windows with the OSOT tools it doesn't work. It just breaks Windows Updates. I've tried the most recent version of the OSOT tool and still does the same thing.