Windows 10: Activate Windows License on Domain PCs/Laptops via CMD

I am trying to activate Windows on Domain Laptops using CMD to save time and effort, but whenever I use slmgr /ato I get the error "DNS-Name does not exist". I've already tried setting the activation domain, but this didn't really help. Also to note, when activating it using Windows settings, I also get the same error. I always hit the troubleshooting button and then it works

:)

 

Win 10 OEM_DM license activation fails in AD domain

My PCs came with OEM_DM windows 10 license. After reinstalling windows, license gets activated as long as the PC is not joined to the windows AD domain. Trying to activate license after joining domain fails with 0xC004F074 error. It seems the PC is trying
to look for volume license KMS server when it is a domain member.

 

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

 

How to check if Windows 10 is activated on domain PC's

Hello

I've searched the internet and can not find a good PowerShell script to verify all my domain PC's are activated. The Domain controller is 2016 standared and about 130 PC's. 1/2 are OEM licensed and 1/2 have been imaged with a Volume license MAK key. I
believe most are activated but I run across some that are not. I would like a complete, definitive answer if they are all activated. The ones I found that are not activated have an error the indicates the Microsoft Activation server cannot be contacted.
Would you have a script or other tool that could help? If I have a list of un activated PC's I can manually add the VL MAK key and activate them.

Thanks

RSC