• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Webcast: Imaging with FOG, Managing with PDQ

    Scheduled Pinned Locked Moved
    Tutorials
    10
    41
    19.1k
    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.
    • T
      Troye Johnson
      last edited by Troye Johnson

      @bmorris Yes I we created a domain user added that users under the “pdq deploy> Preferences>Credentials” to allow it access to deploy apps and then added those credentials into the PDQdeploy script by powershell. Here is my script I encrypted the password for best practices.

      
      <#
      .SYNOPSIS
      Start a PDQ Deploy Deployment on a target machine
      
      .DESCRIPTION
      Trigger a PDQ Deploy deployment to start locally or on a remote machine with PDQ Deploy installed
      
      .EXAMPLE
      Start-Deployment -PackageName "Example Package" -Targets "Wolverine"
      
      .EXAMPLE
      Start-Deployment -ScheduleName "Example Schedule" -Targets "Wolverine"
      
      .EXAMPLE
      Start-Deployment -ScheduleID 123 -Targets "Wolverine"
      
      .PARAMETER DeployComputerName
      The machine with PDQ Deploy installed. This defaults to the local machine
      
      .PARAMETER PackageName
      The names of packages on DeployMachine that you wish to use
      
      .PARAMETER ScheduleName
      The names of schedules on DeployMachine that you wish to use
      
      .PARAMETER ScheduleID
      The schedule IDs on DeployMachine that you wish to use
      
      .PARAMETER Targets
      A list of targets that you wish to deploy a package or schedule to. Leave blank if you wish to target the local machine.
      #>
      [cmdletbinding(
          SupportsShouldProcess = $True
      )]
      Param(
      
          [String]$DeployComputerName = $env:COMPUTERNAME,
      
          [Parameter(ParameterSetName = "Package")]
          [string]$PackageName,
      
          [Parameter(ParameterSetName = "Package")]
          [String[]]$Targets = $env:COMPUTERNAME,
      
          [Parameter(ParameterSetName = "Schedule")]
          [string]$ScheduleName,
      
          [Parameter(ParameterSetName = "ScheduleID")]
          [Int]$ScheduleID
      
      )
      
      Process {
          
          # Add parameters to a hashtable to easily push into invoke-command as an argument
          $MyParameters = @{
              DeployComputerName = $DeployComputerName
              PackageName        = $PackageName
              Targets            = $Targets
              ScheduleName       = $ScheduleName
              ScheduleID         = $ScheduleID
              DeploymentType     = $PSCmdlet.ParameterSetName
          }
      	#OS Check
      	
      	$PSScriptRoot = Split-Path -Parent -Path $MyInvocation.MyCommand.Definition
      	
      	#Credentials
      
      $User = "domain\user"
      $PasswordFile = "$PSScriptRoot\Password.txt"
      $KeyFile = "$PSScriptRoot\AES.key"
      $key = Get-Content $KeyFile
      $MyCredential = New-Object -TypeName System.Management.Automation.PSCredential `
       -ArgumentList $User, (Get-Content $PasswordFile | ConvertTo-SecureString -Key $key)
      
          # This outputs a powershell.log to the root directory of the target machine
          $MyParameters | Out-String | Out-File C:\powershell.log
      
          # Testing to see if PSRemoting is enabled
          If (Test-WSMan -ComputerName $DeployComputerName) {
                  
              Write-Verbose "Test-WSMan test passed on $DeployComputerName"
      
              # Added -Whatif capability to script
              If ( $PSCmdlet.ShouldProcess($DeployComputerName, "Starting deployment with the following parameters:`n $($MyParameters | Out-String)") ) {
                  
                  # Connect to Deploy machine and attempts to start a deployment
                  Invoke-Command -ComputerName $DeployComputerName -credential $MyCredential -ArgumentList ($MyParameters) -ScriptBlock {
                      Param ($MyParameters)
      
                      # This outputs a powershell.log to the root directory of the deploy machine
                      $MyParameters | Out-String | Out-File C:\powershell.log
      
                      # Build command string based on deployment type
                      Switch ($MyParameters.DeploymentType) {
      
                          "Package" {
      
                              $PDQDeployCommand = "pdqdeploy deploy -package ""$($MyParameters.PackageName)"" -targets $($MyParameters.Targets)"
                          
                          }
              
                          "Schedule" {
                          
                              $DB = "$env:ProgramData\Admin Arsenal\PDQ Deploy\Database.db"
                              $SQL = "SELECT ScheduleID FROM Schedules WHERE Name = '$($MyParameters.ScheduleName)' COLLATE NOCASE;"
                              $ScheduleID = $SQL | sqlite3.exe $db
                              $PDQDeployCommand = "pdqdeploy StartSchedule -ScheduleId $ScheduleID"
                          
                          }
      
                          "ScheduleID" {
                          
                              $PDQDeployCommand = "pdqdeploy StartSchedule -ScheduleId $($MyParameters.ScheduleID)"
                          
                          }
                      }                    
      
                      # Append the actual command that will be run to powershell.log
                      "Invoke-command: $PDQDeployCommand" | Out-File C:\powershell.log -Append
      
                      # Create and invoke scriptblock
                      $PDQDeployCommand = [ScriptBlock]::Create($PDQDeployCommand)
                      $PDQDeployCommand.Invoke()
      
                  } 
              }
          }
      }
      

      Im not sure if it works with server mode of PDQ deploy that was just released yet though I have not tested it. If you get a chance to please let me know.

      Fog Server information

      Cent OS 7
      Running Version 1.5.2

      B 4 Replies Last reply Reply Quote 0
      • B
        bmorris @Troye Johnson
        last edited by

        @Troye-Johnson Thank you very much for this. I will report back if this works for server mode of PDQ Deploy.

        Fog Server Info

        Ubuntu 16.04.2 LTS
        Running Version 1.4.0
        SVN Revision: 6069

        T 1 Reply Last reply Reply Quote 0
        • T
          Troye Johnson @bmorris
          last edited by

          @bmorris Please remember to add this registry setting based on PDQ recommendations

          Additionally, you’ll need to add an entry into the registry on the PDQ Deploy machine in order to tell the background service to use TCP/IP:

          Location: HKLM\Software\Admin Arsenal\PDQ Deploy\
          Type: DWORD Name: ServicePort Value: <port number>

          The value needs to be a port number that is allowed within your network.

          or find it here https://www.adminarsenal.com/webcast-bonus-content/

          Fog Server information

          Cent OS 7
          Running Version 1.5.2

          B 1 Reply Last reply Reply Quote 0
          • B
            bmorris @Troye Johnson
            last edited by

            @Troye-Johnson I forgot to ask, which I am sure I will find out anyway through testing, but is your FOG Service running as the default SYSTEM account on the client using this script? Since you are specifying creds in the script, this doesn’t matter now, I assume.

            Fog Server Info

            Ubuntu 16.04.2 LTS
            Running Version 1.4.0
            SVN Revision: 6069

            T 1 Reply Last reply Reply Quote 0
            • B
              bmorris @Troye Johnson
              last edited by

              @Troye-Johnson Thanks for this. PDQ actually provided me with an update that fixes this issue on v13. No need for the registry setting change. The update put us on v13.2.0.0.

              Fog Server Info

              Ubuntu 16.04.2 LTS
              Running Version 1.4.0
              SVN Revision: 6069

              x23piracyX 1 Reply Last reply Reply Quote 0
              • B
                Bob Henderson @Bob Henderson
                last edited by

                @Bob-Henderson said in Webcast: Imaging with FOG, Managing with PDQ:

                @george1421 Actually reminded me to renew the domain name on that one before I lost it! God I need to post more updates.

                We’re still using FOG and PDQ to image out our 1:1 fleet of computers, as well as having it tied into our server deployments automated via Ansible onto our Proxmox KVM boxes. It’s working fantastically.

                The next thing I’m working on (shoot for the moon, right?) is to use FOG to host Snapins and make them accessible outside of the LAN, that’ll then pull down some powershell to grab files via HTTPS from our web cluster to do remote installations if needed. I’ve got a proof of concept working, but I’m a 1 man shop and haven’t had time to do much more on it. But if it works, I’ll effectively be able to push installs both on and offsite, without having to use DirectAccess as the tie back. The powershell has some if’s in there to see if they’re on the LAN, which will then tell it to grab PDQ’s packages, but if they’re off, it’ll grab them from the HTTPS repository and fire off msiexec on them manually.

                It’s poor mans SCCM!

                An update on this. I got it working, and it worked fantastically. Presents a webpage, user pics what apps they want, and it makes an exe that fires off to tell PDQ to install it.

                HOWEVER

                In discussions with PDQ, I was told that it’s a violation of the EULA, as each user who is ‘interacting’ with pdq, in this case telling it to fire off, would need to be licensed. It doesn’t apply as much in this instance, so you’re the one firing it off each time in the image, but something to consider if you have multiple techs who do the imaging, etc.

                B 1 Reply Last reply Reply Quote 0
                • B
                  bmorris @Bob Henderson
                  last edited by

                  @Bob-Henderson Interesting. Probably a good thing each of our techs are licensed for PDQ Deploy then! Good work though.

                  Fog Server Info

                  Ubuntu 16.04.2 LTS
                  Running Version 1.4.0
                  SVN Revision: 6069

                  1 Reply Last reply Reply Quote 0
                  • T
                    Troye Johnson @bmorris
                    last edited by

                    @bmorris Yes no need to change the fog user on the service.

                    Fog Server information

                    Cent OS 7
                    Running Version 1.5.2

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      bmorris @Troye Johnson
                      last edited by

                      @Troye-Johnson Excellent. I will let you know what I find out! Thanks again.

                      Fog Server Info

                      Ubuntu 16.04.2 LTS
                      Running Version 1.4.0
                      SVN Revision: 6069

                      1 Reply Last reply Reply Quote 0
                      • T
                        Troye Johnson
                        last edited by

                        For the licensing aspect you can create different power-shell scripts for each of your techs so that you can keep an audit of who ran what when applications are being deployed. This way not only will you stay in compliance with the eula but you also have an audit if something happens.

                        Fog Server information

                        Cent OS 7
                        Running Version 1.5.2

                        1 Reply Last reply Reply Quote 0
                        • B
                          bmorris @Troye Johnson
                          last edited by

                          @Troye-Johnson Just had a chance to dig into your script. Very new to fog, so forgive my ignorance. How are you getting the password file and key to the tmp fog service directory on the client? I don’t see a way to copy supporting files in the snapin manager in FOG?

                          Fog Server Info

                          Ubuntu 16.04.2 LTS
                          Running Version 1.4.0
                          SVN Revision: 6069

                          1 Reply Last reply Reply Quote 0
                          • B
                            bmorris @Troye Johnson
                            last edited by

                            @Troye-Johnson I should have checked a littler harder. I found the snapin pack option when creating a snapin. It pays to know how to read.

                            Fog Server Info

                            Ubuntu 16.04.2 LTS
                            Running Version 1.4.0
                            SVN Revision: 6069

                            T 1 Reply Last reply Reply Quote 0
                            • x23piracyX
                              x23piracy @bmorris
                              last edited by

                              @bmorris is the 13.2 patch official?

                              ║▌║█║▌│║▌║▌█

                              B 1 Reply Last reply Reply Quote 0
                              • T
                                Troye Johnson @bmorris
                                last edited by

                                @bmorris No problem just let me know if you have anymore questions I am happy to help.

                                Fog Server information

                                Cent OS 7
                                Running Version 1.5.2

                                B 1 Reply Last reply Reply Quote 1
                                • B
                                  bmorris @x23piracy
                                  last edited by

                                  @x23piracy I actually am not sure. They provided a link to me via email for the update, so my assumption is that it is not. You can always reach out to them and get it. Their support is excellent.

                                  Fog Server Info

                                  Ubuntu 16.04.2 LTS
                                  Running Version 1.4.0
                                  SVN Revision: 6069

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    bmorris @Troye Johnson
                                    last edited by

                                    @Troye-Johnson Your script with the creds works perfect with the Server/Client setup of PDQ Deploy. Thanks again for the help!

                                    Fog Server Info

                                    Ubuntu 16.04.2 LTS
                                    Running Version 1.4.0
                                    SVN Revision: 6069

                                    T 1 Reply Last reply Reply Quote 0
                                    • T
                                      Troye Johnson @bmorris
                                      last edited by

                                      @bmorris Happy to help.

                                      Fog Server information

                                      Cent OS 7
                                      Running Version 1.5.2

                                      1 Reply Last reply Reply Quote 0
                                      • W
                                        wahidovic @x23piracy
                                        last edited by wahidovic

                                        @x23piracy
                                        The following thing I’m taking a shot at (shoot for the moon, right?) is to utilize FOG to have Snapins and make them available outside of the LAN, that’ll at that point pull down some powershell to get records by means of HTTPS from our web group to do remote establishments if necessary. I have a proof of idea working, yet I’m a 1 man shop and haven’t had sufficient energy to do considerably more on it. In any case, in the event that it works, I’ll viably have the capacity to push introduces both on and offsite, without utilizing DirectAccess as the tie back. The powershell has a few if’s in there to check whether they’re on the LAN, which will then instruct it to snatch PDQ’s bundles, however on the off chance that they’re off, it’ll get them from the HTTPS store and shoot msiexec on them physically.
                                        Dafont 123Movies FileHippo

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

                                        198

                                        Online

                                        12.0k

                                        Users

                                        17.3k

                                        Topics

                                        155.2k

                                        Posts
                                        Copyright © 2012-2024 FOG Project