From what I understand, it's supposed to do it at the first logon of a user. msi to run at the end of the image deployment. I thought even if you downloaded the custom MSI you still had to make an API call back to TeamViewer to register the device with your TeamViewer account. It's one thing to install TeamViewer but another to register with your TeamViewer account and enable unattended access, enforce policy, etc. I haven't tried this yet, but I'm looking for any other ideas before I take the time to try said in Install TeamViewer during "oobeSystem" (pass 7) said in Install TeamViewer during "oobeSystem" (pass 7) WDS: msi and/or other software has been installed. xml, run another script turning UAC back on after the. Then after deployment, like in the above. One idea I had was to see if I can disable UAC before I sysprep the image, and see if that survives.
msi to install automatically after the image is deployed? I verified this by looking at the event logs, and it says the TeamViewer 11 Host msi failed because it requires admin rights (elevation). It needs to be ran from an elevated prompt. But if I run the "CommandLine" part from the. The commands and script contents work great when ran from an elevated powershell or command prompt. The contents of "FTdeploySoftware.ps1" are: Start-Process -NoNewWindow msiexec -argument "/i \\server\share$\WDS\TV11FThost\TeamViewer_Host-idcqsmsmbk.msi /quiet" -Wait PowerShell.exe -ExecutionPolicy ByPass -File \\server\share$\WDS\FTdeploySoftware.ps1 We can't have TeamViewer installed as part of the image, so this needs to be installed after the image has been deployed to a computer.Īs part of the ImageUnattend.xml attached to the "special image", you would do this via a command or script: This is a "special" image that is used on special computers that do not join the local domain. I have a working Windows10 image that deploys great using Windows Deployment Services (WDS).
0 kommentar(er)
