in black and white
Main menu
Home About us Share a book
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

MCSE Windows XP Professional For Dummies - Weadock G.

Weadock G. MCSE Windows XP Professional For Dummies - Hungry Minds , 2002. - 169 p.
Download (direct link): windowsxpprofesfordu2002.doc
Previous << 1 .. 136 137 138 139 140 141 < 142 > 143 144 .. 145 >> Next

3. A, B, and C. Choice D would be true if it said 'Windows 3.1' instead of 'Windows 98,' but Windows 98 can understand computer names that are longer than the 8 + 3 convention allows. Objective: Configure, manage, and troubleshoot account settings (Chapter 10).
4. B. Windows XP doesn't ask you about performing the file system upgrade, nor does it check to verify that your currently installed version of NT can handle NTFS 5.1. Choice C isn't correct because it's not just the boot sector that's causing the problem, it's the whole doggoned file system. And choice D just isn't true. Objective: Configure file systems by using NTFS, FAT32, or FAT (Chapter 3).
5. A. The Remote Installation Preparation Wizard also goes by the name of its executable file, RIPREP.EXE, which resides on the Windows 2002/2000 server where you've installed the RIS service. Objective: Perform an unattended installation of Windows XP Professional by using Remote Installation Services (RIS) (Chapter 4).
6. B. The network PC gets its own IP address, and that of the RIS server, via DHCP. DNS and Active Directory are necessary for Windows XP to locate the directory service, computer accounts, and the RIS server itself. But those various servers are visible to all five PCs, so the problem must be the BIOS. Microsoft advises setting the network device as the first boot device, not just one in a list of boot devices. Objective: Perform an unattended installation of Windows XP Professional by using Remote Installation Services (RIS) (Chapter 4).
7. C. The regular Users group in Windows XP is more restrictive than the regular Users group in Windows NT 4.0 Workstation. Applications written for Windows XP or 2000 should work fine with the built-in Users group, but older applications may need users to be members of the built-in Power Users group. Objective: Implement, configure, manage, and troubleshoot user and group rights (Chapter 10).
8. A, B, and C. To browse the network for the printer, leave its name blank in the wizard and click the Next button. You can't find a printer in the wizard by using its security ID. Objective: Connect to an Internet printer (Chapter 7).
9. A. If the controller doesn't appear in Device Manager, Windows XP isn't seeing the controller, much less the speakers. Because the controller is typically a motherboard device, the best guess is that it isn't enabled in the BIOS, although it's possible that the motherboard has a hardware problem, too. Because USB is a Plug and Play bus, Windows should autodetect it, therefore running the Add New Hardware Wizard would typically not be necessary. Objective: Install, configure, and manage USB devices (Chapter 8).
10. C. No command exists for copying a user account in the User Accounts control panel or in the Local Users and Groups console (which you access via the control panel's Advanced tab). By renaming the account and immediately choosing a new password, you create a secure account with the same security identifier as the old one - and therefore all the same access permissions, group memberships, and rights. Objective: Configure and troubleshoot local users and groups (Chapter 10).
11. D. Choice A isn't true. As for B, you don't need File and Printer Sharing in order to make a PC accessible via Remote Desktop, and anyway ICF doesn't automatically detect that service and configure itself to forward incoming unsolicited packets. The option specified by choice C doesn't exist. As for D versus E, ICF is running on the PC that connects to the Internet, not the PC that you want to connect to. Objective: Configure, manage, and troubleshoot an Internet connection firewall (Chapter 13).
12. C. You can't simply back up the Registry by checking the folder that contains the Registry files (which by the way is C:\WINNT\SYSTEM32\ CONFIG) because the files are in use by the system. The System State backup does back up the Registry, and it lets you specify any target folder. The Emergency Recovery Diskette Wizard is gone as of Windows XP, having been replaced (sort of) by the Automated System Recovery Wizard. Objective: Recover system state data and user data by using Windows Backup (Chapter 15).
13. A and B. In fact, the only two 'real' root keys are HKLM and HKU. HKEY_DYN_DATA isn't present in Windows XP. Objective: Monitor, configure, and troubleshoot I/O devices (Chapter 8).
14. B. The Local Security Policy console in the Administrative Tools folder is what you want; note that the policies you set under the Account Policies node apply to all local user accounts on that computer. You can't get to the account policy settings via the Computer Management console or the User Accounts control panel, although you can set some user-specific password options there, such as whether to prevent a given user from changing his or her password. Objective: Configure, manage, and troubleshoot account policy (Chapter 10).
15. C. You may also want to remember that the order of precedence for the processing of policies in Windows XP is, from lowest to highest, local - site - domain - organizational unit. Incidentally, no File?Save command exists in the Local Security Policy console. Objective: Configure, manage, and troubleshoot local Group Policy (Chapter 11).
Previous << 1 .. 136 137 138 139 140 141 < 142 > 143 144 .. 145 >> Next