1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

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.

Move PDQ from one computer to another

Avatar
PTL

Hey everyone,

 

Before I proceed, just want to ask if anyone has performed this and if there is anything else I need to do.

https://support.adminarsenal.com/hc/en-us/articles/220538247-Webcast-Moving-PDQ-Deploy-to-a-New-Machine

Basics gathered from video 

  • ensure the same version is on both new and old
  • export the registry keys
  • stop the PDQ services
  • export the database
  • new computer setup - run the reg file to merge and install PDQ
  • stop the PDQ service
  • copy the database over

 

Question :

Does the new computer have to have the same name as the original computer?  Does it matter?

Note : I have deployment files spread between a file server and locally on the computer PDQ is installed on. Was testing the push/pull mode on our network. I don't mind changing referenced locations of files both locally and file server, but wanted to save some time. 

Thanks

Patrick

 

 

 

 

 

0

Comments

3 comments
Date Votes
  • Avatar
    Stephen Valdinger

    I don't *think* it should matter. Typically if you are using the Repository on the PDQ Server for Push deployments the packages is setup with a ($Repository) variable, which is a system variable. So, in theory, no, the machines do not need to have the same name. 

     

    This gets more complicated if you are using scripts/etc that reference the current server by name of course, but in general shouldn't be an issue.

    0
  • Avatar
    PTL

    Just checked my Repository and looks like I changed it to the file server for the purpose of using pull.

    Jotted down on list of the stuff to check. Tackling this one tomorrow. 

    Thanks Stephen

     

     

    0
  • Avatar
    systemsolutions

    in my experience, i have almost all of my deployments point to a different locations (meaning file server with software cache.  i rarely use the import from the software library. 

    at this point, i just exported the list as the xml file and imported it back into the deploy program on the new box.  i would assume that if you have the $repository folder, you can simply copy and paste to the new box in the correct location, and also use the import/export for all deployments to the new box.

    i can not verify that however so take it with a grain of salt.

     

    0