Windows 10: BitLocker - non-domain admin abilities to write to AD

Hello,Working on setting up BitLocker to save the keys to AD, but can't seem to find an answer to my big question. We have non-domain administrators at locations that have been granted delegation rights to their AD OUs. While setting up BitLocker, I created a security group and added these admins to it, delegated them the additional full access rights to msFVE-RecoveryInformation attribute, which gives them rights to see the BitLocker keys in a machine's properties, but can they write the keys to AD when setting up machines?If they do the command: "manage-bde.exe -on C: -recoverypassword" wi

:)

 

How does BitLocker behave on a PC with multiple admin accounts and multiple non-admin accounts?

I'm thinking of enabling BitLocker on a Windows 10 Version 1709 Pro x64 PC and setting the drives to automatically unlock. The PC currently has:

• 2 Microsoft Accounts (AccountA and AccountB) with admin authority. BitLocker will be enabled using AccountA.
• 2 Microsoft Accounts (AccountB and AccountC) with non-admin authority.
• 1 Local, Non-Microsoft Account (AccountD) with non-admin authority.

Given the above, how will BitLocker behave when the PC is booted up and an account
other than Account A is logged in to? Will the OS request the BitLocker password, or will the BitLocker protected drives automatically unlock? I'm hoping for the latter behavior so as not to degrade the user experience for accounts other than AccountA.

Does anyone know?

 

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

 

BitLocker automatically enabled when computer gets added to the domain?

I talked to my boss about this issue, and he claims there is no domain group policy in place to automatically enable BitLocker when computers get added to the domain. Is there any way this could just be a security feature in Windows 10 that any computer
added to any domain gets BitLocker encrypted by default, or is that not a thing that happens in Windows 10? I feel like it has to be a group policy. Are there any other ways BitLocker could get automatically enabled?