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.

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again

Hello,

I am getting this error for some computers on Deploy. This is a reoccurring issue, and I know if I restart the Deploy background service it will fix it. However, the problem is, this is happening for deployments that are sent at night to do patches/updates/reboots. So restarting the Deploy background service every time I get the error is not a good enough fix.

Right now if I try to deploy to that computer, I get that error. I can scan it from Inventory just fine, I can manually connect to the admin share, I can test the IPC share, and if I do a remote repair, everything is green. I just can't send any deployments to it.

I have talked to support and haven't found a resolution yet. Here is what they've had me do:

  • Separate the Deploy and Inventory servers from one another.
  • Change the background service account to be a local admin.
  • Try checking for active SMB sessions and closing them.

I'm sure there's a few other things but I can't think of them at the moment.

Has anyone else ran into this? We really like PDQ here but as it's our main tool to send windows updates, we simply cannot have it failing so often. I would really prefer not to go to a different tool because of this.

Thanks

0

Comments

1 comment
Date Votes
  • Does your domain have two words in the name? (ex: company.com)

    Are the targets remote (VPN connection)?

    This sounds similar to what I ran into with Inventory and I wound up changing the username from "company\username" to "company.com\username" which seemed to help.

    This seemed to help in my case though i won't claim to know why of if it was purely coincidental.

    0