Networking with Windows Server

Course Description

Networking with Windows Server instructs students in utilising and configuring Microsoft Windows servers within enterprise networking environments. The curriculum covers IPv4 and IPv6 addressing implementation, DNS and DHCP server configuration, IP address management, VPN and Direct Access setup, Network Policy Server, Distributed File System and BranchCache, plus advanced networking solutions including software-defined networking and Hyper-V network virtualisation.

Within the SCNS taxonomy, CTS is the Computer Technology and Skills prefix and the C suffix marks a combined lecture-and-laboratory course. Daytona State publishes the related unsuffixed CTS2353 at 3 credits, offered fall and spring, with CTS2308 as corequisite.

⚠ Two divergences on this number

• Suffix: CTS2353C and CTS2353 are distinct SCNS numbers and equivalency does not cross the suffix. Confirm with the receiving institution.
• Title: the statewide inventory carries this number as "Configuring Windows Server" while Daytona State titles it "Networking with Windows Server". The Daytona description makes clear the emphasis is on networking services specifically, which the local title describes more accurately. Read the description rather than either title when judging equivalency.

DNS is the service that quietly determines whether an enterprise network works. Directory services, authentication, mail, and virtually every application depend on name resolution, and a very large share of "the network is down" incidents are DNS problems. Understanding it properly is the highest-return knowledge in this course.

Daytona State does not publish a lecture and laboratory split for its CTS courses. The prefix's C-suffixed courses run consistently at 20 contact hours per credit — CTS2302C, CTS2303C, CTS2321C, CTS2358C, CTS2370C and CTS2375C are all published at 3 credits and 60 hours — while its unsuffixed courses run at 15 (CTS2214 at 3 credits and 45 hours). This course is priced at the C-form convention.

Learning Outcomes

Required Outcomes

• Describe enterprise network architecture and the server's role.
• Describe IPv4 addressing, subnetting, and routing.
• Calculate subnets and address ranges accurately.
• Describe IPv6 addressing and its differences from IPv4.
• Plan and implement an addressing scheme.
• Describe DNS and the name resolution process.
• Install and configure a DNS server.
• Create and manage DNS zones and records.
• Configure forwarders, recursion, and conditional forwarding.
• Troubleshoot name resolution failures systematically.
• Describe DHCP and the address assignment process.
• Install and configure DHCP scopes, options, and reservations.
• Configure DHCP for high availability.
• Describe IP address management and its purpose.
• Describe remote access technologies and their trade-offs.
• Configure a virtual private network and describe its security.
• Describe Network Policy Server and authentication for network access.
• Configure the Distributed File System and describe namespaces and replication.
• Describe BranchCache and distributed content scenarios.
• Describe software-defined networking concepts.
• Describe network virtualisation in a hypervisor environment.
• Monitor network services and interpret their logs.
• Apply security practice to network services.
• Document a network configuration.

Optional Outcomes

• Describe directory services integration in depth.
• Describe certificate services and their network uses.
• Describe network segmentation and micro-segmentation.
• Describe cloud networking and hybrid connectivity.
• Describe automation of network configuration.
• Prepare for a Microsoft server certification.

Major Topics

Required Topics

• Enterprise network architecture
• IPv4 addressing and subnetting
• Subnet calculation
• IPv6 addressing
• Addressing scheme planning
• DNS and name resolution
• DNS server configuration
• Zones and records
• Forwarders and recursion
• Name resolution troubleshooting
• DHCP and address assignment
• Scopes, options, and reservations
• DHCP high availability
• IP address management
• Remote access technologies
• VPN configuration and security
• Network Policy Server
• Distributed File System
• BranchCache
• Software-defined networking
• Network virtualisation
• Monitoring and logs
• Security for network services
• Configuration documentation

Optional Topics

• Directory services integration
• Certificate services
• Network segmentation
• Cloud and hybrid networking
• Network automation
• Microsoft server certification

Resources & Tools

• Virtualisation software — VirtualBox is free, and VMware Workstation Player is free for personal use; a home lab of virtual machines costs nothing but disk space and it is the single best way to learn this material.
• Microsoft Learn (learn.microsoft.com) — free official documentation and learning paths for Windows Server and client administration.
• The Linux Documentation Project, and your distribution's own documentation — free; the Arch and Debian wikis are useful well beyond their own distributions.
• MDN Web Docs (developer.mozilla.org) — free and the authoritative reference for HTML and CSS.
• CompTIA (comptia.org) — A+, Network+, Security+, Linux+, and Server+; employers ask for these by name.
• Microsoft and Linux Foundation certifications — role-based credentials recognised in enterprise hiring.
• man pages and built-in help — learning to read documentation rather than searching for a copyable command is the skill that actually separates administrators.
• Your own documented home lab — a candidate who can describe what they built, what broke, and how they fixed it interviews far better than one listing courses.

Career Pathways

• Network and computer systems administrator — SOC 15-1244.
• Computer user support specialist — SOC 15-1232; the usual entry route.
• Computer network support specialist — SOC 15-1231.
• Windows systems administrator — a large share of enterprise infrastructure roles.
• Linux systems administrator — strongly represented in hosting, cloud, and engineering organisations.
• Cloud infrastructure and DevOps — the growth area, and it builds directly on this material.
• Information security analyst — SOC 15-1212; systems administration is the most common route into security.
• Web developer — SOC 15-1254, for the web foundations pathway.
• Florida's defence, space, and simulation sector, plus healthcare, hospitality, and financial services IT — ⚠ many defence roles require U.S. citizenship and some a security clearance.
• Managed service providers — broad exposure quickly, and a common early career step.

Special Information

⚠⚠ When something is broken, suspect DNS — and learn to prove it

• It is a standing joke in this profession because it is true. An enormous share of application, authentication, and connectivity failures turn out to be name resolution problems, because almost everything depends on DNS and almost nobody checks it first.
• Learn to test resolution directly rather than inferring it from whether an application works — query the specific record from the specific client against the specific server.
• Understand the resolution path: client cache, hosts file, configured server, forwarders, root hints. A stale cache entry produces a fault that appears and disappears without explanation.
• Check what the client is actually configured to use. A machine pointed at the wrong DNS server — frequently a public resolver on a domain-joined machine — produces baffling authentication failures.
• ⚠ Domain-joined clients must use internal DNS. This is the classic misconfiguration, and it breaks directory services in ways that look like everything except DNS.
• Watch time-to-live values when changing records; a long value means the old answer persists after you fix it.
• Keep zones tidy. Stale records cause intermittent failures that are extremely difficult to diagnose.
• Document the DNS design — zones, delegation, forwarders — because the person diagnosing it at three in the morning needs it.

⚠ Remote access is a security boundary, not a convenience feature

• A VPN extends your network to wherever the user is, including to a compromised home machine on an untrusted network. That is the risk it introduces.
• Require strong authentication, and multi-factor authentication for remote access is now a baseline expectation rather than a refinement.
• Apply least privilege to remote sessions. Full network access for a user who needs one application is unnecessary exposure.
• Check device posture where you can — patch level, endpoint protection — before granting access.
• Log and monitor remote access, and review the logs; unusual times and locations are the signal that matters.
• Keep the remote access infrastructure patched. Internet-facing gateways are heavily targeted and have been the entry point for major intrusions.
• Have a revocation process that actually works when someone leaves.
• Test the configuration from outside, not just from the console.

⚠⚠ Administrative privilege has a blast radius — work accordingly

• A mistake made as an administrator affects everyone, immediately and frequently irreversibly. That asymmetry is the defining feature of the role.
• ⚠ Use a separate administrative account, and use it only when required. Browsing the web or reading mail as an administrator is how a single phishing click becomes a domain compromise.
• Apply least privilege to yourself as well as to users — the account with the fewest rights that can do the job.
• Know what a command will do before you run it, especially anything recursive, anything with a wildcard, and anything with a force flag.
• Check which machine you are on. Running the right command on the wrong server is one of the commonest serious incidents in this field — make prompts and window titles unmistakable.
• Change one thing at a time, and know how to reverse it before you make it.
• Follow change control. It exists because unannounced changes cause outages nobody can diagnose, and "it was a small change" is what people say afterwards.
• Test in a non-production environment where one exists, and be honest about the difference when it does not.
• Document what you did and when. The next person troubleshooting is frequently you, months later.
• Own your mistakes immediately. An error reported at once is usually recoverable; one concealed for an hour frequently is not, and organisations forgive the first far more readily.

⚠⚠ Authorisation is the line between a systems professional and a defendant

• Never access, scan, or reconfigure a system you do not have permission to touch. Administrative knowledge is exactly what makes unauthorised access easy, and that is why the rule matters more in this field than in most.
• Federal exposure: the Computer Fraud and Abuse Act criminalises unauthorised access to a protected computer, and "exceeding authorised access" has been read broadly.
• ⚠⚠ Florida exposure is separate and additional: the Florida Computer Crimes Act, Chapter 815, Florida Statutes, makes offences against computer users and equipment punishable under state law independently of federal law.
• Having administrative credentials is not the same as having authorisation. Being able to read a mailbox or a file share does not mean you may, and audit logs record that you did.
• Use the lab. The programme provides an isolated environment precisely so techniques that would be unlawful elsewhere can be practised lawfully — and build your own virtual lab at home, off the production network.
• Get scope in writing before any authorised administrative or testing engagement.
• ⚠ Rule 11 applies — computer crime and privacy law changes; verify rather than relying on a course guide.

How Florida course levels affect transfer

The first digit of an SCNS number denotes the year of offering, not transferability. Courses at the 1000 and 2000 levels transfer transparently between Florida public institutions, and 3000 to 4000 is unproblematic since both are upper division. The boundary that actually matters is 2000 to 3000, where lower-division credit generally cannot satisfy an upper-division requirement — and it is live here, since Daytona State offers both associate-level and bachelor of applied science coursework in this prefix.

CTS2353C is a combined lecture-and-laboratory course, published here at 3 credits and approximately 60 contact hours. Daytona State publishes the related unsuffixed CTS2353 at 3 credits, offered fall and spring, with CTS2308 as corequisite.

⚠ Both the suffix and the title differ from the statewide inventory entry — see the note above.