The Accidental Citrix Admin - The site for those who find themselves supporting Citrix involuntarily or accidentally
While Active Directory (AD) does not need DNS Reverse Lookup Zones, most Citrix and VMware products do. If you are visiting my website, you probably use Citrix and VMware products. If you have heard or read any of my AD conference or CUGC presentations, you know how important AD Sites and Services Subnets and DNS Reverse Lookup Zones are to Citrix and VMware.
One of the questions asked when I am either doing Active Directory (AD) remediation work or preparing a customer for an AD migration is “what domain accounts are used by what services and on what computers?”
That question is what this script is designed to answer.
The original purpose of this script was to backup and report on all Group Policy Objects (GPOs) in an Active Directory (AD) domain. That worked well for small domains, but recently I have worked with domains with hundreds of thousands of Organizational Units (OUs) and many thousands of GPOs. This script update makes working with extremely large AD domains easier.
Back in June 2009, I wrote the original How To Hide Additional Drive Letters article. Recently, someone asked me how to do the same task but with an ADMX file instead of ADM.
I have been working with Microsoft Active Directory (AD) since July 2001 and doing AD Health Checks since September 2003. One item I have done hundreds of times, failed on me yesterday during an AD remediation project. I duplicated the problem in my lab and want to document the solution for future reference.
I do a LOT of Active Directory (AD) Health Checks. One of the things I look for are User Settings in the Default Domain Policy.
Some of you know that I do a lot of work with Active Directory and Group Policy (GPO). I needed a script that would:
On a recent project, I needed to generate a report of all users who had a Home Drive configured on the Profile tab in Active Directory Users and Computers (ADUC).
About a year ago, I released V1.0 of this script and stated if I ever found the time I would update it to not require XenApp 6.5. Finally, I took the time between customer calls to update this script (and two others).