Windows 10: Why cant we connect our Windows 11pro to our domain

We have a server running windows server 2012r2 and we cannot connect new PC with windows 11pro running. We have created a new user account and device on the server. I've tried both changing domain name in windows 11pro and using the windows 2012r2 connection tool with no luck. I get error message domain not found. But I know its there.

:)

 

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

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account? The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join. Thoughts?

 

BOINC for Windows Domain Controllers

Long story short, BOINC stopped supporting domain controllers after version 5.10.45 and 5.10.45 broke because it's HTTPS security certificates are out of date. Requirements:

• Windows Server 2003 R2 x64 Edition or newer (must be 64-bit)
• Must have domain controller role installed.

If neither of these requirements are met, just use the latest version from Berkeley.

The solution:

• Download this ZIP from TPU (thanks @Wizzard!)
• Extract everything from the ZIP to the desktop or some place you can easily access it.
• Run "boinc_5.10.45_windows_x86_64.exe" to install 5.10.45 as normal.
• After it is installed, make sure BOINC is not running. If it is running as a service, you can stop it via Services. If it is running in the tray, right click on the tray icon and click on Exit.
• Navigate to where BOINC is installed. This is usually C:\Program Files\BOINC. You should see a ca-bundle.crt file here (it'll have a different icon from the rest). If you do, you're in the right place.
• Extract the contents of the "certificates" folder to the folder where BOINC is installed. You should be prompted to replace existing files. Do it. If you do not, you're likely in the wrong directory or copied the "certificates" folder instead of its contents. It is very important that the files inside of "certificates" overwrite the installed BOINC files.
• Start BOINC again. If it is a service, go back into Services and start the BOINC service. If it is a tray application, run it from your start menu. You'll also need to start the BOINC Manager if you have it installed as a service for the next step.
• Double click on the tray icon to open the BOINC Manager if it isn't already open. Click on the "Messages" tab and verify it is able to download tasks. If it is, you're good to go. If you see "SSL connect" errors lets us know by replying to the thread.

The "certificates" are copied from 7.6.22.