Installing and Configuring Windows Workstation OS

Course Description

Installing and Configuring Windows Workstation OS targets individuals seeking to develop competency in Microsoft Windows workstation operating system installation, configuration, administration, and support. The programme begins with an overview of contemporary Windows workstation operating system features and enhancements, then progresses through the installation process, followed by comprehensive coverage of configuration, administration, and support procedures.

Within the SCNS taxonomy, CTS is the Computer Technology and Skills prefix. Daytona State publishes this at 3 credits, offered fall, spring and summer, giving approximately 45 contact hours at the prefix's unsuffixed convention.

Client operating system administration is where most information technology careers begin, and it is more consequential than it sounds. The workstation is where users actually work, where malware arrives, and where most support tickets originate — and an administrator who can deploy, secure, and troubleshoot clients at scale is doing the work that keeps an organisation functioning.

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

Learning Outcomes

Required Outcomes

• Describe Windows workstation editions and their differences.
• Describe hardware requirements and compatibility considerations.
• Plan an installation, including partitioning and file system choices.
• Perform a clean installation and an upgrade.
• Describe deployment methods for multiple machines, including imaging.
• Configure initial settings and complete post-installation tasks.
• Install and manage device drivers.
• Configure disks, volumes, and storage.
• Manage local users and groups.
• Configure file and folder permissions correctly.
• Describe the difference between share and file system permissions.
• Join a machine to a domain and describe what changes.
• Configure and troubleshoot network settings.
• Install, configure, and remove applications.
• Configure and verify update management.
• Configure security features, including firewall and encryption.
• Configure and verify backup and recovery options.
• Use the recovery environment and repair a non-booting system.
• Diagnose startup and boot failures systematically.
• Use event logs and diagnostic tools to investigate faults.
• Monitor and troubleshoot performance problems.
• Use command-line and scripting tools for administration.
• Apply a systematic troubleshooting methodology.
• Document configurations and support actions.

Optional Outcomes

• Describe enterprise deployment and management tooling.
• Describe group policy at an introductory level.
• Describe virtualisation on the client.
• Describe remote support tooling and its security.
• Describe endpoint security and detection.
• Prepare for a Microsoft or CompTIA certification.

Major Topics

Required Topics

• Windows editions and differences
• Hardware requirements and compatibility
• Installation planning
• Clean installation and upgrade
• Deployment and imaging
• Post-installation configuration
• Device drivers
• Disks, volumes, and storage
• Local users and groups
• File and folder permissions
• Share versus file system permissions
• Domain join
• Network configuration and troubleshooting
• Application management
• Update management
• Security features, firewall, and encryption
• Backup and recovery configuration
• Recovery environment and repair
• Boot failure diagnosis
• Event logs and diagnostics
• Performance troubleshooting
• Command line and scripting
• Systematic troubleshooting
• Documentation

Optional Topics

• Enterprise deployment tooling
• Introductory group policy
• Client virtualisation
• Remote support tooling
• Endpoint security
• Microsoft or CompTIA 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

⚠ Build a lab and break things in it — that is how this subject is learned

• Reading about an operating system teaches very little. Installing it, misconfiguring it, breaking it, and repairing it teaches nearly everything, and virtualisation makes that free.
• Use snapshots aggressively. Take one before any significant change so you can revert and try a different approach — this is the single feature that makes a virtual lab so much more useful than physical hardware.
• Deliberately break things and fix them. Corrupt the boot configuration, remove a driver, set permissions wrongly, fill the disk — then repair it without reinstalling. That skill is exactly what employers are buying.
• Do it from the command line as well as the interface. Graphical tools do not scale, and an administrator who can only click cannot automate.
• Read the error message properly. Beginners search for the error text; administrators read it, find the event log entry behind it, and follow the actual cause.
• Change one thing at a time so you know what fixed it.
• Write down what you did. A lab notebook becomes your own documentation and your interview material.
• Practise the same task repeatedly until it is fast. Deployment and configuration work is judged on reliability and speed.

⚠⚠ 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.

CTS2308 is 3 credits and approximately 45 contact hours, offered fall, spring and summer at Daytona State.

It is a corequisite of CTS2353 (Networking with Windows Server) — see that guide.