Possibility of multiple background services?

Comments

5 comments

  • TonsOFun

    You could use local accounts? Well, firstly, you'd have to create a local account using a batch file... "Backdoor", "Admin", etc will work. This way all machines have a consistent local account with the same password. (of course if it doesn't exist already). 

    0
    Comment actions Permalink
  • Brigg Angus

    Another option would be to install PDQ Deploy on an additional console (or two) to allow for the concurrent deployments. You could also have a console for each domain to eliminate the need to change background service credentials.

    0
    Comment actions Permalink
  • Ken Staude

    That is our current workaround, when working with our customers we try to as much deployment from a single server if at all possible.

    0
    Comment actions Permalink
  • Michael Muni

    PDQ does allow you to setup multiple credentials.

    you could split up your schedules to target computers on a specific domain and use the credentials for that domain on the schedule settings. By making a separate schedule for each of your domains it would then use the correct credentials for each machine.

    Just right click the schedual, select duplicate, change the credentials to be be used, and then change the targeted machines to only the ones you want to target with the chosen credentials, Give the schedule a new name that includes the domain.

    0
    Comment actions Permalink
  • Ken Staude

    Yeah, where that does work for a good amount of machines, there seem to be still some machines where it doesn't like having the background credentials of another domain. Only when do we set the background credentials + deploy credentials as the same will the servers not get the Access Denied. 

    So until we're able to set the background credentials + deploy credentials per deployment or schedule, we're sticking with the workaround outlined but Brigg's above and using multiple machines, one for each domain.

    I couldn't tell you exactly the configuration as we go from customer to customer and the trusts and permissions are always a little different, but have seen this a few times where this has happened. 

    0
    Comment actions Permalink

Please sign in to leave a comment.