Ox’s closest friend, Hanz (who helps out daily), has a copy of this black book and occasionally compares their list to what Ox has. Names are always being added or removed, often with notes on what a club-goer can and cannot do while inside Club BOFH. Ox uses this black book while providing security every night. If business continues to pick up, Roscoe plans on opening new locations. The night club’s owner, Roscoe, has a black book that contains all club-goers who are authorized to enter and have paid their membership fees. But how do Ox and friends get the list of club-goers who are or aren’t allowed to enter Club BOFH? Active DirectoryĬlub BOFH is unique. Ox does well providing redundant security services. Should one of them get overpowered by an angry person that was ejected from the night club, any one of them can step in and continue providing security services.
Ox has a few friends (member servers acting as domain controllers or DCs) help out. This is the only way to gain access to domain resources (drinks, music, and dancing within the night club). Once Ox authenticates the club goer, they detach the velvet rope and allow the club-goer (a user or computer) to pass. A domain controller hosts a database (the ‘A’ list) that is used for authentication requests (the club-goer giving their name to Ox). The domain controller (Ox the bouncer) or DC, is providing security services for the night club. If they try, they get ejected! The bouncer is providing a critical service to the nightclub owner, who, when not running a club, writes these types of blog posts explaining IT topics. Every hopeful club-goer in line wants to get in, but they have to be on the ‘A’ list. Ox’s job is to check names against a list before letting someone in line get into the club. It’s not just Active Directory VS Domain ControllersĪ bouncer named Ox is standing guard at the door of the nightclub dubbed Club BOFH.