Windows 10: Hi All, Is there a way to deny access to the domain based on the windows 10 build that a...

I have tried searching the internet for an answer to this but most of the articles come up with "how to join back to the domain". What i am looking for exactly is, if my PC is off the domain and is running Windows 10 x64 1809, if I try to join it back to the domain, the domain controller should deny the request based on the build version of Windows. It should then only allow the PC back on the domain when it has been upgraded to for example 21H2.Thanks in advance :

:)

 

LAPTOP is not accessible ..... Access is denied.

I am trying to share a folder on a LAPTOP. I have other a number of other systems that have folders Shared and they work fine, but with this one I get the error "LAPTOP is not accessible ..... Access is denied." when I try to access it from a different Win10 system. So I went thru the entire "How to Share Files and Folders Over a Network in Windows 10" tutorial step by step. File and Print Sharing is enabled, SMB1.0 client & server are running, and Everyone has Full Access to the Share. Still get the error. I have tried it with the Network Public and Private, with the same result. Any suggestions ?

Microsoft Windows 10 Home
Version 10.0.19042 Build 19042

 

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 backup recovery access is denied

Hi Mostafa,

Let's take care of the issue. We suggest visiting the support article
"Access Denied" or other errors when you access or work with files and folders in Windows,
follow the steps provided and see if it helps.

Looking forward to your response.