As someone studying to move to IT this is a great video. With study there is a lot of book work and theory and research but very little of the good solid basics out there. Appreciated seeing how this is implemented in practice.
Awesome video, Im only 3 classes away from getting my associates in IT. I started my journey 2 years ago after watching one of your videos. Thanks for all the good tips!
Thank you so much for this video, I'm currently studying for my A+ and looking for my 1st Help Desk job. A lot of what you covered is knowledge needed for landing these help desk roles, but majority of these things are not touched on in A+ cert prep. I was able to follow along a create my own server, wish users and all, I feel like with this train this is preparing me more for these help desk roles, thank you for all that you, it is greatly appreciated.
@zino I actually did as a technical trainer in a office building , not A HEAVY technical driven position a lot of customers service, with presentations, onboarding and training, GREAT PAY AND BENEFITS and the company will cover the costs of any certifications I want to pursue. I’m loving the journey so far
This is very good video, I learn something new. I came across that organization got multiple directories on-prem/cloud and forest etc. Do you have any video to understand how the physical layout consideration for setting AD for an organization which also acquire diff organization and bring their directories under their forest/tree?
Would Group policy be affected if i had a user listed under both the 'user' group as well as 'hr' group? You get the user in both containers if you find the user and 'add' to 'hr'
thanks for this video, what does it mean when they say don't install always on in domain controller? where it should be configured instead of domain controller?
Location-based OUs are really not best practice. One day half of sales might move to a different building or floor and you’ll end up redoing everything. Of course if you’re an IT manager and you’re close with the C-suite, you might have a lot more foresight for when that could make sense.
Great video, thank you for brief explanation! Your structure can be great education material and reference! What interests me is that, is it good practice to create additional OU's for Users and for Computers under original OU, in this case OU "HR"?
When I created the OU, I left the box that said "prevent this folder from being accidentally deleted" checked, and now I need to delete it and can't. How do I get the priveledge to do so?
Question for you. I have an associates degree in mechanical engineering and am currently about to take a semester off from college (due to being broke and covid) I’m interested in IT and wanna know if the fact I have an associates will help me. I’m willing to study for certifications.
Hey Zach, what are your thoughts on keeping a flat structure? As we all move to Azure Active Directory the only "OUs" we have will be Users and Computers. I like the idea of a flat structure when working on-premise. Instead of assigning Group Policies to multiple OUs, we can instead assign to just the Users or Computers OUs and permission certain Security Groups with Read & Apply Privileges. These Security Groups would be called the same as the Group Policy. This means at a glance we could see what GPOs are assigned to either a User or Computer, Add & Remove then from the GPO Security Groups and not have to worry about the impact of moving either a User or Computer from one OU to another. This is always an issue for departmental restructures, group company mergers etc. Like you, I've seen some crazy OU structures in my time and it only get worse when you start factoring in a multi domain forest with partially connect trusted remote site... lol, Why do we do it 😬
Flat structures are usually considered best practice and ideal. Unfortunately, these are really difficult to maintain in “the real world”. Eventually someone will make an exception and it turns into a mess.
@@ZacharyOtt As I always say there is a balance to be met between practicality and over bearing policy and procedures. However, many IT departments often fall short when it comes to continuously reviewing AD and the reasons for the changes implemented or proposed. In the case of exceptions I believe in challenging the following: 1. Did / do the people that proposed / enforced or made the changes have the correct understanding of the capabilities or the policies and procedure that govern the use of AD/Groups/GPOs. 2. Is there an upstream / downstream process that can be improved / implemented. 3. Is it lack of resources, training, shortest path to expedite, Laziness. 4. Or simply that the product / solution isn't capable. I would say a flat structure does need more consideration upfront or even as you transition. A lot of the above and the decisions made will also depend on the maturity of the IT Team and the approach the business has to Information Technology.
I need your help, I connected my pc to my tv and it's been working fine for the past few days but today it keeps saying there's no signal and I plugged other things in and it worked just fine, any tips?
It's too bad that Novell went belly up back in the day due to mismanagement and some lack of vision at the top! because AD is based off of the Novell Directory structure and it was way easier to view and manage! Same as for Borland whose office suite was way better than MS Office back in those days as well. sigh!
GP, DNS, DHCP That's 75% of Microsoft Server! Master those and the rest is really about securing the servers. Keep up the good TEACHING bro!!
More active directory welcome with group policy discussions and examples. Exciting stuff. Amazing presentation style. You're the best!
These vids are saving my life right now! Just started my career in IT .. I feel a little clueless!
As someone studying to move to IT this is a great video. With study there is a lot of book work and theory and research but very little of the good solid basics out there. Appreciated seeing how this is implemented in practice.
Awesome video, Im only 3 classes away from getting my associates in IT. I started my journey 2 years ago after watching one of your videos. Thanks for all the good tips!
Thank you so much for this video, I'm currently studying for my A+ and looking for my 1st Help Desk job. A lot of what you covered is knowledge needed for landing these help desk roles, but majority of these things are not touched on in A+ cert prep. I was able to follow along a create my own server, wish users and all, I feel like with this train this is preparing me more for these help desk roles, thank you for all that you, it is greatly appreciated.
@zino I actually did as a technical trainer in a office building , not A HEAVY technical driven position a lot of customers service, with presentations, onboarding and training, GREAT PAY AND BENEFITS and the company will cover the costs of any certifications I want to pursue. I’m loving the journey so far
Good video. I'm looking forward to your group policy video.
+1 JUST for that Sears Tower part!!! Thanks Z!
the best tutorial video. it is well explain thank you very much
Love how you explain things! Thanks!
Awesome tutorial. That would be awesome if you did a Windows Server 2019 course.
This is very good video, I learn something new. I came across that organization got multiple directories on-prem/cloud and forest etc. Do you have any video to understand how the physical layout consideration for setting AD for an organization which also acquire diff organization and bring their directories under their forest/tree?
Great Video / answered my question for creating a OU / I have another question, how can delete a Active directory Domain Services?
Thank you so much for this tutorial!!
Awesome explanation
Great video! Nice explanation!
Would Group policy be affected if i had a user listed under both the 'user' group as well as 'hr' group? You get the user in both containers if you find the user and 'add' to 'hr'
thanks for this video, what does it mean when they say don't install always on in domain controller? where it should be configured instead of domain controller?
Location-based OUs are really not best practice. One day half of sales might move to a different building or floor and you’ll end up redoing everything. Of course if you’re an IT manager and you’re close with the C-suite, you might have a lot more foresight for when that could make sense.
Great video! Thanks!
Great piece...thank you
Great video, thank you for brief explanation! Your structure can be great education material and reference!
What interests me is that, is it good practice to create additional OU's for Users and for Computers under original OU, in this case OU "HR"?
Tnx man I am proud of my self I appreciate u 🙏❣️
When I created the OU, I left the box that said "prevent this folder from being accidentally deleted" checked, and now I need to delete it and can't. How do I get the priveledge to do so?
Hello I have a new 2016 application server I’d like to install. We are located just outside Chicago. Do you provide this service?
Question for you. I have an associates degree in mechanical engineering and am currently about to take a semester off from college (due to being broke and covid) I’m interested in IT and wanna know if the fact I have an associates will help me. I’m willing to study for certifications.
i degree always helps
Hey Zach, what are your thoughts on keeping a flat structure? As we all move to Azure Active Directory the only "OUs" we have will be Users and Computers.
I like the idea of a flat structure when working on-premise. Instead of assigning Group Policies to multiple OUs, we can instead assign to just the Users or Computers OUs and permission certain Security Groups with Read & Apply Privileges. These Security Groups would be called the same as the Group Policy.
This means at a glance we could see what GPOs are assigned to either a User or Computer, Add & Remove then from the GPO Security Groups and not have to worry about the impact of moving either a User or Computer from one OU to another. This is always an issue for departmental restructures, group company mergers etc.
Like you, I've seen some crazy OU structures in my time and it only get worse when you start factoring in a multi domain forest with partially connect trusted remote site... lol, Why do we do it 😬
Flat structures are usually considered best practice and ideal. Unfortunately, these are really difficult to maintain in “the real world”. Eventually someone will make an exception and it turns into a mess.
@@ZacharyOtt As I always say there is a balance to be met between practicality and over bearing policy and procedures.
However, many IT departments often fall short when it comes to continuously reviewing AD and the reasons for the changes implemented or proposed.
In the case of exceptions I believe in challenging the following:
1. Did / do the people that proposed / enforced or made the changes have the correct understanding of the capabilities or the policies and procedure that govern the use of AD/Groups/GPOs.
2. Is there an upstream / downstream process that can be improved / implemented.
3. Is it lack of resources, training, shortest path to expedite, Laziness.
4. Or simply that the product / solution isn't capable.
I would say a flat structure does need more consideration upfront or even as you transition. A lot of the above and the decisions made will also depend on the maturity of the IT Team and the approach the business has to Information Technology.
chitown BABY!!! was born and raised !
I need your help, I connected my pc to my tv and it's been working fine for the past few days but today it keeps saying there's no signal and I plugged other things in and it worked just fine, any tips?
Each department is a VLAN i.e Virtual Local Area Network
if your workforce is remote, how fo gpo’s transfer to the cloud?
Azure AD!
Amazon Directory Service (AWS) OR integration of Azure AD and Amazon Directory Service
I'm not sure this structure would do well when scaled, but it's good for a demo
For a large enterprise it wouldn't be the best, but I hope for the purpose of an introduction this video helps bring things into perspective.
@@Itcareerquestions oh for sure as an intro it's a good way of explaining OUs
Good
Grate video, but can you give us some tutorial for group policies? Thanks
👍
It's too bad that Novell went belly up back in the day due to mismanagement and some lack of vision at the top! because AD is based off of the Novell Directory structure and it was way easier to view and manage! Same as for Borland whose office suite was way better than MS Office back in those days as well. sigh!
I want to play you in magic arena