1 / 13

HUIT Domain Joining Utility (DJU)

HUIT Domain Joining Utility (DJU). Kurt Levitan Manager, Desktop Systems Management Kurt_Levitan@harvard.edu. FAS Environment. Over 6000 computers Over 170 Departmental OUs in FAS Domain Multiple Active Directory Domains Pre-2010 all computers in one generic OU

ivria
Download Presentation

HUIT Domain Joining Utility (DJU)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HUIT Domain Joining Utility (DJU) Kurt Levitan Manager, Desktop Systems Management Kurt_Levitan@harvard.edu

  2. FAS Environment • Over 6000 computers • Over 170 Departmental OUs in FAS Domain • Multiple Active Directory Domains • Pre-2010 all computers in one generic OU • Each technician had own method of naming and adding computers to AD • No Standards (tools/process/software/hardware)

  3. Change • Universal Desktop • Introduced standard hardware, tools, and process for building and deploying computers. • AD Consolidation • Needed tool to assist in adding computers to domains in a standard way. • Old DJU (Eric Dropps) had basic functionality.

  4. Requirements • Support for Windows XP, 7 and Macs • Support for multiple domains with different structures • Ability to work with new domains without recoding • Place computers in correct OU • Name computers with standard scheme

  5. More Requirements • Improved security • Collect Survey data • Standard Department name list dynamically built from AD • Install Management Tools (LANDesk, ESET, Connected)

  6. Tool Flexibility • To adapt to the needs of the AD project needed a way to change the program without recoding. • Answer: external configuration file – old style .INI file (easier than XML) • Only hardcoded information is URL of the DJU.ini file

  7. DJU.ini [Domains] PrimaryAccountDomain=FAS_Domain FASUsrBoundServer=dssadc1.ad.fas.harvard.edu FASUsrRootDN=DC=ad,DC=fas,DC=harvard,DC=edu NumDomains=2 Domain1=FAS_Domain Domain2=WJH-AD [FAS_Domain] BoundServer=dssadc1.ad.fas.harvard.edu BaseDN=OU=FAScomputers,DC=ad,DC=fas,DC=harvard,DC=edu RootDN=DC=ad,DC=fas,DC=harvard,DC=edu DomainDNS=ad.fas.harvard.edu LANDeskInstaller=http://webserver.ad.fas.harvard.edu/ldlogon/AGENTS/Windows FAS Standard Agent v4.exe ESETInstaller=http://webserver.ad.fas.harvard.edu/Packages/PC/ESET/ESET_32bit_42712.exe ConnectedInstaller=http://webserver.ad.fas.harvard.edu/Packages/PC/Connected/InstallConnectedDJU.exe BuildingList=http://webserver.ad.fas.harvard.edu/packages/pc/Other/DJU/buildings.txt ConfigSource=http://webserver.ad.fas.harvard.edu/packages/pc/Other/DJU/FASITConfigs.txt LocalAdmin=True [AD_Econ] BoundServer=dc1.ad.economics.harvard.edu

  8. Department list populated from field in the OU data Building list downloaded from web server. Configs: (User, Lab, Kiosk, Shared, etc.) from web server. Each domain can have a different list. Survey data stored in registry

  9. FAS Naming Standard: • 3 or 4 character prefix for department. Official codes used in PeopleSoft. Data read from AD • User name (truncated to fit) • Number of computer (first, second, third) in AD

  10. After reboot program auto-runs and requires technician login. Computer is joined to the domain and user is made a local admin.

  11. After reboot program auto-runs again and gives option to install other software. A Mac version (written by Curtis Minns) has identical functionality.

More Related