Windows 10: this email is part of a reserved domain issue 2020

I clicked "update info" in "settings - accounts - your info" and attempted to add my Microsoft account but keep having the message"this email is part of a reserved domain. please enter a different email address" pop up.


what does it mean and how do i get around it to add my Microsoft account to my computer?


cheers



:)

 

This email is part of reserved domain.

I'm trying to add my daughter to my Windows 10 laptop Users. I get the error, this email is part of a reserved domain. It's my domain name, set up as work, and set up on my laptop as work account (added to Azure too). Now, why can't I add her? I added
my wife.

What is the reason for Reserved Domain?

 

Possible Fix ->This email is part of a reserved domain. Please enter a different email address ...

After spending 5 hours chatting with some nice people with MS Tech support, I thought I would post this. The other questions and discussions I searched and read were not helpful but maybe this will help others' that have the same problem as I did.

I have a microsoft account I created when they upgraded my work laptop from windows 7 to windows 10. My daughter created a microsoft account when she received a new laptop with windows 8 a couple of years ago. When I tried to upgrade our media center pc
from windows 7 to windows 10, it allowed me to use my microsoft account but would not let my daughter create her account. My work owns and runs their own email server. It handles my work domain and it hosts other domains that are free as part of other services
my work offers. When I created my account I used my work email address for registration. My daughter used her email address that is setup in the free domains given to other people from work. The strange part is windows 8/8.1 either of us can login with our
microsoft account login using our thrid party email addresses just fine but only mine works with windows 10. Come to figure out any email address from the free domains is automatically blocked through validation with the error "This email is part of a reserved
domain. Please enter a different email address".

The first tech person brushed off the issue saying limited support and repeated the error message. The second tech support person was much more helpful and even when so far as remote controlling the pc but in the end gave up saying I'd have to contact domain
accounts. In a very nice way, I was told MS has certain rules to follow and I'd have to contact them for support. The only important and critical information I was given by the second tech support person was my account might have been created as a business
account. Which got me to lookup exactly what domain account services really is. This led me to https://www.domains.live.com/ . By the way, my work has never and will never subscribe to any cloud services including Office 365. Other than hosting websites and
email services, the domains are not used internally nor do they use Active Directory Services. No one could offer an explanation why the domain was reserved by Microsoft after that information was shared.

Long story short if you use a third party domain email address as a username to create a microsoft account or an email address that is not one of the major players, they assume it is part of the domain account services even when it is not.

The solution is to login to your microsoft account through mail.live.com.

Click on the gear symbol or settings and click options.

Click on create an outlook.com alias. Verify your account.

Now you will have *** Email address is removed for privacy *** tied to your microsoft account as an additional username.

Now, you can add the existing microsoft account using *** Email address is removed for privacy *** as the username using your old password.

Since it is still your account only a different username, it will pull down your system settings that was tied to your account.

If your going to add your Microsoft account login to more Windows 10 computers I'd advise you keep the alias just to keep from having to perform all these steps again but if not then you can remove it.

I hope this saves someone else the time and aggravation this problem has caused me today. If anyone else has a better solution other than Microsoft should fix the windows 10 "add account email validation form field", feel free to respond. I'd really like to
hear information regarding how Microsoft classifies a domain as reserved.

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW