Hey guys thanks for watching and here is the OCT link that was used to create the XML file for Office 2019 - config.office.com/deploymentsettings As always, thank you for the support and be safe everyone 🤓
Thank you for this one. PDQ and their support is great. These videos are made for people like myself that are dropped in to manage these systems and need to figure it all out on the hop
Been using PDQ Deploy and PDQ Inventory for a few years now and love their software. We have 4 SysAdmins using it at our company. Very affordable for smaller businesses and an excellent support team. And the PowerShell integration is off the chart!
Both PDQ applications have been saving me tons of time for years. It’s super easy to use and user friendly. In our environment we have the enterprise license. What’s great is the fact you can use power shell scripts to help with either tasks to either shutdown, reboot etc or vulnerabilities. There are tons of things you can learn on it.
I would agree with you 100%. it’s very user friendly. I played around with powershell scripting on it a little bit, but this software is really awesome. might have to make this my to go application deployment at the job.
BTNHD what you will enjoy is how you can also create uninstall packages with PDQ inventory. And you can create target lists with PDQ inventory that you can use with PDQ deploy. Example; since you deployed your Microsoft package, instead of adding it manually, you can choose, target lists, or use a txt file that you save and you can choose inventory. But make sure you have also synced your AD OUs so it can reach it. Also you can create and add scripts on PDQ inventory that you can push manually to a specific workstation and or laptop.
You can manipulate your MDT Task Sequences to call for PDQ Deploy packages too. It's great for keeping your "golden image" under control because you can start using PDQ Deploy to manage your application versions.
We use PDQ deploy @ my work as well it work well with AD. You can even use it too keep PC's up to date as it will auto download all the Windows 10 patchs. That's if you don't use WSUS.
We use PDQ Deploy and Inventory and SCCM. PDQ Deploy blows away SCCM for Applications deployments. I wrote a very simple powershell script that triggers the office 2019 Click to Run installer with the source be a local server on my network, of clients hitting MS' CDN.
@@bjtechnewshd yeah it works super easy. Office 2019 removes 2016 and installs 2019 in average time of 7min and change. You should try out PDQ Inventory. It works agent-less and can tell you everything about the PCs and Servers on your network
PDQ Deploy is nice but how do you deal with 5k clients spread across multiple sites with various link speeds? Is there a distribution point concept because pushing 2GB Office files to each machine across the links doesn't sound like a good idea..
Adrian Kielbowicz I don’t have 5k clients, but almost a 1/3 of my deployed clients rely on spotty cell phone signal. (Almost 200 laptops). They are connected through persistent VPN setup. So even if I pushed it from the internet CDN it would have to come in and go out again. It is a little slower over the cell, but doable. If you are dealing with split tunneling or multiple internet access at various locations Deploy can still push the config flies and execute the install while downloading the file from the MS CDN.
@Colby Bouma Thanks. DFS is certainly one way of going about making sure the content will be available. Is there anything like DFS built into PDQ though?
This video was good but what about users that are still logged in to the computer. In a real world setting this is how we would set it up but you would be scheduling something this for after hours or over the weekend. 80% of my users never logoff or close all there programs. Therefore most Office 2013 applications would still be open and running. Would this same setup work if you added a reboot or logoff step?
Question for you, hopefully you see this. I'm in a unique environment in the sense that the environment is within a domain but I do not have access to a domain administrator account. However, I do have access to the local administrator account that I've setup in each system across the office (Same username, same password across all of the clients). Do you think it's possible to setup PDQ deploy in the same fashion and push packages using the local administrator account? or would I need to install those client executable on each machine? Normally I would test this on my homelab but I'm in the midst of a move and have packed it away which has proved to be a bad idea. Let me know your thoughts. Thanks.
Hey guys thanks for watching and here is the OCT link that was used to create the XML file for Office 2019 - config.office.com/deploymentsettings
As always, thank you for the support and be safe everyone 🤓
I been using this application for years and it is definitely a nice alternative. I suggest it for anyone who cant afford SCCM.
Yes, I was very impressed on how easy creating a package within PDQ Deploy was.
Thank you for this one. PDQ and their support is great. These videos are made for people like myself that are dropped in to manage these systems and need to figure it all out on the hop
Been using PDQ Deploy and PDQ Inventory for a few years now and love their software. We have 4 SysAdmins using it at our company. Very affordable for smaller businesses and an excellent support team. And the PowerShell integration is off the chart!
My company it's using PDQ Deploy and PDQ Inventory. Both 👍👍👍, alternative solutions for those who can't afford sccm like my company. Easy to use
I would agree with you on that.
Both PDQ applications have been saving me tons of time for years. It’s super easy to use and user friendly. In our environment we have the enterprise license. What’s great is the fact you can use power shell scripts to help with either tasks to either shutdown, reboot etc or vulnerabilities. There are tons of things you can learn on it.
I would agree with you 100%. it’s very user friendly. I played around with powershell scripting on it a little bit, but this software is really awesome. might have to make this my to go application deployment at the job.
BTNHD what you will enjoy is how you can also create uninstall packages with PDQ inventory. And you can create target lists with PDQ inventory that you can use with PDQ deploy. Example; since you deployed your Microsoft package, instead of adding it manually, you can choose, target lists, or use a txt file that you save and you can choose inventory. But make sure you have also synced your AD OUs so it can reach it. Also you can create and add scripts on PDQ inventory that you can push manually to a specific workstation and or laptop.
You can manipulate your MDT Task Sequences to call for PDQ Deploy packages too. It's great for keeping your "golden image" under control because you can start using PDQ Deploy to manage your application versions.
good to know, but NO!!! golden images! I don't like them but good tip about PDQ Deploy and MDT. I have to look into that. Thanks 🤓
@@bjtechnewshd Poor word choice on my part. I don't actually use a golden image - just bare bones OS that's fully patched.
We use PDQ deploy @ my work as well it work well with AD. You can even use it too keep PC's up to date as it will auto download all the Windows 10 patchs. That's if you don't use WSUS.
SCCM is great for big enterprises and lots of sites. PDQ is great for small to medium size businesses. I started with PDQ in 2011/2012 it’s fantastic
I'm enjoying PDQ Deploy a lot. I might have to budget in the software for my job 😀
BTNHD I’ve never tried imaging a machine via PDQ so you may be relying on SCCM still. Be sure to check out PDQ Inventory as well.
We use PDQ Deploy and Inventory and SCCM. PDQ Deploy blows away SCCM for Applications deployments. I wrote a very simple powershell script that triggers the office 2019 Click to Run installer with the source be a local server on my network, of clients hitting MS' CDN.
Wow! what a setup. You're on point with your deployment environment nice!! 🤓
@@bjtechnewshd yeah it works super easy. Office 2019 removes 2016 and installs 2019 in average time of 7min and change. You should try out PDQ Inventory. It works agent-less and can tell you everything about the PCs and Servers on your network
PDQ Deploy is nice but how do you deal with 5k clients spread across multiple sites with various link speeds? Is there a distribution point concept because pushing 2GB Office files to each machine across the links doesn't sound like a good idea..
Adrian Kielbowicz I don’t have 5k clients, but almost a 1/3 of my deployed clients rely on spotty cell phone signal. (Almost 200 laptops). They are connected through persistent VPN setup. So even if I pushed it from the internet CDN it would have to come in and go out again. It is a little slower over the cell, but doable. If you are dealing with split tunneling or multiple internet access at various locations Deploy can still push the config flies and execute the install while downloading the file from the MS CDN.
@Colby Bouma Thanks. DFS is certainly one way of going about making sure the content will be available. Is there anything like DFS built into PDQ though?
This video was good but what about users that are still logged in to the computer. In a real world setting this is how we would set it up but you would be scheduling something this for after hours or over the weekend. 80% of my users never logoff or close all there programs. Therefore most Office 2013 applications would still be open and running. Would this same setup work if you added a reboot or logoff step?
Question for you, hopefully you see this. I'm in a unique environment in the sense that the environment is within a domain but I do not have access to a domain administrator account. However, I do have access to the local administrator account that I've setup in each system across the office (Same username, same password across all of the clients). Do you think it's possible to setup PDQ deploy in the same fashion and push packages using the local administrator account?
or would I need to install those client executable on each machine? Normally I would test this on my homelab but I'm in the midst of a move and have packed it away which has proved to be a bad idea.
Let me know your thoughts.
Thanks.