Every Sys-Admin or Sys-Eng I know has their own subconcious way of doing things. The one, last hold-out of human intuition and creativity in existence within the data center world. Side note: when the data center is fully automated, and humans are irrelevant, I wonder if AI will develop “preferential discrepancies” which lead to them bickering amongst each other. I hope I don’t live long enough to find out.
Any how, each time I stand up a ConfigMgr site, whether for myself or for a customer, there are some habits I tend to lean on. That is, unless the customer objects or doesn’t feel comfortable with the recommendation. Keep in mind that I didn’t invent these, but like a good homeless person, I collect things for the long haul.
- Sidebar: Re-arrange the console side bar to place Administration on top.
- Devices and Device Collections views: I right-click column headings and add “Active Directory Site”, “Client Version”, “Last Status” and sometimes “Operating System”
- Applications: Right-click column headings and add “Devices with Application”
- Queries: I add queries for grouping by OS, manufacturer, vendor and MAC address
- Discoveries: I enable the option to filter out by x-days since last logon or password update. Because most environments don’t maintain a “clean” AD environment.
- Maintenance: Following Steve Thompson’s advice, I set up reindexing and index defragmentation tasks in both SQL Server and via the ConfigMgr console, so that they don’t step on each other.
- System Discovery: Include the msTPM-xxx attributes (for TPM and BitLocker)
- User Discovery: If customer leverages non-typical attributes (e.g. “EmployeeNumber”) add those to the attributes list. One example was a customer who automated AD user account attributes like “title”, “manager” and so on, and we used those to create queries and collections for targeting various things.
- Boundary Groups: Right-click on column headings and add “Site”
- Monitoring/ Component Status: Right-click column headings and add “Errors” and “Warnings”
- Monitoring / Distribution / Content Status: Right-click column headings and add “Failed”
- IIS Log Management: Add a Windows Scheduled Task to run this PowerShell script to clean up IIS logs to save disk space (thanks to FoxDeploy for this tip!)
And finally, in some situations, I recommend creating at least one custom device collection to isolate VIP devices. That way you can be careful to treat them delicately, or, if you’re being terminated, to target that Windows 10 image deployment, even if they have Windows 10 already.
There are some others, but this is enough for now. So, what do you think? What options/features do you customize when building a new site?