Server BCMDC001
Overview
On-premises Windows Server at BCM office. Originally full domain controller, now primarily used for file sharing.
Server Details
| Field | Value |
|---|---|
| Name | BCMDC001 |
| Role | Domain Controller + File Server |
| Domain | bcm.local |
| Location | BCM Office |
Services Running
Active Directory
| Service | Status |
|---|---|
| AD Domain Services | Running |
| DNS Server | Running |
| Kerberos KDC | Running |
Entra Connect
| Service | Status |
|---|---|
| Microsoft Azure AD Sync | Running |
| Entra Connect Health Agent | Running |
Primary Use: File Shares
The main reason this server exists is to share the database folder.
| Share | Path | Users |
|---|---|---|
| Database | \\BCMDC001\Database | \~5 users |
Users access this via mapped drives configured in Intune.
Entra Connect Sync
Current state: Syncing \~1 user (the secretary who still uses domain login)
Sync scope: Limited OUs - most users are cloud-only
Consider decommissioning: Once secretary moves to cloud-only login, Entra Connect can potentially be disabled.
Key Commands
Force Entra Connect sync:
Start-ADSyncSyncCycle -PolicyType Delta
Check sync status:
Get-ADSyncScheduler
Open Synchronization Service Manager: Start menu → "Synchronization Service"
Decommissioning Considerations
To fully retire on-prem AD:
- ✅ Move all users to cloud-only (in progress)
- ⬜ Move secretary to cloud-only login
- ⬜ Disable Entra Connect
- ⬜ Keep server for file shares only (no AD role)
The server can remain as a simple file server without Active Directory if needed.
#bcm/environment/server