AD Account Getting Locked

[jsira7]

Hey Doug… For some reason my account keeps getting locked out each time I try to initiate any type of deployment command within Batch Patch. I’m logged into our Batch Patch server with a Domain Admin account (different from the one being locked), but each time I try to Deploy Software it immediately gives off the error:

Deployment: Error: Failed to create remote working directory. Please check permissions on the target computer and verify your target working directory path in Actions > Deploy > Create/modify deployment: The system cannot contact a domain controller to service the authentication request. Please try again later.

And it locks my account, which is different from the account that I’m logged into Batch Patch as. Are there any areas within Batch Patch that would hard code credentials?

[doug]

If you entered ‘alternate credentials’ for a given row in the BatchPatch grid, then BatchPatch would use those alternate credentials. They are stored per-row. If you didn’t enter them, then BatchPatch will use ‘integrated security’ and try to perform the action using the account that was used to launch BatchPatch.exe.

I cannot imagine any circumstance in which BP would/could trigger your account being locked out. Furthermore, we have never heard any report of similar issues. Lastly, the message that you are seeing “The system cannot contact a domain controller” does not sound like a lockout issue. It’s sound like maybe a DNS issue or a network connectivity issue of some kind, assuming that there is actually a domain controller available but just not able to be reached.

-Doug

[jsira7]

Thanks for the quick response. I haven’t used any alternate credentials. Is there a way to view what’s being used for ‘integrated security’?

Yeah, that’s the weird part. Each time I try to deploy software it immediately locks out my account and gives off that error message. I did try to use alternate credentials just a second ago with a different domain admin account and it worked. But when I perform it straight from the grid without using alternate credentials it locks my account.

[doug]

The account that is being used for integrated security is the account that is used to launch batchpatch.exe. So if you are logged on to the computer as “Domainuser1” and you launch BatchPatch by doubleclicking the batchpatch.exe, then the account that BatchPatch will use for integrated security is “Domainuser1” If you use “run-as” to launch the batchpatch.exe with a different account, then whatever account you specify in the “run-as” dialog will be the account used by BatchPatch for integrated security.

In the current version of BatchPatch the account that was used to launch BatchPatch is displayed in the lower-left corner of the main window. This can be disabled/enabled under ‘Tools > Settings > General > show ‘running as’ user label…’ If you do not see this option then you are not running the latest version of the application.

As for your account lockout situation, I really don’t know what to make of it. It sounds like some type of issue with your environment/configuration, not an issue with BatchPatch. Maybe consider reviewing the security policies in place on the network. Maybe review the security logs on your domain controller(s).

-Doug

[Author]

Posts