G33kman

In the video, it claims your CPU is running at 4.3Ghz. Max turbo frequency for the 4770k is 3.9Ghz.

does it still happen when you uncap the fps

The poor kid... that said one of my friends did basically end up learning linux cause they got a broken laptop and wanted to make use of it, so assuming they don't sink that is a valid way of learning. Still I think it'd be better to start with something higher level rather than low level stuff just cause the effort to reward ratio is much better when working with higher level languages. It's not as tedious to make something neat and exciting.

( this is my personal opinion and experience )
 
If i started coding in terminal at the start. I would have quit quickly. I began my journey into coding by programming runescape bot scripts in Java. I quickly pick up on the basic variables, conditional statements all the basic stuff.  Then I got more advance by learning about classes and how to deal with multi threaded processes. Then I move to C++ followed by C#.
 
To sum my point that is not really clear in the above text. There is no good or bad way to get into programming. You just have to start 

I'm not sure about making use of an existing game engine. It just seems like it'd add an unnecessary level of complexity. Maybe using python with the turtle graphics library would be simpler and easier to teach skills that can easily transfer to other areas of computer science.

No problem. Ultimately it's just a case of applying agile engineering principals i.e. small iterative chunks of desecrate development.
 
Moreover as a parent of two I find that they often respond very well to 'quick and easy wins', something that this kind of iterative process tends to provide. All the better if you make some form of development backlog or product vision ahead of time.
 
Have a read of the Agile Methodology and you should get the idea.

You should consider a simple matching squares game with scoring.

LOOOL. Anyway, good luck.
 
P.S: Some flash drives are very small they can be linked to one's keys

I worked for a company where passwords were predictable and we were not allowed to change them. We were able to guess each other's passwords very easily. It made the admin look stupid.
 
 I like to remember a sentence and then scramble it in my head. Something I can remember but is not in any dictionary and does not have pr3d1ct4bl3 substitutions. It can also be very long if I wanted it to.
For example take every third letter from a song chorus and every second letter from a verse, there are your random looking letters

I would say go for somewhat complex passwords and then stick with them. Many places are still in the practice of requiring frequent password changes, but it's actually better to just have a very secure password than a constantly changing simple one, as it's harder to brute force and guess and it doesn't require the users to remember a new password every month or so. Once the phase of learning the complex passwords is over, it should be pretty secure. 
 
You could also look into some biometric security to replace, or go alongside complex passwords. Logging in with fingerprints or similar makes it easier on the users and really, unless you have some particularly sensitive data that someone wants, it's unlikely someone will actually spoof someone's fingerprint. 
 
To be honest, I would be most concerned with network security more than passwords on each system. In general, it's best to avoid using WiFi where possible, and where it is needed, you should separate areas of the network that don't need to communicate with other areas to reduce the amount of potential entry points. If you just have WiFi for people to connect their phones to in order to have internet access or something and no actual business related stuff goes over the WiFi, then have it all on a separate VLAN from the business parts of the network to make it harder to gain access to business data. 

Yeah I'm firmly in the 'doesn't really matter' side. Give them a guideline of common passwords to not use (password, 1234, qwerty, etc etc) and let then pick there own.

Considering that logging password for Windows can be cracked/removed easily, it doesn't really matter...

That's a good start and it's really easy to get past the dictionary word problem. Replace the first letter of each word with the first letter of your first name and replace vowels with the character or number that it looks like. For example, Linus would turn "chairstaplercoffee90" into "Lh@!rLt@pl3rL0ff3390." Unfortunately, that is probably too complicated for some. 

Get them to change their password, get them to change their passwords to 3 objects that they see in the office (Chair, Stapler, Coffee), add their internal phone number or the last 2 digits of their mobile number (chairstaplercoffee90), and you are off to the races. That may not be a particularly strong password since it has 3 dictionary words in it, but it is good enough for your use case.
 
Honestly, I think the employees knowing eachothers passwords is not a bad thing (not a good thing though), especially since how small the company is, the threat would likely extend from attacks, so if reakless not-so high up employee has the same password as the accountant, and their password gets leaked, the attacker would also have access to the accountants account.

Another thing to consider is that a move to 2016 requires 2016 CAL's for the users. Depending on the copy you have it might be better to up both machines to 2012 R2 using downgrade rights on your 2016 license (if it supports it). There is quite a few compelling reasons to ditch the 2008 R2 machine it you already have a full win10 environment. However a lot would depend on what type of workload you are running, being basic file and print or any sort of network applications/file database workloads.
 
Often the best upgrade path can be dedicated by the licenses you are running and not the hardware you have in a small business environment.

oh that is weird, all my servers are clones from a template (2012R2) and no issues, good ol' M$, never consistent. (Good job security at least)

https://emeneye.wordpress.com/2016/02/16/group-policy-order-of-precedence-faq/
 
Hopefully this is helpful and will allow you to change those GPOs to not enforced. Enforced doesn't actually make them get applied any better to computers it only effects how GPOs are processed and can produced unintended settings/problems if not carefully used.
 
Edit:
Meaning unlike how GPOs are normally applied, settings set at an OU take precedence over the same setting applied higher up, enforced is top down and not bottom up.
 
I realize the guide you followed told you to do that but it's incorrect and poorly worded step.
Link Enabled enables a GPO not enforced.

OK so I can leave it the way it is. Perfect! That just saved me a huge headache I think. Lol
Thanks for your help!

Well Server 2016 still fine to use, RDS is only one role and not one you're planning to use. I've been using it since technical preview 3 so a very long time. I wouldn't do a new install not using Server 2016 personally, servers hang around for a long time so it's good to use the newest when possible. AD/DHCP/DNS/IIS/File and Print are all stable so there isn't any reason not to use it.
 
For the above point about patching and rebooting servers that's always been a thing, it's not new to Server 2016. You need to use Group Policies to tell your servers how to handle Windows Updates as the defaults are not production appropriate.

2016 is a B***H to handle
stay on 2012 R2, you (and your sanity) will be thanking me for the warning
also don't use 2016 as a DNS (or other server that has to stay on 24/7) as the system auto reboots everytime there is an update
there is an option to turn this off in policies
the second post explains how to disable it permanently and still update system, their is also a reddit link but i haven't checked that out:
https://www.experts-exchange.com/questions/29003500/Windows-Server-2016-Disabling-Automatic-Updates-Reboot.html 

Have you tested your ethernet cables by swap testing them (use those cables with the other server or other computer) or using a cable tester? Also have you swap tested ports on the switch? It sounds to me like you may have bad cables or switch ports.

Not 100% correct, but close enough, fuck it, works this way in practice.

That may not have been the problem but it's still useful information, while you don't actually need to setup DNS forwarders it's always good to do so and usually best to use your ISPs for quicker response.
 
If you don't setup forwarders it will directly query the DNS root servers and then flow on down from there which can take a while to build up a useful DNS database cache which will cause rather slow internet browsing or failure to load pages the first time at all.

I ran into a similar issue setting up my home server just this week, after changing the DHCP config (i left DHCP on my router) to point to the PDC as primary DNS everything lost internet connectivity. For me the issue was that I had not set up any DNS forwarders, and the DC only had itself set as DNS. After adding a DNS forwarder everything came back to life. I'll be honest, I didn't read the whole thread, so this may be of little help. 

if it is 1Gbps on the other machine then its the NIC or adapter settings.