Windows 10: Can't login domain user to Windows

We have 1 domain user can't login his account into this Shared PC already join domain, this PC is using Wi-Fi, not LAN. Error: We ran into a problem with one of the following setup steps. For more help, contact your organization's support person. Account Setup: Failed. Solution we have tried: Bring this PC to admin, plug LAN cable, gpupdate/force, Windows Update and try login again -> can't. Remove User Profile and try again -> can't. Check user account AD -> normal Test login user account on Helpdesk personal laptop -> normal. Test Helpdesk account on this

:)

 

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

 

Windows 10Pro unable to login 2008 domain from domain user after upgrade

• I upgraded our Windows 7 Pro to Windows 10 and it's done successfully
• When I log in with domain Administrator account and it works fine
• But when I tried to log in with existing domain user or new domain user after entering the password the welcome screen shows then sign out immediately

• Windows 10 Pro is activated by digital license
• Windows 10Pro inbuilt antivirus only
• Windows 2008 R2 Domain controller -- Forest and domain set as 2008 R2

[Moved from: Windows / Windows 10 / Windows update, recovery, & backup]

 

How can I get this mapped drive to reauthenticat at login

I'm trying to get this mapped drive on an xp machine to reauthenticate when the computer reboots or is logged back in. The account the user uses is on a domain that is currently unavailable (server failure). The physical drive being mapped is on the other server which has the other domain here.

Now i can login as another user i create on the domain, check reconnect at login no problem. But the next day files won't open unless she clicks the drive and enters the user password there. its not a big intervention, but id like it to be seemless.

Suggestions?