Windows Admin Credentials Not accepted to run as service

[cjamt]

Attempted to enable Run As Service but BI does not recognize credentials for local admin account. Any suggestions?

 

[cferd5]

I've seen this. If you've changed your Microsoft account password after the PC was already set up, you need to use the old password not the new one.

 

[cjamt]

I've seen this. If you've changed your Microsoft account password after the PC was already set up, you need to use the old password not the new one.

Thanks for the reply. This was a clean install of Win 11 Pro. The admin PW has not changed. If that is the way BI works, it seems a little screwy to me. Any other ideas? Thanks again.

 

[cferd5]

I've used the same Admin username and password for both BI user and local user account without a problem. But if you're looking to keep the password as BLANK, the Help files describe an override when you can't login.

 

[cjamt]

Copy. However, my local admin account requires user name and PW. I prefer it that way. Where is BI looking to verify credentials?

 

[cferd5]

Is the local admin account what you use to log into Windows?

 

[looktall]

Create a new local account with admin privileges.

 

[IAmATeaf]

As above the account needs to be a local admin account and not a cloud MS account.

 

[cjamt]

I do not allow Windows to phone home. The account is a local admin account and the original account on the machine. I found this link which I thought might work but to no avail: Managing “Logon As a Service” Permissions Using Group Policy or PowerShell – TheITBros. I have a ticket in with BI but I don't know when I will hear from them.

 

[IAmATeaf]

The other thing it could be as I’m sure I’ve read that somebody else had this issue is the characters you use in the password. Can’t quite call but it might be worth resetting the password to remove any special chars to see if that changes the behaviour?

 

[cjamt]

Thanks for the reply. That is an interesting thought. I do use special characters in my PW for Windows and it works fine logging into windows. But, as I understand it, all BI should be doing is authenticating the credentials. They are what they are. It just seems that BI is not able to look in the right place or have the right process to authenticate. I just got a response from BI support. It basicly said create another admin account which just does not sound right. I responded and I am waiting for a response. Thanks again for taking the time to reply.

 

[cferd5]

Just for kicks I created a new local admin account. Unchecked the "Run as a Windows service" box in BI, restarted, Checked the box again and entered the new credentials which were accepted without a problem.

 

[cjamt]

Hmmm... Thanks for taking that step. I might have to try that. Did your new PW have special characters? I would have to break my system of setting up accounts in each of my 3 machines the same. Same credentials for each. Makes admin easier as my setup is not to remember the last user and require Cntl.Alt-Del to get the login screen. Might be a last resort. Thanks again.

 

[AzN_NiNjA01]

try using "Administrator" instead of "Admin" as user. That is how mine is setup.

 

[cjamt]

try using "Administrator" instead of "Admin" as user. That is how mine is setup.

Thanks. I use a name for mine. Not Admin or Administrator. I always disable the default admin account.

 

[AzN_NiNjA01]

Thanks. I use a name for mine. Not Admin or Administrator. I always disable the default admin account.

You could try doing blank user and just put in the pass. I think it was blank if you want localsystem

 

[cjamt]

Interesting. I wonder what PW I would use?I might give it a try to see if it works. Not something I would want to run with in the long term.

 

[AzN_NiNjA01]

Interesting. I wonder what PW I would use?I might give it a try to see if it works. Not something I would want to run with in the long term.

didn't you say you have a windows user and not the default admin and a password to log into your windows account? Try leaving the user part blank and use the windows login pass to turn on run as services to see if it works

 

[cjamt]

Hmmmm. Now I get it. A little slow. I will give that a try.

 

[cjamt]

Nope. No joy. This time, instead of "(1326)" at the end of the error dialogue it is now "(87)". Thanks for trying.