Problems logging in with newly created Administrator account
Windows 10 Pro
I am setting up a new laptop for a client. They have a very active Azure AD. As an experiment I have set up the laptop using the Microsoft account for the user. This has worked brilliantly as the user and the laptop are nicely connected to Microsoft and the Active Directory.
However, I need to do two things...
(A) I need to add an Administrator User
(B) I need to change the original user I created to User rather than Administrator
So I go to Accounts and add a local (non-domain, non-Microsoft account) user.
I switch back to the original user who is still classed as "Administrator"
I go to Accounts and give my local user Administrator privileges
I have NOT yet downgraded the original user to "user"
I try to switch back to the new Administrator account and it asks for an Email address and Password. This is supposed to be a local account, not a domain registered or AD account. The account name has been changed (on the login screen) to "other user" rather than the name I gave the account.
Nothing I do gets me to a stage where I can login using the newly created local Administrator account.... what am I doing wrong?
I do know there is a "hidden" Administrator account but at this point I have not tried to use the policy editor to "unhide" it.
I really need to resolve this as soon as possible as I need to get this installation sorted and shipped to my customer. Any help would be seriously appreciated.
Cheers
Chris
P.S. This is the first time I've tried setting up in this way. Usually I would add a local account when setting up the laptop and then add the user account. The "new" way appears to be a great way to get this done as it automatically connects to "Work or School" and "Active Directory" without any further setup.
I am setting up a new laptop for a client. They have a very active Azure AD. As an experiment I have set up the laptop using the Microsoft account for the user. This has worked brilliantly as the user and the laptop are nicely connected to Microsoft and the Active Directory.
However, I need to do two things...
(A) I need to add an Administrator User
(B) I need to change the original user I created to User rather than Administrator
So I go to Accounts and add a local (non-domain, non-Microsoft account) user.
I switch back to the original user who is still classed as "Administrator"
I go to Accounts and give my local user Administrator privileges
I have NOT yet downgraded the original user to "user"
I try to switch back to the new Administrator account and it asks for an Email address and Password. This is supposed to be a local account, not a domain registered or AD account. The account name has been changed (on the login screen) to "other user" rather than the name I gave the account.
Nothing I do gets me to a stage where I can login using the newly created local Administrator account.... what am I doing wrong?
I do know there is a "hidden" Administrator account but at this point I have not tried to use the policy editor to "unhide" it.
I really need to resolve this as soon as possible as I need to get this installation sorted and shipped to my customer. Any help would be seriously appreciated.
Cheers
Chris
P.S. This is the first time I've tried setting up in this way. Usually I would add a local account when setting up the laptop and then add the user account. The "new" way appears to be a great way to get this done as it automatically connects to "Work or School" and "Active Directory" without any further setup.
ASKER
@John
Thanks for getting back to me...
Problem - the "first account" is the domain linked organisational account, linked to Microsoft and the Active Directory. It's only an Administrator account because it was the first account I created after setting up Windows 10 Pro.
The "second" account was an account I created using the Administrator privileges of the first account. This account needs to be a local machine account and that's how I set it up. Of course when it was set up it was set up as a "User" account not Administrator. So... I changed its type to "Administrator". Great - now we have a local Administrator account on the machine, without having to "un-hide" the built-in Administrator account.
The "first account" should not be an Administrator account, so I try to login as the second account (which has been elevated to Administrator) so I can downgrade the initial account to "User" but leave the account connected to the domain and AD. When I do this I get prompted with a username for an account called "other user" and which calls for an Email address and password. Aaaarrgh!
I'll try that and get back to you right away.
Many thanks
Chris
Thanks for getting back to me...
Problem - the "first account" is the domain linked organisational account, linked to Microsoft and the Active Directory. It's only an Administrator account because it was the first account I created after setting up Windows 10 Pro.
The "second" account was an account I created using the Administrator privileges of the first account. This account needs to be a local machine account and that's how I set it up. Of course when it was set up it was set up as a "User" account not Administrator. So... I changed its type to "Administrator". Great - now we have a local Administrator account on the machine, without having to "un-hide" the built-in Administrator account.
The "first account" should not be an Administrator account, so I try to login as the second account (which has been elevated to Administrator) so I can downgrade the initial account to "User" but leave the account connected to the domain and AD. When I do this I get prompted with a username for an account called "other user" and which calls for an Email address and password. Aaaarrgh!
First, make sure the First Account at installation time remains a member of Administrators.
Then, delete the other Account and restart the computer.
Now try making a Local Account again and make sure (a) it is local and (b) has a password.
Does that work?
I'll try that and get back to you right away.
Many thanks
Chris
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@John
OK - I tried that but it hasn't worked. I guess my next step is to reset the machine and start again, this time using a local account (i.e. non-Organisation account) when I set up the first User.
I'll let you know when that's done and perhaps you can then tell me how your team goes about adding the unit to the AD etc.?
Many thanks
Chris
OK - I tried that but it hasn't worked. I guess my next step is to reset the machine and start again, this time using a local account (i.e. non-Organisation account) when I set up the first User.
I'll let you know when that's done and perhaps you can then tell me how your team goes about adding the unit to the AD etc.?
Many thanks
Chris
I think that would be the best thing to do.
Chris, This is just a shot int he dark, but you may have luck with checking the Local Security Policy for logon, and specifically specifying that you want the logon to be for a local account and not for an online services account.
ASKER
Thanks so much, John, for your input on this. I set the unit up first with the local Admin account, then create the user account. I have managed to get the user added to the School or Work account and all looks good at this point.
Cheers to all for your replies.
Chris
Cheers to all for your replies.
Chris
You are very welcome and I was happy to help you.
Then, delete the other Account and restart the computer.
Now try making a Local Account again and make sure (a) it is local and (b) has a password.
Does that work?
Then change the password of the First Account so the user does not know this password.
Now all should be fine. Do not enable the built-in Admin account.