Windows 10: Auto Login to Domain no longer works after upgrading Windows 11 to 24H2

Hello,I work for a school district using that is using smart panels in the classrooms using a windows PC for teachers to use. Since these are big touch screen devices, we have them auto-login to a specific Active Directory account so that the panel can be used without having the teacher sign in using the on-screen keyboard and showing what their password is. This has been working fine for years until last week when we pushed the 24H2 update. Now, any panels that were upgraded, no longer auto-login to the system. Every 30 seconds or so you can see the screen flash like it is trying to login

:)

 

Factory reset Windows 11 24H2 (build 26100.863)

Hi, I am Dave, I will help you with this.

There are no currently listed problems resetting version 24H2 of Windows 11 and no specific steps you need to perform, are you experiencing any problems with that insider build that is causing you to perform a Windows reset?

 

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

 

Auto login and pictures at login

Hi,



Thanks for writing to Microsoft Community Forums.



Though you have enabled auto login and there is no lock screen, you should still be able to see the user account picture on the Welcome screen and the same picture (set as user account picture) can be set as the login page background.



To set the custom picture as the login screen background, please follow the steps given below.

• Go to Settings->Personalization->Lock screen.
  
• Click on the dropdown list under Background and select
  Picture.
  
• Click on the Browse button under
  Choose your picture.
  
• Browse to the location where the picture is saved and select the desired picture.
  
• Similarly, to set the same image as the user account picture, open the Settings app.
  
• Go to Accounts->Your info->Browse for one.
  
• Browse to the location where the image is saved and select it to set it as the user account picture.
  

Since you’re on the Enterprise edition of Windows 10, we do have a dedicated support forum for Enterprise versions of Windows, Windows servers and systems which are part of any domain or corporate environment. I suggest to post your query in Microsoft
TechNet forums for further help and information about
this issue.



Regards,

Peer Samie

Microsoft Community-Moderator