On Windows I would avoid Apache. Use IIS.
On Windows Server 2012 I'm serving courses to about 400 users per day. Tests on Server 2016 show similar performance. No major issues (except with the stupid Internet Explorer browser!)
How many server nodes do you plan on deploying with your Moodle setup? Just one?
Don't install Moodle on a production server using one of the "all-in-one" installer packages like Bitnami or XAMPP. Those installers don't give you a Moodle/PHP configuration that's ideal for a production site - especially one with 100 students logging in at the same time.
On Windows first install the operating system and make sure it's ready for production (install patches, firewall, etc.)
Then setup IIS and PHP. Make sure they're both secure and fine tuned for production. Run PHPInfo() to confirm the PHP setup.
If you're using MySQL then install that and create your blank Mooldle database. Make sure PHP can connect to the database.
Where are you putting your Moodledata folder? If you have just one node in your web server setup then you can create it on that server - on a different drive and outside the IIS web root. You don't want users to be able to access Moodledata from the web.
Is your Moodle site going to be available to users on the internet or only in your two labs? If you need it on the internet then you need to do the DNS setup for your Moodle domain name. Speak to your ISP about that. You'll need to register the domain name and have it linked to the IP of your Moodle server.
Lastly, now you can finally install Moodle. Download the Standard Moodle package from https://download.moodle.org/releases/latest/ and extract it to a folder on the web server. Point your IIS site to that folder. If you want a custom theme copy the theme to the Moodle \themes folder before you run the setup so that you can select that theme during the Moodle installation.