Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Switching from SCCM - client access questions in PDQ

Mike Sanders

April 02, 2021 15:17

Hello,

We are planning on transitioning to PDQ Deploy for our package deployments, but have a few questions...

1. I noticed that both file and print sharing and network discovery must be enabled on the client PC in order for them to receive package pushes. For security reasons, we wouldn't want to leave these turned on in the long-term. What is the recommended practice for configuring these settings from PDQ's point of view?

2. 40% of our clients are remote users connected via VPN. What is recommended for us to integrate these users seamlessly so that they can receive packages without issue? Is the RAS VPN tool recommended for this integration?

Thanks!

Comments

1 comment

Colby Bouma
April 02, 2021 16:23
1. PDQ is agentless, so those services need to be left on. You can configure client-side firewall rules to only allow access from the PDQ server. Here are the ports that PDQ requires: https://help.pdq.com/hc/en-us/articles/220533627-Windows-Firewall-Ports-and-Exceptions
2. The RAS VPN tool is one way to do it, but if you already have a VPN you can probably configure it to work with PDQ. https://www.pdq.com/blog/using-your-vpn-to-manage-your-remote-computers-with-pdq/
  https://www.pdq.com/blog/setting-up-pdq-to-work-with-remote-workers/
0