Windows 10: failure to update windows over domain

i have this issue

Windows update failure so am facing the problem as in the image below on most of domain computers so i cant install updates and i also tried update agent but cant update as well what could be the cause??

:)

 

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 8 failure configuring updates and reverting

I agree 8 is awful! It's not for me though... I replaced a broken screen in a Win 8 laptop that was given to me and I am going to give it for free to someone that can't afford one so they can do homework at home. Yes I took it from 8 to 8.1 back on 10/09/2014. This is what I posted there...

"Great post! I found a similar one. I would like to point out that you may want to edit your OP...

1. Step 1 should read to disable AUTOMATIC updates, not disable manual updates.

2. KB2871398 should really read KB2871389

I would like to say that KB2917499 may also be needed as it was in my case. I also had to run the Windows Update Troubleshooter after installing those 2 updates. After these steps I was able to begin my 8.1 download from the Microsoft store. I don't know if it made a difference or not, but I also went into the Bios and disabled "Secure Boot."

It was a helpful post. Thanks!

 

Windows 'domain'?

Hello,

Thank you for sharing your concern in the Microsoft Community. Follow these steps to find the domain name:

• Press the Windows key + R then choose System.
• The name of your computer will be listed as the Full computer name.
• The domain your computer belongs to will be listed as the Domain. If, instead of Domain, you see Workgroup, your computer
  is not a member of any domain.

If you have any questions or things you'd like to clarify, feel free to ask.