Using Vista Client and Office System 2007 Desktops
BackBy Certification Magazine — 14 August 2008
These questions are based on 70-624: TS: Deploying and Maintaining Windows Vista Client and Microsoft Office System 2007 DesktopsMicrosoft
Self Test Software Practice Test
Objective: Deploy the 2007 Microsoft Office system.
Sub-objective: Install Office 2007.
Single answer, multiple-choice
You have created a network share, \\server1\share\Office2007, for Office 2007 installations. You have customized the setup files for the accounting and HR departments. You have created Accounting.msp and HR.msp files and stored them in a folder in the \\server1\share\installation folder. After a number of installations are performed from the installation point, you are informed by a user in the accounting department that installations from the installation point have failed. You check the installation point and notice a number of files are missing. You want to ensure such a problem does not occur in the future.
What should you do?
A. Ensure permissions to all source folders are set as read-only.
B. Ensure the \Office2007 folder has read-only permissions and the Accounting.msp and HR.msp files have read-write permissions.
C. Exclude all users from the Administrators group on their local computers.
D. Remove the Accounting.msp and HR.msp files from the network share and copy them onto users' desktops.
Answer:
A. Ensure permissions to all source folders are set as read-only.
Tutorial:
You should ensure permissions to all source folders in the installation point are set as read-only. If you do not, users will have the privileges to delete contents within the installation point. When you are defining the installation point, you should not define the installation point in the root of the server. As the scenario describes, you have defined the installation folder in the \share folder. You will need to create the customization files, which in this case are Accounting.msp and HR.msp. These installation files are customized per your requirements. You can use the Office Customization Tool to customize the installation files, which need to be present in the root folder of the server.
You should not set read-write permissions on the HR.msp and Accounting.msp files. Both files are source files and need to be secured from any modifications. You should set both files as read-only.
You should not ensure all users are excluded from the Administrators group on their local computers. If you exclude the users from the Administrators group on their local computers, users will not be able to perform the installation.
You should not remove the Accounting.msp and HR.msp files from the network share and copy them onto users' desktops. For users to initiate the installation from the installation point, you need to copy the customized installation files to a folder in the installation point. In this scenario, the \installation folder under the \share folder is the defined folder.
Reference:
Office System > 2007 Office Resource Kit > Deployment for the 2007 Office release > Preparing to deploy the 2007 Office system > Create a network installation point for the 2007 Office system
Objective: Configure Windows Vista automated installation settings.
Sub-objective: Manage Windows Vista catalogs.
Single answer, multiple-choice
You are a desktop support technician for your company. You are in the process of deploying the Windows Vista operating system on all client computers. You create a Windows Vista image to deploy Windows Vista on the target computers. You need to add one or more language packs to an existing offline Windows Vista image.
Which utility you should use?
A. The Windows System Image Manager (SIM).
B. The ImageX command-line utility.
C. The Package Manager utility.
D. The INTLCFG.EXE utility.
Answer:
C. The Package Manager utility.
Tutorial:
To add one or more language packs to an existing offline Windows Vista image, you should use the Package Manager utility. Using this utility, you can add one or more language packs to a Windows Vista image. You can use Package Manager to install, uninstall, configure and update Window Vista features. In addition, you can use an unattended installation file to update Windows Vista features on an offline Windows Vista computer.
Windows SIM will not help you add language packs to or remove language packs from an existing Windows Vista image. Windows SIM is used to create an answer file for Windows Vista unattended installations. The SIM also is used to generate a new catalog of settings after you edit an existing image.
The ImageX command-line utility will not help you add language packs to or remove language packs from an existing Windows Vista image. The ImageX command-line utility is run from the command prompt or from the Windows Preinstallation Environment (PE) and is used to capture a volume image to a Windows Imaging (WIM) Format file.
The INTLCFG.EXE utility will not help you add language packs to or remove language packs from an existing Windows Vista image. When you add or remove language packs to an existing Windows image, you use the INTLCFG.EXE utility to recreate the LANG.INI file. This file includes the list of available language packs included in a Windows image.
References:
Microsoft TechNet > Windows Vista Technical Library > Windows Vista: Deployment > Windows Automated Installation Kit (Windows AIK) User’s Guide> Windows Preinstallation Phases > Phase 3: Preinstallation Customization > Customization How-To Topics > Manage Language Packs for Windows > Add a Language Pack to a Windows Image > Install a Language Pack to an Offline Image > To install a language pack with Package Manager
Microsoft TechNet > Windows Vista Technical Library > Windows Vista: Deployment > Windows Automated Installation Kit (Windows AIK) User’s Guide> Deployment Tools Technical Reference > Package Manager Technical Reference > Package Manager Command-Line Options
Objective: Deploy Windows Vista.
Sub-objective: Deploy Windows Vista using ZTI.
Single answer, multiple-choice
You are a desktop support technician for your company. You plan to deploy Windows Vista using Zero Touch Installation (ZTI) on all client computers. You install System Management Server (SMS) 2003 on a site server. What should you do next?
A. Install Business Desktop Deployment (BDD) 2007 on the SMS 2003 site server.
B. Create a BDD 2007 deployment point on the SMS 2003 site server.
C. Install Windows Deployment Service (WDS) on the SMS 2003 site server.
D. Install the SMS 2003 operating system deployment (OSD) Feature Pack on the SMS 2003 site server.
Answer:
D. Install the SMS 2003 operating system deployment (OSD) Feature Pack on the SMS 2003 site server.
Tutorial:
After installing SMS 2003 on a site server, you should install the SMS 2003 OSD Feature Pack on the SMS 2003 site server. If your company's network has more than one site server, you should install SMS 2003 Service Pack (SP) 1 on all site servers to support the SMS 2003 OSD Feature Pack.
For ease of administration and to leverage the inheritance of the SMS hierarchy, you should deploy the SMS OSD on the central or top primary site server in the hierarchy. This ensures the SMS OSD can be easily managed with the least amount of administrative effort. You also must install the version of the SMS Administrator Console included on the SMS 2003 SP1 media.
After installing SMS 2003 on a site server, you should not install Business Desktop Deployment (BDD) 2007 on the SMS 2003 site server. You should install BDD 2007 on the SMS 2003 site server after installing the SMS 2003 OSD Feature Pack.
After installing SMS 2003 on a site server, you should not create a BDD 2007 deployment point on the SMS 2003 site server. You should create the BDD 2007 deployment point by using the Deployment Point Wizard in Deployment Workbench after installing BDD 2007 on the site server.
After installing SMS 2003 on a site server, you should not install Windows Deployment Service (WDS) on the SMS 2003 site server. WDS is an enhanced version of Remote Installation Services (RIS). WDS also is used to perform an unattended Windows operating system installation using network boot Pre-Boot Execution Environment (PXE) in Lite Touch deployment.
Reference:
TechNet > TechNet Library > Deployment > Desktop Deployment > BDD 2007 Documentation > Information Center: Documentation > Deployment Process > Zero Touch Installation Guide > Preparing the Deployment Environment
Objective: Use Business Desktop Deployment Workbench.
Sub-objective: Configure a distribution point in BDD 2007 Workbench.
Single answer, multiple-choice
You need to install multiple Office 2007 products from a distribution point that is located on a server named App1. Users should be able to install the respective Office 2007 product. Users who wish to install Office 2007 Enterprise Edition and Office 2007 Professional, should be able to install it. What should you do?
A. Create a config.xml file and place it in the \Updates folder.
B. Create a config.xml file and place it in the product specific folder.
C. Create a custom.msp file and place it in the \Updates folder.
D. Create a custom.msp file and place it in the root of the installation point.
Answer:
B. Create a config.xml file and place it in the product specific folder.
Tutorial:
You should create a config.xml file and place it in the product specific folder. By doing this, users will be able to install the specific product of the Office 2007 suite. For users who wish to install Office 2007 Enterprise, you would need to place the config.xml in the Enterprise.WW folder.
The Config.xml file can be used to customize various aspects of the installation. As another example, if you configure two Office 2007 network installation points on Server1 and Server2, you could edit the Config.xml file to specify the paths to the network installation points. Configuring two network installation points helps in fail-out situations. If one network installation point goes off-line, the other will be available to install Office 2007 on the client computers.
If you want to customize the setup installation, you need to edit the config.xml file and place it in the \Updates folder on the distribution point. A product specific installation will not work when placed in the \Updates folder, which is the default.
Creating a custom.msp and placing it in the \Updates folder or the root of the installation point will not provide the desired results.
Reference:
TechNet > TechNet Library > Office > Office System > Office Desktop Applications > 2007 Office Resource Kit > Planning and architecture > Evaluating the new Setup architecture > Streamlined customization model for the 2007 Office system
Objective: Application Compatibility Toolkit.
Sub-objective: Install and configure ACT 5.
Single answer, multiple-choice
You are a desktop engineer for Verigon Corp. The company network consists of Windows XP client computers. The company uses various applications that are developed and customized by internal developers.
You plan to upgrade the client computers on your company network to Windows Vista. Before upgrading all client computers to Windows Vista, you perform a pilot upgrade to Windows Vista on a test computer to enable the developers to test and identify the compatibility and security issues for applications.
Which tool should the developers use to test the custom applications?
A. Microsoft Application Verifier.
B. Microsoft Standard User Analyzer.
C. Application Compatibility Toolkit.
D. Program Compatibility Assistant.
Answer:
C. Application Compatibility Toolkit.
Tutorial:
The developers should use the Application Compatibility Toolkit. This can be used to test and fix application compatibility issues with Vista. It includes tools that create an application compatibility fix. Once a long-term solution for the issue is in place, you can remove the fix with the Uninstall a Program option in Control Panel.
The developers should not use the Microsoft Standard User Analyzer tool to test the custom applications. The Microsoft Standard User Analyzer tool assists developers in identifying issues that can prevent an application from running successfully. However, this tool only identifies issues related to applications that are prevented from running as a standard user. Before you install the Microsoft Standard User Analyzer tool on a computer, you must install the Microsoft Application Verifier tool.
The developers should not use the Program Compatibility Assistant tool to test the custom applications. This tool automatically detects an older program that has a compatibility problem on a Windows Vista computer. The Program Compatibility Assistant tool also provides a fix for the compatibility problem or provides an option to check for a possible solution.
The developers should not use the Microsoft Application Verifier tool to test the custom applications. This is an older tool used to run several compatibility tests that software developers find useful when designing applications for Windows XP.
References:
TechNet > TechNet Library > Windows > Windows Vista > Windows Vista Service Life-Cycle Management > Microsoft Application Compatibility Toolkit 5.0
http://technet.microsoft.com/en-us/library/cc507852.aspx
Microsoft TechNet > Microsoft Windows Vista Technical Library > Windows Vista: Management and Operations > Understanding and Configuring User Account Control in Windows Vista
Industry News
Spammers Use Google Sites to Host Spam
MessageLabs' July Intelligence Report highlights spammers’ continuing abuse of Google’s hosted applications.
Read more http://www.certmag.com/read2.php?in=3254
In Slumping Economy, Colleges Forced to Keep Enrollment Numbers Up
The U.S. economy is forcing colleges and universities to find new tactics to accommodate students' growing need for financial aid and to maintain enrollment numbers.
Read more http://www.certmag.com/read2.php?in=3244
IBM Embedded Software Gives Mobile Customers Access to Lotus E-Mail
To power businesses and consumers with mobile Web computing capabilities, IBM has expanded its relationship with wireless carriers to provide broader e-mail access to customers who use IBM Lotus Notes and Domino on their devices.
Read more http://www.certmag.com/read2.php?in=3245
Viewed 7161 times.
