hello thanks alot if i have site token and i want to attach it to the agent i want to install how and if i have workgroup and i want to install as package on many devices
Hmm i was just wondering if you can export them into a single exe or msi package since my workplace doesn't have a server yet, the active directory thing is not an option for us.
PDQ Deploy does not have the ability to export into a portable installation file, however, you can export packages between consoles in an air-gapped environment. If you need help with specifics or can give us more detail, please email support@pdq.com.
If you have an account that exists on ALL of the machines in a workgroup, that should work. The credentials should have local admin rights. A "Server" does not have to exist; is not a limiting factor. Good luck.
I'm not familiar with that error. A good idea is to try to get the installation to run silently from an elevated command prompt running as the deploy user.
So im still confused the difference between exe and msi ?????? Are we only using silent particular exe file ? About the softwares that’s in the library are those ready to be push or do u have to add an /S???
Without going into too much detail on msi and exe, both can be used to install software, but they behave in different ways. MSI complies with current standards that make it easier to work with on our end, while exe allows the developer a lot more control, but their parameters can change based on whoever created it. For how it works for our products? Because MSI follows a standard the silent parameters are never going to change, and because of that if you choose an msi file to install we will add the silent parameters for you. Exe has no standard so we cant enter the silent parameters by default. If the package you are using is in the package library then we will have done the research for you and have the needed silent parameters ready to go. The only spot where you need to go searching for your own is if you are building a custom package that has an exe for the installer. - Jordan
I have not looked into installing either of those, but if they require the application not to be running to install we have a few options. I think the best would be to have a powershell step as step on that tests for the process. Not knowing the process name for autcad I used notepad. if(Get-Process notepad){ Exit 42 } This example will exit the powershell with error code 42. This will not install, but let you know the reason it failed is that the application is running. If you wanted to be REAL aggressive at getting this done change the exit 42 to powershell command to kill the process. That will test for the process, kill it if found, and then go on to the install….probably make some people angry with that route though. - Jordan
msix can install with powershell using the add-apppackage command. If you add the msix file in the additional files of the powershell step and have that run "Add-AppPackage -Path ".\filetoinstall.msix" it should install for you. I tested this our with the msix install of windows terminal and it seems to work great! - Jordan
Hey Lex, thanks for the video. Very informative, and I enjoyed your educational style.
A side note - many installers have case sensitive switches, watch out for those!
thx
hello thanks alot
if i have site token and i want to attach it to the agent i want to install how
and if i have workgroup and i want to install as package on many devices
Hmm i was just wondering if you can export them into a single exe or msi package since my workplace doesn't have a server yet, the active directory thing is not an option for us.
PDQ Deploy does not have the ability to export into a portable installation file, however, you can export packages between consoles in an air-gapped environment. If you need help with specifics or can give us more detail, please email support@pdq.com.
If you have an account that exists on ALL of the machines in a workgroup, that should work. The credentials should have local admin rights. A "Server" does not have to exist; is not a limiting factor. Good luck.
What is that song? Reminds me of a band called the Life and Times
Not Life and Times but from a band called DERM song Old Man
ruclips.net/video/BDU64BNSVS4/видео.html
Hello how are you, I'm Brazilian, can you tell me why error extended appears when I try to install an app through PDQ DEPLOY?
I'm not familiar with that error. A good idea is to try to get the installation to run silently from an elevated command prompt running as the deploy user.
So im still confused the difference between exe and msi ?????? Are we only using silent particular exe file ?
About the softwares that’s in the library are those ready to be push or do u have to add an /S???
Without going into too much detail on msi and exe, both can be used to install software, but they behave in different ways. MSI complies with current standards that make it easier to work with on our end, while exe allows the developer a lot more control, but their parameters can change based on whoever created it.
For how it works for our products? Because MSI follows a standard the silent parameters are never going to change, and because of that if you choose an msi file to install we will add the silent parameters for you. Exe has no standard so we cant enter the silent parameters by default. If the package you are using is in the package library then we will have done the research for you and have the needed silent parameters ready to go. The only spot where you need to go searching for your own is if you are building a custom package that has an exe for the installer. - Jordan
Can I run this install if a user has Revit or Autocad open and running/using???
I have not looked into installing either of those, but if they require the application not to be running to install we have a few options. I think the best would be to have a powershell step as step on that tests for the process. Not knowing the process name for autcad I used notepad.
if(Get-Process notepad){
Exit 42
}
This example will exit the powershell with error code 42. This will not install, but let you know the reason it failed is that the application is running. If you wanted to be REAL aggressive at getting this done change the exit 42 to powershell command to kill the process. That will test for the process, kill it if found, and then go on to the install….probably make some people angry with that route though. - Jordan
@@pdq Ok, i will test soon. I hope it works. Been stumped for a while. Thank you.
how do we use msix in PDQ Deploy?
msix can install with powershell using the add-apppackage command. If you add the msix file in the additional files of the powershell step and have that run "Add-AppPackage -Path ".\filetoinstall.msix" it should install for you. I tested this our with the msix install of windows terminal and it seems to work great! - Jordan