Today we’re playing catch up since we’ve missed a week or two getting your webcast recap published. During the week of October 17th, Lex and Katie walked us through how to access and use multiple central servers efficiently without all the stress. Since we are all about taking the easy road when it comes to sysadmin related tasks, this post will help you avoid needless tears and wake up wanting to go to work in the morning. It’s ok if you missed it live, you can still watch it below and even get caught up on different users’ questions.
Question: When I import a folder from Deploy to another Deploy console I will get a new folder (Folder2). Anyway to overwrite the old? 8:20
Question: I have central servers at all locations in the US and Mexico. I want to put one in my Brazil location. Does PDQ support being run in Brazil? Does PDQ offer packages for other countries with Deploy? 19:00
Question: Are there any potential conflicts with having the same PCs in two central servers? Ex, database getting screwed up, etc. 22:44
Question: Upgrading server OS, would you recommend setting an existing client-server as the central or just creating one from new? Any potential conflicts with having the same PCs in two central servers? 26:35
Question: The PDQ.COM CORPORATION cert is expiring tomorrow, how will that be addressed? 28:08
Question: It takes quite some time to open the help menu (F1) on my clients apps. Why is this? Will there be a fix in the future? 29:58
Question: We have one client-server currently running 2016, so should I make that the central or make new one central? 30:57
Question: Suggestions on how to copy packages to multiple sites and set up the deployments to use their local site repositories? Essentially setup PDQ Deploy to mirror distribution points in SCCM. 32:14
This recap was short and sweet but thanks for catching up with us and as always make sure to tune in every Thursday at 10 Am MST to PDQLive if you don’t want to miss us live.