This is generally a role of a Sysadmin or Endpoint Engineer that works on the Desktop Engineering team that handles software packaging, SCCM, Operating system delivery, and managing GPOs for endpoints. The team i work with that manages all the RHEL stuff is reffered to as Client Engineering. I deal with the UNIX side of things with Mac and Red Hat.
Yes you are on point! We don't have a dedicated team at work so sometimes I also do this task. oh wow I'd also like to learn RHEL someday. Thank you for sharing!
You are a life saver. Isnt this a system admin role? Your earlier vids seemed to be geared more to Networking. I guess learning both worlds makes you more marketable!
@@EastCharmer it is a good thing to be exposed to other things in the IT field, never know what you need to work on and what may peak your interest for future jobs.
Oh yeah it's doable with labs! It just gets complicated sometimes in real world because of company policies and user needs but if you have a solid foundation, you will be able to set this up well.
Thank you very much for another interesting and informative video. I like to use either a C_ for computer policies or a U_ for user policies or C_U_ for computer/user policies for naming the policy at the beginning. You can also write a comment for a policy, which helps another administrator to understand the policy. The loopback policy is another important policy in the interaction between computer and user policies. Thanks again for the video
@@EastCharmer Quite an informative video on GPO's there! I need go over this again as determining which type of configuration (User and Computer) can be lil confusing especially watching some of the activities. Some of them sounded more of computer configuration and vice versa to me lol. But as I said, I need to go over again. Thank you as always for your easy to understand videos. You are changing lives! Quick question: Is AD now Entra ID? Also, will you be doing some videos on Azure AD since things seem to be going in the cloud direction?
For account lockout policy :computer configuration > policies >windows settings>security settings>account policy> account lockout policy>> set threshold time like 3, duration like 60 mins,lockout counter like 60mins. Is that correct?
I had something similar in mind though I would have gone with 5 (or 10) for the threshold and 0 mins for duration, that way only an admin can unlock it.
@@AlderT00 i think threshold defines the number of failed sign-in attempts so its recommended to keep it as lower as possible to prevent brute force attack. So that they can have less change to crack credentials😜☺
