Off cause we want to avoid software that does not support silent install. Unfortunate it is not up to IT to decide what software to use :).
I am totally new to PDQ Deploy, but if I understand correctly I have two options.
Create an MSI from the EXE, or automate the install and run as the log on user.
I have tried to use AppDeploy in an installation, but it would not work. AppDeploy actually hangs when creating the package. So it does not work even on its own.
I have made an AutoIT installation that clicks threw the interface. This works beautifully when the user do not interrupt, (click cancel or something). AND the deployment in PDQ Deploy is set to “run as logged on user”. This however only works when the user is a local admin or has access to install software himself.
Any workarounds for this situation?
I was thinking something like; Wen running the deployment as “Logged on user”, how about in the same session use “RUNAS” some elevated user, but that would involve sending the password with the command.. right?. It can even be encrypted using this utility: http://www.softtreetech.com/24x7/archive/53.htm
And still there is the possibility that the users would somehow stop the installation by accident.. But better than nothing.
Is there any possibility that you would support a solution like this natively in PDQ Deploy? (add an RUNAS option in the “Run as logged on user” deployment, and passing the RUNAS credentials, encrypted)?
Another suggestion is to start a new RDP session to the computer to witch I want to install the software, and then deploy it and then close the RDP connection. I think I have all the steps necessary except running/starting the RDP session from the same machine as PDQ Deploy is installed on and killing it. Is there a way step where you can run “local” stuff. In local I mean directly on the PDQ Deploy machine.
Step1: Enable RDP (in case it is not)
\\adminarsenal\FileShare\Tools\psexec /accepteula \\%computername% reg add "hklm\system\currentcontrolset\control\terminal server" /f /v fDenyTSConnections /t REG_DWORD /d 0
\\adminarsenal\FileShare\Tools\psexec /accepteula \\%computername% netsh firewall set service remoteadmin enable
\\adminarsenal\FileShare\Tools\psexec /accepteula \\%computername% netsh firewall set service remotedesktop enable
Step2: Start RDP connection to the computer automaticly (this needs to run ON PDQ machine and offcause not on the remote machine witch I want to RDP to … )
powershell.exe "cmdkey /generic:TERMSRV/Win764TestOff /user:User@domain /pass:vrysecretpwd"
powershell.exe "mstsc /v:TheRemoteComputer"
powershell.exe "cmdkey /delete:TERMSRV/TheRemoteComputer "
Step3: Run the AutoIT install
Deployment set to “Run as logged on user”, this would now be the User@domain user.
Step4: Somehow log of user og worst case of terminal server user.
Step5: Kill terminal server process on PDQ Machine.
taskkill /im mstsc.exe
Biggest problem with this solution is to run stuff on the PDQ Deployment machine (Step 2 and step 5)…
And it could only be deployed to one machine at a time, since it killes the MSTSC. Or is there way to run the deployment in sequence on multiple computers, not in parallel?
When running these step 2 and 5 on the PDQ Deployment machine manually this works in fine J
I am off cause interested in other possible ways to install applications that have no silent install capability.
Please sign in to leave a comment.