Windows 10: Setup a new user with a work domain name

What is the proper procedure for creating a work account with a work domain for a user on a new PC? I know how to create a local user, but the local user cannot access the SharePoint and O365 desktop apps. They can login to Office or Outlook.com but the PC wants the user to sign-in with a Microsoft account.

:)

 

Getting a domain name...

Just simple 3 steps to make your website glow to millions…
Step 1: Sign up now and get a FREE domain!
Step 2: Design your new website in minutes!
Step 3: You are live! Share your life online!

Click here…

 

User Name or Password Incorrect When Trying to Log In as Domain User

I've tried searching repeatedly for an answer to this problem but I seem to be getting nowhere.

My client purchased a desktop PC with Windows 10 Home edition installed. I upgraded the machine to Windows 10 Pro. I added a Microsoft account to the machine.

I logged in using this account and added the machine to the domain (Windows Server 8). When prompted to enter a domain user account, I used my Administrator account. The machine was added fine. I can see it in the list of devices on the server.

Now when I try to log in to the machine as a domain user or the domain administrator, I get an error. Here are my steps at the login screen:

1. Click on Other user (Note that "Sign in to: <DOMAIN>" is displayed)

2. Enter user name (I've also tried DOMAIN\User and *** Email address is removed for privacy ***)

3. Enter password.

4. Click on arrow.

5. Message displayed is "The user name or password is incorrect. Try again."

I've tried multiple domain accounts and verified their passwords. It seems that only the local/Microsoft account will let me into the PC.

 

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