Skip to content

Lab07ServerCore

Jump to bottom
echadbourne edited this page Oct 10, 2023 · 5 revisions

Basic Setup

As with any new box, the first step involves properly cabling the computer to the LAN and starting it up. When it started it prompted me for a new Administrator password, which I set, and I finished the initial setup with the sconfig tool.

Using the sconfig tool I was able to verify the date and time, make sure automatic updates were turned off, set the hostname to fs01-elizabeth, and set the ip information, which is as follows:

  • IP address: 10.0.5.8
  • Subnet Mask: 255.255.255.0
  • DHCP Enabled: False
  • Default Gateway: 10.0.5.2
  • DNS Server: 10.0.5.6

Domain Join

Next I was able to join the computer to the domain using sconfig, since there was a domain option in there. I joined it to elizabeth.local and used my domain admin's username and password to finish the join. The box then rebooted.

After the reboot was finished I logged in with my domain admin credentials and verified that all of the information had stayed the same.

RSAT

First I had to install a new feature on the AD02, which was "File Service Resource Manager Tools" using the Roles and Features Wizard. Once that was completed I could move on to adding a new server in Windows Server manager in the "All Servers" section, in this case FS01.

After FS01 was properly connected to server manager and AD02, I added a small OU that includes data for users Alice and Bob, and a Sales-Users group which Alice got to be a part of.

After the roles were installed, I ran the following command to open the firewall for managing the file server:

  • netsh advfirewall set rule group="Remote File Server Resource Manager Management" new enable=yes

Then I verified that I could open the "File Server Resource Manager" from AD02

Create a New Share on FS01

In "Shares" Under "File and Storage Services" in Server Manager, create a new share. I used the SMB Quick Share option, and the paths are as follows:

  • Local: C:\Shares\Sales
  • Remote: \fs01-elizabeth\Sales

I created the share, then changed the share permissions to allows Sales-Users Full Control and got rid of the "Everyone" option. Now all I needed to do was test that it worked as intended (which I did. And it did)

Map the S:\ Drive to Sales-Users

In order to map the S Drive to Sales-Users I had to create a new group policy called MapSales which mapped the \fs01-elizabeth\Sales share to the drive S:. I also had to include Item Level Targeting to ensure only Sales-Users could see this.

I checked and was able to see the drive mapped when logged in as Alice, and the gpresult /r showed the applied policy "MapSales"

I referenced this Blog Post: https://www.terminalworks.com/blog/post/2017/12/28/windows-file-server-2016-map-network-drive-for-users-and-group-drive-using-gpo1

Extra Research

I wanted to take some time to explore what other stuff "sconfig" did in Windows Server Core, so I booted up fs01 and just explored the tool some more.

  • I found how to check the time zone and double-checked that it was in the same time zone as the other windows machines (it was)
  • I had already added a new local administrator to the box, but i took note of that option
  • Right under the Windows Update Settings there is the option to manually download and install updates. Again, I did not use it but took note of it.
  • Under Date and Time is something called telemetry settings. I didn't know what that was so I looked it up. Its essentially the recording of diagnostic information to send to Windows if the computer runs into a problem, similar to how in humans it is for recording heart rhythms.

Everything under that I understood. I know it's not much but for this section I wanted to take the time to make sure I understood sconfig for potential future labs that may require me to do something with it.

Clone this wiki locally