Previous Semesters
Previous Semesters
Previous Semesters
Hello, and welcome to the week one announcements video for CIS 527 and CC510 in fall 2025. My name is Russell Feldhausen. I’ll be your instructor for this semester. My contact information is here on the screen. You can also find it on the Canvas homepage, on the syllabus, just about anywhere you look with this class. You can find my contact info. My email is here. My website is here. You can also find me on Teams and Discord as at russfeld. I’m pretty easy to get a hold of. One thing to be aware of, I do work remotely. I live in Kansas City, and so I’m working remotely Tuesdays through Fridays. I am on campus on Mondays. So if you want to see me in person, you can meet with me on Mondays. Usually Monday mornings is when I’m going to be available. And there is a way to schedule that that I’ll talk about here in just a minute. But just be aware of that. The rest of the week, I work remotely, which does mean I’m pretty easy to get a hold of on Teams or Discord or Ed Discussion anytime you have a question.
For the semester, I do have one graduate teaching assistant, Josh Barron. Josh worked with me last year on this class. So this is his second year working on this class. So he’s going to be a really good resource for you as well. So definitely get to know Josh. His Calendly link is also on the homepage and on the syllabus. So if you need to schedule a time to work with Josh, please do so. For this course, I encourage you to schedule with Josh first if he is available, mainly because I am paying him. And so we want to make sure we make good use of his time and make sure that he is very valued in this course. If you can’t get a hold of Josh or you need extra help and Josh is not available, please feel free to schedule with me. But definitely we want to make sure we make use of Josh’s time primarily if we can to make sure that we get our best value with Josh and that he gets lots of experience working with you. So that would be great.
So in this course, this course uses gated modules on Canvas. There’s one module due every other week. So make sure you check the due dates on Canvas. I will start publishing the modules probably. But by the time you see this video, the first couple modules will be published. I’m actually recording this video on Wednesday of the week before class, a little bit behind the scenes there. I still haven’t finished the first couple of assignments. I need to do them again to make sure that they actually work. But by the time you see this video, they will be published. So check the due dates on Canvas. For each lab assignment, for a lot of them, we’re going to do live grading. And I talk about that a little bit later. So just be aware. So, and then we’ll have some discussions. Throughout the semester, I try and bring in three to five guest speakers that work in industry, that work in IT. And so I bring them in, give them a chance to tell you about their job, what they do, and then you get to ask some questions of them. And then at the end of the semester, we’ll do a final project.
So communication in this course is pretty simple. There’s an Ed discussion board that is linked on the left side of Canvas. That is the place to go for questions for this course, discussions. Every lab assignment is going to have a mega thread there. That’s where I’m going to post my tips and tricks and ideas and anything that come up during the assignments. So please, please, please keep an eye on Ed Discussion. That is going to be the place to find the cool information. If you have a personal issue, a grading question, a to-do item for me, etc., email the help email address, which is cis527-help at ksu emailprod.onmicrosoft.com. If you’re using webmail, just type in cis527-help and it will auto-fill that for you. That is a great place. It goes to both me and Josh, and so either of us can respond to that pretty quickly. So what I tell students is email is the official communication, but ed discussion is much more flexible. And so we’ll use that for a lot of the stuff in this course.
So to be successful in this course, this course is fun because this course represents a lot of what it’s like to be an actual system administrator. However, that does mean that it can be very frustrating at times, or it can feel like I’m not giving you all of the answers, or things are a little harder than they should be. That’s kind of the way it is. I hate to say it. That is what being a sysadmin is like, and you’re going to experience that a little bit in this class. So I encourage you to come into this class with a growth mindset. You can do it. Anybody in this class can do everything I’m asking you to do. You just have to be willing to accept the fact that you have to learn a little bit and it’s going to take some struggle and that’s okay. Second big thing, do not just read or watch the content, but engage with the content. I’m going to, throughout my videos and throughout the assignments, I’m going to show you certain things. I really encourage you to engage with that. Follow along. Do it yourself. Try and do something a little bit different and see what happens. If you just skim through the videos and then jump right into the assignment, you’re going to feel like you don’t know what’s going on because you really didn’t engage with the content. So really take some time, engage with the content. Click the links that I have. Almost every page has a set of links at the top of it. They’re the links that I read when I was putting this page together. Click those links. Those are going to be so important for you. A lot of times those are the real documentation that you need to read in order to get the assignments to work.
Another big thing in these assignments is work iteratively, pick out a small goal, get that goal working, and then move on to something else. I see a lot of students that they’ll take an assignment that has seven bullet points and they’ll try and work on all seven bullet points at the same time. And that’s just nearly impossible to do. Pick one thing, get it working. Pick another thing, get it working. There’s a reason that I have the assignments broken out into several bullet points. And typically they’re in the order that I encourage you to work on them on. I don’t usually switch those up too often. So work on that. As always, save early, save often, make backups of your files. I guarantee at least once the semester, somebody in this course will make a change to a file in their virtual machine. They will roll back their virtual machine to a previous snapshot, and then they will realize that their file was not present in that snapshot and they lost all of their work. It happens every semester. I know it will happen. Hopefully it doesn’t happen to you. So save early, save often, back your stuff up. Be careful. Every sysenman learns this the hard way. I can share with you some great stories online of like there was a developer that worked for, I want to say it was GitHub or no, it was GitLab and accidentally deleted the production database because he forgot what terminal he was working in and just did the delete database command, thought he was working in the dev machine, ran that in prod, dropped all their data, lost a whole bunch of stuff. So be careful.
Last big thing, if you get stuck, ask for help. I do not expect anybody in this course to pass this course without asking me for help at least once, unless you have already been a sysadmin in your life. And even then, it might be really tricky. So I really encourage you to ask me for help. Ask Josh for help. We are here to help you out. We have some hints already ready to give you, but you have to ask. So don’t be afraid to ask for help if you get stuck.
So let’s talk about lab grading. Lab grading, the way we do most of the labs is we grade them interactively. What that means is when you’re done with your lab, you’re going to schedule a time to meet with either Josh or I using our scheduling link. Josh currently uses Calendly. I use the Office 365 booking tool. They’re basically the same thing. You’ll schedule a time with us via Calendly. You can schedule that time before your lab is done. So if you know you’re going to have your lab done on Friday, you can go ahead and schedule a time for Friday, even on Tuesday, but you have to get graded after your lab is done, obviously. So you can schedule at any time. Check Josh’s schedule first. If he’s not available, then schedule with me. But again, I want to prioritize scheduling with Josh so that we’re using up his time wisely. It does require up to four hours notice on both his calendar and my calendarly. So if you get done Friday at 3, you are SOL because you can’t schedule for Friday at 4.30. Also, probably it’s already been scheduled. So just be aware of that.
What you’ll do is you will have your lab open on your computer. This allows you to work on your desktop at home, whatever machine you’re running your virtual machines on. You’re going to load up your virtual machines. Please have them running when you join the Zoom. You’re going to join the Zoom. You’re going to share your screen with your virtual machines. And Josh and I are going to talk you through what we want to see. We expect you to be prepared to do the things we ask you to do. You should know how to do them. For example, in the first lab, we’re going to ask you, show us the file permissions for this folder that you created. I give you the command in the lab. You should be prepared to run that command and know what it does. That’s one big thing is make sure that you are prepared to demonstrate what you have done in this lab. You may want to practice a little bit to make sure you’ve got it. And then, of course, the other big thing is you cannot change once you’ve started. Once we have started grading, you run a command, you’re like, oh, crap, that doesn’t look right. It’s too late. You already turned it in. We saw it. That’s what it is. We are a little lenient about that, but generally you can’t make a change once you’ve started grading. So just be aware of that.
So there are some discussions that we’re going to have. Like I talked about, I’m going to bring in some guest speakers. So I’m going to send out a survey here pretty quick to try and figure out what day and time works best for everybody. And we’re going to set that as kind of an office hours time for this course. So please respond to that survey when you see that come out probably sometime this first week of class. We’ll schedule a time online via Zoom. What you’ll do is about a week before our discussion session, I will announce who the speaker is. I’ll give you a little bit of their background, their bio. And then what I ask you to do is submit questions for that person on Canvas before the presentation session. So one to three questions you want to ask that person. And then during the discussion, you can either join the live session and participate by asking one of your questions. Or if you’re not able to attend live in person or you don’t get your question asked during the in-person session, you can write a short little response that shows that you are there or watch the video afterwards. It’s pretty easy to do, but it gives you a chance to see and hear from some people working in industry. I definitely know one of the ones I’m going to get this semester is Seth Gallitzer, who was formerly the CSS admin. He’s now overseeing a lot of the engineering support staff. And so I really would love to hear from him and the change in his job responsibilities as he has migrated to a new job over the last year. So be aware that that’s coming.
All right. I think that’s all you need to know for this first week. As always, if you have any questions, please feel free to keep in touch. Ed Discussion is the primary place to do that for this course. However, I’m available on Discord and Teams, so you can reach out to me either of those places. I usually can respond pretty quickly to those. I hold tea time office hours, usually on Monday mornings. Tea time is a good time to come in and chat with me and hang out and talk about anything outside of class. So life, the universe, and everything. And then, of course, you can always schedule one-on-one office hours with me using my schedule link that’s going to be on the syllabus on the homepage. And at the bottom of every email you’ve ever seen from me, it’s going to have the link right there to schedule office hours with me. So best of luck this semester. I really enjoy working with this class. I was a sysadmin for several years. This is my fun class to teach that I really enjoy working with you. So best of luck this semester. I hope things go well. And most likely you’ll hear from me about every other week in this class. I’ll try and post an announcements video as we go through the classes. We have each new assignment up there. So just be aware of that. You’ll be able to see these in the announcements on Canvas. Like I said, best of luck this semester, and I will see you again in a week or two.
Hello and welcome to the week two announcements video for CIS 527 and CC 510 in fall 2025. So this week you should be getting started on the first lab. Please bear in mind I do have a megathread on ed discussion for this lab. So if you have any questions or concerns with this lab, I’d really recommend that you post in the ed discussion and also check there, but you can also email to do lab grading. I get a lot of questions about lab grading in this class. The way this works is you’re going to schedule a time slot to meet with either the GTA Josh or myself. You need to meet with us before the lab is due. You can schedule your time slot anytime. So even if you’re not done with the lab right now, you can schedule a time slot for next Wednesday sometime when the lab is due, but you need to have the lab done before that time slot, obviously. So you schedule a time slot. Please check Josh’s calendar first. And then if he doesn’t have any times available that works for you, then schedule with me. Please bear in mind, I am generally very busy on Mondays because I’m on campus and then a little bit on Wednesdays and Thursdays as I have lab meetings and other things going on those days. Tuesdays and Fridays are usually pretty open for me. So anyway, schedule with Josh first, then me using our calendly links, or I also have a booking link that you can use.
Before the lab grading time, make sure you make snapshots of everything so that they’re all ready to go. Have everything ready to go when you join the Zoom. Please, please, please don’t join the Zoom. And then we have to sit there and wait five minutes while all your VMs load. Have everything up and ready to go. And then be prepared to demonstrate everything that you did on the lab. We’re going to ask you things for this first lab, like show us how you changed the computer name. Where’s the computer name now? Show us where the user accounts are. Can you show that you got all the user accounts created? Show us that the files are created and have the correct file permissions. Those sorts of things. We’re going to ask you to show us that. And so we expect you to remember how you did it and be able to demonstrate that you did it correctly. So we’ll be prepared to kind of coach you along if you’re not sure. We really want you to demonstrate the work that you did. It’s a very live grading type of situation. And then, of course, don’t forget that as soon as we start grading, everything is locked in. If you notice you made a mistake, it’s too late to change it. But we’re pretty lenient on things, so don’t worry too much about it. We really just want to make sure that you’re understanding what’s going on and get things working the way they’re supposed to.
So second thing going on in this class is the live discussions. Hopefully everybody filled out the survey. It’s looking like we’re going to do those Tuesdays, Tuesday afternoons. So the schedule is coming soon. Usually the first one I try and get is Seth Gallitzer, our former C assistant administrator, and I wanted the SysAdmins for Engineering. So I will try and get the schedule put out soon. We’re going to have anywhere from three to five of these discussions throughout the semester. If you remember, the discussions are a chance for me to bring in somebody in industry that works in a field related to system administration, and you get to talk with them, hear about their experiences and what they’re up to. The way the discussions work is I will post the discussion topic and the person and their little bio about a week beforehand. You need to go in and ask two questions beforehand in the Canvas assignment. Then you can either attend the live session on Zoom or you can watch the video afterward. If you attend the live session, you just have to ask one of your questions to get points. Otherwise, if you don’t ask a question or if you watch the video afterward, there’s a short prompt that I’ll have you respond to. It’s like a few sentences for the prompt, just to show that you watched the video and paid attention and kind of have some comments on what was said. On the days that we don’t have a discussion, I’ll use those as kind of an office hours. So again, those will probably be Tuesdays out in the afternoon starting next week. So watch for a more detailed announcement with that coming up.
To get help in this class, there are three big ways to get help. First and foremost, we have the CIS 527 help email. That goes to both Josh and I. However, I really prefer that you use the Ed Discussion board as your primary source of help. I post mega threads for each of the lab assignments on there. It’s a great place to have discussion. My mega thread header includes some hints for all of these labs. I went ahead and pre-populated the first four labs worth of Ed Discussion posts already. So they’ll be posted on a schedule as those labs come available. So definitely check Ed Discussion. Check those mega threads. Check some of the other threads in Ed Discussion that are going on. I’ve gotten a lot of questions via email about using a Mac silicon to do this class. I already have a post on Ed Discussion about that. So please check the stuff in Ed Discussion. And then, of course, if you need to schedule a one-on-one time with me, you can either schedule with Josh and his Calendly or me and my Calendly. Again, I prefer if you start with Josh just to keep him busy. He’s an excellent GTA. He’s been doing a lot of good work in this class, but you can also always schedule with me if you have any questions as well.
So that’s really all that’s going on for this first week of class. The first lab is not due until middle of next week, but hopefully you’re getting started on it this week. Usually we have to work out a few little bugs and errors and things as we get this first lab up and running, especially if you’ve never worked with virtual machines or installed operating systems before. It’s a lot of new experiences this first time. And so I really like this class because it’s a good experience. It gives you a lot of opportunities to do things in system administration you’ve probably never done before. So as always, if you have any questions, let me know. Otherwise, best of luck this week, and I will see you again next week.
Hello and welcome to the week three announcements video for CIS 527 and CC510 in fall 2025. So this week you should be working on lab one. Lab one is due tomorrow by 7 p.m. So make sure you get that done. Basically all you need to do if you haven’t already is schedule a grading time with either Josh or myself. We will meet with you on Zoom. We will have you share your screen and walk through getting all your lab graded. Remember that every day a lab is late. It is 10% off of the total points in the class or in the project. So this lab is worth 50 points. If you get graded after Wednesday, it’s going to be worth 45 points and it goes down from there. Then next week on Wednesday, the module two quizzes are due. And then the week after that on Wednesday the 24th, Lab 2 is due. Lab two, you don’t have to schedule a grading time for. All the grading for that is done on Canvas. So unless you have questions or want to do an interactive grading, all you have to do for Lab 2 is submit your two puppet manifest files on Canvas and we’ll grade those offline. Also, our first discussion is going to be coming up soon. I’m still waiting to hear back from some of our speakers and I’ll talk about that in just a second.
So the discussion sessions, it looks like Tuesdays at 2.30 is the time that works for everybody. So I’m going to get that on the calendar. Starting not this week, but next week, I will try and have office hours during the Tuesdays from 2.30 to 3.30 time slot. I’m going to send some invites to speakers that are people in industry working in IT and related fields. And our first speaker is to be announced very shortly. I’m hoping it’s Seth Gallitzer, and I can get him in here in the next couple of weeks. So watch for more announcements for that. As soon as the discussion sessions are announced, you’ll be given a week to come up with questions that you want to ask our speaker. There’ll be an assignment posted on Canvas. You just submit a couple of questions and then join the live discussion session or watch the video afterward to get points.
So we’re going into lab two. The point of lab two is to basically redo the first lab, but this time you’re going to use Puppet. So for this lab, you’re going to start with two brand new VMs. You’re going to reinstall the operating system. You’re going to do some updates, install Puppet, and then you’re going to make a snapshot at that point. You don’t have to do any other setup other than what the lab tells you to do. Basically install the OS, set the computer name, do some updates, install Puppet, make a snapshot. Then what you’re going to do is you’re going to write a Puppet manifest file to do all the rest of the setup, including creating user accounts, installing software, setting up files and folder permissions, groups, et cetera, et cetera. You’re going to write a manifest file to do all of that for you, and you’re going to test that manifest.
The easiest way to test that manifest is to copy paste it into the VM, run the puppet manifest, and then for testing, you need to run it, reboot, and run it again, and then check to see if everything works. The reason you have to reboot, if you’re a member from Lab 1, is group memberships do not take effect immediately. They need a reboot for them to take effect. And so you run your puppet manifest, reboot for the groups to take effect, run it again to get the file permissions right, and then check for everything. Try and keep your puppet manifest very simple. A good solution is less than 200 lines of code. I think my solution is even less than 100 lines of code. It can be very simple. Use the puppet resource command to query the system as it’s set up, but don’t use the output of that. Just use individual lines of things you want to change. Kind of follow my lab instructions, but remember a solution can be pretty simple.
So another big thing to keep in mind in this class is a growth mindset. The labs in this class are challenging. They are meant to be challenging. This is a 500 level technical elective for a lot of you. And if you aren’t challenged, then you don’t learn and you don’t grow. So you need to come into this with a growth mindset. You can do it. Anybody can do it, but it is going to be challenging. The things that you can do for success, read the link to documentation, ask for clarification on things, start early on the lab and try and work through it methodically. I guarantee a recipe for not succeeding in this class is to wait until the Sunday before lab is due and then start on the lab because you’re going to run out of time and you won’t have time to ask questions. So start early, work methodically, and make snapshots. Snapshots in VMware are your friend. They are the auto-saves that you can use to go back anytime you need to go back.
So other than that, if you have any questions, you can keep in touch. We’ll have good discussions on Ed Discussion. You’ll see a mega thread posted there for every lab so you can work there. I’m going to start doing office hours like I scheduled next Tuesday starting at 2.30. So you can join office hours or you can always schedule a one-on-one time.
Also, don’t forget coming up tomorrow is the ACM Back to School Bash. It is Wednesday, September 10th in the engineering atrium from 5 to 7 p.m. It is open to everybody, computer science students, ICS students. If you are in this class, you are welcome to attend. The Back to School Bash is a great way to see what the student organizations are up to in computer science. You can learn about ACM, Cyber Defense Club, Hat Case State, all of the things that are going on. They’re going to have free food. So I encourage you to sign up and join. Again, back to School Bash is tomorrow, Wednesday, September 10th from 5 to 7 in the engineering atrium.
So hopefully things are going well. I know I’m asking you to do things again. That’s the way it goes in computer science, but you’re going to get really good at it. So hopefully it’s not too bad to have to do a lab setup again. As always, if you have any questions, let me know. Otherwise, best of luck, and I will see you again next week.
Hello and welcome to the week four announcements video for CIS 527 and CC 510 in fall 2025. So this week you should be working on lab two. The quizzes for lab two are due this Wednesday, so make sure you get those done soon. The next lab is due on next Wednesday, so you’re going to turn in lab two then. And in two weeks from now, we’re going to have our first discussion. So the questions for that discussion topic are going to be due two weeks from today, actually. So make sure you got that on your calendar.
So for lab two, real quick, just a reminder on lab two, where you’re doing Puppet, it is Canvas only. There is no meeting required for Lab 2 grading. All you’re going to do on Canvas is you’re going to take your two Puppet script files, the .pp files. You’re going to upload those to Canvas. And then Josh and I, what we’re going to do is we’re going to take your scripts, run them on our brand new updated VMs. We’re going to run your script once, reboot it, run it again, and then we’re going to check to make sure it did everything it’s supposed to do. So hopefully that makes sense. If you have questions on Lab 2, you can still schedule a meeting, but generally Lab 2 does not require any interactive grading. You just submit everything on Canvas.
So I’ve been working on getting our discussions speakers scheduled. I’ve got the first two on the calendar. First up is going to be Seth Galitzer, who is speaking two weeks from today on September 30th at 2.30. Seth is the engineering IT manager and formerly the computer science system administrator. He was our sysadmin for over 15 years. He’s also a K-State CS grad from the late 90s. So he knows a lot of the classes that you’re taking right now as a computer science student. Seth is a really great resource on campus. He’s one of the best sysadmins I know. And so he’s going to come in and talk to you a little bit about his job, what he does to help manage the systems for an academic department like computer science. And also he’s going to talk a little bit about his transition and role from the CSS admin to now engineering IT manager as we consolidate IT across all the different departments within engineering. So put that on your calendar.
Quick reminder for these to get points for them, you need to submit questions before the session starts. So sometime before Tuesday at 2.30, you need to submit some questions for Seth. And then you can either attend the live Zoom and ask Seth a question. You have to ask a question to get points for attendance. Or if you’re unable to ask a question or you’re unable to attend in person, I will have the session recorded and then you can watch the recording afterward and there’ll be a short discussion prompt I’ll have you respond to based on that recording. So there are many different ways you can can participate in this. I really want people to try and attend the video if you can and that’s why we tried to schedule as best we could the most people are available. But if not, that’s okay. You’ll be able to watch the recording.
One other thing that’s coming up next week is, if you know, I host tea time office hours in the computer science department every week. Tea time office hours is a great chance for you to meet with faculty, staff, advisors, and other students and talk about life, the universe, and everything. Specifically, we host a few panels every semester. And so our first panel is going to be coming up this Monday, September 22nd at 10 a.m. It’s a career fair prep and industry panel. We’re going to host the career center person for engineering, which is Liz Parks. She’s going to come in and talk about what the career center can do. And then we’re going to have a panel of industry and alumni folks that you can talk with. They’re going to give you tips on how to work a career fair, on resumes, on job searching, on interviews, anything you want to know there. So again, this is Monday, September 22nd at 10 a.m. It’s in Engineering 2168, which is the conference hall at the west end of the second floor by the CS offices, or you can join on Zoom. The Zoom link is posted online a lot of places. So hopefully you can find it, or you can always ping me and let me know.
So other than that, hopefully things are going well. If you have any questions, keep in touch on Ed Discussion. You can also find me on Discord and Teams and during office hours. So best of luck this week, and I will see you all again next week.
Hello and welcome to the week five announcements video for CIS 527 and CC510 in fall 2025. So this week you should be working on lab 2, which is due this Wednesday. We’ll talk about lab 2 in just a second, but remember that’s due tomorrow. Next Tuesday, we’re going to have our first discussion, so make sure you’re planning ahead for that. Next Wednesday is going to be the lab 3 quizzes, and in two weeks, we’re going to have lab 3 due and also our second discussion as well.
So for lab two grading, remember you’re working on two puppet manifest files. So make sure you’re getting those done. Lab two grading is Canvas only. You just submit your manifest files on Canvas and Josh and I will grade them offline. You don’t have to schedule a meeting with us or anything. We will just take care of that. What we’re going to do is for everybody that is submitted lab to by the deadline, I will go in shortly after the deadline and put in a temporary grade of one point for everybody. That will unlock module three so you can start working. But I’m only going to do that for people that have submitted lab two. Once I do that, that will give you access to the lab two model solutions. And so I want to make sure I only unlock the module for people who have submitted a lab. If you have questions or concerns about that, email the help email and we will help you get access to the things you need.
So next Tuesday, remember our first speaker is going to be Seth Gallitzer. Seth is the engineering IT manager and formerly our computer science sysadmin. It’s also a K-State computer science grad. So Seth really knows a lot about what he’s doing and working in IT and system administration. So he’s going to be coming in next Tuesday, a week from today at 2.30 p.m. via Zoom. The Zoom link and everything is on Canvas. Remember to get points for this, you have to do two things. You have to ask a couple of questions before 2.30. So fill out that assignment. And then to get attendance points, you either have to attend the session and ask a question, or you can watch the video afterward and write a quick response to the prompts that I give there. Either one of those is a great way to participate, but I really hope you’ll consider joining us and listening to what Seth has to say about his experience in system administration.
So then we’re going to start working on Lab 3. Lab 3 is where we introduce core networking services. And so in Lab 3, you’re going to set up some IP addresses for your systems. You’re going to install a DNS and DHCP server on Linux. You’re going to install an SNMP server on Linux and play around with that. You’re also going to play around with Wireshark a little bit. There’s a lot of technical detail going on in Lab 3, and a lot of this is going to be new for you. So I encourage you to take a look at the hints and diagrams in Lab 3, especially in the textbook. There are some diagrams. There is a video showing a working solution. There’s lots of cool stuff going on. So take care with Lab 3. Lab 3 is one of the harder labs in this class, especially if you have no experience with networking. And don’t be afraid to ask questions or come to office hours and get help. We are happy to help you out with that.
Other than that, hopefully things are going well this semester. You can always keep in touch on Ed Discussion. There will be a mega thread for Lab 3 posted very soon. I’m always available on Discord and Teams. I still host tea time office hours every Monday morning at 10 a.m. You can join on Zoom or in person, and you can always schedule one-on-one office hours with me. So hopefully that works out. So now we’re on to lab three where we’re going to get started networking. Hopefully you enjoy that. For anybody watching this video, I’m trying some new mic settings. So hopefully my audio sounds a little bit better. If you have any feedback on my audio for my mic, let me know. I’m still playing around with that, trying to get better sound out of my mic here. But hopefully things go well with Lab 3. If you have any questions, let us know. Otherwise, best of luck. And I will look forward to seeing you all next week.
Hello, and welcome to the week six announcements video for CIS 527 and CC510 in fall 2025. So, this week today, we’re hosting our first discussion session just shortly after this video gets posted. So, make sure you get the questions in for that. Tomorrow is when the lab three quizzes are going to be due. And then you’ve got until next week to work on lab three. I’m not saying Tuesday, but lab three, I believe, is actually due next Wednesday. But the second discussion will be next Tuesday, so make sure you’re watching out for that.
So as you know, you’re working on Lab 3, where we introduce core networking services. You’re going to be setting IP addresses. You’re going to be building DNS and DHCP servers, SNMP servers. Like I said last week, please take a look at the hints and diagrams at the end of this chapter in the textbook. There’s lots of good information in there about what we’re trying to do with this lab. And of course, when in doubt, please, please, please take some time and ask questions and get help if you get stuck.
So lab three grading. This will be grading live like we did for the first lab. So you’ll need to schedule a time with either Josh or myself sometime late this week or early next week. To do lab three grading, we want you to demonstrate the remote connections between your systems. So you should be able to use the remote desktop tool to remote into your Windows client. You should be able to use SSH to remote into your Ubuntu server. You should have a static IP on your Ubuntu server. You should have a DNS server that we can do lookups on. You should have a DHCP server that is running your network within your VM. And then you should be able to demonstrate that you can do an SNMP query and you have the pictures of that activity and the pictures of the Wireshark activity ready to go. So just be prepared for that. Lab 3 grading goes pretty quick. There’s just a few things we want to test and make sure it all works before we move on.
So then you’re going to work on Lab 4. Lab 4 is about installing an Active Directory and an LDAP server for authentication. So you’re going to create a virtual machine for Windows Server. You’re going to configure some of your clients and interoperability. And then, of course, you want to make sure you make snapshots for this. Big thing for Lab 4 is follow the instructions. Make sure you make snapshots before you promote your Windows Server to Active Directory and before you try and configure OpenLDAP with SSH or SSL. Those are the two things that most people have trouble with. And then, of course, if you’re running on Mac Silicon, this is where we hit the point where you need Windows Server. So far, I have heard from everybody that you have an alternative system that you can run on. If you do run into issues with this running on Mac Silicon chips, just let me know and we’ll work around that.
So as always, success in this class, you got to read things carefully, see my hints, use your resources. Big thing I want you to keep in mind is don’t spin your wheels. If you’ve been working on something for about an hour or so, take a break, step away, think about it, reach out for help. We’re here to help. So don’t just sit there and spin your wheels for eight hours and not make any progress. That gets really frustrating. And sometimes it is possible that you run into problems that it’s difficult to solve. So we’re used to that. We will help you out.
So today we’ve got our first guest speaker, which is Seth Galitzer. Seth Galitzer is the engineering IT manager for the Engineering College, formerly the CS admin for the computer science department for something like 17 years, I believe. He’s a CS grad from here at K-State, and so he’ll be speaking today at 2.30 on Zoom. It’s the same Zoom we use for office hours. So make sure you get your questions in for that before we get to that session so you’re ready to go.
And then next week on Tuesday, we’re going to have another speaker, Kyle Hutson. Kyle Hutson currently works at Lambda Labs, but he formerly worked at Canran, which is the internet service provider for K-State. And before that, he was a BayoCat sysadmin for about 12 years. So he’s going to be here next Tuesday on October the 7th at 2.30. So make sure you’re watching for that as well.
Last big thing to cover, I’m going to be fully remote the rest of this week, Wednesday through Friday. That means my email responses will be a little bit slower because I’ll be mainly able to check email in the mornings and evenings. I also will have blocked off my calendar just because I can’t immediately respond to appointment requests. If you need an appointment with me, you can schedule with me via email and I will get back to you. Josh’s calendar should be open for early grading on lab three if you get done early. Otherwise, we’ll be available early next week for lab three grading. Not a problem.
So other than that, hopefully things are going well. Feel free to keep in touch with me, all the different ways that you can keep in touch. But otherwise, hopefully things are going well in this lab. Hopefully it’s not too frustrating. I know that this is where the class starts to get a little bit more difficult. So take your time, use your resources, let us know if you have any questions. But otherwise, best of luck, and I will see you again next week.
Hello and welcome to the week 7 announcements video for CIS 527 and CC 510 in fall 2025. So this week you should be working on lab 3. That’s really the only thing going on this week. So lab 3 deadline is this Friday. I did say last week it was due earlier in the week, but I’ve updated the deadline in Canvas to make sure everything matches. So lab 3 will be due this Friday. So make sure you schedule a time to meet with either Josh or I to get your lab 3 graded via Zoom before or on Friday of this week. Then we have a whole week where there’s nothing really due, but you should be working on lab 4. The quizzes for lab four are going to be due Monday, October 20th. And then Tuesday, October 21st, we’re going to have our third discussion prompt, and I’ll talk about that in just a second. And then Friday, 10/24, sorry, I didn’t get that date right. Lab 4 is going to be due. So all these dates are correct on Canvas. So when in doubt, check Canvas. It should always have the correct dates.
So as you know, you’re working on Lab 3. Lab 3 is all about core networking services. Hopefully things are going well with Lab 3. If you have any questions, please make sure you check out the hints and the diagrams at the end of the textbook chapter for Lab 3. I think it gives a really good example of what everything should look like and talks you through some common debugging issues on DNS. And then, of course, if you get stuck, ask questions and let us know and we will help you out with that.
So for lab three grading, you’re going to do this grading on Zoom. So make sure you’re prepared to demonstrate all of these things. Remote connection between your two systems, static IP, DNS lookups, DNS server settings, DHCP server settings, SNMP and Wireshark. That last one, SNMP and Wireshark, we’re just looking for screenshots to show that you did the activities. That’s all you really need to do. You don’t need to actually run Wireshark or SNMP during grading. We’re just going to look at your screenshots, especially in the Wireshark screenshots. Make sure you are drilling down into that bottom section and showing us the exact packet that we’re looking for. Don’t just have a screenshot where, oh, the packet’s in there somewhere. We want you to show us the right packet and show us down in the data that you can prove that that’s the packet we’re looking for. So make sure you’re doing that.
So next week, we’re going to start working on lab four. Lab 4, we’re going to add in yet another virtual machine. This time is Windows Server. For those of you running on non-x86 or x64 hardware, this is the one you’re going to have trouble with because Windows Server does not run on ARM platforms. So you’ll need to work around that either by running it on another computer or working with me to run it in Azure or some other system. Windows Server allows us to use Active Directory, which is still the big behemoth in terms of authentication systems. We’re also going to configure OpenLDAP, which is the open source kind of competitor to Active Directory. We’re going to configure some clients. We’re also going to configure some interoperability a little bit. Big thing is with all of these labs, make snapshots. Especially the two times you’re going to want to make a snapshot for sure in this lab are before you promote your Windows Server VM to an Active Directory domain controller. I would say my lifetime success rate is about 90% at that one. So that means one in 10 times that I have tried to promote a Windows Server to an Active Directory controller, something has gone wrong. I don’t know why. And then I roll back to the snapshot and I try again. The other one that trips a lot of people up is adding the TLS certificates to an Open LDAP server. There’s a lot of commands that you have to type in. It’s all in the document. You just mostly copy paste the commands and tweak a couple of things. It is really, really hard to undo some of those changes once you make them. So again, make a snapshot before you start adding TLS certificates to your LDAP server. That way, if it doesn’t work, you can switch back to the prior snapshot, go through it again carefully, and make sure you didn’t miss anything. So just be aware of those things and make sure you’re prepared to deal with all of that.
So like I say, every time I talk about these videos, success in this class really depends on reading carefully, using your resources, and asking questions. Lab 3 and Lab 4 are the two hardest labs in this class, I believe. The later labs build on top of it, but I don’t think they’re quite as technically difficult as these two labs can be. So don’t spin your wheels. If you get stuck, take a minute, ask questions, let us know how we can help. We’d be glad to do that.
So as you saw with my announcement, I’ve had to shuffle around the discussion schedule a little bit. So it’s going to be confusing, but the dates are going to be right on Canvas. So what we have is discussion three is going to be next Tuesday, a week from this week. So it’s going to be Tuesday the 21st, or two Tuesdays from today, actually. It’s going to be Nick Eggleston and Nathan Wells. They are the two Beocat sysadmins. They’re going to be coming in Tuesday, October 21st at 2:30. So that’s going to be discussion three. The questions are going to be due, obviously, on the 21st before they speak, and then you can do your response afterward. But this is going to be discussion three, but I will get the dates out there so that it’s correct. They’re going to be out of order. But discussion three is going to be Nick and Nathan, our Beocat sysadmins. And then I rescheduled Kyle, who is supposed to speak today. I’ve rescheduled him out a couple of weeks. And so discussion two with Kyle will now be Tuesday, October 28th at 2:30. And so I will get those dates updated on Canvas if I haven’t already. So that’s coming up as well.
So once again, barring any weather catastrophes, I probably will be fully remote again this week working from my parents’ farm on Thursday and Friday. That just means email responses are a little slower. I will be watching my email, but it may take me a little bit longer to get back to you. Likewise, if you want an appointment with me on Thursday and Friday, you have to send me an email because I won’t have free calendar times. If that becomes a problem with lab three grading, I will take a look at things. I’m not afraid to waive some late penalties for lab three if we don’t have enough time to get everybody on Josh’s calendar. But just be aware, I may be working remotely for parts of Thursday and Friday this week, weather permitting. So just be aware of that. I will be catching up over Saturday and Sunday as well. So hopefully that’s everything. As always, keep in touch. Lots of good posts on Ed Discussion. You can always find me on Discord and Teams or come to office hours. I’m always happy to help. But anyway, best of luck as you wrap up lab three, and I will see you again next week.
Hello and welcome to the week 8 announcements video for CIS 527 and CC 510 in fall 2025. So we don’t really have anything due this week, but next week on Monday are the quizzes for lab 4. Then next Tuesday we’re going to have the third discussion with the current BayoCat sysadmins. And then lab four is going to be due a week from this Friday on the 24th. Then on Tuesday the 28th right before Halloween we’re going to have our second discussion which is Kyle Hudson. But there’s nothing available and nothing due this week. I just want you to get started on lab four and start working on that because it is one of the harder and more time consuming labs for this semester. So make sure you get started on that soon.
Lab 4, you’re going to create a Windows Server VM and then install a Windows Active Directory on that. You’re also going to install Open LDAP on your Ubuntu server and then configure clients to connect to those. We’re also going to play a little bit with interoperability where we’re going to take an Ubuntu client and put it onto your Windows Active Directory, which is pretty cool. Unfortunately, we don’t go the other way where we put a Windows client on Open LDAP. That’s really difficult to do. But I do show you a video of what that looked like from a couple years ago. And then, of course, don’t forget, make snapshots and use those. I give a lot of hints in the lab for times when you want to make snapshots.
To get set up for lab four, you’ve really got three options. Ideally, if your DNS and DHCP server from lab 3 are working fully, you can go ahead and continue to use that lab 3 setup. Just make sure your Ubuntu server is always running in the background, providing that DNS and DHCP. If you didn’t get those running, you can use a static DNS entries in your Lab 3 config. So basically, your Ubuntu talks to your Lab 3 DNS server. Your Windows talks to your Windows server for DNS. So you can do some of that. And then if that doesn’t work, you can also set static host file entries. Generally on Windows, especially, you want to set a static DNS address that points directly to the Windows server so that the AD works. And then same thing when you’re setting up an Active Directory on Ubuntu, set that so that the DNS server points to the Windows server. Everything works great. If you have any questions on Lab 4 setup, let me know and I’m happy to help.
So for Lab 4 grading, this one’s pretty straightforward. We check and see if your Windows server is installed and you have an Active Directory user and group setup and then that your Windows client logs in on AD. Then we go to your Ubuntu server, check that LDAP is installed, has a correct user and group in it, and then you have an Ubuntu client that logs in via LDAP and another Ubuntu client or another snapshot of an Ubuntu client that logs in via Active Directory. That’s all it is.
So we’ve got two speakers coming up. Next Tuesday, we have Nick Eggleston and Nathan Wells, our two current BayoCat sysadmins. So make sure you’re thinking of questions for them. And then two weeks from that, two weeks from today is going to be Kyle Hudson, who is a former BayoCat admin and now currently works at Lambda Labs.
Other than that, feel free to keep in touch. There’s a lot of stuff going on. If you haven’t already, please register and attend Hack K-State if you’re available this weekend. It is in the business building. It’s a great chance to hang out with computer science students and either do your homework and get free food or actually do a hackathon project and get free food. So feel free to hang out with us this weekend at Hack K-State. I should be there most of the time. So I look forward to hopefully seeing some of you there. Other than that, we’re at the halfway point of the semester. Hopefully things are going well. Best of luck this week. And I will see you again next week.
Hello, and welcome to the week nine announcements video for CIS527 and CC510 in fall 2025. So this week you should be working on getting lab 4 finished up. Because we had all the outages yesterday, I’ve moved the lab 4 quizzes to tomorrow, which is Wednesday. Today we have our third discussion, which will be today at 2.30 that I’ll talk about briefly. Lab 4 is due this Friday. And then next Tuesday, we’re going to have our second discussion that I will also talk about briefly. So the schedule is a little weird. Hopefully it all makes sense. And all of these dates should also be accurate on Canvas.
So this week you’re working on Lab 4. We’ve talked about it a little bit already. Basically, the big idea is to add an Active Directory and Open LDAP to your Ubuntu and Windows systems and then configure the clients to log in via those systems. Make sure you read the instructions very carefully, make snapshots where I tell you to make snapshots. And of course, if you have questions, either post on Ed Discussion or email the cis527-help and we would be happy to help you out.
So there are three different ways you can do Lab 4 setup. If you have a working Lab 3, you can use your Lab 3 DNS and DHCP servers. Those work great. The only thing I usually recommend is on the Windows client or the Ubuntu client that is pointing to the Windows Active Directory that you add the static DNS entry to point to the Windows server instead of the Ubuntu server. That seems to fix a lot of problems with Active Directory. If you don’t have a working one, you can do static DNS entries or host file entries. There is a network setup document that talks about some of this. If you have questions or have trouble getting the Lab4 network set up, let me know. I’d be happy to help.
So Lab 4 grading is pretty straightforward. We just want to see that your Active Directory server is set up, has the correct user and group on it, and that your Windows machine can log in with Active Directory. Then on Ubuntu, you’re going to have an Open LDAP server with a user and group on it. And then you’ll have an Ubuntu client that logs in via LDAP and an Ubuntu client, either another VM or another snapshot of the same VM that can log into Active Directory. If everything’s working, takes less than five minutes to grade. If things are not working, it’s kind of frustrating to debug, but we will do the best we can to see where you’re at in the process and try and give you partial credit for as far as you got.
So then after that, we’re going to switch to Lab 5. Lab 5 may not be published yet on Canvas, but I’m going to get it published very soon. Lab 5, we’re going to move out to the cloud. We’re going to create some droplets on DigitalOcean. We’re going to set up SSH and firewall on those droplets. And then we’re going to set up some websites, DNS, and we’re also going to play a little bit with Docker. I think Lab 5 is a little bit simpler than Lab 4. Generally, it’s much lower in terms of time requirements, but it’s a good setup for the last couple of labs that we’re going to do in this class. So this one, we’re going to move to the cloud.
One of the things you might want is the GitHub Education Pack, which you can find at education.github.com slash pack. There are some other things that you can find out there if you Google real quick. That second URL, it gets cut off. It’s try.digitalocean.com slash free trial offer. That will get you $200 in free credits to DigitalOcean as long as you sign up a new account. You can also go to nc.me to sign up for a Namecheap account. I have referral links for both of those as well if you want those. So you can ask me for some referral links. Total cost to you at most, even if you have to pay for everything out of pocket, should be about $11. But with these trial links, everything should be cheap. I think the only thing you really have to pay for is the domain name, which should be 99 cents for the first year. Again, if you have trouble, let me know. I also know last year we had trouble with some students getting signed up on DigitalOcean that they got flagged as spam. If that happens, let me know. I’ve got some extra email accounts that we can use to sign you up to get you started. So just reach out to me anytime. But those are some of the resources you’ll need for Lab 5.
So we’ve got two discussions coming up. This week, we’ve got Nick Eggleston and Nathan Wells, our two BayoCat sysadmins. They’re going to be speaking today at 2.30. So make sure you get your questions in for that. And then next week, we’re going to have Kyle Hudson. He is the former BayoCat admin, also formerly at Canren, which is the ISP that provides internet to universities in Kansas, such as K-State. And he currently works at Lambda Labs. And he’s going to be in next Tuesday at 2.30. So make sure you have your questions prompt for that.
Other than that, feel free to keep in touch. I’m always available on Ed Discussion, Discord, Teams, Tea Time office hours, et cetera, et cetera.
But hopefully things are going well. I had to include this XKCD comic, especially where we’re moving into the cloud next week. And also, we had a big cloud outage yesterday. And so it’s just important to remember that to you, it’s the cloud, but to everybody, it’s to somebody, the cloud is just somebody else’s computer. Hopefully, it’s more than just a box sitting in somebody’s apartment with a single cable. But that’s really the thing to keep in mind. So hopefully everything goes well this week. Best of luck. If you have any questions, let me know. Otherwise, I will see you again next week.
Hello and welcome to the week 10 announcements video for CIS 527 and CC510 in fall 2025. So this week today we’ve got our second discussion. It’s really our third discussion, but it’s discussion two and the announcements. We’ll talk about that. That’s coming up today. Then this Friday your response for discussion three that was last week is going to be due as well as the quizzes for lab five. So make sure you’re watching all those due dates on Canvas.
So like we talked about last week, lab five, we’re going to move into the cloud. We’re going to create two droplets on DigitalOcean. We’re going to set up things like SSH and firewall rules. And then we’re going to set up some simple Apache websites. And we’re also going to do some work with Docker and set up a reverse proxy to a couple of Docker websites. So this is a little bit lower in terms of difficulty with Lab 4, but if it’s the first time you’ve worked in the cloud and worked with all these online services, there’s still quite a bit of learning to do with this lab. So be aware of that. But hopefully this lab works out really well.
So for grading on lab five, the first thing we’re going to do is we’re going to make sure that we can SSH to your front end and to your back end. For the SSH to front end, if you’re on campus, you’ll just have to use the virtual console. We won’t be able to directly SSH to it. That’s fine. But your front end should be able to SSH to your back end. That’s part of the setup. We’re going to check firewall. We’re going to check for Apache, DNS, HTTPS, and the reverse proxy for Docker. All of it should be pretty straightforward. If you have any questions on it, let me know.
So don’t forget for this lab, you may want to use some things from the GitHub Education Pack. For example, in DigitalOcean, if you go to the free trial offer website, you can get up to $200 in free credit for 60 days. If you go to nc.me, you can register for a .me domain for $11. If you want my referral links for any of these, I’m happy to share them with you. But at worst, even if you have to pay for everything out of pocket, your total cost for this should be about $11. As always, if this presents a hardship for you or if you’re concerned about using any of these online resources, please let me know. I do have alternative options out there, but I’m really encouraging you to play with some of these real world surfaces because I think it’s a really great way to learn how to do all these things in the cloud. And I think this is one of the more straightforward ways to do it.
So another question that’s come up a couple of times is the final project. Hopefully you have noticed in this class that there is a final project coming up at the end of the semester. So big short version of the final project is it is 90% a thought exercise. What I want you to do is make an IT proposal toward me, pretending that I’m your CIO and you’re trying to propose something you want to do in IT. You can build something or you can fix something. Some examples would be like a web resource for a new startup company, setting up laptops for a school, designing a central authentication system for a company, discussing whether you want to replace the thin clients in a lab with thick clients, discussing what antivirus you want to use, what cloud providers you want to use, tons of stuff. Basically what this project is, propose an IT project, and then instead of doing the project, what you’re going to do is a SWOT analysis, strengths, weaknesses, opportunities, and threats to show me that you have thought through this project really well and that you can explain to me as your CIO what the benefits are of this project, what the drawbacks of this project are. And your goal is to try and convince me that this project is a good idea. Like I said, it’s 90% of thought exercise. It’s just making the proposal, going through the analysis, doing some reading, doing some research, presenting your materials. And then there’s about 10% of it that is really actually doing a small proof of concept.
So for example, if you’re playing around with an antivirus system, for example, you might load up a VM and install two or three different antivirus systems in there just to play around with them. If you’re doing a web resource for a new startup, you might throw a web resource up on a Docker instance or an AWS instance. It doesn’t have to be much. It should take you just a couple hours, but I want you to at least show me that you’ve played around with this idea or tinkered with it a little bit so that your analysis really makes sense with what your real world expectations are. If you’re having trouble coming up with a final project, you can chat with me for ideas. The big thing that you’re going to turn in is a written report and then also a recorded presentation that’s about 10 to 15 minutes in length that is going over the highlights in your report. That’s really what I’m looking for. And as always, if you have any questions on this, let me know.
So today we’ve got our second discussion session, which is going to be Kyle Hudson. Kyle Hudson currently works at Lambda Labs, but formerly worked as a Bayochet admin and also as an IT person for Canren. He’s going to come in and talk about his experience working on high-performance computing. Kyle is always a very engaging speaker, so I hope everybody can make it today. And remember, that is today at 2.30. Other than that, keep in touch with me if you have any questions. I’m available just about everywhere you try and find me. But otherwise, we’re kind of nearing the end of the semester. It is week 10 out of 16. So hopefully you can start to feel that we’re getting there. As always, if you have any questions, let me know. Otherwise, best of luck. And I will see you again next week.
Hello and welcome to the week 12 announcements video for CIS 527 and CC510 in fall 2025. So coming up this week, the Lab 6 quizzes are due on Friday. I just posted Lab 6 so you can get started on that. And then Lab 6 itself is going to be due next Friday. That’s the Friday before fall break. So make sure you get that done. And then Lab 7 will be coming up after fall break. But we’ll talk about everything in today’s announcements.
So for lab six, we’re going to focus on a couple of different things. First, we’re going to talk about setting up file servers in both Windows and Linux. We’ll set up file servers on our servers. We’ll also set up some automated drive mappings on our clients so that we can get access to those file servers automatically. And then we’ll set up an application server on Windows. We’re going to install a .NET web application on our Windows server. And then in the cloud, we’re going to make a web app in the cloud. So we’re going to install a database and a web app in the cloud. These are kind of common scenarios that you run into if you’re actually deploying your own applications on your systems. If you do any self-hosting, this will be kind of similar in both aspects there. So we’re going to take a look at some of that.
Then for lab seven, we’re going to do a smorgasbord of all the things that I wish I could get to in this class, but I don’t have enough time. And honestly, most of these things on lab seven could be entire classes unto themselves. But in lab seven, we’re going to do a little bit with backups. We’re going to do a little bit of system monitoring. We’re going to do a little bit of DevOps with webhooks. And then we’re going to do a little bit of logging as well. So lab seven is kind of a catch-all for all these other things that I really want to cover this semester.
One thing to keep in mind for lab seven, there will not be any grading meeting required for lab seven. You just submit four things on Canvas. You can submit them separately or all as one submission, however you want to do it. But basically for lab seven, because we’re coming up on finals week when lab seven is due, there’s no meeting required to get lab seven graded. Unless you don’t get something to work and you want to do a meeting just to get some partial credit for the things that are working, we can definitely do that. So really the last lab that you need to have interactive grading for is on lab six. Also a clarification on lab six, because we are not around over Thanksgiving break. If you don’t get lab six graded by the Friday before Thanksgiving break, we’re not going to assess any late penalties beyond the usual one-day late penalty until you can get graded after fall break. It’s just the way this always kind of lines up. So if you don’t get lab six done on time, you get basically an extra week to work on it for free because we’re not available to grade it. So just be aware of that.
All right. Last big thing coming up in this class is the final project. You can find the final project module in Canvas. It’s been published since the beginning, but you may have to scroll back up to the top to find it. The idea behind the final project in this class is 99, it’s about 90% a thought exercise. What I want you to do is propose some sort of IT sysadmin thing that you want to do. Pretend you’re working for a company. I’m your CIO. You have a project you want to do and you have to convince me that that project is a good idea. And so it could be building something or fixing something about your organization. It could be speccing out a web resource for a new startup, setting up laptops for high school, designing an authentication system for a company, debating thin clients versus thick clients in computing labs, debating which antivirus software to use, what platforms to deploy your software on. Just about anything is fair game that we have talked about in this class or something that you have experience in. It can be a real organization or one that you make up. Either way, you just have to set the stage by providing the appropriate background for what you’re doing. If you’re not sure what project you want to do, you can chat with me for ideas. I’m happy to do that.
What you’re going to do is write a short proposal that is due coming up soon. Check the dates on Canvas. It will tell you exactly when that’s due. I will review your proposal and basically give you a thumbs up, thumbs down that that’s a good idea. And then you’ll have a couple more weeks to wrap up your project itself. Basically, again, you’re proposing something you want to do as a sysadmin, as an IT person. You’re trying to convince me, your CIO, that it’s a good idea. I know tech, but also I’m not like in the trenches like you are. So you’re going to have to share some of the technical details. And you’re also going to do a SWOT analysis. And the project explains that a SWOT analysis looks at strengths, weaknesses, opportunities, and threats. Strengths and weaknesses are internal to the idea. Opportunities and threats are external to the idea, external to the organization. There’s some great articles online about SWOT analyses if you’ve never done that before, but that’s really what I’m looking for.
So for the final project, you’re going to turn in three things. Really, you’re only going to turn in two, and then you’re going to do three things. The first one is you’re going to turn in a written report. I give a template that just gives you some section headings. In the template, it has bulleted points under each section heading. I do not want you to write bullet points. I want you to replace those bullet points with paragraphs. The bullet points tell you what those paragraphs should cover. The template is very loose. You don’t have to follow it, but a lot of students ask me, how do I structure this project? When in doubt, use the template, use the headings. It kind of works. You’re going to research, propose it, do a SWOT analysis. You got to give me the background for everything and the SWOT analysis and then a conclusion. You know, conclusion could be very simple. Based on my SWOT analysis, I feel like the strengths outweigh the weaknesses and we can mitigate the weaknesses as I’ve described in this paper. Therefore, I think it’s a good idea. That’s a conclusion. Include graphics, data, citations as needed. Treat this like any other project that you would do in a college-level class. So you’re going to submit a written report. There is no minimum or maximum length. It’s however much it takes to convince me that it’s a good idea without being so long that I feel like I’m reading a book.
Then you’re going to do a presentation. The presentation is about 15 minutes. It’s something that you can pre-record at home. Basically, your presentation is going to be the TLDR version of your written report. Convince me it’s a good idea. Tell me your background. Tell me your analysis. Tell me your conclusion in about 15 minutes or so. Basically convince me that you have done your homework and have analyzed this project well. And then the last thing you’re going to show as part of your presentation is a small prototype. For example, if you’re playing around with a central authentication system, you might play around with a version of that. Or if you’re looking at different hosting providers, you might set up a platform on AWS and a platform on Azure. Doesn’t have to be much. I just want you to get a little bit hands-on with the idea that you’re working on. In total, I expect you to spend about two to four hours on your prototype. I don’t expect you to go very deep. I just want you to play around a little bit with something that you have proposed, install it, play around with it, load it in Docker, whatever it means. If you’re not sure what to do for a prototype on a project, chat with me. I’d be happy to help you figure that out. So, like I said, presentation, you’re going to pre-record a video. You can use Zoom or any other tools that you want. Ideally, I would like to see both slides and you as your presenter on that video. Hopefully, you have access to a webcam. If not, let me know and we can work on that. But the nice thing about pre-recorded videos, you can do as many takes as you like. You can edit it however you need. But I want to see you give the presentation. And then you can either upload the video to Canvas itself, or if it’s too large to put on Canvas, you can put it in your personal KSU OneDrive, share the link with me, and I can get it that way.
Other than that, that really covers the rest of the semester. There are two labs and a final project left. Hopefully things are going well. Lab six and lab seven generally aren’t too bad. They’re just a lot of little details and things. And especially in these two labs, I give you less of the direct instructions and more of the go do this. And then you’ll have to read some of the documentation and figure out how to do it. So hopefully things are going well. But as always, if you have questions, you can post on Ed. You can find me on Discord or Teams. You can schedule an office hours with me. I’m always happy to help. I’m always available, except for fall break when I will be gone. Other than that, hopefully things are going well. Best of luck as you work on these next couple labs. Let me know if you have any questions, and I will see you again next week.
Hello and welcome to the week 15 announcements for CIS 527 and CC 510 in fall 2025. So we’re almost at the end of the semester, so there’s not a whole lot remaining in this class. Big things to remember is lab 7 is due the end of finals week, which is December 19th, and your final project is due December 19th as well. And then of course, you should be completing your teaching evaluations.
So for lab 7, there’s no meeting required for lab 7 grading. There are just four tasks that you can do any combination of and upload to Canvas. Task 1, you just need to send your zip file of your backup and your README for how to restore it. Task two, you just send me your monitoring URL for Moonen and I will go in and check that. For task three, you need to send me your GitLab or GitHub. Add me as a maintainer at least on that so I can make a commit and then send me the URL of where I will be able to see those commit changes put in. And then for task four, you just need to set up the logging system and then do a quick write-up on what you see in the logs. Hopefully all of this is pretty straightforward, but if you have questions, feel free to let me know and I’d be happy to help you with that. And then of course, like I talked about, do whatever parts of Lab 7 you want to do to get the final grade that you want in Canvas. Make sure you look really closely at my most recent announcement in Canvas to describe how final grading works in this class. And let me know if you have any questions.
So for the final project, as you complete your final project, you’re going to be turning in three things. Actually, two of them you’re going to turn in. The third one just gets recorded in the video. You’re going to turn in a written report. I want you to use the template that I provide if you’re not sure what to do, but remember the template uses bullet points to explain what should be in the paragraphs. You should be writing paragraphs, not filling out a bulleted list of things. Basically, you’re going to propose your change, tell me the background, tell me the change, and do a SWOT analysis, include graphics and data as needed in your SWOT analysis. Then you’re going to record a presentation that’s around 15 minutes long. Pretend you’re pitching it to me as your CIO. Convince me you’ve analyzed it well. One thing that’s very important to keep in mind with this project, it is okay for your analysis to say, you know what, this is actually a bad idea and we shouldn’t do it. That’s fine. The big thing I’m looking for is the analysis itself. Then, of course, I want you to do a small prototype and just demo the prototype inside of your presentation video. The prototype is meant to be very small, just a toy problem that goes along with your change. Should spend no more than two to four hours on the prototype. Don’t make it harder than it is. But if your change is like, I want to move stuff to AWS, your prototype should be, I played around in AWS for a couple hours. That’s all I’m really looking for.
So like I said, your presentation, it should be a pre-recorded video. You can upload it to Canvas, or if it’s too large to share on Canvas, I encourage you to upload it to OneDrive and then share the link with me on OneDrive. Make sure that I have access to that link on OneDrive. If you have the ability, some students have uploaded it to places like YouTube. That’s fine. You can make an unlisted YouTube video. I can find it. Just send me the link or the file or whatever I need to know so I have access to your video. And that’s really all you need to do is submit your video and submit your write-up.
So last big thing for this class, teaching evaluations. Teaching evaluations went out this morning. So hopefully you’ve already gotten an email encouraging you to fill those out. Please take the time to fill out the TEVAL for this course. I really, really do appreciate all of your honest and constructive feedback in this course. This course has definitely changed over the last decade or so that I’ve been teaching it. And I really want to hear from you what works, what doesn’t work, what changes I should make, what things I should add. So any and all comments and feedback are welcome. Remember at K-State TEVALs are both anonymous to me, which means I will not know anything about who you are when you write stuff in the textbook in the TEVAL, and they’re also delayed. I do not get to see the TEVALs until after I’ve submitted final grades. So please feel free to give me any and all honest and constructive feedback in the TEVAL. I really, really do appreciate it. You’ll get reminders over the next couple weeks to fill that out if you haven’t already.
And then last big thing, final grades. Please keep an eye on Canvas. Final grades will be due for me Monday the 22nd. So at some point, you will get an announcement from me in Canvas saying that grades are final in Canvas. Please check your Canvas now and email me if you have any concerns about what your grade looks like or you’re not sure how your grade is going to be calculated. Because of the condensed timeline this semester, there will not be a whole lot of time between when I finalize grades in Canvas and when I have to upload them to KSIS. So check your grades now. Let me know if you have any questions or concerns, but be prepared sometime on Monday, you’ll get an announcement saying the final grades are in Canvas. And then the grade you see in Canvas is the grade that will show up in KSIS.
So we are at the end of the semester. Hopefully things are going well. As always, if you have any questions, let me know. Otherwise, best of luck as you wrap up things in this class. And for a lot of you, I look forward to seeing your final presentation videos over the next week. So best of luck.
Hello everyone and welcome to the week one announcements video for CIS 527 and CC fall 10 in fall 2024. So as you probably saw in the introduction video my name is Russ Feldhausen my contact information is here you can find it on Canvas you can find it on the syllabus. I’m really excited to be teaching this class I think this is my eighth time teaching the system administration class. It’s a really fun class it’s one of the most valuable classes that I get to teach at K -State and I’m really excited to be working through it with you. Every week I’m going to do an announcements video maybe every week maybe every other week it’s generally unscripted it’s me talking through everything that’s in my head so you’re gonna see a much different version of me in these announcements videos versus what you see in the videos for the class.
So for this semester I have one teaching assistant Josh Barron. Josh Barron is a GTA that’s working with me he is new to this class but he’s really excited to be catching up and learning with all of you all. He’ll be handling a lot of the questions and grading in this class and then I’ll also be available to answer questions help with grading whatever we can do. We have a pretty big class this semester I think I have 32 enrolled right now which is the largest version of this class I’ve had in several years so it will take a little bit of getting used to as we get used to the scale and taking care of all the grading so just bear with us as we get started on that.
So like I talked about in the introduction with this course there are seven modules in the course plus the final project it’s a 16 week semester so you’re going to do one module every other week. I generally recommend that you start on the modules as soon as they’re available because really some of these lab assignments may take you a couple weeks to get done. The one thing that I have seen students do in this class that causes them to fail is wait to start the lab assignment until the weekend before it’s due and then they get stuck and then it takes them time to get help and sometimes it takes multiple times to get help and then they’re two or three days late and they sacrifice 30 or 40 percent of their grade on the lab because they started two days before it was due. So I encourage you to start your labs early and check the due dates and put them on your calendar. In most chapters I have the lab assignment right up front so you can start working on the lab as you go through the of the content. You don’t have to read and watch everything before you can start on the lab. I do recommend reading the entire lab assignment before you start on it, but generally you can get started as soon as you get to a new module.
For the lab assignments, what we’re going to do is live grading. It’s the best way I’ve come up with to grade this course. So generally what happens is you’ll schedule a time on Calendly with either Josh is preferred, if his calendars fold and you’ll schedule on my calendar. I do that to protect my time, but also because I’m paying for 20 hours of Josh’s time and I want to make sure we use up Josh’s time more effectively than using up my time because I’m actually bouncing between about four different classes this semester. So you schedule a time to grade, you’ll get a Zoom link in that scheduled calendar invite. And so you’ll join the Zoom, you’ll share your screen, and then either Josh or I will talk you through some things that we want you to demonstrate. In general, you should be prepared to demonstrate everything that you did on the lab. So if we ask you, show us where the users are, you should know where to go and show us what users you set up. If we ask you to confirm that your DNS server works by querying these few things, you should know how to query your DNS server. We shouldn’t have to tell you the commands to do that. We’ll prepare to do that if we have to, but really it’s a demonstration of your ability and understanding of the system. So not only do you have to set it up and have it working, but we expect you to know how to use it so that when we ask you to demonstrate things during the lab, you should be able to go, oh yeah, I know how to do that and get it figured out. So be prepared for that.
We’re also gonna have some live discussions throughout the semester. The plan for the live discussions is to bring in a industry person or some sort of other person and have them talk about their experiences with system administration. I can tell you the first one is most likely going to be Seth Galitzer, our computer science system administration here, system administrator for computer science. I’m probably gonna try and get somebody from Bayocat. I’ll probably try and get Kyle Hudson, who used to be a Bayocat, and then was a Canran, and now he’s moved on to some high -performance computing stuff in industry, which is really cool. And then generally I try and get somebody from larger industry and I try and get somebody from more administration side of things like CIO, CEO type roles. So I’m working on scheduling those and we’ll get those figured out soon. So just keep your eyes open for that.
So for communication in this course, like I talked about, the best thing to do is to post in the Ed discussion board. Ed discussion allows you to post questions. In general, I recommend posting the questions openly and publicly so that everybody can see them and answer them. I know that that’s asking a lot, especially because you may not want to ask that question publicly due to imposter syndrome, but it’s okay. If you have that question, probably everybody else in the class does too. But if you’re concerned about that, you can post a question anonymously so that other students won’t be able to see who you are. Full disclosure, Josh and I will know who you are. but it won’t be public to anybody else. Or you can post a question privately just to Josh and myself and we’ll answer it there. But we do reserve the right to copy paste your question and anonymize it and post it publicly if we think other people should see it. So just be aware of that. Outside of that, you can email us, if you have any personal issues, grading issues, to -dos, things like that. The help email address, CIS527 -help. If you type it in in web mail, it should auto complete. But if not, you need to use the full email address here on the slide. That goes to just Josh and myself. It’s a great way for us to keep track of stuff. Please email that help email address instead of emailing us individually. That way if one of us is not available, the other one might be able to respond very quickly. So I tell people email is official and discussion is much more flexible and that’s why we like to use it in this course.
So how do you succeed in the system administration course? This course is notoriously difficult. I’m not gonna lie. System administration requires a growth mindset. I’m going to give you a lot of lab assignments. that are purposefully vague. It’s not meant to be vague, but it’s meant to represent what you’re going to get in industry. Thankfully, I give you pretty direct ideas of where I want you to go, but some of the lab assignments might say things like, set up an Active Directory, it needs to have this Active Directory domain and these users. What I don’t tell you is these steps to actually do that. However, you’re going to have a lot of videos where I’m going to walk through some of those steps, and there are tons and tons of links to documentation and discussions for how to do this. And so the real key to success in this class is having a growth mindset and understanding that I’m giving you the framework to work within, but you may have to do some of your own reading and your own research outside of my textbook to really figure things out. And so that’s why I tell people, don’t just read the content or watch the videos, but try and engage with it. Try and follow along as best you can. And especially on the lab assignments and on a lot of my pages, click the links. For example, on like lab assignment three, I tell you set up a DNS server, and then right below that are three or four links to the documentation that I read when I set up a DNS server. And so I’m really trying to point you at these other resources to show how people are going to do this in industry and what kind of resources are available. So please, please click the links that are available. In this class, there are something like 300 links to other content. It’s a pain in the butt every semester to go through and review those because the links constantly get changed but I do the best I can to keep them up to date. If you find a broken link, let me know. You can get some bug bounty points for that.
Other big thing I tell you in this class is to work iteratively and save early and often. Try and do a little bit of a lab at a time. Don’t try and do like all five things at once. Try and pick one task and get it mostly working before we move on to the next one. And take advantage of the fact that the virtual machine software we’re using, VMware allows you to make snapshots. For any of you that play video games, it’s like a quick save. Anytime you think you’re going to do something that might break, you might wanna make a snapshot. before you do that. Especially when you get to some of the later labs, every semester it happens at least once. I have somebody that sets up a computer and then either sets up an LDAP server or an Active Directory server and the setup fails. Sometimes it fails through no fault of your own, it just happens. And then they ask me how to fix it. And I tell them, unless you have a snapshot, the only way to fix it is to wipe your machine, reinstall the operating system and try again. And usually they only do that once and then they remember to make a snapshot. But I’m warning you now, that happens every semester. So make snapshots early, make snapshots often and especially make snapshots when I tell you to in the labs.
And then the other big thing to be successful in this class is to ask for help. This class is not designed for anybody to be able to breeze right through it without asking for help. That’s totally an intent of this course. Is I… I definitely know that almost everybody’s gonna get stuck. Something’s gonna be vague. You’re gonna misinterpret something, something won’t work right, whatever. It’s really, really easy to run into problems like that. And I see students all the time that spend six or seven hours trying to solve a problem that turns out that they don’t have the capability to solve or it may not even be solvable. And so I really hate seeing students do that and then they get discouraged and frustrated with the course. I don’t want that. And so instead what I tell you to do is if you’ve been stuck on a problem or you’re not making any forward progress for about a half hour on whatever task you’re working on, that’s a great time to stop and ask for help. You should be able to constantly make forward progress. You may take a few steps back at times, but if you’re stuck debugging a problem and you haven’t figured it out for a half hour or so, take a step away, ask for help, get on our office hours list, post an ed discussion, whatever, and just kind of step away and let it sit for a while. Sometimes you’ll figure it out on your own. Sometimes we’ll figure it out when we get to you. But the worst thing you can do is sit there and be frustrated and trying to just continually spin your wheels and solve a problem. That doesn’t really work in this class. So don’t be afraid to ask for help. That’s why I’m here. That’s why Josh is here. Anybody that’s ever taken this course will tell you that the best thing you can do is take a break and ask for help. I’m usually very willing to sit down and help and solve problems, answer questions, anything that you need to be successful.
So I talked a lot about the lab grading already, but just as a quick reminder, schedule on Calendly. Check Josh’s schedule first. I want you to schedule with him if at all possible. I’m kind of the backup person to schedule grading. And then we’ll set up a Zoom. The other big thing to remember is generally our Calendly calendars require you to schedule four hours in advance. So don’t look at my calendar at three o ‘clock on a Friday expecting to find that four o ‘clock slot open because it does not allow you to schedule times within four hours. Also, the four o ‘clock slot on Friday is almost always taken early in the week because somebody got there on Monday to schedule that time on Friday. So. The other big thing to be clear about lab grading, you need to not only schedule your grading time, but your grading time needs to happen before the due date. In years past, I’ve had people schedule a time on Friday for some time next Tuesday and think that that’s allowed. But no, the grading meeting, the appointment has to happen before the due date. So you really have to think ahead on this. The last thing on the lab grading is once you have started the grading process, and generally Josh and I will both ask you to confirm, are you ready to start? Do you have any questions before we begin? As soon as you start the lab grading process, you cannot make any changes to your lab. If we see something is wrong, even if you immediately notice that it’s wrong and try and fix it, it will be counted wrong. We have to kind of freeze your lab where it is when you start the grading process. So just be aware of that.
I also talked about the discussions a little bit. I’m gonna be sending out a survey here in the next few days that we’ll try and figure out what time of the week works best for everybody. Once I get at least a plurality of times that are available. We’ll schedule it online via Zoom. I’ll start getting people on the schedule itself. For the discussions, the way this works is you’re going to submit some questions before the discussion starts. And then during the discussion, you can either participate in the discussion by asking some of your questions or you can write a response afterwards. There is a little module in Canvas that explains all this, but it’s pretty easy to do.
So that’s really all I’ve got this week. This is probably gonna be the longest announcement video that you’re gonna get throughout the semester. I’ll try and do these, like I said, about every week, every other week or so, just to let you know what’s on my mind or if there’s anything going on. As of right now, modules one through four are posted and tested. The other big thing with the modules in this class is I have a couple of disclaimers in there. The version of this class you’re going through was originally written for Windows 10 and Ubuntu 20. Obviously those are old at this point. And so I’m redoing everything for Windows 11 and Ubuntu 24, all of the labs have been tested with those versions of software. Not all of the videos are going to get recorded this time. And so a lot of the older videos are perfectly applicable. It all works or it’s very similar in the current systems. But if you see a video that looks like completely out of whack and wrong, let me know, I’ll put it in as a bug bounty. I may rerecord some quick videos if I need to go through and fix anything. But just be aware that a lot of the documentation and a lot of the textbook is gonna refer to Ubuntu 20 and Windows 10, it may even refer to Ubuntu 18 in a few places. We’re gonna be using the latest and greatest in Windows 11 and Ubuntu 24. So just be aware of that.
So throughout the semester, if you wanna keep in touch, we’ve got a discussion that’s a great place to chat with me there. I’m also on the Discord server and on Microsoft Teams and I will chat with you there as well. Email is always available, the CIS 527 help address is there. The other things you can do every Mondays, I host Tea Time Office Hours with David and Virgo in the computer science department. It’s available via Zoom, it’s also available in person. I believe we’re gonna be in one of the classrooms this year. I think we’re in 11, 17, but I’m not sure. Those are Monday afternoons at one o ‘clock so you can come join us there and hang out. Or you can schedule one or more office hours either with myself or with Josh anytime you need help in this class. So feel free to keep in touch. Other than that, good luck this semester. I hope everything goes well and I look forward to seeing you again in a couple weeks on the next announcements video. Good luck.
Hello and welcome to the Week 2 Announcements video for CIS 527 and CC510 in Fall 2024. So this week you should be getting ready to have your first lab grading scheduled. So what you need to do to get your labs graded is schedule a time slot to meet with either Josh or myself. Sometime via Zoom before that lab is due. Remember not only do you have to schedule your grading time but the grade time has to happen before the deadline. We have some students that are unclear that they just have to schedule the lab grading and then they can get it graded after the deadline. The grading actually has to happen before the deadline.
So when you schedule your time slot you’ll go to the home page on Canvas. You’ll scroll down a little bit and you’ll find the instructions for this. What I’d like you to do is check Josh’s calendar first and schedule a time with Josh if he’s available during a time you’re available. If his calendar is full or any of his times don’t work for you then you can schedule with me. We just do that so that Josh’s time gets used up most efficiently and then you can take up my time as needed. When you schedule our meetings by default are only 15 minutes long so we kind of depend on you to come prepared. And so that means that you should have everything ready to go have your VMs both booted have everything pulled up. You can even look at the lab a little bit and figure out what things we’re going to want to look at. There’s some lab grading checklists out there. So do the best you can have everything ready to go so that we can just click through it. If everything is ready it should only take a few minutes to grade. But if you have trouble or you don’t have your lab started up sometimes that can take a long time.
But basically be prepared to demonstrate your work. We will ask you to show us things that you did in the lab. We may not exactly tell you how to do them. So you need to be prepared to demonstrate your work and your understanding. So if we ask you to show us where all the users are at and prove to us that you created the users you’re supposed to. You should be able to find a place where you can show us that and prove that some of the times we will just give you some commands. For example on Linux we may just give you some terminal commands to check things just because that’s a lot quicker. So we’ll work with you on that. If you have any questions or concerns about the lab grading let us know. pretty straightforward, but you just have to kind of try it once and you’ll see what it looks like.
So for the discussions, I sent out a when to meet poll on the announcements earlier last week. So please check that out and fill that out if you can. I’ll try and get the discussion scheduled later this week. And then the full schedule of speakers is coming soon. We’ll try and have our first discussion here in early September. I try to get between three to five guest speakers each semester. So the schedule will be coming very soon. Remember for the discussions to get full credit for those, you need to submit two questions on Canvas before the discussion starts. And then you can either attend the live discussion session on Zoom or you can watch the video afterward and write a small response to that video just to show that you watched it. And then outside of that, whenever we don’t have a guest speaker, we’ll use that discussion time as live office hours where I will hang out in Zoom for a little while if you have any questions there.
So, as a quick reminder in this class, you can get help a couple of ways. One of the best things to do is email the cis527-help email address. That email goes to both myself and Josh so that either of us can answer that email very quickly. If you email one or the other of us directly and we’re busy, it may take a little bit longer to get an answer. So, please remember to use that help email if you can. Another great place to ask for help is a discussion. Josh and I have both been very active on the discussion answering questions there. So, please check that out. And then if you need to meet with us one -on -one for office hours, we have Calendly links available for office hours and grading. So, you can always use Calendly. Hopefully, everything’s going well this semester. We’ve kind of made the change from Windows 10 and Ubuntu 22 to Windows 11 and Ubuntu 24. I think that’s been mostly a smooth transition so far, but there are some little questions coming in. So, if you’re running the issues, check ed discussion, see if we’ve talked about your issues before. And if not, feel free to make a post there and we’ll try and answer it. Josh and I are on top of things. We’ve got our model solutions ready to go so we can check things out if you run into something strange. But otherwise, hopefully lab grading this week goes well and let us know if you have any questions. Otherwise, I will see you in another announcements video next week. Good luck.
Hello and welcome to the week three announcements video for CIS 527 and CC 510 in fall 2024. So this week lab one is due tomorrow on Wednesday by 7 p .m. so make sure you’re working on getting that completed and don’t forget to schedule a grading time either with myself or with Josh to get that graded. I know my calendar is pretty limited today and tomorrow because of a lot of meetings and I’m on campus tomorrow due to the Labor Day holiday so if you have trouble finding a grading time let us know and we’ll work with you on that. Generally for the first lab I’m pretty lenient on late penalties as long as you get a grading time scheduled before it’s due and if we have trouble with that let us know. I’m also working with Josh that we may adjust the day of the week that labs are due just to better fit our schedule. It seems like a lot of my meetings tend to have been on the first part of the week so we may move the due dates a little bit just to make more room for that. So make sure you’re getting lab one done. The quizzes for module two are due next week so make sure you’re getting those started and our first discussion prompt is actually on next week on Wednesday September 11th. We’ll talk about that in just a second and then September the 18th is when lab two is due.
So the discussion sessions I sent out a quick announcement those are going to be Wednesdays from 2 .30 to 3 .30 not this week starting next week on September 11th because of this week I’m on campus on Wednesday. Normally we’ll just do office hours during those but three to five times throughout the semester I’m going to bring in a guest speaker to talk with us. Our first speaker is on September 11th and I’ll be posting information about that guest speaker and it’ll give you a chance to actually write some questions to ask our guest speaker. I’ll probably announce his name in next week’s video but it’s going to be Kyle Hutson so I’m going to get some information from Kyle and I will post that out in an announcement so you can write some questions for Kyle and have those submitted before our discussion session.
So after this week you’re going to start working on lab two. Lab two is basically a redo of lab one but this time instead of manually installing everything and setting it up you’re going to script it using a scripting tool called puppet. Puppet along with Ansible and Chef and SaltStack and some of these other tools are really great for defining a configuration in code and then applying it to an operating system. So what you’ll do for Lab2 is you’ll create two brand new VMs. You’re not going to reuse your VMs from Lab1. You’ll reinstall the operating system, you’ll install Puppet and Updates, and then as soon as you get Puppet installed, you’ll make a snapshot. And then what you’ll do is you’ll write a Puppet manifest file, you’ll test it on your VM, and then you’ll roll back to that snapshot and try it again. Make sure you keep in mind where your manifest file is. If you’ve been working in your VM with your manifest, make sure you copy it out of your VM before you roll back to your snapshot. Every year I have somebody lose a Puppet manifest file because they rolled back a snapshot and it disappears. So make sure you’re careful there. The other big thing with Puppet manifests is keep it simple. Try and use the Puppet resource command that I show you in several of the labs to query information. And it only sets the things that you care about. For example, if you use Puppet resource to query a user, you might get 30 or 40 things. Most of those are defaults you don’t need to set. you only need to grab the few things that actually need to be set when you’re defining that resource. So you don’t have to be exhaustive about defining these. And so because of that, a model solution for this is less than 200 lines of code each. The other thing to be clear about this, you can make two separate manifest files, one for Ubuntu and one for Windows. You don’t have to make a combined manifest. You totally can if you want, but most students choose to do separate manifest files. So make sure you read those pretty closely. And I’ve got some tips and tricks as well. So hopefully you can get through lab two.
All right, other big thing in this class, I really want you to come at this class with a growth mindset. This is a 500 level technical course. And because of that, it requires you as a student to be up to the challenge and be willing to come at it with a growth mindset. And so what I want you to kind of keep in mind is the labs that I set in this class are meant to be challenging. They are meant to be things that you’ve never done before. And specifically a lot of the labs, I do not give you all of the instructions to do the labs. Especially in system administration, if I give you all of the instructions to do, then this entire class just becomes following along with the things I tell you to click on. There’s no learning that happens. And so I set these challenging labs and then it’s up to you to read the documentation, go through my videos and things and understand what I’m asking you to do and then do that action yourself. So it requires you to grow and change a little bit as a student, as you’re learning how to do these things. I’m not just going to tell you how to do things. If you are stuck, however, feel free to ask for clarification. I’ve told several students that I do not expect anybody to pass this class without asking a question at least once. Unless you have a background in system administration, it is very likely I’m going to say something that you don’t understand. And so that’s a chance to come to me or to Josh and ask for clarification. The other big thing on these labs that I will tell you helps a lot is to start early and work methodically. I heard from a lot of students over the weekend that just started working on the labs on Saturday and Sunday and that’s going to make it really difficult to succeed in this class if you start the weekend. before the labs are due. So start early, work methodically, try and work a little bit every day. And of course, the big thing is make snapshots. If you play video games, you can understand the quality of having a lot of auto saves. Feel free to do the same thing with your snapshots. If you run out of disk space, don’t forget, you can go back and delete older snapshots that you’re not gonna roll back to. That will help save some disk space on your system. So hopefully that helps.
Other than that, feel free to keep in touch. We’ve got great discussions on EdSTEM. I’ve got office hours. I’m available on Zoom anytime. I’m also available via email and on Teams and on Discord. So lots of opportunities to get help. So feel free to reach out and keep in touch. If you do chat with me on either Teams or Discord, feel free to just at me so that I see the notification pop up. That way I actually see it quickly and can get to you. So, other than that, hopefully you’re looking forward to doing Lab 2. I know it feels like you’re having to do Lab 1 again, but that’s really what we kind of want to get across in this lab, is that you can automate a lot of the things that we used to do manually in system administration, and so that’s what we’re going to play with. Hopefully Lab 2 goes well. If you have any questions, let me know. Otherwise, good luck, and I will see you again next week.
Hello and welcome to the week four announcements video for CIS 527 and CC 510 in fall 2024. So this week you should be working on the discussion questions for our first discussion this Wednesday, which will be hosted by Kyle Hutson. I’ll talk about him in just a second. Those questions are due about an hour before the session starts so that I can go through them, but you’re invited to attend live in person so you can see his presentation and ask him questions via Zoom and get your response points there as well. Next week lab two is due on Wednesday so make sure you’re working on lab two to get that done soon and then next Wednesday the response for discussion one is also going to be due.
So for lab two to clarify really quick lab two grading is done on canvas only. All you have to do is submit your puppet manifest files. You’ll probably submit one or two files. Most students will submit two files, one for Ubuntu and one for Windows. You can combine them in the one file if you want, but you don’t have to. You’ll just submit your manifest files via canvas and then we will go through and we will grade those offline by running them on RBMs to make sure that they work. If you want to move ahead to lab three and you are done with lab two, you can email us and I will put in a one point score until we get the grading updated. That will unlock lab three, but it also unlocks the model solutions for lab two. So be aware that once we put that point in and unlock the model solutions, you can’t go back and work on lab two again. But if you want to move ahead, just let us know. We’re happy to do that. But for lab two, you just have to submit stuff on canvas. You don’t have to schedule a Zoom meeting unless you have any questions.
So our first discussion is coming up tomorrow on Wednesday at two thirty. Our speaker this time is going to be Kyle Hutson. Kyle Hutson currently works at Lambda Labs, which is a big provider of GPU compute in the cloud for AI. He previously worked at KANREN, which is the Internet service provider for research organizations across Kansas, including K-State. Before that, he was a Beocat system admin for many, many years and got to be a really good friend with Kyle when he was here on campus working with Beocat. But now he works for Lambda Labs. He’s going to be able to talk all about. performance computing and some of the stuff that he did both at Canren and at Lambda and that discussion again is on Wednesday at 2 30. It’s in the Zoom room that we have for office hours. The Zoom information is posted on the homepage of Canvas.
To get points for this, there are two things you need to do. The first thing you need to do is submit a couple of questions you’d like to ask Kyle before he presents on Wednesday. So you can look him up, you can go to Lambda Labs, you can find Kyle Hutson on LinkedIn, you can look at KANREN and Beocat to learn more about his history and see if there are a couple of questions you come up with that you want to ask him. Then you can either attend the live session Wednesday at 2 30 and participate by asking at least one question to get your participation points or afterwards you can watch the video and then write a short response to respond to a couple of prompts that I will have based on our discussion with Kyle. You respond to the prompts mainly just to show that you watched the video and understood what Kyle was talking about. Those are your two ways to get points for these discussions so make sure you keep that in mind. The questions are due tomorrow about an hour before the session starts. And then the response is due a week after that, next Wednesday.
That’s really all we’ve got going on this week. If you have any questions, you can keep in touch on Ed discussion. You can also keep in touch on Discord or Teams. You can join me for Tea Time office hours every Monday. We hold that every Monday at one o ‘clock in 11, 17 on campus or on Zoom. Or you can also schedule one -on -one office hours with either myself or Josh. We’re always here to help. Hopefully everything’s going well in lab two. If you have any questions, let us know. Otherwise, I will see you next week.
Hello, and welcome to the week five announcements video for CIS 527 and CC 510 in fall 2024. This week, you should be working on lab two, which is due today. We’ll talk about that momentarily. You also should be working on your response to the first discussion we had last Wednesday with Kyle Hudson. That response is due today, so make sure you get that submitted on Canvas. Then you’ll start in on lab three. So the quizzes for lab three are due next week. And then you’ll have the second discussion questions are due next Wednesday. And then in two weeks, you’ll be turning in lab three and your second discussion.
So for lab two, all you have to do is submit your two puppet manifest files via Canvas. You don’t have to schedule a meeting with myself or Josh unless you have any questions about your submission. Once you get your stuff submitted, we’ll probably go in tomorrow and enter a grade of one for everybody that has submitted the labs so that it will unlock lab three so you can get started on it. That will unlock the model solutions for lab two as well. And so that’s why we wait until you’ve submitted it and we put in a grade so that it will unlock the next lab. So no meeting is required for lab two. If you have any questions, feel free to post on that discussion or send us an email and we’d be happy to help.
So next Wednesday, our second discussion will be Seth Galitzer. Seth Galitzer is a name you’ve hopefully seen before. He is our computer support person for computer science. He runs all of our research servers. He runs the CS Linux server that you probably interacted with and has a lot of experience doing both desktop and server support at K -State. So we’re going to have that talk with him, not this Wednesday, but next Wednesday at 2:30 p.m. in our office hours Zoom room. So make sure you think of some questions you wanna ask Seth so that you get those published on Canvas by next week. So we’ve got some questions to ask Seth when he is here.
So next week, you’re gonna start working on lab three. Lab three involves core networking services such as DNS, DHCP, SNMP, Wireshark, all of these cool network tools. It’s purely done mostly in Ubuntu. You don’t do much in Windows on this lab except maybe test a couple of things in Windows. So the big thing with lab three is you’re gonna want to read the documentation for all of these tools very carefully and make sure you understand them. There’s a lot of hints and diagrams out there that you can look at. And of course, as always, ask questions. One of the big keys of this class is I don’t give you all of the answers right away. I expect you to come to me and ask questions if something doesn’t make sense. So don’t be afraid to reach out and ask questions and learn from that discussion as well.
So that’s really all I’ve got this week. As always, you can keep in touch by posting an Ed discussion on Discord or Teams by coming to Tea Time Office Hours, which are Mondays at one o ‘clock, and then by scheduling one -on -one office hours with either Josh or I anytime that you need help via Calendly. So hopefully you’re really excited about getting into networking this week. I think it’s one of the most interesting topics we cover in this class, and it’s definitely one that you probably haven’t done a lot with in the past unless you have some server experience. So hopefully this is a really interesting lab for you. As always, if you have any questions, let us know, and I will see you again next week.
Hello and welcome to the week six announcements video for CIS 527 and CC510 in fall 2024. This week we have our second discussion session hosted on Wednesday, so we’ll talk about that in just a minute. Next Wednesday the response for that discussion is due and the questions for that discussion are due this Wednesday right before we start. And then also next Wednesday lab three is due as well. So for lab three, which you should be working on this week is adding some core network services to our Ubuntu VMs. You’re going to set static IP addresses. You’re going to install a DNS server and a DHCP server. You’re also going to install SNMP so that you can view some of your network statistics across the network. You’ll also install Wireshark and use that to capture some packets. All of this is really useful stuff to understand how networking services work.
Some big hints for lab three are to look at the hints and diagrams that I have, especially at the end of the textbook. There’s a lot of good hints there. And when all else fails, I encourage you to ask questions. Definitely one thing I’m seeing in this class is a lot of students are starting the lab assignments the day it’s due or the day before it’s due. And then they’re running in the questions and it takes a little time back and forth to get those questions answered. It’s much, much easier if you start these labs a bit early so that if you do run into problems or get frustrated, you can take a break, you can ask questions, you can come back to it when you’ve got a fresh mind. That’s really one of the big things to do in this class is take advantage of the fact that you have a full two week period to work on these labs and try and work on them a little bit at a time instead of trying to run it all in one shot.
So as a quick reminder for lab three, we’re going to do live grading again this time. So you’ll need to schedule a time to meet with either Josh or I to get lab three graded. As before, please check Josh’s calendar first. He’s most likely to have the most available time and be able to meet with you next week to get the lab graded. If he’s not available or his times don’t work for you, check my calendar and schedule some time with me. As a fair warning, I’m usually very busy Mondays and Tuesdays. So it’s hard to get time on my calendar those days. My calendar opens up later in the week, but it does mean that it’s after the deadline for lab three. So just be aware of that. When we do grading for lab three, we’re gonna ask you to show us several things. We wanna see that you can do remote connections using RDP to connect to your Windows machine, using SSH to connect to one of your Ubuntu machines. You should be able to show that you have a static IP on your Ubuntu VM labeled server. To be clear about that, you don’t have to install the server version of Ubuntu on that VM. You can use the desktop version just like we’ve been using, but you should name it as a server so that we’re gonna treat it like that. You should be able to show your DNS server settings and we’ll have you run some commands to do some DNS lookups to make sure your DNS server is working. We’ll check your DHCP settings, and we’ll also check to make sure your VMs are getting DHCP addresses from your DHCP server. And then we’ll also look for some screenshots of your SNMP process and your Wireshark process as well. You don’t have to show us those. You should be able to just show us the screenshots of those things, and then we’ll look at your screenshots real quick and make sure that they show exactly what we’re looking for.
All right. So after that we’re going to switch to Lab 4. Lab 4 is notoriously one of the more difficult labs in this class because you start working with Windows Server. And so in Lab 4 you’re going to set up a VM for Windows Server. For those of you that are working on Apple Silicon Max, you’ll want to do this in Azure. And I’ll be posting some videos later this week or early next week to show the process of doing this in Azure. For those of you that don’t have Apple Silicon Max, but if you want to play around with Azure, you can definitely do this in Azure. Just make sure that you have your student credits available in Azure. And if not, let me know. And we’re trying to figure out a way to renew those credits. So I’m working on that, but hopefully that should work for everybody. What we’re going to do on Windows is we’re going to set up an Active Directory server so that we can use that. That’s kind of the default standard for doing this shared logins on Windows. On Ubuntu we’re going to set up an OpenLDAP server. We’re going to configure clients to connect to those. And we also do one example of interoperability where we’re actually going to add an Ubuntu VM into our Windows Active Directory to show how that works. As with all of these labs, it’s really, really important that you make snapshots early and make snapshots often, especially when you’re doing the Active Directory and OpenLDAP installation part. If either of those fail, it’s really hard to undo them and try again. It’s much, much better to just roll back to a snapshot and try again. So make sure you make ample use of snapshots if you can as you’re going through that process.
So again, to be successful in this class, you really need to read the labs carefully. Take a look at all the post -it hints and resources. A lot of times in the lab assignments, if I ask you to do something and then below that I have a few links to resources, those are the documentation resources I read when I have to do this. And so it gives you a good idea of what I think is valuable resource versus just going out to Google and taking the first result that you find. I’ve tried to curate a list of resources that I find to be particularly useful and helpful for setting these up. But of course, things may not make sense. So if you get stuck, ask questions, if I can clarify something, if I can give you a little bit more direct hint, I’m happy to do that. You just have to ask some questions. The other big thing I’d students to do in this class is don’t spin your wheels. If you feel like you’re working on a project and you haven’t gotten anywhere in about a half hour or so, like if you just run up against a wall and you’re not making any progress, don’t sit there and spin your wheels for four or five hours. I always hate to hear that students have spent like five hours trying to debug a problem and then they email me and it’s a very simple fix that I can help them with. Don’t waste that five hours getting frustrated and spinning your wheels trying to solve a problem. It is totally possible in this class for you to come up against a problem that I’ve never seen before and it’s very difficult to debug. I would say every semester I have at least two or three students come up with a problem that is brand new that I’ve never seen before that we sometimes have to spend some time debugging if we can or we try and come up with a workaround. So it’s part of just working in a system administration class is we’re always going to get weird stuff. So if you get stuck, don’t spin your wheels, ask us questions. We’re more than happy to help you get unstuck. And I’d much rather do that than hear that a student gets frustrated trying to solve an area that they can’t even solve. So just be aware of that that is totally possible for those things to happen and we’re here to help.
So our speaker this week is Seth Galitzer. Seth is going to join us Wednesday at 2:30 for our discussion time. Seth Galitzer is the computer science support person. He works on all of our computer systems in computer science. He maintains our research systems, our servers, our desktop clients. He maintains everything for all of our department to function. He’s been doing that role for several years at this point. And so I really value Seth’s opinion and advice on things. So I’m really looking forward to have Seth come in and talk about his background and his experience as a computer support person. And again, that’s this Wednesday at 2 .30. Make sure you go in and write a couple of questions that you’d like to ask Seth and submit those to get your points for the discussion questions. And then you can either attend the live session and ask him a question to get your response points or you can watch the video afterwards, write a quick response and submit it. I’ll try and get that posted usually within an hour at the end of the meeting on Wednesday.
So that’s all I’ve got for today. Please feel free to keep in touch on Ed discussion, discord, teams, tea time, office hours. One other thing I wanted to mention in this class is I’ve gotten a lot of responses from the start -top stop continue survey to hold more office hours for this class. It’s really difficult to do that because of the asynchronous nature of this class. We don’t have a dedicated time where a lot of students are available and the few times in the past where I have held office hours. For example, I did office hours last Wednesday. We had one student drop in. And so it’s really difficult to do scheduled office hours for a class like this, which is why we have one -on -one office hours available all the time. Both Josh and I have a calendly setup that has all of our times available. So anytime you have a question and want to actually meet with us one -on -one, you can schedule a time on office hours. You can post on ed discussion. You can post on teams. We’re readily available to help you. And I find that that’s a much better use of our time than having these scheduled office hours. that nobody is able to show up for because it doesn’t match their schedule. So just keep that in mind. Likewise, if you’re working full -time and you wanna meet with me after hours, just email me and let me know. I’m available after hours. I just don’t have that available on my calendly because let’s face it, if I made those hours available, they would always get booked up and it would be hard for me to have a life outside of school. So I don’t make those openly available, but I do have times available in the evenings if you email me and ask for those. So that’s all I’ve got. I hope you don’t find this lab too frustrating. I know that labs three and four can be some of the more difficult labs in this class. I kind of front load some of the difficulty just to get over the hump and then you can get to some of the fun stuff toward the end of the semester. So as always, if you have any questions, let us know and I will see you again next week.
Hello and welcome to the week seven announcements video for CIS 527 and CC 510 in fall 2024. This week you should be working on the response to our second discussion with Seth Galliser. Those responses are due today, so make sure you get those posted. And then this Friday, lab three is due. Hopefully you saw the announcement earlier that I have moved all of the lab deadlines to Friday. That seems to work better for Josh and I and our schedule. We have a lot more time for grading on Wednesday, Thursday, Friday. Please bear in mind, you can go ahead and schedule your grading time right now as long as you know you’re going to have your lab done before that deadline. So if you want to reserve your time on Friday, go ahead and get it scheduled and we will take care of that. But just bear in mind that labs are now due on Fridays and then for the times when that conflicts I’ve moved things around. So just check the deadlines in Canvas because those are the accurate timelines for all of this.
So for lab three, you should be working on setting up core networking services on your servers. Most of this is done on a single Ubuntu VM with a Windows and Ubuntu client VM for some testing. You’re going to set a static IP address on your Ubuntu server. You’re going to install DNS and DHCP, install SNMP. You’re going to configure remote access on a couple of machines. Feel free to ask questions. I’m constantly fielding questions from students both in ed discussion via email and on Discord. I have a mega thread on ed discussion where I’m trying to consolidate all of the information that I get from all the different students I chat with. So feel free to check that out if you have any questions that might have a frequently asked question there that can answer some of your problems. But as always, don’t be afraid to ask questions or let us know either meet with Josh or I and we can help you out.
So for grading on lab three, the big things we’re going to ask you to do are demonstrate your remote connections. So be prepared to show that you can use remote desktop from one of your Ubuntu clients into the Windows machine using Remina. Also be able to show that you can use SSH from either Windows or Linux to get into your Ubuntu server. You should know what those commands are and how to use them. Make sure you can show us your static IP is set on your Ubuntu server. So you’ll just go into the. of the settings there. Be prepared to show us your DNS server settings. We’re gonna ask you to look at all those config files that you created and then we’ll have you run a few DIG commands to do some lookups. So make sure you’re comfortable with that. We’ll also check your DHCP settings and we’ll check to make sure that your clients are getting DHCP addresses from your DHCP server. For the SNMP part and the Wireshark part, we’re just gonna grade your screenshots. So make sure you have screenshots of the SNMP activity that we have you do and have screenshots of the eight different Wireshark packets that we have you capture and make sure it’s really clear in those screenshots that you found the thing that we’re looking for. Really, for a lot of this grading, I expect you, if everything goes well, to know how things work and you should be able to do these pretty quickly, we’ll be prepared to prompt you if you’re unsure. But let us know if you have any questions or concerns and we’ll work with you from there.
So for lab four, you’re going to create a Windows Server VM, and we’re going to set up Active Directory and open LDAP and configure the clients to work with those. We’re also going to configure one instance of interoperability, where we’ll have an Ubuntu client login to Active Directory, which is really cool. The big thing for this lab is to make snapshots as often as you can, especially when installing the Active Directory part of Windows Server, and when configuring the LDAP on Ubuntu, especially the security certificates, those tend to cause a lot of problems with students. So having a snapshot where you can roll back and try again is always helpful. For the few students that are going to do this in Azure, I’m going to get those videos hopefully posted in the next couple of days that give some basic ideas of how to set up virtual machines in Azure. If you want to work in Azure, you’re welcome to. It does work really well for this. I was able to do the Windows parts of lab four in Azure pretty easily, so just be aware of that. But lab four is probably the more difficult lab. It’s one of those that it either works or it doesn’t, and so grading this lab is actually really simple. It either works or doesn’t, but there’s a lot of different gotchas and things that you could run into to get lab four working. Most students in the past have said that lab four is probably the most difficult. It’s kind of tied between lab three and lab four, so just be aware of that. Start early, ask questions, let us know if you have trouble.
So as always, I’ve said in this class, the big key to success is reading the labs carefully, looking at the posted hints and discussions. I’m always willing to give hints and pointers and help debug stuff. It’s not that I’m going to tell you, oh, I don’t know what the error is. I will help you. You just have to reach out and ask. Use the resources that are available. And the big thing I tell students is don’t spin your wheels. If you’ve been debugging a problem for 20, 30 minutes, you haven’t made any progress and you’re not figuring anything out, that’s a good time to take a step back, relax, ask us a question, send us some screenshots, and we’ll help you figure it out.
So that’s really all I’ve got for this week. As always, feel free to keep in touch. We’ve got a great discussion going on. discussion. I’m on Discord. I’m on Teams. I’ve got office hours today for this class from 2 .30 to 3 .30. I have tea time office hours on Mondays if you want to chat about other stuff. And then, of course, you can always schedule a one -on -one time with either Josh or I, and we’d be happy to help you out. So best of luck as you wrap up Lab 3 and get started on Lab 4. If you have any questions, let us know, and I will see you again next week.
Hello and welcome to the week 8 announcements video for CIS 527 and CC 510 in fall 2024. So coming up we’re working on lab 4 so by next Monday you should have the quizzes done for lab 4 and then by next Friday you’ll be turning in lab 4 itself. This really this couple of weeks this is probably the hardest part of this class I know a lot of students struggle with getting lab 4 up and running not necessarily because it’s difficult but because there’s a lot of bits and pieces to deal with and there’s a lot of dependencies that you have to work around as well. So those are all things to keep in mind.
So like you’ve seen before lab 4 involves creating a Windows Server virtual machine and installing Active Directory on it. We’re also going to install the open LDAP server on our Ubuntu system. We’re going to configure clients to log in through those systems so we’ll configure Ubuntu to log in through LDAP and we’ll configure both a Windows and an Ubuntu to log in via Active Directory. That’s really all it is. One thing I definitely will tell you to do is make snapshots in this lab especially before you configure Active Directory on Windows and before you configure open LDAP and the TLS part of open LDAP on Ubuntu. Those are two steps that might cause you issues and so having a snapshot you can roll back to is really really useful.
So for the lab 4 setup there are a couple of different ways you can do lab 4. I have a document in the textbook that describes this but there’s basically three options. If you have a working lab 3 solution and you want to keep working on it you can continue to use the lab 3 DNS and DHCP server and it should work well for all of this. The only thing you really have to do on lab 4 is on the Windows client you have to set a separate static DNS address to point to the Windows server. If your DHCP is not working but you want to use your DNS you can use your DNS server from lab 3 as static DNS entries or the third option and this is usually what I recommend if you’re not so sure about your lab 3 setup is to set up manual hosts file entries. I’m gonna try and record a video for that later today or tomorrow and post that out there so you can see what I mean when I talk about that setup but there’s really three different ways that you can set up lab 4. so that the Active Directory and OpenLDAP parts will actually work correctly.
So for grading on Lab 4, this lab is actually really easy to grade. It either works or it doesn’t for the most part. So we’re gonna check that your Windows Server is installed, that you have a user and a group in your Active Directory, and then we’ll double check to make sure your Windows client can log in using your Active Directory. On the Ubuntu side, we’re gonna check that you have OpenLDAP installed. We’re gonna look at the LDAP account manager to make sure there’s a user and a group configured there. And then you should have an Ubuntu client that logs in via LDAP and an Ubuntu client that also can log in via the Active Directory. Those may be the same client with two different snapshots. Either way you wanna do that is fine. But most of the point of this lab is if your clients can log in via the appropriate AD or LDAP server, that’s what we’re looking for and you’ll get the points for this lab.
So that’s really all I’ve got going on this week. So as always, there’s gonna be a mega thread on ed discussion if you have any questions there. You can ping me on Discord and Teams. You can come to Office Hours. I’m really here to help. I’m also going to be trying to schedule a couple more discussion sessions over the next month. So be on the lookout for that as I get those schedules posted. I just need to hear back from a couple of speakers to see what days work best for them. We’re going to try and get at least two more, maybe three more scheduled this semester, depending on if the scheduling works out for everybody. So we’re at the halfway mark of the semester. This is week eight. Hopefully things are going well. For most students, they point at lab four is one of the more difficult labs in this class. After this, we’re going to switch gears a little bit and do some other stuff. So hopefully everything goes well with this lab. But as always, if you have any questions, let us know. And I will see you again next week.
Hello and welcome to the week nine announcements video for CIS 527 and CC 510 in fall 2024. I’m coming to you this week from my office on campus because I’m on the road a little bit. Hopefully the video quality is not too bad and you can get everything that I need to get across in these announcements. So for this week you should be working on lab four. Lab four is due this Friday so make sure that you’re getting that done and have your grading time scheduled. Right now I have a lot of availability on Friday and I believe Josh should also have availability toward the end of the week so hopefully you can get your grading time scheduled. If you’re having any questions or issues with the lab let us know and we’ll definitely work with you on that and then next week you’ll transition over and start working on lab five.
So for lab four the grading for lab four is actually really straightforward it kind of just works or it doesn’t. What we’re going to look at is that you’ve installed a Windows Server and configured that with an Active Directory that has a user and a group in it as directed and then you should configure a Windows client to log in using that Active Directory. On the Ubuntu side of things you should on your Ubuntu server install OpenLDAP and have it configured with the user and group through the LDAP account manager and then you should have an Ubuntu client logs in via LDAP and then another Ubuntu client which could be either a different VM or a different snapshot of the same VM that then logs in via Active Directory. That’s what we’re looking for for lab four. Generally if it works we just check that your server has AD you show us that you’re logged in check that OpenLDAP is running and show us that you’ve logged in on both Ubuntu’s that’s really all it takes. If everything is configured and running takes less than five minutes if you’re having issues with it then we’ll have to dig in a little bit and figure out exactly what’s working and what doesn’t so we can at least get you some partial credit. So as always success in this class involves reading the assignments carefully looking at the posted diagrams. I just posted a video last week showing some network setups for lab four including how to set things up in Azure so take a look at those videos and ask me if you have any questions. Use the resources that are available especially in the lab I usually link right below a task in the lab I link the resource that I use to do those tasks and finally if you get Don’t spin your wheels if something’s not working and you’re not sure stop and ask us a question Post on a discussion email us post on discord, whatever Josh And I will try and answer as soon as we can And it’s much easier to maybe get the right answer than to spin your wheels and try a whole bunch of things Especially unless you’re very careful and have a snapshot in VMware that you can roll back to in order to get things working again.
So for lab 5 coming up next week, we’re gonna move totally into the cloud for some of this class What I normally do with this class is build droplets in digital ocean I find the digital ocean is the easiest to use cloud platform for this We’ll set up SSH and firewall although we’ll need to make a couple of changes to that because campus is now blocking SSH So I’m working on getting that lab updated Then we’re gonna set up some simple Apache websites a DNS domain name And we’re also going to play a little bit with Docker instead of a Docker reverse proxy Notta Notta Notta So, Lab 5 is generally a little bit smaller than Lab 3 and 4. It’s much more straightforward. It’s working in the cloud, in DigitalOcean, in a couple of droplets. If you want to do Lab 5 on a different cloud provider such as AWS or Azure, you’re welcome to do that. I will just warn you that I don’t have as much experience with those platforms versus DigitalOcean where I host my own stuff and so I find it a little bit easier to debug and work on things in DigitalOcean versus those other platforms but really you can go any way you want.
For this lab you’ll need to set up a DigitalOcean account and you’ll also need to set up a domain name if you so choose. You can get all of this through the Education GitHub Pack. DigitalOcean also has a free trial offer that URL gets cut off but it’s try .digitalosion .com slash free trial offer or if you just google it. Likewise if you go to nc .me you can get a .me domain for $1. So both of those are really great. I also have credits that I can share on these and so if you want my referral link for either of these just let me know. I’m happy to share that with you. In total if you even have to pay for this out of pocket it should cost you about $11, a dollar for the domain name and $10 on DigitalOcean but most of this you should have more than enough free credits to do this. You can also use an existing domain name if you have one or contact me if you don’t want to set up your own domain name and I can set you up as a sub -site under the cis527 .org site that I own so that you can work with it from there.
That’s really all I’ve got for this week. I’ll spend a little bit more time next week talking more in depth about lab 5 but in the meantime if you have any questions keep in touch on id discussion on discord teams come to office hours and let us know how we can help. So next week we’re really going to start leaning into the cloud. I always remember this particular xkcd comic that talks about the cloud. We’ll get into this a little bit next week in my lectures but really the cloud is just a point of view it’s just somebody else’s system and so in theory the entire cloud could just be some server in somebody’s basement with a lot of caching. So I really like this xkcd comic it gets the idea across. So hopefully everything goes well this week. As always if you have any questions let us know and I will see you again next week.
Hello and welcome to the week 10 announcements video for CIS 527 and CC 510 in fall 2024. So this week you should get started on working on lab five, which is our first lab completely done in the cloud and DigitalOcean. That lab is going to be due next Friday by 5 p .m. So make sure you get that done and are scheduled to get that graded. We also have our next discussion session coming up, not this Wednesday, but next Wednesday, October 30th.
So make sure you take a look at that and start thinking of some questions for our guest speaker. For lab five, the grading that we’re looking at is basically your ability to connect to the front end either via SSH or via the cloud terminal that’s available on DigitalOcean. From front end, you should be able to SSH to back end by just typing SSH back end. That confirms that you’re using an SSH key and that you have an SSH config file that is working correctly. We’re going to check the firewall settings on both systems as well as the date and time being set correctly. On the back end, you’re going to have Apache set up and you’re going to have at least one virtual host running in Apache. We’ll check to make sure your DNS and HTTPS is working on that system. And then on the front end, you’re going to run a Docker reverse proxy of some kind and have two front end websites working there as well. Those won’t be using HTTPS because we’re using a reverse proxy that may not support HTTPS directly, but hopefully you can get that up and running and be able to show the CIS 527, Alpha, Bravo, and Charlie websites working on your domain name.
For next week, we also have a discussion coming up. We’ve got our speaker, Ethan Bergstrom. Ethan Bergstrom works at Oracle Health, previously Cerner, works in the IT department. He actually manages a lot of their cloud infrastructure for hosting their health system for small and medium hospitals across the country. He does a lot of stuff at this large scale of system administration, being on call, working on performance tuning, working on monitoring and maintenance of these large systems. He has a wealth of knowledge, and so I’m really excited to bring Ethan in to talk about what he does in the IT world. That talk is going to be… Wednesday, October 30th at 2 .30 PM. I’ve posted a little bit of his bio and also a link to his LinkedIn on Canvas so you can learn a little bit more about Ethan and his background and write some really good questions to ask Ethan. You can also see a video that he did about four years ago, the last time I brought him in. I know things have changed a lot since then, so I’m really excited to see what he’s been working on.
Then the next lab, we’re gonna switch to Lab 6 in a couple of weeks. Lab 6 is kind of a hybrid lab where we’re going to work on file servers and drive mappings in VMware. We’re also going to work on building an application server both on the Windows server that you did the Active Directory domain on, and we’re going to work on adding some web apps to our digital ocean droplets as well. That lab is not posted yet. I need to make a few updates to that lab based on some changes this year, but I’ll try and get that posted within the next week or so so that if you’re working a little bit ahead, you can get started on Lab 6 soon.
Finally, the other big thing to think about in this class is this class does include a final project and the final project is coming up in about a month. The idea for the final project in this class is mostly a thought exercise. I don’t expect you to actually build something or fix something, but what I expect you to do is propose something that you want to do. And that proposal could be about building something IT related or fixing something IT related. It could be designing a web resource for a new startup company. It could be a way to automatically set up laptops for school. It could be a central authentication system for a company or nonprofit. It could be a discussion of whether you should have thin clients versus thick clients in computer labs. Anything that you can think of that revolves around anything that we’ve talked about in IT so far is a fair game for the final project. The final project itself consists of three parts. The first part, you’re going to do a SWOT analysis, which is a strengths, weaknesses, opportunities and threats analysis of your proposal. So you kind of have to define your proposal, define your scope and what you’re trying to propose. Do an analysis of it. You’ll make a writeup of your analysis that includes your SWOT analysis in that writeup. It’s kind of a technical white paper style of writeup. You kind of pretend that I’m your CIO or CTO and you’re trying to convince me that this is a good idea. Or likewise, you may convince me that this is a bad idea that we don’t want to do it based on your SWOT analysis.
The only thing that you’ll actually do in the tech field is you’re going to make some sort of a proof of concept for your idea. So for example, if your idea is to migrate all of K -State systems to Azure, then your proof of concept might be to build a system on Azure just to show that you have a little familiarity working with Azure. Likewise, if you’re looking at antivirus clients, you might in a VM install a few different antivirus clients and decide which one of those you want to use. That’s kind of the idea for the final project. What you’ll do is you’ll submit your writeup and a short video talking about your project. That’s really all it takes. If you have any questions or aren’t sure about any ideas, you can schedule a time to chat with me. I’m happy to work with you to try and find an idea. The ideas themselves are due before Thanksgiving break. That gives me a quick time to take a look at your idea. And then it gives you a couple of weeks around Thanksgiving. giving before the finals week to actually write up and do your SWOT analysis and things like that. The final project is only 10% of your grade, so I don’t expect you to spend more than about a week or two on it. It’s mainly meant to take the place of a last lab assignment which are also about 10% of your grade.
So for lab five, you’re going to be using DigitalOcean for cloud providers. If you don’t have a DigitalOcean account, I encourage you to get signed up for one ASAP. You can go to this link, try .digitalocean .com slash free trial offer. That should get you a hundred free credits there. If you want, I also have a signup link that you can email me for. I have a code that gets you a $200. free trial, it does give me $25 back if you spend $25 with DigitalOcean. So I don’t put it on here, but if you want it, ask me for it and I can get you a link that will get you $200 of free credit on DigitalOcean. The other thing that you’ll do is you’ll register a domain name. You can do that through Namecheap by going to nc .me and signing up with your ksu .edu email account, which gets you a free .me domain for the first year. Both of these are optional. I can’t make you spend any money in this class. So if you don’t want to do that, please let me know. I can set you up as a subdomain under mycis527 .org domain. And likewise, I can set you up as a sub team under my DigitalOcean account. I prefer that you set your own up because I think it’s really cool that by the end of the semester, you’ll have your own web hosting, your own domain name. You can set up your own website, however you want to do it. But if you don’t want to do that or you’re concerned about signing up for any of these things, let me know. And I have options for you as well.
So that’s really all I’ve got this week. If you have any questions or concerns, please let me know. I’m available on ed discussion. There’s already a lab five mega thread out there that you can post in. You can chat with me on Discord or Teams. You can come to Tea Time office hours. And as always, we have our one -on -one office hours as well. I’ll definitely have office hours this Wednesday if you have any questions on lab five. So feel free to stop by. We’re kind of nearing the end of the semester. Hopefully things are going well. If you have any questions, let me know. Otherwise, I will see you again next week.
Hello, and welcome to the week 11 announcements video for CIS 527 and CC 510 in fall 2024. This week, you’re working on lab 5, lab 5 is due on Friday. As before, you’ll need to schedule a grading time with either Josh or I to get your lab graded. Lab 5 is pretty straightforward to grade, we’re just going to check some settings on your digital ocean droplets, and then we’re going to make sure that you’ve set up a domain name and have HTTPS working, the Apache sites working, and the Docker sites working. It usually only takes a few minutes to grade if everything’s working correctly. So hopefully you get everything done. Lab 5 is usually a little bit of a downward curve on the difficulty in this class, so hopefully it goes well. Also, don’t forget, our third discussion session is coming up tomorrow, Wednesday this week at 2:30.
So for lab 5 grading, like I said, we just want to see that you can SSH to your front end either from your VM or using the virtual terminal on digital ocean. Once you’re in front end, you should be able to SSH directly from front end to back end just by typing SSH front end and have the key set up there. That’s the big thing we’re going to check. We’re going to check that your firewall is set, your date and time is set correctly. Then on the back end, we’re going to check that Apache is set up with a proper virtual host, has HTTPS working, we’ll check on the front end that your Docker reverse proxy is set up with at least two different hosts there, and then your DNS name should work for all three of those sites as well.
So also coming up this week, we have our third discussion session. Our speaker is Ethan Bergstrom, who works at Oracle Health, formerly Cerner. He works a lot in their hosted provider, so where they provide hosting services for hospitals that want to host their Cerner software on their premises. So Ethan’s got a lot of good background in system administration at a very high, large industrial level, so I’m really excited to bring him back in. He will be here tomorrow on October 30th at 2 .30. If you haven’t already, please go online and fill out some questions that you want to ask Ethan. I have linked his bio and his LinkedIn on the discussion assignment so that you can find that. So feel free to check that out and come prepared with some really good questions for Ethan. Again, that’s tomorrow at 2 .30.
So after this week, we’re gonna switch over to lab six, which is about file servers and application servers. This lab is a little bit more complex than lab five. I will get this posted later on this week so you can get started on it. Basically, we’re going to take both our Windows and our Linux server and add file server capabilities to it. And we’re gonna look at how we can actually automatically map some of those server drives on both systems. Then we’ll also create an application server so that we can install a web application on both. The web application we’re gonna do in DigitalOcean on the Droplets, on Windows we’re gonna do on the Windows server. The goal at the end of this is you should have a working file server and a working application server in both Windows and Linux.
Finally, don’t forget you should be thinking about your final project. The final project in this class is to basically propose either building something or fixing something, and then you’re going to do a SWOT analysis and present a write -up and a proposal in a video about this project. There’s lots of great ideas for the final project out there. The best thing I can tell you is if you’re not sure what you want to do for your final project, start scheduling some time and chat with me for ideas. I’m happy to talk about things. The proposal for your final project is due the Friday before you leave for Thanksgiving break. I will review them pretty early Thanksgiving break week and give you a thumbs up if your final project proposal is approved. Then you can do the SWOT analysis and create the write up and the video proposal of your final project. It should be pretty straightforward, but if you have any questions or concerns, let me know. The other question I’ve gotten a lot on the final project is on grading. The final project is worth 10% of your grade, but it scales linearly. So if you look at your grade at the end of the semester and you’re on track to get an A, if you only get half of your final project, then you can just do either the write up or the video. You don’t have to do both and I will grade it as 50%. So talk to me if you’re not sure about that, but I have some flexibility in your final project. If you know where your grade is going to be, we can work with you to make sure that you’re not overloading yourself if you’ve got other things going on during finals week.
So that’s all I’ve got this week. As always, if you have any questions, you can keep in touch with me on Ed discussion, Discord teams and come to office hours. We’re always happy to help. Otherwise, I hope you’re having a good time getting through this class. We got Halloween week coming up, so hopefully you’ve got some fun plans for Halloween. Best of luck this week and I will see you again next week.
Hello and welcome to the week 12 announcements video for CIS 527 and CC 510 in fall 2024. So you should be starting on lab six this week. Lab six is going to be due next week on Friday. We’re also going to have our fourth discussion session next week on Wednesday. So our next discussion speaker is Sarah Allen. Sarah Allen is a computer support person for McCon Gordon construction. Sarah was a student in this class a few years ago and now works in industry as a frontline support tech. She has a lot of good experience and stories to tell from working in that industry. So she’s going to come in and be our guest speaker this Wednesday, November 13th. So a week from this Wednesday at 2 30 p .m. So make sure you put that on your calendar. The questions post is already up so you can get questions asked for Sarah. I’ve also linked her LinkedIn so you can learn a little bit more about her background and what she does.
So for lab six that you’re working on, we’re going to do a whole bunch of different things. This is kind of where we break out a little bit. We’re going to explore file servers on both Windows and Linux using your local VMs for the most part. If you’re working in Azure, you’ll do your file server on the Windows server in Azure. We’re also going to work on drive mappings between the two so you can connect to those file servers. We’re going to build an application server on Windows. We’re going to do that on the Windows server by installing a web application. And then on Linux, we’re going to do that in the cloud using our Digital Ocean Droplets to build some working web apps there.
So don’t forget the other thing in this class is there is a final project in this class. It is worth 10 percent of the grade. The proposal for your final project is due the Friday before Thanksgiving, so I can review those and get those back to you pretty quickly. The idea, remember, behind the final project is to do a proposal and a SWOT analysis. The proposal is to build something or fix something I .T. related. It could be a web resource for a startup like how would you build a website with high availability and failover modes? How would you automatically set up laptops for school? How would you define a central authentication system for a company using Active Directory or LDAP? Discussing the pros and cons of thin clients versus thick clients in computer labs, lots of different things you can do. to remember this is mostly a thought exercise where you get to set the framing and then you get to do the analysis, but you’ll also have a small proof of concept of your project that’s something related. If you’re not sure what to do, feel free to chat with me for ideas. I’m always happy to work with you and kind of help you find some ideas or final projects that might work for you.
So that’s all I’ve got this week. Hopefully if you’re on campus, you’re looking at either volunteering for the high school programming contest, which is tomorrow, or participating in Hack case eight, which is this weekend, albeit both events. So other than that, keep in touch on Discord or come to Tea Time Office Hours or chat with me on Ed discussion. We’d be happy to work with you if you have any questions, but that’s all I’ve got this week. So good luck and I will see you again next week.
Hello and welcome to the week 13 announcements video for CIS 527 and CC510 in fall 2024. This week you should be working on lab six, which is due on Friday. So make sure you get your grading time scheduled sometime this week to get that turned in. We’re also going to have our fourth discussion session this Wednesday. So make sure you get those questions posted before two o’clock that day. And then you’ll be able to meet with our speaker and ask questions when she speaks at 2.30.
So our discussion speaker this week is Sarah Allen from Account Gordon Construction. Sarah is a former student in this class and now works as a frontline tech support person for a large construction company. She has a lot of really good experience working in the front lines of tech support and has some really good advice for you in your career. She’s going to be speaking with us tomorrow at 2.30 via zoom. So make sure you set that on your calendar if you’re available to join us, but don’t forget to ask your questions beforehand. And if you can’t join us, make sure you watch the video and respond to it afterward.
So for lab six that you’re working on right now, we’re going to be setting up file servers and drive mapping so that we can automatically connect to different systems. We’re also going to be setting up application servers. So this is a web server either on Windows or on Ubuntu and working with some web apps as well. These kind of exercise all the different VM setups that we have. So it’s a pretty cool lab, I think. And it really gets to some of the later stuff that we’re going to do in system administration.
So last thing to keep in mind is don’t forget that you need to be thinking about a final project. Your final project presentation is due before you leave for Thanksgiving. The idea behind the final project is to propose either building something, fixing something like a web resource or setting up laptops. It’s a thought exercise. So all you have to do is set the stage. So give the background of what you’re actually doing, talk about your proposal, do a SWOT analysis of your proposal, and then tell me whether it’s a good idea or not. You can pretend that I’m pretty technical as your reader, like a CIO or a CTO. And basically you’re proposing this idea of something you want to do. You don’t even have to be able to actually do it. For example, you can propose something way bigger and more complex than you could actually accomplish. But you should know enough about it to be able to reason about it and write a SWOT analysis about it. And that’s really what we’re looking for in this final project.
Other than that, I think things are going well in this class. So if you have any questions, you can keep in touch with us on Ed discussion, on Discord and Teams. You can come to Office Hours. We’re always able to help. We’re on week 13 of 16, so we’re looking toward the end of the semester. As always, if you have any questions, let us know. And otherwise, I will see you again next week.
Hello and welcome to the week 14 announcements video for CIS 527 and CC 510 in fall 2024. So remaining in this class is just a few things. The discussion for response is due tomorrow, so make sure you get that turned in. Your project proposal is due this Friday, so that’s just your quick proposal for your final project. It should be about a paragraph or so. And then the rest of the class, Lab 7 and the final project are both due by the end of finals week. And then of course you’ll also get some TVALs from me as well.
So for Lab 7, I have posted Lab 7. The grading for Lab 7 is all offline. There’s no interactive meeting required. You can even submit these tasks separately as you get them done. That’s totally fine. For the first task, you’re going to upload a zip file and a readme for your backup project. For the second task, you’ll upload the URL for your monitoring system. And then for the third task, you will share us either your GitHub or your GitLab repository and the URL where your website is deployed. That’s all you really have to do for Lab 7. It’s kind of all or nothing. It either works or it doesn’t, but it gives you a good chance to get some last-minute points for this class. As always, if you have questions on Lab 7, let us know and we are happy to help.
So the last part of this class is working on a final project. If you haven’t come up with a good final project idea yet, I encourage you to schedule some time to meet with me this week so we can chat about it. In general, I tell you to think about the thing that you’ve liked most in this class and kind of build upon that. The idea is it’s a thought exercise. You’re going to work on designing and implementing a solution for a problem. So you’ll spend some time defining the background and the problem and the specs around that problem and what you want. Then you’re going to propose a technical solution for that that uses system administration techniques. And then you’ll do a SWOT analysis of your proposal and give us a conclusion that says hopefully that it’s good. This is targeted at me as your CIO or CTO. So it can be pretty high level and pretty technical. You can assume that I kind of know what you’re talking about, but really you should assume that I’m a skeptic and that I’m looking at your your project and your proposal and trying to decide if it’s a good idea for our company to put resources into the solution. So you really have to convince me that you know what you’re talking about.
What you’ll turn in is two things. You’re gonna turn in a written report. There is a template that you can use. That template has some bullet points in it to just tell you what those paragraphs should be. Do not just use the bullet points and answer the questions. It should be in paragraph format where it’s like a written report. Likewise, your SWOT analysis should not be just a bulleted list. It should be like a written out. Here’s the strengths I’ve identified, why these are strengths, why I’ve highlighted them, things like that. You can include graphics and data as needed. You may also include citations as needed, so make sure you include that. So your written report is half the project. The other half the project is a presentation. Your presentation is going to be around 15 minutes of length and basically it goes through the basic high points of your written report and it’s supposed to convince me that you’ve analyzed it well. So. Again, in a corporate setting, you would give your presentation to me. You’d hand me the written report with more details. I would review that and decide if I think it’s a good idea. The last thing you’re gonna do is a small prototype. The prototype should be covered in your presentation. The prototypes spend about two to four hours on it. It shouldn’t be too much, but for example, if you’re writing about doing some stuff in AWS, I would expect your prototype would be setting up a virtual environment in AWS just to play around with it, something like that.
So for the presentation itself, you’re going to submit a prerecorded video of your presentation. You can use tools like Zoom to create that really easily, or there’s tombs in both OneDrive, or you can grab OBS, anything you’d like. You’ll submit that by uploading it to Canvas, or you may have to upload the video to OneDrive if it’s too large to put on Canvas. But all you have to do is record yourself and then upload that along with your written report for this project.
So last big thing in this class, I will send out T-Vals for this class. They’ll be sent out sometime during finals week. As always, I encourage you to respond to the T-Vals honestly with all your feedback. Remember that T-Vals are anonymous and I cannot access them until after grades have been submitted for this class. All comments and feedback are welcome. This class especially changes a lot over the time. It’s a really different class experience, and so I’m always looking for feedback of things I can improve or do better. So please feel free to be honest on your T-Vals and let me know if you have any comments. And then once we get to finals week, final grades will be posted on Canvas by the Tuesday after finals week. I will email everybody once those are posted. If you have any concerns with your final grades, let me know and I can take a look.
So other than that, hopefully things are going well. We’ve got good discussions on Discord and EdSTEM if you have questions. I also still have one-on-one office hours so I’m available anytime. Otherwise, best of luck. I hope you feel like you’re getting there. You’ve solved the puzzle of this class. If you have any questions, just let me know. Otherwise, best of luck and I will see you in a couple of weeks.
Hello and welcome to the week 15 announcements video for CIS 527 and CC 510 in fall 2024. So all that’s really remaining in this class is lab 7 and the final project both of which are due on the Friday of finals week so you’ve got a little bit over a week and a half to work on those. We’ll also have teaching evaluations at the end of the semester so let’s talk about all of that.
For lab 7 no meeting is required for grading there are just three things that you’re going to submit on Canvas. You can submit them in three separate submissions if you want just note that in the comments so that we know to go through and look at those. For task 1 you’re just going to submit a zip file and a readme for your backup. For task 2 you’re just going to submit the URL of your monitoring instance so we can check it. And for task 3 you’re going to add us to your GitLab or GitHub repository and send us the URL where it gets posted. For grading that we’re just going to make a commit to GitHub or GitLab and then check to see that the commit shows up at that URL. Pretty easy to take care of and you’ve got until Friday of finals week to get all of that turned in.
For your final project there are three things that you’re going to turn in. The first thing is the written report. What I want you to do is use a written report template. Note in that template that it has bullet points under each heading. Those are just telling you what should be in that heading. You should actually write paragraphs and not bullet points because there’s a written report. So you’ll do a SWOT analysis and kind of convince me that your idea is good. So make sure your written report includes the background, your idea, the SWOT analysis, and a summary. There’s some other stuff that you want to include in there as well. You should also record a short about 15 minute presentation with a few slides that goes through the same exact content. So your background, your SWOT analysis, your your conclusion to make sure I have all of that. You should also have a small prototype that will be presented as part of your presentation. So you’ll do a screen share, show me whatever your small prototype is. It should be pretty easy to do. Spend only a couple hours on building the prototype. But in your presentation, you should switch to your small prototype and show it to me really quickly just to show that you’ve been playing around with whatever. you’re talking about.
So, for the presentation, you’re going to do a pre-recorded video. You can upload that to Canvas or OneDrive. Generally, videos are large enough. You don’t want to upload them on Canvas, so a lot of students will upload it to their K-State OneDrive and then share that link and then post it in Canvas so that I can see it that way. If you use YouTube or Vimeo or something, you’re also welcome to do that. It’s up to you. But that’s what we do to get the presentation. For recording the presentation, it’s easiest to just open Zoom, create a private Zoom meeting, and hit record in Zoom. You can also use more advanced tools such as OBS, which is what I’m using right now. Any of that is valid for recording your presentation video. If you have any questions or concerns on that, let me know.
So, last big things in this class are T-Vals. T-Vals or teaching evaluations will be sent to you during finals week. You’ll get it via email. You’ll get about three email reminders to fill that out. Please take the time to respond honestly in the T-Vals and give me all of your feedback, both positive and negative. Everything is really welcome, especially in this course because this course is constantly changing and I’m always looking for ways and ideas to improve it. So let me know. Don’t forget the T-Vals at K-State are both anonymous so that I won’t know anything about who you are unless you write it in the text comments of course. And they are delayed. I don’t actually see the T-Vals until I submit final grades. So you don’t have to worry about that influencing me at all. So please be as honest as you want in the T-Vals. I really do appreciate your feedback. The last thing is final grades will be posted. I will update Canvas with final grades and I will send an email to everybody once grades are finalized because there are going to be about 30 final presentations I have to watch during that weekend. It may be late on Monday or early on Tuesday after finals week before grades are completely finalized. As soon as they are, I will email everybody. Please keep an eye on Canvas and let me know if you have any concerns. Grades will be posted to cases by the Wednesday after finals week at 8 a.m.
So make sure you check there. Other than that, that’s really all I’ve got going on. So feel free to keep in touch. We’ve got discussions on Discord and Ed discussion. I’ve got availability for one-on-one office hours yet this week and next week. So let me know if you have any questions. Otherwise we’re at the finish line. Congratulations everybody for making it to the end of the class. I hope things are going well. I look forward to seeing your final project presentations but this is probably the last you’ll hear from me directly. So I wish you all the best of luck in the future. Feel free to keep in touch and good luck on finals week.