User credentials cannot be used for local connections

[notnAP]

Running Batchpatch 2023.3.30.18.3 on Win 10 (fully patched) in an AD Domain.
Roughly after recently upgrading to that vers of batchpatch (and who knows how many patch tuesday updates) I’m noting that I cannot use batchpatch to manage the computer batchpatch is running on.
Doing even a simple Get Host Name returns “User credentials cannot be used for local connections”
I’ve tried using a domain admin login and a local admin login, with no change.
I know I’d seen his problem in the past, but do not know how I got beyond it.
I have seen the instructions on specifying alternate credentials, including the registry tweak that may be necessary on help pages like https://batchpatch.com/using-alternate-logon-credentials-in-batchpatch
I do remember from the last time I saw this problem that in addition to these instructions, a special step was needed when the computer you are trying to manage also happens to be the computer you are running BatchPatch on, but I haven’t found that page.
Any ideas?

[doug]

You can’t use alternate credentials to connect to the local computer. Remove the credentials so that BP uses integrated security (no credentials) to connect to the local computer. Generally if you want to put the local computer into BP as a target computer then you have to use integrated security (no alternate credentials) and run BP elevated as admin. If you don’t run BP as elevated in this scenario, you’ll find that some things work and others do not.

[Author]

Posts