I've got it working great when installed in the master image. Try this below.. Per-machine installation Console Copy msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 A...
See more...
I've got it working great when installed in the master image. Try this below.. Per-machine installation Console Copy msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1 This process installs Teams to the Program Files (x86) folder on a 64-bit operating system and to the Program Files folder on a 32-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups. The next interactive logon session starts Teams and asks for credentials. Here's the page explaining it..Teams for Virtualized Desktop Infrastructure - Microsoft Teams | Microsoft Docs Then just use DEM to capture the settings you want.
Try using this... Import this with DEM in the registry settings and you can mess around with the setting within as well. Try 0 at first, then increase to 2 and give it a shot. That should get ...
See more...
Try using this... Import this with DEM in the registry settings and you can mess around with the setting within as well. Try 0 at first, then increase to 2 and give it a shot. That should get rid of the black screen delay. [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Serialize] "StartupDelayInMSec"=dword:00000000
I'm looking for some VMware documentation about the recommended or "best practice" for how long to keep a linked clone or instant clone VM around before either refreshing or deleting/recreating. ...
See more...
I'm looking for some VMware documentation about the recommended or "best practice" for how long to keep a linked clone or instant clone VM around before either refreshing or deleting/recreating. Does anyone know of where I can find this documentation? I am looking for something straight from VMware because in my current env we have users logged into the same VM for 5 to 7 days before getting a new one. There are issues that the users have that are direct contributing factors to this and I am looking to change the way my company looks at virtual desktops. In other words, they think a virtual desktop is just like a physical machine in a sense where "I can have it on all the time and everything will be fine". I know that it's highly recommended that clones vm's are only to be used for 48 max in most cases because of the page file/OS disk filling up and causing issues. Cloned vm's were never created to be left around for very long at all. I need some sort of documentation that proves what I'm trying to say that I can give to the right people to start making this change. Any help is appreciated.
Appvolumes 2.16 Horizon 7.8 UEM 9.6 We're currently running into some issues with auto activation's within our env with Office 365. Our writable volumes hold the OST info for all users in a ...
See more...
Appvolumes 2.16 Horizon 7.8 UEM 9.6 We're currently running into some issues with auto activation's within our env with Office 365. Our writable volumes hold the OST info for all users in a standard template. I need to make changes to the snapvol.cfg file per writable volume that will resolve some issues we're having. Is there an easier way of editing the exclusions in the snapvol.cfg file so that everyone can get the changes with a new template or do I need to manually make the changes on everyone's volume? Is there a way to edit or create a new template? Thank you.
That's what I figured considering I couldn't find anything after digging around the internet. I'm not having any problems with users getting the wrong pool vm's I am just looking to split the loa...
See more...
That's what I figured considering I couldn't find anything after digging around the internet. I'm not having any problems with users getting the wrong pool vm's I am just looking to split the loads between sites and I thought this would be an awesome way to go about it.
I have two sites currently that are both part of the same pod federation. I want to know if it's possible to assign a floating linked clone vm per site based on the ip of the client station? I c...
See more...
I have two sites currently that are both part of the same pod federation. I want to know if it's possible to assign a floating linked clone vm per site based on the ip of the client station? I can't seem to find anything about it anywhere. If I have a user assigned to a global entitlement that is linked to a pool in SITE A and have the same global entitlement linked to another pool in SITE B, is it possible depending on which site (IP Address) they're connecting from to determine which pool they would receive a desktop? Thanks for any help provided..
Can't seem to get anything to stick with changes to default applications within Windows 10. Is there a registry setting or config file that anyone has used to work past this? I couldn't find a...
See more...
Can't seem to get anything to stick with changes to default applications within Windows 10. Is there a registry setting or config file that anyone has used to work past this? I couldn't find anything on this build of the OS (1607 LTSB) there were some issues with the newest update build but nothing listed for this one. Thanks in advance for any help.
Can't seem to get anything to stick with changes to default applications within Windows 10. Is there a registry setting or config file that anyone has used to work past this? I couldn't find any...
See more...
Can't seem to get anything to stick with changes to default applications within Windows 10. Is there a registry setting or config file that anyone has used to work past this? I couldn't find anything on this build of the OS (1607 LTSB) there were some issues with the newest update build but nothing listed for this one. Thanks in advance for any help.
I have this one user who has access to multiple desktop pools. For some reason everytime that he logs in no matter it be on the Zero client or the Horizon Client, he is auto connected to one desk...
See more...
I have this one user who has access to multiple desktop pools. For some reason everytime that he logs in no matter it be on the Zero client or the Horizon Client, he is auto connected to one desktop and isn't given a choice on which to connect. We've checked the Horizon Client settings and made sure that auto connect is off, same for the zero client. Any insight on why this could be happening? The only way that he can connect to another desktop is to pull his entitlement from the one that keeps auto connecting. Thank you.
Try this. Run this command in Powershell as Admin: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
In UEM you can create a shortcut, put it where you want. Then you can create a "condition" for the shortcut, that way only certain users in a group can see it.
AppVolumes takes profiling during the actual install of a program. You can either put the shortcut on the parent image or use UEM to complete this too.
