Active Directory(AD)
Angleški izraz: Active Directory
Microsoft's system for centralized management of users, devices, permissions, and settings in a Windows environment.
Kaj pomeni Active Directory?
Active Directory (AD) is a directory and authentication system that enables centralized management of all users, computers, servers, and permissions within a business network. It typically runs on one or more Windows Server domain controllers.
When a user logs into a work computer, the computer sends a request to the domain controller, which verifies the password and returns the user's permissions. Through Group Policy, administrators can configure settings that apply to all computers or only to specific groups.
It is important to distinguish between classic Active Directory (on-prem) and Microsoft Entra ID (cloud, formerly Azure AD). These are related but distinct services that can be linked in hybrid environments via Entra Connect.
Zakaj je to pomembno za podjetja?
Without centralized identity management, IT administration in a company with more than a few computers is practically impossible. Every change (new employee, permission update, departure) would require manual work on each device separately.
AD simultaneously enables uniform rules: all users have the same password policies, the same security settings, and the same permissions for shared folders. Without this, a 'security policy' is just a note on paper rather than something that actually applies to all devices.
Kje se to pojavi v praksi?
A typical example: a new employee gets a user account in AD, the administrator assigns them to the appropriate groups (e.g., 'Accounting'), and they immediately have access to the correct folders, printers, and applications. Upon their departure, the administrator disables the account, removing all permissions in one step.
Another common example: a Group Policy sets all work computers to automatically lock after 10 minutes, disables USB storage, and ensures updates are installed at a specific time. Without AD, this would have to be configured on each computer individually.
Najpogostejše težave ali napake
The most common issue is the domain controller as a single point of failure. With only one domain controller, its failure means users cannot log in, share files, or use internal services. At least two are recommended.
Another common mistake: permissions that have accumulated over the years based on the 'let’s just make it work, we’ll sort it out later' principle. The result is a disproportionately high number of users having access to shared folders containing sensitive data.
Third issue: administrative accounts (Domain Admin) used for everyday work. A breach of such an account means total control over the entire domain.
Kako pri tem pomaga VitalIT
At VitalIT, we first check the domain health of existing AD environments: replication between domain controllers, DNS status, organizational structure, Group Policies, and a review of administrative accounts. Only then do we propose sensible steps.
In practice, we assist with upgrading domain controllers, organizing the structure and permissions, setting up hybrid connectivity with Microsoft 365 (Entra Connect), and managing Group Policies. We adapt solutions to the actual environment and the agreement with the client.
Povezane storitve
Pogosta vprašanja
- Is Active Directory still necessary if we use Microsoft 365?
- It depends. Smaller companies working exclusively in the cloud can use only Microsoft Entra ID without local AD. For environments with local servers, file shares, and legacy applications, local AD often remains sensible.
- How many domain controllers do we need?
- For a business environment, at least two, so that one can fail without affecting users. In larger organizations with multiple locations, we add a domain controller at each major site.
- What is the difference between Active Directory and Microsoft Entra ID?
- AD is the classic, local system for managing a Windows environment. Entra ID is a cloud-first identity management service for Microsoft 365 and other cloud applications. Their functionalities overlap, but they are not identical.
- Does AD need its own DNS?
- Yes. AD is heavily dependent on correctly configured internal DNS. Poorly configured DNS is one of the most common causes of AD environment issues.
