Evernote Flashcards
(166 cards)
You are using the Windows Automated Installation Kit (Windows AIK) to deploy Microsoft Windows 7 in your organization. You configure a technician computer and install the Windows AIK.
You need to create an automated answer file that you can use to perform an automated installation on your reference computer.
What should you do first?
- Copy a Windows image (WIM) file to the reference computer.
- Copy a Windows image (WIM) file to the technician computer.
- Launch Windows System Image Manager (SIM) on the technician computer.
- Run Sysprep on the reference computer.
Copy a Windows image (WIM) file to the technician computer.
You need to copy a WIM file to the technician computer. After you do this, you will use Windows SIM to create an answer file based on that image. You can then copy the answer file to a USB flash drive (UFD) to control the installation on the reference computer. Installation on the reference computer will require the Windows installation DVD and automated answer file.
You should not copy a WIM file to the reference computer. You will install from an image to create the reference computer, but you must first create the answer file.
You should not launch Windows SIM on the technician computer. You will use Windows SIM to create the answer file, but not until after you have copied an image to the technician computer.
You should not run Sysprep on the reference computer. You would not need to do this until after you have installed and configured the reference computer to prepare it for image creation.
You are configuring a small number of remote client computers running Microsoft Windows 7. The client computers are configured to use IPv6 for communication over the Internet. Your local network is configured to use IPv4 and IPv6.
You need to configure end-to-end DirectAccess to give remote clients access to resources on your intranet. Some devices do not support IPv6. You need to ensure that DirectAccess clients can access these devices.
What should you do?
- Configure the remote clients to use IPv4 only.
- Configure the remote clients to use IPv4 and IPv6.
- Deploy multiple DirectAccess servers.
- Deploy a Network Address Translation-Protocol Translation (NAT-PT) device.
Deploy a Network Address Translation-Protocol Translation (NAT-PT) device.
You should deploy a NAT-PT device. This provides DirectAccess clients access to the IPv4-only devices without having to make other changes to the network, clients, or resource servers. The NAT-PT device provides a gateway between the DirectAccess server and the IPv4-only resources.
DirectAccess clients connect to the network using IP Security (IPSec) through one or more DirectAccess servers. If the target network is not configured to support IPv6 traffic, you must use the 6to4 and Teredo IPv6 transition technologies to support DirectAccess traffic across an IPv4 network. Because the network is configured to support both IPv4 and IPv6, this is not required in this situation.
You should not configure remote clients to use IPv4 only or IPv4 and IPv6. This does nothing to get you closer to a solution. DirectAccess requires client computers running Windows 7 and connecting to the target network using IPv6.
You should not deploy multiple DirectAccess servers. Even if you deploy multiple servers, each would provide the same service to the network, providing IPv6 connections for DirectAccess clients. It does nothing to add support for resources that support IPv4 only.
You manage client computers for your organization.
You need to upgrade a computer running Microsoft Windows Vista to Windows 7. The target computer exceeds the minimum hardware requirements for Windows 7. You need to keep the requirements to complete the upgrade to a minimum. You insert the Windows 7 installation DVD.
What should you do next?
- Run Windows Easy Transfer.
- Run a custom installation.
- Run a default installation.
- Run the User State Migration Tool (USMT).
Run a default installation.
You should run a default installation. Setup should launch automatically when you insert the installation DVD. When you run the installation, you will be prompted to upgrade the computer by default.
You should not run Windows Easy Transfer. Windows Easy Transfer is used to transfer files and settings between computers. This is not necessary in this scenario.
You should not run a custom installation. A custom installation is more complicated to run than a default installation and is not required.
You should not run USMT. USMT is used to migrate user profiles, application settings, operating system settings, and so forth to a computer after a clean installation.
You upgraded a computer to Microsoft Windows 7. Several folders on the computer were configured to use Encrypted File System (EFS) encryption. Group Policy allows for self-signed certificates if a certificate authority (CA) is not available.
You need to ensure that all files and folders are encrypted using elliptic curve cryptography (ECC). In the Group Policy Public Key Policies, you configure the Elliptic Curve Cryptography policy to Require.
What else should you do?
- Configure the Elliptic Curve Cryptography policy to Allow.
- Deny the use of self-signed certificates.
- Decrypt encrypted files and folders and re-enable encryption.
- Shut down and reboot the computer.
Decrypt encrypted files and folders and re-enable encryption.
You should decrypt encrypted files and folders and then re-enable encryption. Setting Elliptic Curve Cryptography to Require requires ECC encryption for all new encryption, but files and folders encrypted under an earlier Windows version are still encrypted under RSA encryption.
You should not configure the Elliptic Curve Cryptography policy to Allow. This would allow the use of both ECC and RSA encryption for new encryption.
You should not deny the use of self-signed certificates. Self-signed certificates can be used for ECC encryption. Windows 7 supports 256-bit, 384-bit, and 531-bit ECC certificates.
You should not shut down and reboot the computer. This would force application of new Group Policy settings, but it does not change the existing files.
You have a computer running Microsoft Windows 7. Users access the computer using an account that is a member of the Users group.
SueS attempts to execute an application, but she receives access denied errors.
You need to enable SueS to execute the application.
What should you do?
- Select Run this program as an administrator on the Compatibility tab of the program.
- Add SueS to the Administrators group. Select Run this program as an administrator on the Compatibility tab of the program.
- Set the Compatibility mode to Windows XP on the Compatibility tab of the program.
- Create a shim and install it in the compatibility database.
Add SueS to the Administrators group. Select Run this program as an administrator on the Compatibility tab of the program.
You should add SueS to the Administrators group and select Run this program as an administrator on the Compatibility tab of the program. Windows 7 imposes stricter application security than earlier Windows operating systems. If an application needs administrator permission, you will need to enable the Run this program as an administrator option on the Compatibility tab of the program. However, a program can only run as an administrator if the user who is executing it is a member of the Administrators group. Therefore, you will need to add SueS to the Administrators group.
You should not only select Run this program as an administrator on the Compatibility tab of the program. You also need to add SueS to the Administrators group to permit permission elevation.
You should not set the Compatibility mode to Windows XP on the Compatibility tab of the program. The Compatibility mode allows you to configure an environment that emulates an older version of Windows when executing an application. However, it does not circumvent security restrictions.
You should not create a shim and install it in the compatibility database. You can create a shim and install it in the compatibility database to act as a layer of abstraction between an incompatible program feature and Windows 7. For example, if the program did not really require administrative permission, but checked for it, you could create a shim for the function that checks permission that always returns true. However, in this case, the application actually requires administrative permission, so you cannot correct the problem with a shim. You cannot use a shim to circumvent Windows 7 User Account Control (UAC).
A user complains of system problems after a printer device driver is updated on a computer running Microsoft Windows 7. The user did not notice any problems with the original printer driver. You have the user restart the computer, but the problem continues.
You need to correct the problem as quickly as possible. The user needs access to the printer.
What should you do?
- Disable the device through the Device Manager.
- Open the device properties and roll back the device driver.
- Manually reinstall the original device driver.
- Restart the computer and choose the Last Known Good Configuration.
Open the device properties and roll back the device driver.
You should open the device properties and roll back the device driver. This will force the computer to revert to the previous version of the device driver. Because the user did not notice any problems with the original device driver, this should correct the problem and leave the printer available to the user.
You should not disable the device through the Device Manager. This will leave the printer unavailable. You may be prompted to restart the computer after disabling a device driver.
You should not manually reinstall the original device driver. If the original device driver shipped with Windows 7, you might not have the file available for manual installation. Also, this option is more time-consuming than rolling back the driver.
You should not restart the computer and choose the Last Known Good Configuration. This would not make any difference in this situation. Because the computer was able to successfully restart with the new device driver, the last known good configuration has been updated to include that device driver.
Your network is configured as a central office and two remote branch offices. Each office is configured as two subnetworks. You want to implement Hosted Cache mode BranchCache to reduce communication over remote links.
You need to determine the minimum number of Hosted Cache servers required to implement BranchCache throughout the network. You need to deploy only required servers.
What should you do?
- Deploy one Hosted Cache server.
- Deploy two Hosted Cache servers.
- Deploy four Hosted Cache servers.
- Deploy five Hosted Cache servers.
Deploy two Hosted Cache servers.
You should deploy two Hosted Cache servers, one for each remote office. The content server (or servers) will be deployed in the central office. Each branch office requires its own Hosted Cache server. The Hosted Cache server can provide content for all of the subnets configured in the remote office.
You should not deploy one Hosted Cache server. You must have at least one in each remote office.
You should not deploy four or five Hosted Cache servers. There is no need to deploy multiple Hosted Cache servers in each of the remote offices. There is also no need to deploy one in the central office.
You set up a computer running Microsoft Windows 7 and custom applications. You plan to use the computer for testing applications.
You need to be able to restore back to the custom installation quickly if problems occur. You need to be able to control the recovery through the Windows Recovery Environment (RE) using Windows RE manual tools.
First, you need to create the recovery image.
What should you do?
- Run ImageX from a command prompt.
- Use Windows Backup.
- Open the Windows RE menu during startup.
- Launch Windows RE from the installation DVD.
Use Windows Backup.
You should create a full backup using Windows Backup. You need to create the backup on a disk partition other than the system’s startup partition. For example, you can create the backup on an external hard disk or in a network location.
You should not run ImageX from a command prompt. ImageX is used to create a Windows installation image (WIM) file. In this scenario, you need a backup file rather than an image file.
You should not launch Windows RE. You use Windows Backup, not Windows RE, to create the copy. When you need to restore the computer, you would then launch Windows RE (from the hard disk or installation DVD) and run a complete PC restore from the manual tools menu.
You have a computer running Microsoft Windows Vista Ultimate.
You are planning to upgrade the computer to Windows 7.
Which edition or editions of Windows 7 support a direct upgrade from Windows Vista Ultimate?
- Professional and Ultimate
- Enterprise and Ultimate
- Professional, Enterprise, and Ultimate
- Ultimate
Ultimate
You can only directly upgrade from Windows Vista Ultimate to Windows 7 Ultimate. Supported upgrade paths do not affect the availability of upgrade pricing. You can purchase Windows 7 for an upgrade price even if your current edition of Windows Vista does not support an upgrade to the edition of Windows 7 you purchase. However, you would need to migrate settings and perform a Custom installation instead of performing an upgrade.
You cannot directly upgrade to Windows 7 Professional. Only Windows Vista Business can be directly upgraded to Windows 7 Professional.
You cannot directly upgrade to Windows 7 Enterprise. Only Windows Vista Business and Windows Vista Enterprise can be directly upgraded to Windows 7 Enterprise.
You are configuring a computer running Microsoft Windows 7 for use as a public terminal.
The computer is configured to log on automatically as a local standard user. You want to prevent users from being able to run administrative programs and make changes to the computer.
What should you do?
- Disable User Account Control (UAC).
- Disable Secure Desktop.
- Configure local security policies for standard users to automatically deny elevation requests.
- Configure User Account Control (UAC) prompts to elevate without prompting.
Configure local security policies for standard users to automatically deny elevation requests.
You should configure local security policies for standard users to automatically deny elevation requests. This policy is used to prevent user privilege escalation when a standard user attempts to run an administrator application, effectively preventing standard users from running administrator applications. An administrator application is one that requires administrator privileges to make changes to a computer.
You should not disable UAC. You can disable UAC by setting the UAC Control Panel slider to Never notify. Users or applications would be able to make changes to the computer without any notification displaying.
The UAC Control Panel slider supports four settings:
* Always notify on every system change (High) - Secure desktop notification is displayed if changes are attempted by a user or application.
* Notify me only when programs try to make changes to my computer (Medium) - User changes, such as changing Windows settings, do not generate notifications. Attempts made by applications by computers do generate a Secure Desktop notification.
* Notify me only when programs try to make changes to my computer, without using the Secure Desktop (Low) - This is the same as the medium setting, except prompts appear on the normal desktop instead of using Secure Desktop.
* Never notify (Off) - UAC is disabled.
You should not disable Secure Desktop. This causes notifications to display on the normal desktop instead of secure desktop, but users can still choose to make modifications.
You should not configure UAC prompts to elevate without prompting. This is a local security policy setting and applies only when a user is logged on as a local administrator. The setting causes administrator applications and setup programs to automatically run under the administrator security context, without being blocked or displaying any warning notification, when the user is logged on as a local administrator.
You are defining application restriction policies for computers running Microsoft Windows 7.
You create application execution rules through AppLocker. You need to determine how these rules will impact standard users. You need to have minimal impact on users’ access to applications while testing your application rules.
What should you do?
- Configure rule enforcement mode as Not configured.
- Create and apply default application rules.
- Create publisher rules for each of the applications tested.
- Configure rule enforcement mode as Audit only.
Configure rule enforcement mode as Audit only.
You need to configure rule enforcement mode as Audit only. This lets you determine what the impact of the rules will be without directly affecting users’ access to applications. After you have determined if the rules work as expected, you can change the rule enforcement mode to Enforce rules.
You should not configure rule enforcement mode as Not configured. This is the default rule enforcement mode. This setting does not audit the impact of the rules on users. Also, if any linked Group Policy object (GPO) already exists, it will apply instead of the AppLocker rules.
You should not create and apply default application rules. Default rules enable all users to run the programs in the default Program Files folder and in the Windows folder. They are not used for testing custom rules.
You should not create publisher rules for each of the applications tested. A publisher rule is used to enable rules to apply to an application after an upgrade rather than having to create a new rule each time you upgrade an application.
Your environment includes several Windows 7 computers that have WS-Management protocol enabled. Your technician computer is also running Windows 7.
You need to execute a PowerShell command on all the computers from your technician computer.
What should you do?
- Run Enter-PSSession.
- Run Invoke-Command.
- Run Enable-PSRemoting.
- Run Invoke-Expression.
Run Invoke-Command.
You should run Invoke-Command. The Invoke-Command PowerShell cmdlet allows you to list the computers on which to run a specific command. The command is then executed on the computers in a “fan-out” configuration. Invoke-Command requires that WS-Management protocol be enabled. You enable WS-Management by running the Enable-PSRemoting cmdlet.
You should not run Enter-PSSession. The Enter-PSSession cmdlet is used to initiate an interactive PowerShell session with one computer. During an interactive session, you can execute multiple commands.
You should not run Enable-PSRemoting. You use Enable-PSRemoting to enable WS-Management on a computer. The computers already have WS-Management enabled.
You should not run Invoke-Expression. The Invoke-Expression cmdlet can only be used to execute commands on a local computer.
You create a weekly system image backup of a Microsoft Windows 7 computer and store the backup on a DVD.
The computer boots, but Windows 7 will not start.
You need to restore the system image.
What should you do?
- Boot from the DVD that contains the system image backup.
- Boot from a DVD that contains Windows Preinstallation Environment (PE)
- Press the F8 key as the computer restarts and select Repair your system.
- Start the computer by using Recovery Console.
Press the F8 key as the computer restarts and select Repair your system.
You should press the F8 key as the computer restarts and select Repair your system. Pressing the F8 key during startup causes the Advanced Boot Menu to be displayed. You can select Repair your system to display the System Recovery options menu. One choice on this menu is to restore the computer using the system image backup. All changes made since the backup will be lost unless they can be recovered from other backups. Another option is to boot from the installation DVD or a system repair disc.
You should not boot from the DVD that contains the system image backup. The system image backup is not bootable. If you want to create a bootable DVD that can be used for recovery, you need to create a system repair disc.
You should not boot from a DVD that contains Windows PE. Windows PE is used when installing Windows 7 from an installation image, not when recovering to a system image backup.
You should not start the computer by using Recovery Console. Recovery Console was used in Windows XP to allow you to run certain commands. It has been replaced by the System Recovery options, which provide more robust tools for troubleshooting and resolving a problem.
You have a Microsoft Windows 7 computer.
You need to prevent the Recycle Bin from being displayed on the desktop.
What should you do?
- Right-click the Recycle Bin icon and choose Properties.
- Right-click the Desktop and choose Personalize.
- Right-click the Desktop and display View options.
- Right-click the Desktop and choose Gadgets.
Right-click the Desktop and choose Personalize.
You should right-click the Desktop and choose Personalize to open Personalization in the Control Panel. From the Personalization window, you can select Change desktop icons to display a dialog box that lets you check and uncheck default desktop icons, such as Recycle Bin.
You should not right-click the Recycle Bin icon and choose Properties. The Recycle Bin Properties dialog box allows you to configure the amount of disk space the Recycle Bin can use and whether a confirmation dialog box should be displayed when a user empties the Recycle Bin.
You should not right-click the Desktop and display View options. The View menu allows you to change how the desktop icons are arranged and the icon size. You cannot remove individual icons by using the View menu.
You should not right-click the Desktop and choose Gadgets. Gadgets are mini-programs, such as Weather and Calendar, that you can display on the Desktop. In Windows Vista, gadgets could only appear on the Sidebar. The Recycle Bin is not a gadget.
You are configuring your network to support both IPv4 and IPv6. You are currently documenting assigned addresses.
A computer running Windows 7 has the following address:
FE80::2AA:FF:FE3F:2A1C
How is this address used?
- To communicate between subnets on the same network
- To provide a globally unique unicast address
- To provide loopback communications for testing
- To communicate with other hosts on the same subnet
To communicate with other hosts on the same subnet
The address is used to communicate with other hosts on the same subnet. This is an example of a link-local address, which is used like an Automatic Private IP Addressing (APIPA) IPv4 address and is used for local communication only. You can recognize the address as a link local address by the FE80 prefix. The remaining address values are taken from the computer’s Media Access Control (MAC) address.
The address is not used to communicate between subnets on the same network. This would require a site-local address, which would have a prefix of FEC0.
The address is not used to provide a globally unique unicast address. This would be an address in a format similar to the following:
2001:DB8:2A3C:F282:2AA:FF:FE3F:2A1C
The value 2001:DB8:2A3C is a global routing address for the site. F282 represents a subnet on that site. The remaining address value, 2AA:FF:FE3F:2A1C, identifies a unique host on that subnet, based on the MAC address.
The address is not used to provide loopback communications for testing. An address of ::1 is used for IPv6 loopback testing.
Your Microsoft Windows 7 computer is a domain member that has a wireless network adapter.
Your wireless router is configured to use Temporal Key Integrity Protocol (TKIP) encryption. It is not configured to use a pre-shared key.
You need to configure the computer’s wireless connection to use the strongest possible security.
Which security type should you use?
- WPA2-Personal
- WPA2-Enterprise
- 802.1x
- WPA-Personal
WPA2-Enterprise
You should use WPA2-Enterprise. The Wi-Fi Protected Access (WPA2) Enterprise security type supports either TKIP or Advanced Encryption Standard (AES) for an encryption protocol. When you use WPA2, you have the choice of using either an 802.1x server or a pre-shared key for authentication. In this scenario, you know that the access point does not have a pre-shared key. Therefore, the network must have an 802.1x server. WPA-Enterprise is another security type that supports 802.1x authentication and both TKIP and AES encryption. WPA2 is more secure than WPA, but it is not supported by older wireless access points.
You should not use WPA2-Personal or WPA-Personal. These security types require authentication using a pre-shared key.
You should not use 802.1x as the security type. The 802.1x security type only supports Wired Equivalent Privacy (WEP) encryption. It can use Microsoft Protected Extensible Authentication Protocol (PEAP) or certificate authentication, so it does not require a pre-shared key.
You upgrade a computer running Microsoft Windows XP to Windows 7. You use Windows Easy Transfer to transfer files and settings to the new installation.
You need to make the applications that were running on the computer before you installed Windows 7 available to the computer’s user.
What should you do?
- Run User State Migration Tool (USMT).
- Reinstall the user applications.
- Reboot the computer.
- Run the BCDedit command.
Reinstall the user applications.
You should reinstall the user applications. Windows 7 does not support a direct upgrade path from Windows XP. After installing Windows 7, you must reinstall any applications that you still want to have available.
You should not run USMT. USMT is used to migrate user profiles, application settings, operating system settings, and so forth to a computer after a clean installation. In this situation, it does not migrate user applications.
You should not reboot this computer. This does not do anything to make the applications available.
You should not run the BCDedit command. BCDedit lets you manage the boot options in a multiple-boot installation and has nothing to do with migrating application support.
A Microsoft Windows 7 computer is configured to use IPv6. The computer receives its IP configuration from a Dynamic Host Configuration Protocol (DHCP) server.
The router normally used to reach a branch office fails. You need to configure the computer to use a different route.
Which utility should you use?
- Ipconfig
- Netsh
- Pathping
- Tracert
Netsh
You should use Netsh. The Netsh interface ipv6 command can be used to view and modify the IPv6 routing table.
You should not use Ipconfig. The Ipconfig utility can be used to view IPv4 and IPv6 configuration settings, to release and renew IPv4 or IPv6 addresses, and to flush the Domain Name System (DNS) cache. It cannot be used to modify the routing table.
You should not use Pathping. The Pathping utility is used to test connectivity. It returns the addresses of each router along the path to a destination.
You should not use Tracert. The Tracert utility is used to test connectivity. It returns information about the time it takes to traverse each hop to a destination, as well as the IP address of each router along the path.
You have a Windows 7 computer in a homegroup. There is also one Windows Vista computer on the network. The Windows 7 computer contains files that should be accessible for Read access by all other users in the homegroup. The files are located in the FamilyInfo folder in your My Documents folder.
You need to enable other users in the homegroup to access the folder.
What should you do?
- Select the FamilyInfo folder and choose Share with | Homegroup (Read).
- Move the FamilyInfo folder to the Public Documents library.
- In Advanced Sharing, grant Everyone Read access.
- In Advanced Sharing, grant Homegroup Read access.
Select the FamilyInfo folder and choose Share with | Homegroup (Read).
You should select the FamilyInfo folder and choose Share with | Homegroup (Read). When a computer belongs to a homegroup, users can access files in any Public folder by default. You can allow users who log on to other computers in the homegroup to access other files by using the Share with command. To allow users Read-only access, select Share with | Homegroup (Read).
You should not move the FamilyInfo folder to the Public Documents library. The Public Documents library allows Read/Write access by default.
You should not grant Everyone Read access in Advanced Sharing. Advancing Sharing is used to configure file share permissions for resources shared through traditional file sharing methods. When Everyone is granted Read access, any authenticated user can access the files, not just members of the homegroup.
You should not grant Homegroup Read access in Advanced Sharing. Homegroup is not accessible through Advanced Sharing. To grant permission to a homegroup, you need to use the Share with menu item.
You are managing several computers running Microsoft Windows 7. Several users have removable USB hard disks to provide additional storage.
You need to ensure that data on removable hard disks is encrypted. The data on the hard disks should be readable by computers running Windows XP or Windows Vista, as well as Windows 7.
What should you do?
- Format the removable disks as NTFS and require BitLocker on the disks through Group Policy.
- Format the removable disks as NTFS and require Encrypting File System (EFS) on the disks through Group Policy.
- Format the removable disks as FAT32 and require BitLocker on the disks through Group Policy.
- Format the removable disks as FAT32 and require Encrypting File System (EFS) on the disks through Group Policy.
Format the removable disks as FAT32 and require BitLocker on the disks through Group Policy.
You should format the removable disks as FAT32 and require BitLocker on the disks through Group Policy. You can require the use of BitLocker on removable disks, referred to as BitLocker To Go in this use, through Group Policy. To make the data accessible to older versions of Windows, you must format the disk as FAT or FAT32 and must include the BitLocker To Go Reader on the hard disk.
You should not format the removable disks as NTFS. When you apply BitLocker To Go to removable hard disks formatted as NTFS, it cannot be read by older versions of Windows.
You cannot require EFS encryption through Group Policy.
Client computers running Microsoft Windows 7 are configured to support BranchCache in Hosted Cache mode. BranchCache is configured through linked Group Policy objects (GPOs).
You need to convert the clients to support BranchCache in Distributed Cache mode. You run the following on each of the client computers:
netsh branchcache set service mode=DISTRIBUTED
You need to finish configuring Distributed Cache mode support.
What should you do?
- Configure each client’s firewall to enable WS-Discovery protocol.
- Manually start the BranchCache service on each computer.
- Enable the BranchCache for remote files feature.
- Unlink the GPOs configuring clients for hosted mode.
Unlink the GPOs configuring clients for hosted mode.
You should unlink the GPOs configuring clients for hosted mode. Configuration settings applied through linked GPOs take precedence over configuration changes made when you run netsh.
You should not configure each client’s firewall to enable WS-Discovery protocol. Windows Firewall is configured automatically when you run netsh.
You should not manually start the BranchCache service on each computer. There is no need to do this manually.
You should not enable the BranchCache for remote files feature. This feature is available only on server computers configured as file servers and is only necessary on files servers also supporting BranchCache.
A computer is running Microsoft Windows Vista Home Premium.
You need to install Windows 7 Professional on the computer. You must preserve user configuration settings and applications. You must perform the installation using the least amount of effort.
What should you do first?
- Start the computer in Windows Vista. Insert the installation DVD and choose Upgrade.
- Start the computer from the DVD. Choose Custom.
- Start the computer in Windows Vista. Insert the installation DVD and run Migsetup.exe.
- Start the computer from the DVD. Choose Upgrade.
Start the computer in Windows Vista. Insert the installation DVD and run Migsetup.exe.
You should start the computer in Windows Vista, insert the installation DVD, and run Migsetup.exe. You cannot directly upgrade a computer running Windows Vista Home Premium to Windows 7 Professional by performing an upgrade installation. You must perform a custom installation. However, because you need to preserve settings, you will need to first migrate them using Easy Transfer (Migsetup.exe). You will need to store the files on an external hard drive, such as a Universal Serial Bus (USB) flash drive, or you will need to use an Easy Transfer Cable.
You should not start the computer in Windows Vista, insert the installation DVD, and choose Upgrade. You would complete these steps if this upgrade path were supported. You can only directly upgrade to either Windows 7 Home Premium or Windows 7 Ultimate from Windows Vista Home Premium edition by performing an upgrade installation.
You should not start the computer from the DVD and choose Custom. You need to migrate the settings before you perform the installation.
You should not start the computer from the DVD and choose Upgrade. You can only directly upgrade to either Windows 7 Home Premium or Windows 7 Ultimate from Windows Vista Home Premium by performing an upgrade installation.
You upgrade several computers to Microsoft Windows 7. All of the computers are part of the same Active Directory domain.
You must support an application with a known compatibility problem after upgrading the computers. You need to create and deploy a custom compatibility mode to correct the problem. You need to keep the effort needed to correct the problem to a minimum.
What should you do first?
- Run Sdbinst on each of the upgraded computers.
- Run the Standard User Analyzer (SUA) wizard on each of the upgraded computers.
- Launch the Create a Custom Compatibility Mode Wizard.
- Create a new compatibility database.
Create a new compatibility database.
You should create a new compatibility database. Before you can create and distribute a custom compatibility mode, you must first create a custom compatibility database as a destination. You then distribute the fixes contained in the compatibility mode as part of the custom database.
A compatibility mode is a set of compatibility fixes. You can create a compatibility mode by copying an existing compatibility mode and then modifying it or by creating a new mode and adding individual fixes.
You should not run Sdbinst on each of the upgraded computers. The Sdbinst command is used to distribute the custom compatibility database after it is completed.
You should not run the SUA wizard on each of the upgraded computers. The SUA wizard is used to detect User Account Control (UAC)-related compatibility issues. The scenario states that you are working with a known compatibility issue.
You should not launch the Create a Custom Compatibility Mode Wizard. You must create the custom compatibility database first. You will then select the compatibility database before launching the Create a Custom Compatibility Mode Wizard.
You are configuring a computer to boot from a virtual hard disk (VHD). The VHD must be installed using an image located on a network share.
You create a VHD and configure it with a primary partition.
What should you do next?
- Start the computer by using Windows PE.
- Detach the VHD.
- Run ImageX with the /apply option.
- Run Bcdboot.
Run ImageX with the /apply option.
You should run ImageX with the /apply option. After you configure the partitions, you need to apply the image. You can apply the image by running ImageX with the /apply option.
You do not need to start the computer using Windows Preinstallation Environment (PE). Windows PE is used when applying an image to a physical hard disk. You can apply an image to a virtual hard disk when you are booted to Windows 7.
You should not detach the VHD. The VHD needs to be attached to apply the image.
You should not run Bcdboot. You will run Bcdboot on the target computer after you apply the image on the VHD, copy the VHD to the target computer, and attach the VHD. The Bcdboot command copies the boot files in the VHD to the system partition on the target computer.









