User Tools

Site Tools


software:microsoft:windows:activedirectory

Active Directory

————————————————————————————————————————————————-

Active Directory Group policy

Active Directory Group policy, we created a group policy for the entire domain. We defined: Computer Configuration, Policies, Windows Settings, Security Settings, Local Policies, Security Options, interactive logon: Message Text for users attempting to log on and interactive logon: Message title for users attempting to log on

The message should appear before the user enters Windows credentials, not after reaching the desktop. On a typical Windows 10/11 console:

  1. Start or restart the computer.
  2. Dismiss the initial lock screen or press Ctrl+Alt+Delete, if required.
  3. The legal-notice dialog appears.
  4. The user must click OK.
  5. Windows then presents the normal username/password/PIN sign-in screen.

It generally does not appear when merely unlocking an already signed-in session. Test using a full restart or sign-out, preferably from the computer’s physical console. Microsoft describes it as a dialog displayed before users can sign in. (Microsoft policy documentation)

Test it on one affected computer

Open Command Prompt as Administrator and run:

gpupdate /target:computer /force

Confirm that it reports:

Computer Policy update has completed successfully.

Then restart—not merely lock—the computer:

shutdown /r /t 0

Test the next sign-in from the local console.

Verify the resulting registry values

After the policy refresh, run this in an elevated Command Prompt:

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v LegalNoticeCaption
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v LegalNoticeText

You should see your configured title and message. These are the effective Windows settings:

Policy Registry value
Message title LegalNoticeCaption
Message text LegalNoticeText

If both values contain the expected text, Windows has received the setting. Restart and test at the console.

If they are missing, empty, or contain different text, the GPO is not applying as intended or another policy is overriding it.

Confirm that the GPO applies to the computer

Because these settings are under Computer Configuration, they apply according to the location and permissions of the computer account, not the user account.

Create a Group Policy Results report:

mkdir C:\Temp
gpresult /scope computer /h C:\Temp\ComputerPolicy.html
start C:\Temp\ComputerPolicy.html

In the report, examine:

  • Applied Group Policy Objects — your legal-notice GPO should be listed.
  • Denied Group Policy Objects — look for security filtering, WMI filtering, or other denial reasons.
  • The resulting settings under:

Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options

Microsoft recommends gpresult for viewing the full resulting policy set because rsop.msc does not necessarily display every setting. (Microsoft gpresult documentation, Microsoft RSoP guidance)

For a quick text-only check:

gpresult /r /scope computer

Check the GPO itself

In Group Policy Management, verify all of the following:

  1. The GPO is actually linked to the domain or an OU containing the affected computer accounts.
  2. The link is enabled.
  3. Computer Configuration Settings are not disabled.
  4. Security filtering permits the computer to Read and Apply Group Policy.
  5. A WMI filter is not excluding the computer.
  6. The computer’s OU does not have Block Inheritance enabled.
  7. Another GPO linked closer to the computer’s OU is not replacing the title or message with blank values.

A common source of confusion is GPO Status: Enabled. That status only means the GPO’s Computer and User sections are available for processing. It does not prove that the GPO is linked, within scope, permitted by security filtering, or applied to a particular computer.

If it still does not apply

Check the client’s Group Policy operational log:

Event Viewer
  Applications and Services Logs
    Microsoft
      Windows
        GroupPolicy
          Operational

Look for errors at the time you ran gpupdate.

Since three weeks have passed, this is not an ordinary refresh-delay problem. Computer policy normally refreshes approximately every 90 minutes plus a randomized interval and is also processed at startup. The most likely causes are an incorrect link/scope, security filtering, blocked inheritance, or another higher-precedence GPO overriding the values. (Microsoft Group Policy processing documentation)

Configure Microsoft Entra hybrid join

Bringing your devices to Microsoft Entra ID maximizes user productivity through single sign-on (SSO) across your cloud and on-premises resources. You can secure access to your resources with Conditional Access at the same time.

https://learn.microsoft.com/en-us/entra/identity/devices/how-to-hybrid-join

Viewing the active Directory with ADSIEDIT.MSC

List Active Directory Email Addresses

Server4 Aphelian Connection to Active Directory

Host info
Name: activedirectory
Host: etspowergroup.local
Port: 389
Version: 3
Base DN: DC=ETSPowerGroup,DC=local

User Info
User DN: Matthew Jados,CN=Users,DC=ETSPowerGroup,DC=local
Password: 

Mac OS/Linux/Windows Single Sign-On

Well Known Security Identifiers

From: https://support.microsoft.com/en-us/help/243330/well-known-security-identifiers-in-windows-operating-systems

SID: S-1-5-11
Name: Authenticated Users
Description: A group that includes all users whose identities were authenticated when they logged on. 
Membership is controlled by the operating system.

Computer login

2022-04-05

Deny User or Group to Sign in Locally in Windows 10

From <https://winaero.com/deny-user-group-sign-in-locally-windows-10/>

From: https://community.spiceworks.com/topic/216823-implications-of-removing-nt-authority-authenticated-users-user-from-users-list

Andre Canis Jalapeno Best Answer Andre Canis Apr 17, 2012 at 6:08 AM A better way would be to do it in the security policy (secpol.msc)

Security Settings > Local Policies > User Rights Assignments > Allow log on locally.
Remove the “Users” group from this policy and
add those users you want to allow to log on.

From: https://community.spiceworks.com/topic/199167-active-directory-2008-r2-control-user-login-to-computer

ChristopherO Mace ChristopherO Feb 15, 2012 at 6:54 AM
You could certainly do this in 2003.
If you want to be granular, you will need to update the Users group on each computer
- remove Domain Users and add in the specific accounts/groups that can log into that computer.
If it's going to be the same for a large number of computers (ie, users in the Sales group can log into any computer in the Sales department) you can use Restricted Groups in Group Policy - just remember, with Restricted Groups it will remove ALL other users/groups from that local computer group and ONLY allow in what you set in the policy.

From: https://community.spiceworks.com/topic/338040-how-to-stop-domain-users-from-logging-into-my-pc

From: https://community.spiceworks.com/topic/126427-restrict-certain-users-from-login-on-certain-computers

From: http://windowsitpro.com/security/restricting-interactive-user-logons

Remote Login Active Directory

Local Secpol.msc security “Allow login Through Terminal Services”

PowerBroker Identity Services

From: http://www.powerbrokeropen.org/ Download: http://download1.beyondtrust.com/Technical-Support/Downloads/PowerBroker-Identity-Services-Open-Edition/?Pass=True

linux login active directory

RE:[linuxadmin-l] Centralized Login Solution For All The Linux And AIX
Inbox
JJ_AIX	
Reply from JJ_AIX on Sep 14 at 4:03 PM Thanks guys , I appreciate it , I saw ...
2:34 PM (22 hours ago)
nawzs-se
12:55 AM (12 hours ago)

Reply from nawzs-se on Sep 15 at 12:49 AM
Well, Powerbroker Open is free, if you can manage without a support agreement. .. 
It'll take care of the unified logon, the paid version can also handle GPOs for your linux and unix systems. 
On the other hand, we use sssd and that one works well too. 
One small but important difference between the two setups is that with sssd (or nslcd) you need to set the unix attributes in your ldap directory ( such as uid,gid,unixhome and loginshell). If you go with Powerbroker it'll take care of that for you by hashing the SIDs for uid, gid and assigning defaults for the rest. Defaults are customizable.

rd-gateway-ports-and-certificates

From: https://social.technet.microsoft.com/Forums/windowsserver/en-US/a241a5be-e39d-4dfc-a513-e4f83c4dc906/rd-gateway-ports-and-certificates?forum=winserverTS

In this deployment, RD Gateway needs the ports to be opened on the internal firewall for the following purposes:
To authenticate users
To authorize users
To resolve the DSN names of internal resources
To forward RDP packets from the client
To get the Certificate Revocation List
To send RADIUS requests (in a central NPS server scenario)

ADSI Edit

From: https://technet.microsoft.com/en-us/library/Bb124152%28v=EXCHG.65%29.aspx?f=255&MSPPError=-2147217396

ADSI Edit is implemented as a snap-in that runs in the Microsoft Management Console (MMC). The 
name of the default console containing ADSI Edit is AdsiEdit.msc. You can add the snap-in to any 
.msc file through the Add/Remove Snap-in menu option in the MMC, or you can just open the AdsiEdit.msc 
file from Windows Explorer.

Backup of Active Directory

From: http://support.microsoft.com/kb/888794

  An Active Directory domain controller requires regular system state backups to recover from user, hardware, 
  software, or environmental problems. The default useful life of a system state backup is 60 or 180 days, 
  depending on the operating system version and the service pack revision at play during the installation. 
  This useful life is controlled by the tombstone lifetime attribute in Active Directory. At least one domain 
  controller in every domain in the forest should be backed up every tombstone lifetime number of days.
  
  Note the value in the Value column. If the value is <not set>, the value is 60 days.

Things to consider when you host Active Directory domain controllers in virtual hosting environments

From: http://support.microsoft.com/kb/888794

  Virtualized DCs in clustered hosts 
  In order for the nodes, disks and other resources on a clustered computer to auto-start, authentication 
  requests from the clustered computer must be serviced by a DC in the cluster computer's domain. 
  To insure that such a DC exists during cluster OS startup, deploy at least 2 domain controllers in the 
  clustered host computer's domain on physical hardware. The physical DCs should be kept online and be 
  network accessible (in DNS + all required ports and protocols) to the clustered hosts. If the only DC’s 
  that can service authentication request during cluster startup reside on a cluster computer that is being 
  restarted, authentication requests will fail and manual recovery steps will be required to make the cluster
  operational. 
  
  Note: Always have at least one DC that is on physical hardware so that failover clusters and other infrastructure 
  can start.

Free Active Directory Tools

From: http://www.manageengine.com/products/free-windows-active-directory-tools/free-active-directory-tools-index.html

  ADManager Plus presents a complete suite of Active Directory tools that will certainly 
  help the Windows Active Directory administrators and users in efficient handling of all 
  the Active Directory Data. You can download 'RIGHT NOW' the entire suite at absolutely 
  NO COST!. 

Permissions Analyzer for Active Directory

From: http://www.solarwinds.com/downloads/

  Not a whole lot of help
  can get same results from going to folder or file and checking permissions
  

JXplorer The World's Finest Ldap Browser

http://jxplorer.org/

JXplorer is an open source ldap browser originally developed by Computer Associates' eTrust Directory development lab. It is a standards compliant general purpose ldap browser that can be used to read and search any ldap directory, or any X500 directory with an ldap interface. It is available for immediate free download under a standard OSI-style open source licence.

See: https://confluence.atlassian.com/display/DEV/Identifying+Active+Directory+connection+details for details of configuration parameters for Active Directory

Microsoft Active Directory Credentials

From: https://confluence.atlassian.com/display/DEV/Identifying+Active+Directory+connection+details

  ad.atlassian.com is the DNS name of our AD server so that's how we worked out
  CN=Administrator,CN=Users,DC=ad,DC=atlassian,DC=com. 
  We prefixed each part of the DNS name with DC (which stands for Domain Component).
  
  Any folders or subfolders that branch from the server, we prefix with CN, 
  hence CN=Administrator,CN=Users,DC=ad,DC=atlassian,DC=com (as the Administrator user 
  account sits in the Users folder).
  
  Please specify the full name of the account for CN. So, if the user 
  is John Smith, you would use: CN=John Smith,CN=Users,DC=ad,DC=atlassian,DC=com
  
  For baseContext, just specify DC=ad,DC=atlassian,DC=com (the DNS name prefixed with DC's)
  

https://confluence.atlassian.com/download/attachments/164873/jxplorer_connect.gif?version=1&modificationDate=1141791701655&api=v2

software/microsoft/windows/activedirectory.txt · Last modified: by superwizard