Download
active directory n.
Skip this Video
Loading SlideShow in 5 Seconds..
Active Directory PowerPoint Presentation
Download Presentation
Active Directory

Active Directory

221 Vues Download Presentation
Télécharger la présentation

Active Directory

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Active Directory Software Installation

  2. Windows Installer • Service for managing installed applications • Installed on Windows 2000 PCs and started as required • Can be installed on Windows NT, 95 and 98 PCs • Some programs will install it for you • E.g. Office 2000/XP, Technet

  3. Features of Windows Installer • Runs under local System account • Supports unattended installation • Prevents conflicts with shared DLLs • Repairs corrupted applications (e.g. missing files) • Removes applications • Supports on-demand installation of features

  4. Requirements for Deploying an Application • Following three methods can be used • Obtain or create native Windows Installer package • Repackage an application • Create .zap file

  5. Native Windows Installer Package • Database file (*.msi) containing installation and removal instructions • Generally provided by software developer • Typical components • Summary • Files • Installation instruction database • Optional modifications

  6. Creating a Windows Installer Package • Authoring Tools to create native Windows Installer Packages • WISE Solutions Inc. • InstallShield • Repackaging Tools • Use before/after snapshot techniques to create installer package • Seagate Software WinInstall LE

  7. Package Modifications • Modifications allow customization of package to suit local requirements but using single set of installation files • E.g. Office

  8. ZAP Files • Use application’s own setup program to deploy • Various limitations • Can only be published to users, not assigned (more later) • Cannot be installed with elevated privileges • Cannot be installed without user intervention • Cannot repair themselves • Cannot be rolled back

  9. Steps to Deploying Software • Create a software distribution point • Choose a method of deployment • Implementing deployment through Group Policy

  10. Create the Software Distribution Point • Create shared folder on server • Set permissions so that users have read access • Copy Windows Installer packages or application files and .zap file into folder

  11. Choose a Deployment Method • Assign Applications to Computers • Automatically installed when computer starts • Appear on Start Menu for all users • Cannot be removed using Add/Remove Programs (except Administrators) • Use if application is required by anyone using that computer

  12. Choose a Deployment Method • Assign Applications to Users • Appear on user’s Start Menu or Desktop after logon • Installed when started for the first time • Will reappear automatically at next logon if removed using Add/Remove Programs • Installed through document association • Use if application is required by the user

  13. Choose a Deployment Method • Publish Applications to Users • Installed and removed by user via Add/Remove Programs • Installed through document association • Use if programs are not always required by users, but may be useful to them

  14. Implementing Deployment Through Group Policy • Create a new GPO or modify an existing one • Computer Configuration/Software Settings/Software Installation • To assign to computer • User Configuration/Software Settings/Software Installation • To publish or assign to user

  15. Group Policy Deployment Options • If using modifications, must choose “Advanced” option when creating the software installation package • Cannot change later • Other options available through “Advanced” option, or through package properties • E.g. packages upgraded; whether upgrade is required or optional • Whether application appears in Add/Remove Programs

  16. Removing Software • Remove the package in GPO • All Tasks/Remove • Two options • Immediately uninstall from all users and computers • Allow users to carry on using but do not allow new installations

  17. Design Considerations • Software required by different groups of users may impact on OU design • Need to decide whether to assign or publish; whether assigned to computers or users

  18. References • How to Publish non-MSI Programs with .zap Files • http://support.microsoft.com/support/kb/articles/Q231/7/47.ASP