SYS‐255 Server Core Remote Administrator Tools - aljimenez28/champlain GitHub Wiki

Objective

The goal of this lab was to configure a Windows Server Core machine (FS01) and join it to the Active Directory domain alejandra.local. Once joined, the lab focused on installing File Server Resource Manager (FSRM), creating a shared folder called “Sales,” setting proper permissions, verifying access from client workstations, and mapping the Sales share automatically using Group Policy.

Steps Completed

  1. Configured FS01 Network Settings

    • Verified FS01 network adapter was connected to the LAN/Internal network (not WAN).
    • Assigned static IP: 10.0.5.8
    • Subnet Mask: 255.255.255.0
    • Default Gateway: 10.0.5.2
    • DNS Server: 10.0.5.6 (domain controller AD02)
    • Confirmed connectivity using ping to AD02 and DNS resolution.

  2. Joined FS01 to Domain

    • Used sconfig on FS01 to select “Join Domain.”
    • Entered domain name alejandra.local and credentials for the domain administrator.
    • Rebooted FS01 after successful domain join.

  3. Installed File Server Resource Manager (FSRM)

    • From Server Manager on AD02, added FS01 to the server pool.
    • Installed the File Server Resource Manager role on FS01.
    • Verified FSRM was running correctly.

  4. Created and Shared the Sales Folder

    • On FS01, created C:\Shares\Sales.
    • Shared the folder as “Sales.”
    • Configured advanced security permissions to remove “Everyone” and add “Sales-Users” with Full Control.

  5. Configured Sales-Users Group

    • In Active Directory Users and Computers on AD02, created a security group called “Sales-Users.”
    • Added Alice as a member of the group (Bob and Charlie were left out for permission testing).

  6. Verified Permissions

    • Logged into WKS02 as Alice and accessed \\fs01-alejandra\sales.
    • Confirmed Alice could open the folder and create files.
    • Logged in as Bob and confirmed access was denied.

  7. Mapped Drive Using Group Policy

    • Created a new GPO called “Sales Drive Mapping.”
    • Configured drive mapping under User Configuration → Preferences → Windows Settings → Drive Maps.
    • Set location to \\fs01-alejandra\sales, labeled it “Sales Share,” and assigned drive letter S:.
    • Filtered the GPO to apply only to the “Sales-Users” group.
    • Ran a policy update and rebooted WKS02.
    • Verified the Sales share was automatically mapped to the S: drive for Alice.

Problems Encountered and Solutions

Problem 1: FS01 Could Not Join Domain

Issue: Received “The specified domain either does not exist or could not be contacted.” Cause: FS01 was connected to the WAN instead of the LAN/Internal network. Solution: Switched FS01 to LAN, reconfigured the IP settings, restarted, and retried the domain join successfully.

Problem 2: WKS02 Users Could Not Log In

Issue: Alice could log in, but Bob and Charlie could not. The system displayed “Your domain isn’t available.” Cause: WKS02 was assigned an APIPA (169.254.x.x) address, which meant it couldn’t reach the domain controller. Solution: Assigned a static IP and set the DNS to AD02’s IP. Verified connectivity with ping. Logins succeeded afterward.

Problem 3: Cannot Access Sales Share

Issue: Accessing \\fs01-alejandra\sales failed with a network error. Cause: FS01 was powered off, causing the path to be unreachable. Solution: Turned FS01 back on, confirmed IP and connectivity, flushed DNS, and accessed again successfully.

Problem 4: Group Policy Drive Not Mapping

Issue: The Sales share did not appear under “This PC.” Cause: Group Policy had not been applied yet. Solution: Ran a manual policy update and rebooted WKS02. After restarting, Alice’s mapped drive appeared correctly.

Important Commands Used

sconfig – Server Core configuration utility for network and domain setup

gpupdate /force – Forces a Group Policy update

ipconfig /flushdns – Clears cached DNS entries

ipconfig /registerdns – Re-registers domain and DNS

repadmin /syncall /AdeP – Forces Active Directory replication

net use * \server\share – Manually maps a network share

Results

  • FS01 successfully joined the alejandra.local domain.
  • File Server Resource Manager was installed and configured.
  • The Sales folder was shared and secured correctly.
  • Alice (member of Sales-Users) had access to the Sales share.
  • Bob and Charlie were denied access, confirming correct permissions.
  • The S: drive automatically mapped for Alice after applying Group Policy.

Takeaways

  • Always verify that the server is connected to the correct LAN network before joining domains.
  • DNS must always point to the domain controller for proper communication.
  • File permissions should use security groups for easier management.
  • Group Policy Preferences make drive mapping simple and dynamic based on user groups.
  • Consistent testing and verification steps ensure every part of the lab functions as intended.

Lab Status: Completed Successfully ✅