The MCSE 2003/8 encompasses applicant and server operating systems as able-bodied as their administration and deployment aural action calibration environments. Network assay and architecture application Microsoft technologies is an capital accountable alveolate throughout the MCSE syllabus, ensuring that all MCSE acceptance accept a absolute compassionate of Microsoft technologies and services.
The following are the best practices for deploying software with Group Policy:
Assign or publish just once per GPO A Windows Installer package should be assigned or published no more than once in the same GPO. For example, if you
assign Office to the computers affected by a GPO, then do not assign or publish it to users affected by the GPO.
Assign or publish close to the root in the Active Directory hierarchy Because Group Policy settings apply by default to child Active Directory
containers, it is efficient to assign or publish by linking a GPO to a parent OU or domain. Use security descriptors—access control entries (ACEs)—on the GPO for finer control over who receives the software.
Make sure Windows Installer packages include modifications before they are published or assigned Remember that modifications are applied to packages at the time of assignment or publication. Therefore, you should make sure the Modifications tab in the Properties dialog box for the package is set up as you intend before you click OK. If you neglect to do this and assign or publish a modified package before you have completely configured it, you must either remove the software and republish or reassign it or upgrade the software with a completely modified version.
Specify application categories for your organization It’s easier for users to find an application in Add Or Remove Programs in Control Panel when you use
categories.
Take advantage of authoring tools Developers familiar with the files, registry entries, and other requirements for an application to work properly can author native Windows Installer packages using tools available from various software vendors.
Repackage existing software You can use commercially available tools to create Windows Installer packages for software that does not include natively
authored .msi files. These work by comparing a computer’s state before and after installation. For best results, install on a computer free of other application software.
Set properties for the GPO to provide widely scoped control This spares administrative keystrokes when assigning or publishing a large number of packages with similar properties in a single GPO—for example, when all the software is published and it all comes from the same SDP.
Set properties for the Windows Installer package to provide fine control Use the package properties for assigning or publishing a single package.
Know when to use Group Policy Software Installation and Systems Management Server (SMS) Use Group Policy Software Installation for simple software installation and deployment scenarios. Use SMS when scheduling, inventory, reporting, status, and support for installation across a wide
area network (WAN) is required.
When an object is created, the user creating an object automatically becomes its owner. Administrators create and own most objects in Active Directory and on network servers when installing programs on the server. Users create and own data files in their home directories and some data files on network servers. The owner controls how permissions are set on the object and to whom permissions are granted.
Ownership can be taken by
An administrator. By default, the Administrators group is given the Take Ownership Of Files Or Other Objects user right. User rights are discussed in Chapter 13,”Administering Security with Group Policy.”
Any user or group who has the Take Ownership permission on the object.
A user who has the Restore Files And Directories user right.
In Windows Server 2003, quotas can be specified in Active Directory to control the number of objects a security principal (user, group, or computer) can own in a given directory partition. Active Directory quotas can help prevent the denial of service that can occur if a security principal creates objects until the affected domain controller runs out of storage space. Domain Administrators and Enterprise Administrators are exempt from quotas. In some cases, a security principal might be covered by multiple quotas such as a quota assigned to a user and a quota assigned to a group to which the user belongs. In this case, the effective quota is whichever is the largest quota assigned to the security principal.
If a security principal is not assigned a quota, a default quota on the partition governs the security principal. If a default quota is not explicitly set for the partition, then the partition has no limit. For quotas to be effective on a domain directory partition, all domain controllers in the domain must be running Windows Server 2003. For quotas to be effective on the configuration partition, all domain controllers in the forest must be running Windows Server 2003. The schema partition has no quotas.
To create and maintain Active Directory quotas, you use the dsadd quota, dsmod quota, and dsquery quota commands. For detailed information about using these commands, refer to Windows Server 2003 Help.
There simply isn’t a better source to learn Microsoft questions and answers than a Test-King Microsoft MCSE 2003 boot camp. The complete training you receive using these excellent products will guarantee your success in the Microsoft MCSE 2003 actual test.
Recent Articles