Install TeamViewer during "oobeSystem" (pass 7) WDS
-
@DustinB3403 said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
Your image has a admin user built in, right?
Yes but with a blank password.
Pipe those credentials in and it'll work.
I haven't done that before. Do know off the top of your head how I would set that up for example?
It doesn't matter at this point if this local username/password is in clear-text anywhere.
-
Something like this would probably work.
runas /savecred /user:administrator "\\path\to\executable.msi" -
Using a command prompt for this is kind of backwards though, use powershell.
-
It's one thing to install TeamViewer but another to register with your TeamViewer account and enable unattended access, enforce policy, etc. 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.
-
Try this within powershell.
runas /user:<administrator username here> "msiexec /i <Path and Filename of MSI" /qn -
@NetworkNerd correct, deploying is easy is the actual activation that requires either a manual step or as you note.
-
@DustinB3403 said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
Try this within powershell.
runas /user:<administrator username here> "msiexec /i <Path and Filename of MSI" /qnLooks like /qn needs to be within the quotes. Changed that:
It will not run in a non-elevated powershell.
Ran the above command in non-elevated powershell:
Three things... 1) it asks for a password 2) Error says 1327: Account restrictions are preventing this user from signing in, 3) if I want to set the execution policy to bypass, it's a no go. -
@Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
@NetworkNerd correct, deploying is easy is the actual activation that requires either a manual step or as you note.
How is deploying TeamViewer during the image deployment process with WDS easy when it simply (seemingly) cannot be done automatically?
I've tried everything. I'm open to more ideas if you've got them!
What it comes down to, is that somewhere in the deployment process, there needs to be a way to run a .msi via an elevated CLI. I just don't think it's possible so I'm about to move on.
I'm thinking the whole method is flawed. Even if I would be able to find a way to get the .msi to run, it doesn't seem like the .xml command will even start the process.
This basically what I'm trying to accomplish, but with TeamViewer: https://www.saotn.org/software-deployment-through-wds/
-
@NetworkNerd said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
It's one thing to install TeamViewer but another to register with your TeamViewer account and enable unattended access, enforce policy, etc. 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.
This is already taken care of with the .msi installer. No issues there. The issue is actually getting the .msi to run at the end of the image deployment. From what I understand, it's supposed to do it at the first logon of a user... and when the image is done, it logs on to a local admin user automatically. Does the normal dance before the desktop appears, but never any teamviewer install.
-
@Tim_G said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
@NetworkNerd said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
It's one thing to install TeamViewer but another to register with your TeamViewer account and enable unattended access, enforce policy, etc. 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.
This is already taken care of with the .msi installer. No issues there. The issue is actually getting the .msi to run at the end of the image deployment. From what I understand, it's supposed to do it at the first logon of a user... and when the image is done, it logs on to a local admin user automatically. Does the normal dance before the desktop appears, but never any teamviewer install.
Take a look at this:
https://community.teamviewer.com/t5/Community-Blog/Deploy-TeamViewer-Host-Modules-to-Thousands-of-Devices-via/ba-p/3031 -
@Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
@Tim_G said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
@NetworkNerd said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
It's one thing to install TeamViewer but another to register with your TeamViewer account and enable unattended access, enforce policy, etc. 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.
This is already taken care of with the .msi installer. No issues there. The issue is actually getting the .msi to run at the end of the image deployment. From what I understand, it's supposed to do it at the first logon of a user... and when the image is done, it logs on to a local admin user automatically. Does the normal dance before the desktop appears, but never any teamviewer install.
Take a look at this:
https://community.teamviewer.com/t5/Community-Blog/Deploy-TeamViewer-Host-Modules-to-Thousands-of-Devices-via/ba-p/3031None of those are relevant:
@Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
This isn't a scenario in which deploying TeamViewer to networked computers is happening. The only way to do this is either via the imaging process of the PC, or manually after the image is deployed.
@Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
These computers are not on a domain, so cannot be deployed via GPO.
@Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:
I don't need to do anything with the .MSI itself. It is set up, customized, registered, unattended access, everything, exactly the way we need it already.
To clarify, the .msi is located on a network share. TeamViewer needs to be installed as part of the imaging process, automatically and without user intervention. Deploying TeamViewer TO the PC by any means is not an option, whether centrally or not.
The issue is that the TeamViewer.msi only installs if it's ran via an elevated CLI, whether it's cmd, powershell, vbs, whatever... it has to be elevated, and it needs to run so it can be installed if you know what I mean.
-
I've got one more trick to try:
I will try to create a scheduled task on the image itself before I do sysprep, that runs during logon, which runs fully escalated and privileged as a local admin user. It will run a powershell script that installs TeamViewer, ending with deleting the scheduled task itself.
This is all banking on the fact that a scheduled task survives a sysprep. I have never tried it.
-
@tim_g Did it work?
-
The scheduled task survives and runs at first login as planned.
But Win10 and TV have a known issue with silent installation. Hopefully it gets fixed.
