It has been discussed in this thread with some sample scripts that I posted. https://communities.vmware.com/t5/Dynamic-Environment-Manager/Hybrid-AD-Join-as-a-DEM-startup-task-on-Instant-clones/m-p/...
See more...
It has been discussed in this thread with some sample scripts that I posted. https://communities.vmware.com/t5/Dynamic-Environment-Manager/Hybrid-AD-Join-as-a-DEM-startup-task-on-Instant-clones/m-p/2860764#M7125
My first recommendation would be to open a ticket with VMware as this is a production issue and the forums are probably not the best place for this type of troubleshooting. But if you wanted to look...
See more...
My first recommendation would be to open a ticket with VMware as this is a production issue and the forums are probably not the best place for this type of troubleshooting. But if you wanted to look at something while waiting for a response, I would start with the firewall as it looks like something is being blocked on the firewall. Make sure TCP and UDP is allowed as well.
You can only purchase licenses in minimum packs of 10 (for 10 users). So, if you have 88 users for example, you need to buy 9 of those 10 packs for a total of 90 licensed users.
We've seen a similar issue and I'm assuming you are doing a Hybrid Azure AD join? When a user logs in, they get a primary refresh token (prt) from Azure AD. If there was one captured during the insta...
See more...
We've seen a similar issue and I'm assuming you are doing a Hybrid Azure AD join? When a user logs in, they get a primary refresh token (prt) from Azure AD. If there was one captured during the instant clone process, it can cause issues. There is a scheduled task that performs this action. As part of the gold image build process, we delete this scheduled task, and re-create it after the machine is built and joined to the domain as a post-install process. One way to find out if this is the issue, have the user do a CTRL+ALT+DELETE and lock their machine, and then unlock it again. Restart Outlook, Teams or whatever is failing.
It's unable to edit the hosts file. Typically, an AntiVirus app will prevent editing this file. You can temporarily disable it. --OR-- just add the line yourself to the hosts file. If it finds th...
See more...
It's unable to edit the hosts file. Typically, an AntiVirus app will prevent editing this file. You can temporarily disable it. --OR-- just add the line yourself to the hosts file. If it finds the pattern it will skip that step This is the line it's looking to match - just add it manually to the hosts file. 127.0.0.1 view-localhost # view localhost server vdmInstUtil: 09/09/22 11:44:55 Entering custom action VMAddViewLocalHostEntryToHostsFile vdmInstUtil: 09/09/22 11:44:55 --- VMAddViewLocalHostEntryToHostsFile() : Adding view-localhost entry to the 'etc\hosts' file. vdmInstUtil: 09/09/22 11:44:55 File exists: "C:\WINDOWS\system32\Drivers\etc\hosts" vdmInstUtil: 09/09/22 11:44:55 Searching for '127.0.0.1 view-localhost # view localhost server' in "C:\WINDOWS\system32\Drivers\etc\hosts" vdmInstUtil: 09/09/22 11:44:55 File exists: "C:\WINDOWS\system32\Drivers\etc\hosts" vdmInstUtil: 09/09/22 11:44:55 Pattern not found! vdmInstUtil: 09/09/22 11:44:55 Appending text to file: "C:\WINDOWS\system32\Drivers\etc\hosts" vdmInstUtil: 09/09/22 11:44:55 ERROR: Failed to open file: "C:\WINDOWS\system32\Drivers\etc\hosts": 13 vdmInstUtil: 09/09/22 11:44:56 Appending text to file: "C:\WINDOWS\system32\Drivers\etc\hosts" vdmInstUtil: 09/09/22 11:44:56 ERROR: Failed to open file: "C:\WINDOWS\system32\Drivers\etc\hosts": 13 vdmInstUtil: 09/09/22 11:44:56 retry 1 - Util_AppendLinesW failed
Also, if you don't have the scheduled task that was deleted, you will get tons of these warning messages in the "User Device Registration" event viewer folder. Failed to enable task \Microsoft\Windo...
See more...
Also, if you don't have the scheduled task that was deleted, you will get tons of these warning messages in the "User Device Registration" event viewer folder. Failed to enable task \Microsoft\Windows\Workplace Join\Automatic-Device-Join. Error: The system cannot find the file specified.
Timing and state of the machine is everything. Which is why I had it in a powershell checking name and if it's joined to the domain before attempting anything AAD related. On another note, I do thin...
See more...
Timing and state of the machine is everything. Which is why I had it in a powershell checking name and if it's joined to the domain before attempting anything AAD related. On another note, I do think the dsregcmd has a bug of some sort. MS claims to have fixed it with 20H2, but everything that they claimed to have fixed didn't happen to us with 1809, but we now see it in 20H2. Releasing Windows 10 Build 19042.962 (20H2) to Release Preview Channel | Windows Insider Blog
I have a custom powershell script that gets called on machine startup via a scheduled task. The scheduled task is configured to run as SYSTEM. All this does is check to see if the machine name matche...
See more...
I have a custom powershell script that gets called on machine startup via a scheduled task. The scheduled task is configured to run as SYSTEM. All this does is check to see if the machine name matches a certain criteria (based on your naming scheme). Once it meets that criteria only then it launches the initializevdi script. ComputerStartup Script $computername = [System.Environment]::MachineName if((Get-WmiObject -Class Win32_ComputerSystem).PartofDomain) { if($computername -match "vdi") { Start-Process -FilePath $InitializeVDI -ArgumentList "optional arguments" } } InitializeVDI script #Other initialization tasks #Inject SCP values if not present in the AD schema $tenantId = "<guid>" $tenantName = "company.com" New-Item -Path HKLM:\Software\Microsoft\Windows\CurrentVersion\CDJ -Name AAD -Force Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\CDJ\AAD -Name TenantId -Value $tenantId Set-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\CDJ\AAD -Name TenantName -Value $tenantName #Re-create scheduled task Invoke-Command -scriptblock { cmd.exe /c "C:\<FolderPath>\CreateSchtask.cmd" } -computername . #Start Horizon Agent Service Set-Service -Name "WSNM" -StartupType Automatic Start-Service -Name "WSNM" #End script CreateSchtask.cmd "C:\Windows\System32\schtasks.exe" /create /xml c:\<FolderPath>\Automatic-Device-Join.xml /TN "\Microsoft\Windows\Workplace Join\Automatic-Device-Join" >> C:\<FolderPath>\crtask.log Controlled validation of hybrid Azure AD join - Azure AD | Microsoft Docs Primary Refresh Token (PRT) and Azure AD - Azure Active Directory | Microsoft Docs
The trick isn't to find the correct version. It's to exclude the SVGA drivers when installing VMtools. Horizon Agent puts it's version down and that will always match what it needs.
I've had a similar issue before and it turned out to the AntiVirus software. The client install tries to write an entry in the hosts file of a Windows machine and some AV software will block that. Yo...
See more...
I've had a similar issue before and it turned out to the AntiVirus software. The client install tries to write an entry in the hosts file of a Windows machine and some AV software will block that. You can temporarily disable the AV software, while installing the client.
A similar thread that might help someone. This was the issue in our environment. Outlook 2016 - O365 freezes VM - but only on the s... - VMware Technology Network VMTN https://kb.vmware.com/s/ar...
See more...
A similar thread that might help someone. This was the issue in our environment. Outlook 2016 - O365 freezes VM - but only on the s... - VMware Technology Network VMTN https://kb.vmware.com/s/article/2078739
What is this path in your install for Visual Studio Community 2019 build? C:\Users\<userid>\AppData\Local\Microsoft\VisualStudio\16.0_xxxxxxxxx I may have a fix for this.
We use DEM in our environment for favorites. For the Desktop, we only backup .lnk files using DEM. We train our users to not store files on their desktop. They will lose them when they sign out. ...
See more...
We use DEM in our environment for favorites. For the Desktop, we only backup .lnk files using DEM. We train our users to not store files on their desktop. They will lose them when they sign out. we re-direct Documents and Pictures to a path in their Home Share. It works well for us.