TopicActive Directory →
⌚ About 2 min read
Create a new AD user properly using the Active 1992ry module.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Open Power Shell with AD Tools.
Use an administration position with the Active-Writary module.
-
2
Prepare the initial password.
Store the password in a SecureString.
-
3
Create Account.
Use New-AD 3.1r with name settings, SamAccount(1), UPN and OR path.
-
4
Check account.
Use the Well-AD-User to check the created object.
-
5
Assigning the necessary groups.
Add only the groups corresponding to the employee's role.
Commands utiles
$ password = Read-Host 'Original password' -AsSecureString.
New-AD 8.1r - Name 'Jean Dupont' - Given Name 'Jean' -Surname 'Dupont' -SamAccount Name 'j.dupont' - UsernamerPrincipal Name 'j.dupont@example.local' -Path 'OR=Users,DC=example,DC=local' -Account password $password -Enabled $true -ChangepasswordAt Logon $true.
The Commission shall, in accordance with Article 3 of this Regulation, adopt the following measures:.
À retenir
- Always test the path of the,OR before execution.
- N, grant no administrative privileges by default.
AD user creation: identity, OU and attributes must stay coherent
Technical checkpoints
- sAMAccountName is historically limited to 20 characters for compatibility; UPN must be unique and use an allowed/routable suffix.
- The target OU DistinguishedName must be exact: creating in the wrong container can change GPOs, delegation and provisioning.
- Groups, cloud licensing and mailbox provisioning are separate steps; do not confuse them with AD object creation.
PowerShell
Review values first, then create using a SecureString password.
New-ADUser -Name "Alice Dupont" -SamAccountName adupont -UserPrincipalName adupont@example.com -Path "OU=Users,DC=example,DC=local" -Enabled $trueTopic-specific pitfalls
- Reusing an existing UPN or sAMAccountName can fail or create ambiguity.
- Immediately adding privileged groups without separate validation increases risk.
How to validate
- The user is in the expected OU, has intended attributes/groups and authenticates after replication.
- Changes are visible on at least the DC used by affected clients.