He has worked with Microsoft Windows since 1990, and with Active Directory since 1999, when Windows 2000 came out. The work is forest and domain design, migrations, Group Policy, delegated administration, Azure hybrid identity, and Windows Server from early versions through current builds. That includes environments of more than 150,000 users and more than 725,000 systems. Clients hire him for the part that has to hold up later. Patch rings that stay in order, CIS and STIG baselines, least-privilege access, and an evidence package an examiner can read.
Regulated work
He has done that engineering where outside rules applied. He prepares the evidence. He does not sign the certification.
- Healthcare Windows and identity work where HIPAA and HITRUST set the bar, including systems that hold PII and PHI. Access, logging, baselines, and the evidence an examiner expects.
- Finance SOX control evidence for external audits, including packages prepared for Deloitte, KPMG, and PwC.
- Aerospace Two aerospace plants in the Phoenix area, and an earlier plant in Washington. Active Directory and Windows Server for production and SCADA, physical servers virtualized onto VMware, and access reviews under ITAR and DFARS. Audits in that work included Nadcap, KPMG, and Deloitte.
- Government Public, local, state, and federal government environments, including those projects where public trust was required. Same identity and Windows engineering, with the access and evidence those environments require.
Before the server work
Before he moved into IT, Chuck installed and managed telecommunications. He started in the field on PBX systems, cabling, and the infrastructure equipment those systems sit on, for organizations such as the City of Boulder, the City and County of Denver, and Genie Industries in Redmond, Washington. He also installed cable television for Cox, Time Warner, Charter, and Comcast, and did quality-assurance spot checks after technician installs. He then moved into telecom management. That meant audits, pre-sales site surveys, and closing a site out. Walking the rooms, checking existing cable and equipment, planning the cutover, coordinating the carrier and the vendors, keeping the inventory of circuits and rooms, and leaving test results and as-builts so the next person was not guessing.
What a first call is
Thirty minutes is enough to say which lane you need. Tier 3 engineering is identity, Windows Server, patch operations, hardening, and audit evidence. Local IT assistance is the lighter, practical work, and it stays a separate lane. He will tell you which one fits.
Book Discovery is the next step. You get Chuck, not a coordinator.