ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Install TeamViewer during "oobeSystem" (pass 7) WDS

    Scheduled Pinned Locked Moved IT Discussion
    21 Posts 4 Posters 3.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403
      last edited by

      Not if you provide credentials

      1 Reply Last reply Reply Quote 0
      • DustinB3403D
        DustinB3403
        last edited by

        Your image has a admin user built in, right? Pipe those credentials in and it'll work.

        ObsolesceO 1 Reply Last reply Reply Quote 0
        • ObsolesceO
          Obsolesce @DustinB3403
          last edited by

          @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.

          1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by DustinB3403

            Something like this would probably work.

            runas /savecred /user:administrator "\\path\to\executable.msi"

            1 Reply Last reply Reply Quote 0
            • DustinB3403D
              DustinB3403
              last edited by

              Using a command prompt for this is kind of backwards though, use powershell.

              1 Reply Last reply Reply Quote 1
              • NetworkNerdN
                NetworkNerd
                last edited by

                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.

                dbeatoD ObsolesceO 2 Replies Last reply Reply Quote 1
                • DustinB3403D
                  DustinB3403
                  last edited by

                  Try this within powershell.

                  runas /user:<administrator username here> "msiexec /i <Path and Filename of MSI" /qn

                  ObsolesceO 1 Reply Last reply Reply Quote 1
                  • dbeatoD
                    dbeato @NetworkNerd
                    last edited by

                    @NetworkNerd correct, deploying is easy is the actual activation that requires either a manual step or as you note.

                    ObsolesceO 1 Reply Last reply Reply Quote 1
                    • ObsolesceO
                      Obsolesce @DustinB3403
                      last edited by

                      @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" /qn

                      Looks 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.

                      1 Reply Last reply Reply Quote 0
                      • ObsolesceO
                        Obsolesce @dbeato
                        last edited by

                        @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/

                        1 Reply Last reply Reply Quote 0
                        • ObsolesceO
                          Obsolesce @NetworkNerd
                          last edited by

                          @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.

                          dbeatoD 1 Reply Last reply Reply Quote 0
                          • dbeatoD
                            dbeato @Obsolesce
                            last edited by

                            @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

                            https://community.teamviewer.com/t5/TeamViewer-12/Installation-of-customised-TeamViewer-Host-via-GPO/td-p/1920

                            https://community.teamviewer.com/t5/Knowledge-Base/Deploy-TeamViewer-Host-MSI-Package-with-Assignment-Tool/ta-p/310

                            ObsolesceO 1 Reply Last reply Reply Quote 0
                            • ObsolesceO
                              Obsolesce @dbeato
                              last edited by

                              @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/3031

                              https://community.teamviewer.com/t5/TeamViewer-12/Installation-of-customised-TeamViewer-Host-via-GPO/td-p/1920

                              https://community.teamviewer.com/t5/Knowledge-Base/Deploy-TeamViewer-Host-MSI-Package-with-Assignment-Tool/ta-p/310

                              None of those are relevant:

                              @Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:

                              https://community.teamviewer.com/t5/Community-Blog/Deploy-TeamViewer-Host-Modules-to-Thousands-of-Devices-via/ba-p/3031

                              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:

                              https://community.teamviewer.com/t5/TeamViewer-12/Installation-of-customised-TeamViewer-Host-via-GPO/td-p/1920

                              These computers are not on a domain, so cannot be deployed via GPO.

                              @Eltolargo said in Install TeamViewer during "oobeSystem" (pass 7) WDS:

                              https://community.teamviewer.com/t5/Knowledge-Base/Deploy-TeamViewer-Host-MSI-Package-with-Assignment-Tool/ta-p/310

                              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.

                              1 Reply Last reply Reply Quote 0
                              • ObsolesceO
                                Obsolesce
                                last edited by Obsolesce

                                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.

                                dbeatoD 1 Reply Last reply Reply Quote 0
                                • dbeatoD
                                  dbeato @Obsolesce
                                  last edited by

                                  @tim_g Did it work?

                                  1 Reply Last reply Reply Quote 0
                                  • ObsolesceO
                                    Obsolesce
                                    last edited by

                                    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.

                                    1 Reply Last reply Reply Quote 0
                                    • 1
                                    • 2
                                    • 1 / 2
                                    • First post
                                      Last post