Rules to Better Active Directory

Hold on a second! How would you like to view this content?
Just the title! A brief blurb! Gimme everything!
  1. Do you add Staff profile pictures into AD?

    You can upload Staff profile pictures into Active Directory. Exchange and Lync will automatically use these profile pictures. 

    ​Using a free third party tool AD Photo Edit tool which can be downloaded from http://www.cjwdev.co.uk/ you can upload Staff profile pictures into AD. You need to run the application with Domain Admin rights. After you have uploaded the picture for a user it will take some time for the change to be replicated through to Exchange and Lync if you have use these solutions.

    ExchangeAdPhoto.jpg
    Figure: Profile picture imported from AD into Exchange 
    Lync.jpg
    Figure: Profile picture imported from AD into Lync
  2. Do you have a postmaster account in your Microsoft Exchange?

    ​What is a postmaster account? 

    It is an RFC mandated specification email address use to identify the administrator of a mail server. Any errors in email processing are directed to the postmaster address.

    The email received at this address is sent to the mail server administrator, in our case the SysAdmins. 

    At SSW we have configured postmaster@ssw.com.au as a distribution group, with mail server administrators as members of this distribution group.

    postmaster.png
    Figure: Group members of postmaster@ssw.com.au​
  3. Do you standardise AD group names

    ​The use of standardised AD Group names is a simple yet crucial step towards building more manageable software. Raining in on the number of AD Groups used by an application will make it simpler to manage and allow new developers to pick up an existing project faster.​

    ​You can save yourself countless confused conversations by standardising AD Group Names.​

    For example: This is a list of AD groups associated with products.

    SSWSugarLearningEvents
    SSWCodeAuditorAlerts
    SSWLinkAuditorDevs

    Figure: Bad Example – It is difficult to know the correct name for an AD group​

    SSWSugarLearning
    SSWSugarLearningEvents
    SSWCodeAuditor
    SSWCodeAuditorEvents
    SSW​LinkAuditor
    SSWLinkAuditorEvents

    Figure: Good Example – By standardising the names of AD groups it saves confusion.

    It is recommend by default to have two AD groups per product. The following table should be used as a guide for naming them:

    NameTypePurpose
    SSW<ProductName>Distribution groupThis email is used to send emails to the development team for a product.
    SSW​<ProductName>EventsMailboxActs as the collection point for all automatic notifications. For example notifications from Elmah and/or application insights.
    ​​
  4. Do you use Group Policy to Apply Settings to all of your PCs?

    ​​Group Policy is simply the easiest way to reach out and configure computer and user settings on network based on Active Directory Domain Services (AD DS). If your business is not using Group Policy, you are missing a huge opportunity to reduce costs, control configuration, keep users productive and happy, and harden security. Think of Group Policy as "touch once, configure many."

    ​You can manage all aspects of Group Policy by using the Group Policy Management Console (GPMC). You start the GPMC from the Start menu: Click Start, All Programs, Administrative Tools, Group Policy Management. You can also click Start, type Group Policy Management, and then click Group Policy Management in the Programs section of the Start menu. Windows Server 2008 onwards include the GPMC when they are running the AD DS role. 

    GPO.jpg 

    Figure: Group Policy Management Console showing GPO

  5. Do you use Group Policy to enable Hibernate option

    Group Policy is a fast and effective way to configure Hibernate on multiple PC's

    ​To enable Hibernate option in Group Policy open up Group Policy Management. 

    1. Create a new Group Policy Object and name it "EnableHibernate"

    2. Right click on "EnableHibernate" and click on Edit to bring up Group Policy Management Editor

    3. Select 'Show hibernate in the power options menu' from Computer Configuration | Policies | Administrator Templates | Windows Component | File Explorer and set to Enabled
    HibernateGPO.jpg

    4. Back in Group Policy Management Enable Link for "EnableHibernate"  
    GPOLink.jpg

    5. Wait for a few moment for GPO to refresh and apply. Alternatively manually force a GP Update through Command Prompt - GPUpdate /force. Check that Hibernate Option is now in Start Menu.
    StartHibernateEnabled.jpg


  6. Do you use separate Administrator account?

    When using a single account for normal user login and admin tasks the first thing that comes to mind is all of the Group Policy settings associated with that account. This could include scripts, software installations, drive mappings, printers and many other settings that would apply when you log on to a computer in the domain. You wouldn’t want all of these to apply when log on to a Domain Controller of any other servers.

    Another reason is you may step away from your computer and forget to lock the computer. This will expose your computer for your co-workers and tinker with your system and as a consequence if that account has domain administrator privilege they can change system security and settings on any Domain Controller and other servers.

    To prevent this, at SSW we create a separate Administrator account, with the prefix Admin. This signifies that it is an Admin account and does have administrator privileges. The Admin account is also placed in a separate OU to ensure that it is not receiving unnecessary Group Policies. This allows us to setup permissions easier, only provide access to machines required, and also makes the user aware that they are doing something dangerous so they are inheritably more careful. A standard account (Non Admin prefix account) does not and should not have access to any servers.
    image001.png
    Figure: SSW AD Users and Computers showing Admin accounts in separate OU