I hope that I explained my self a little bit. As you might see, english is not my first language, apologise. Right click the Start button , select System , under Windows edition , confirm your Windows 10 edition. If it's Windows 10 Home edition, it's not allowed to join the domain. Windows 10 Pro, Enterprise and Education edition could join the domain. If it's not Windows 10 Home edition, please Right click the Start button , select System , under Computer name, domain, and workgroup settings , check if your computer is a part of workgroup or domain.
Note: you need sign in local administrator account to do above steps and provide a domain user account to join the domain. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.
If you have feedback for TechNet Support, contact tnmff microsoft. Was your issue resolved? If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
Did you mean:. Sign In. Sonia Cuff. Published Aug 03 AM Pre-requisites To start with, let us assume that the Windows 10 device you are logging on with is Hybrid Joined. The hybrid join single-sign-on process The computer's Local Security Authority has already done its thing, using Keberos to authenticate you to the Active Directory Domain. So what's a PRT? A PRT is issued to a user on a specific device. The session key is used to sign requests for tokens and requests to renew your PRT.
Accessing an application When you open an application that has Azure Active Directory as its identity provider, another part of the process kicks in. Tags: authentication. Version history. Last update:. Updated by:. Education Microsoft in education Office for students Office for schools Deals for students and parents Microsoft Azure in education. Education Sector. Microsoft Localization. Microsoft PnP. Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.
Privacy policy. This reference topic for the IT professional summarizes common Windows logon and sign-in scenarios. The Windows operating systems require all users to log on to the computer with a valid account to access local and network resources. Windows-based computers secure resources by implementing the logon process, in which users are authenticated.
After a user is authenticated, authorization and access control technologies implement the second phase of protecting resources: determining if the authenticated user is authorized to access a resource. The contents of this topic apply to versions of Windows designated in the Applies to list at the beginning of this topic. In addition, applications and services can require users to sign in to access those resources that are offered by the application or service.
The sign-in process is similar to the logon process, in that a valid account and correct credentials are required, but logon information is stored in the Security Account Manager SAM database on the local computer and in Active Directory where applicable. Sign-in account and credential information is managed by the application or service, and optionally can be stored locally in Credential Locker.
To understand how authentication works, see Windows Authentication Concepts. The logon process begins either when a user enters credentials in the credentials entry dialog box, or when the user inserts a smart card into the smart card reader, or when the user interacts with a biometric device. Users can perform an interactive logon by using a local user account or a domain account to log on to a computer. Credentials that the user presents for a domain logon contain all the elements necessary for a local logon, such as account name and password or certificate, and Active Directory domain information.
The process confirms the user's identification to the security database on the user's local computer or to an Active Directory domain. This mandatory logon process cannot be turned off for users in a domain.
0コメント