Chapter 1. Introduction to Windows 8.1 administration

Windows 8.1 is designed primarily as an operating system for client devices. This chapter covers getting started with Windows 8.1 and the fundamental tasks you need for Windows 8.1 administration. Throughout this and the other chapters in this book, you’ll find detailed discussions of changes that enhance all aspects of computer management and security. Although this book focuses on Windows 8.1 administration, the tips and techniques discussed throughout the text can help anyone who develops for, works with, or supports Windows 8.1.

This book zeroes in on user and system administration tasks. You’ll find detailed coverage of the following topics:

  • Customizing the operating system

  • Optimizing the Windows environment

  • Configuring hardware devices

  • Installing and maintaining programs

  • Managing user access and global settings

  • Troubleshooting system problems

Also, it is important to note that just about every configuration option in the Windows operating system can be controlled through Group Policy. Rather than add caveats to every discussion that feature A or B can be configured only if allowed in Group Policy, I’m going to assume that you understand the global impact of Group Policy on system configuration and management. I’m also going to assume that you are familiar with the command line and Windows PowerShell. This will allow me to focus on essential tasks for administration.

Getting started with Windows 8.1: the quick tour

Windows 8.1 is the latest release of the Windows operating system for client computers. Windows 8.1 natively supports image-based installation and deployment. Windows 8.1, Windows 8.1 Pro, and Windows 8.1 Enterprise support 32-bit x86 and 64-bit x64 processors for PCs and tablets. Windows 8.1 RT supports ARM processors. For many advanced features, including BitLocker, Encrypting File System, Domain Join, Group Policy, and the Remote Desktop host, computers will need Windows 8.1 Pro or Windows 8.1 Enterprise.

Windows 8.1 has many enhancements to improve security, including memory randomization and other improvements to prevent malware from inserting itself into startup and running processes. Windows 8.1 uses address space layout randomization (ASLR) to randomly determine how and where important data is stored in memory, which makes it much more difficult for malware to find the specific locations in memory to attack.

Windows 8.1 has enhanced support for devices that use Trusted Platform Module (TPM). Although always-on devices require TPM 2.0, all other devices require at least TPM 1.2. Firmware can use TPM to store hashes, which verify that important operating system files haven’t been changed, and keys, which verify that digital signatures are valid.

Windows 8.1 requires a processor that includes hardware-based Data Execution Prevention (DEP) support. DEP uses the Never eXecute (NX) bit to mark blocks of memory as data that should never be run as code. DEP has two specific benefits. It reduces the range of memory that malicious code can use and prevents malware from running any code in memory addresses marked as Never eXecute.

If your organization doesn’t use an enterprise malware solution, you’ll also be interested to know that Windows Defender for Windows 8.1 has been upgraded to a more fully featured program. Windows Defender now protects against viruses, spyware, rootkit, and other types of malware. Rootkit detection helps to safeguard PCs and tablets from malware that inserts itself into non-Microsoft drivers. If Windows Defender detects that a non-Microsoft driver has been infected, it prevents the driver from starting. It’s important to point out that other features, such as Secure Boot, Trusted Boot, and Measured Boot, protect Microsoft drivers and other critical operating system files.

Real World

Firmware runs internal integrity checks to verify the firmware’s digital signature as part of initialization. With Secure Boot, firmware also verifies the digital signature on the Windows bootloader as part of initialization. If a rootkit is installed and the firmware or the Windows bootloader has been modified, the computer will be prevented from starting. After the Secure Boot, the bootloader verifies the digital signature of the operating system kernel as part of Trusted Boot. Also as part of Trusted Boot, the kernel in turn verifies all remaining boot components, including boot drivers and startup files. Finally, Measured Boot allows third-party software running on a remove server to verify the security of every startup component as well.

Separate distribution media is provided for 32-bit and 64-bit editions of Windows 8.1. To install the 32-bit edition of Windows 8.1 on an x86-based computer, you need to use the 32-bit distribution media. To install the 64-bit edition of Windows 8.1 on an x64-based computer, you need to use the 64-bit distribution media. Generally, if you are running a 32-bit operating system and want to install a 64-bit operating system (on hardware that supports both), you need to restart the computer and boot from the installation media. The same is generally true if you want to install a 32-bit operating system on a computer running a 64-bit operating system.

Note

Windows 8.1 RT normally is preinstalled on devices with ARM processors, and it is very different from other editions of Windows 8.1.

Windows 8.1 uses modularization for language independence and disk imaging for hardware independence. Each component of the operating system is designed as an independent module that you can easily add or remove. This functionality provides the basis for the configuration architecture in Windows 8.1. Microsoft distributes Windows 8.1 on media with disk images that use compression and single-instance storage to dramatically reduce the size of image files. The format for disk images is the Windows Imaging (WIM) format.

The Windows Preinstallation Environment (Windows PE) replaces MS-DOS as the preinstallation environment and provides a bootable startup environment for installation, deployment, recovery, and troubleshooting. The Windows Preboot Environment provides a startup environment with a boot manager that lets you choose which boot application to run to load the operating system. On systems with multiple operating systems, you access operating systems prior to Windows 7 in the boot environment by using the legacy operating system entry.

User Account Control (UAC) enhances computer security by ensuring true separation of standard user and administrator user accounts. Through UAC, all applications are run by using either standard user or administrator user privileges, and you get a security prompt by default whenever you run an application that requires administrator privileges. The way the security prompt works depends on Group Policy settings. Additionally, if you log on by using the built-in Administrator account, you typically do not get elevation prompts.

Windows 8.1 has several key UI elements, including the following:

  • Start screen

  • Charm bar

  • Search panel

  • Settings panel

  • PC Settings screen

  • Apps screen (also referred to as All Apps)

The Start screen replaces the traditional Start menu. Start is a window, not a menu. Programs can have tiles on the Start window. Tapping or clicking a tile runs the program. When you press and hold or right-click a tile, an options panel rather than a shortcut menu normally is displayed.

From Start, one way to quickly open a program is by simply typing the file name of the program and then pressing Enter. This shortcut works as long as the Everywhere Search box is in focus (which it typically is by default).

Pressing the Windows key switches between the Start screen and the desktop or the current app you are working with (or, if you are working with PC Settings, between Start and PC Settings). On the Start screen, there’s a Desktop tile that you can tap or click to display the desktop. You also can display the desktop by pressing Windows key + D or, to peek at the desktop, press and hold Windows key + , (that’s the Windows key plus the comma key).

The Charm bar is an options panel for Start, Desktop, and PC Settings. With touch UI, you can display the Charm bar by sliding in from the right side of the screen. With a mouse and keyboard, you can display the Charm bar by moving the pointer over the hidden button in the upper-right or lower-right corner of the Start, Desktop, or PC Settings screen; or by pressing Windows key + C.

The Charm bar has the following five charms:

  • Search. Tap or click the Search charm to display the Search panel. Any text typed while on the Start screen is entered into the Search box on the Search panel. Areas the Search box can be focused on include Everywhere, Settings, or Files. When it is focused on Everywhere, you can use Search to quickly find installed programs, files, settings, and more. When it is focused on Settings, you can use Search to quickly find settings and options in Control Panel. When it is focused on Files, you can use Search to quickly find files.

  • Share. Tap or click the Share charm to share from a desktop app. For example, when working with the Maps app, you’ll typically get options for sharing the map with which you are working.

  • Start. Tap or click the Start charm to switch between Desktop and Start (or, if you are working with PC Settings, between Start and PC Settings).

  • Devices. Tap or click the Devices charm to work quickly with attached devices, such as a second screen.

  • Settings. Tap or click the Settings charm to access the Settings panel, which provides access to important options, including the power options for sleep, shutdown, and restart.

Tip

Normally, Everywhere Search is the default. Thus, from Start, you can quickly open a program by typing the program name and pressing Enter.

You also can display the Settings panel by pressing Windows key + I. From the settings panels, you can:

  • View connected networks and network status.

  • View and change audio output levels.

  • Change brightness levels of the display (portable devices only).

  • Hide notifications temporarily.

  • Access power options.

  • Display the touch keyboard (touch UI devices only).

  • Access the PC Settings screen (by clicking Change PC Settings).

Start Settings, Desktop Settings, and PC Settings have nearly—but not exactly—identical Settings panels. The Start Settings panel has a Tiles option that you can tap or click to display an option for adding or removing tiles for the administrative tools to the Start screen and an option for clearing personal information from tiles. The Desktop Settings panel has several quick links, including:

  • Control Panel. For opening Control Panel

  • Personalization. For opening personalization settings in Control Panel

  • PC Info. For opening the System page in Control Panel

  • Help. For opening Windows Help and Support

Thus, when you are working with the desktop, one way to quickly open Control Panel is by pressing Windows key + I, and then clicking Control Panel on the Settings panel.

File Explorer is pinned to the desktop taskbar by default, which means you can also access Control Panel by following these steps:

  1. Open File Explorer by tapping or clicking the taskbar icon.

  2. Tap or click the leftmost option button in the address list.

  3. Tap or click Control Panel.

Another technique you’ll want to quickly master is getting to the Apps screen, which lists installed apps alphabetically within app categories. Apps are listed first in the results whenever you perform an Everywhere search. On the Start screen, you’ll find a button with an arrow pointing down; tapping or clicking this button displays the Apps screen. On the Apps screen, you’ll find lists of all installed programs, organized by category. Apps listed in the Windows System category are ones you’ll often use for administration, including Command Prompt, Control Panel, Task Manager, File Explorer, This PC, and Windows PowerShell. Administrative tools are only displayed on the Apps screen if you previously selected the Tiles option on the Start Settings panel and then selected Show Administrative Tools.

Note

With Windows 8.1 Pro and Windows 8.1 Enterprise, Windows PowerShell is normally added as a feature. From Start, a quick way to open Windows PowerShell is to type powershell, and then press Enter. This shortcut works as long as Windows PowerShell is the first match found for the keyword “powershell.” If multiple matches are found, tap or click the one that you want to run rather than pressing Enter.

Tip

If you’ve opened the Apps screen on your computer, you might want to add pinned items to Start or to the desktop taskbar. To do this, press and hold or right-click the item, and then tap or click Pin To Start or Pin To Taskbar as appropriate. For easier administration, I recommend adding Command Prompt and Windows PowerShell to the taskbar.

With Windows 8.1, you might want to use Windows PowerShell as your go-to prompt for entering both standard Windows commands and Windows PowerShell commands. Although anything you can enter at a command prompt can be entered at the Windows PowerShell prompt, it’s important to remember that this is possible because Windows PowerShell looks for external commands and utilities as part of its normal processing. As long as the external command or utility is found in a directory specified by the PATH environment variable, the command or utility is run as appropriate. However, keep in mind that Windows PowerShell execution order could affect whether a command runs as expected. For Windows PowerShell, the execution order is (1) alternate built-in or profile-defined aliases; (2) built-in or profile-defined functions; (3) cmdlets or language keywords; (4) scripts with the .ps1 extension; and (5) external commands, utilities, and files. Thus, if any element in 1 to 4 of the execution order has the same name as a command, that element will run instead of the expected command.

Windows 8.1 ships with Windows PowerShell. When you’ve configured Windows PowerShell for remote access, you can execute commands on remote computers in a variety of ways. One technique is to establish a remote session with the computers with which you want to work. The following example and partial output shows how you can check the Windows edition on remote computers:

$s = new-pssession -computername engpc15, hrpc32, cserpc28 invoke-command
-session $s {dism.exe /online /get-currentedition}

The following is the resulting partial output:

Deployment Image Servicing and Management tool Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Current Edition : Ultimate
The operation completed successfully.

The internal version number for Windows 7 is 6.1, whereas the internal versions for Windows 8 and Windows 8.1 are 6.2 and 6.3 respectively. Thus, based on this output, you know the computer is running Windows 7 Ultimate edition (and hasn’t been upgraded to Windows 8.1 yet).

Note

With the New-PSSession command, you use the –ComputerName parameter to specify the remote computers to work with by Domain Name System (DNS) name, NetBIOS name, or IP address. When working with multiple remote computers, separate each computer name or IP address with a comma.

Understanding 32-bit and 64-bit computing options

Since it was introduced for Windows operating systems, 64-bit computing has changed substantially. Not only do computers running 64-bit versions of Windows perform better and run faster than their 32-bit counterparts, they are also more scalable because they can process more data per clock cycle, address more memory, and perform numeric calculations faster.

Windows 8.1 PCs and tablets support x64 architecture. This architecture is based on 64-bit extensions to the x86 instruction set, which is implemented in AMD Opteron (AMD64) processors, Intel Xeon processors with 64-bit extension technology, and other processors. This architecture offers native 32-bit processing and 64-bit extension processing, allowing simultaneous 32-bit and 64-bit computing.

In general, 64-bit computing is designed for performing operations that are memory intensive and that require extensive numeric calculations. With 64-bit processing, applications can load large data sets entirely into physical memory (that is, RAM), which reduces the need to page to disk and increases performance substantially.

Currently, the prevalent firmware interfaces are:

  • Basic input/output system (BIOS).

  • Extensible Firmware Interface (EFI).

  • Unified Extensible Firmware Interface (UEFI).

Computers based on x86 use BIOS and the master boot record (MBR) disk type for boot and system volumes. Computers based on x64 use UEFI wrapped around BIOS or EFI. UEFI and EFI support the GUID partition table (GPT) disk type for boot and system volumes. This means that there can be differences in the way you manage computers with these architectures, particularly when it comes to setup and disk configuration. However, with the increasing acceptance and use of UEFI and the ability of Windows 8.1 to use both MBR and GPT disks regardless of firmware type, the underlying chip architecture won’t necessarily determine what firmware type and disk type a computer uses. This decision is in the hands of the hardware manufacturer.

Note

Generally, BIOS-based computers use MBR for booting or for data disks and GPT only for data disks. EFI-based computers can have both GPT and MBR disks, but you must have at least one GPT disk that contains the EFI system partition (ESP) and a primary partition or simple volume that contains the operating system for booting.

In most cases, 64-bit hardware is compatible with 32-bit applications; however, 32-bit applications perform better on 32-bit hardware. Windows 64-bit editions support both 64-bit and 32-bit applications by using the Windows on Windows 64 (WOW64) x86 emulation layer. The WOW64 subsystem isolates 32-bit applications from 64-bit applications. This prevents file system and registry problems. The operating system provides interoperability across the 32-bit/64-bit boundary for the Component Object Model (COM) and for basic operations such as cutting, copying, and pasting using the Clipboard. However, 32-bit processes cannot load 64-bit dynamic-link libraries (DLLs), and 64-bit processes cannot load 32-bit DLLs.

In the shift to 64-bit computing, you might want to track which computers in the enterprise support 64-bit operating systems, which computers are already running 64-bit operating systems, or both.

With Windows PowerShell, you can:

  • Determine whether a computer has a 64-bit operating system installed by using the OSArchitecture property of the Win32_OperatingSystem object. An example is

    get-wmiobject -class win32_operatingsystem | fl osarchitecture

    And the resulting output is

    osarchitecture : 32-bit
  • Determine whether a computer supports a 64-bit operating system by using the Name and Description properties of the Win32_Processor object:

     get-wmiobject -class win32_processor | fl name, description
    
     name        : Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz
    description : x64 Family 6 Model 15 Stepping 7

Here, the first sample output tells you the computer is running a 32-bit version of Windows. The second sample output tells you the computer has an x64 processor. As a result, you know the computer can be upgraded to a 64-bit version of Windows 8.1. Rather than check each computer individually, you could create a script to do the work for you.

Although Windows 8.1 continues to support 16-bit applications, it’s important to point out that Windows 8.1 might restrict access to the 16-bit MS-DOS subsystem (ntvdm.exe). If so, the MS-DOS subsystem is prevented from running, and this in turn prevents 16-bit applications from running.

In Group Policy for Active Directory Domain Services or local policy for the computer, the Prevent Access To 16-bit Applications setting under Computer ConfigurationWindows ComponentsApplication Compatibility controls whether 16-bit applications can run. As with previous versions of Windows, when this setting is enabled, Windows 8.1 blocks access to 16-bit applications and prevents them from running.

In an important change, if the setting is not configured in policy, Windows 8.1 runs the 16-bit application control panel, which might require elevated administrator privileges to run the 16-bit application. Therefore, if you want to allow 16-bit applications to run without requiring elevated administrator privileges, you must set Prevent Access To 16-bit Applications to Disabled.

Deploying Windows 8.1

With Windows 8.1, you can deploy custom builds to computers through manual and automated processes. To deploy Windows by using manual processes, you need to create the required boot and installation images and optionally create recovery images. To automate the deployment process, you need to install Windows Deployment Services. Whether you use a completely manual process, a completely automated process, or some combination of the two, you’ll perform similar administrative tasks. These tasks require you to understand and use the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 and Windows Deployment Services.

The Windows Assessment and Deployment Kit for Windows 8.1 is available from the Microsoft Download Center (download.microsoft.com) and contains the tools for deploying Windows images, including the following:

  • Application Compatibility Toolkit (ACT)

  • The standard deployment and imaging tools

  • User State Migration Tool (USMT)

  • Volume Activation Management Tool (VAMT)

  • Windows Assessment Services

  • Windows Assessment Toolkit

  • Windows Performance Toolkit (WPT)

  • Windows Preinstallation Environment (Windows PE)

You can use Windows Deployment Services to deploy Windows 8.1 over a network. You can add the Windows Deployment Services role to any server running Windows Server 2012 RTM or R2.

Windows 8.1 and Windows Server 2012 RTM or R2 use Windows PE. Windows PE is a bootable startup environment that provides operating system features for the following:

  • Installation. When you install Windows 8.1, the graphical tools that collect system information during the setup phase are running within Windows PE.

  • Deployment. When a new computer performs a network boot, the built-in Preboot Execution Environment (PXE) client can connect to a Windows Deployment Services server, download a Windows PE image across the network, and then run deployment scripts within this environment.

  • Recovery. Windows PE enables you to access and run the Startup Repair tool if Windows 8.1 fails to start because of a corrupted system file.

  • Troubleshooting. You can manually start Windows PE to perform troubleshooting or diagnostics testing if Windows 8.1 is experiencing problems that can’t otherwise be diagnosed.

Windows PE is modular and extensible, and it provides full access to partitions formatted by using the FAT or NTFS file system. Because Windows PE is built from a subset of Windows components, you can run many Windows applications, work with hardware devices, and communicate across IP networks. Several command-line tools are available in Windows PE, including:

  • BCDBoot. A tool that initializes the boot configuration data (BCD) store and allows you to copy boot environment files to the system partition.

  • Bootsect. A tool for creating and working with boot sectors on hard disks and flash drives.

  • Copype. A tool for creating a directory structure for Windows PE files and then copying the Windows PE media files. Running this tool is a prerequisite for creating bootable Windows PE media.

  • DiskPartA tool for creating and working with disks, partitions, and volumes.

  • DISM. An advanced tool for servicing and maintaining images.

  • Drvload. A support tool for adding device drivers and dynamically loading a driver after Windows PE has started.

  • ImageX. A tool for capturing and applying Windows images.

  • Lpksetup. A tool for adding and removing a language pack.

  • Makewinpemedia. A tool for creating bootable Windows PE media.

  • Net. A set of support commands that enables you to manage local users, start and stop services, and connect to shared folders.

  • Netcfg. A tool that configures network access.

  • Oscdimg. A tool for creating CD and DVD ISO image files.

  • Wpeinit. A tool that initializes Windows PE every time it boots.

Copype and Makewinpemedia are new tools that allow you to more easily create bootable Windows PE media. You use Copype to set up the Windows PE build environment. After you optimize the build as necessary, you can use Makewinpemedia to create the bootable media, which can be a CD, DVD, USB flash drive, or external USB hard drive.

Using DISM

Deployment Image Servicing and Management (DISM) is one of the most important deployment tools. DISM is included with Windows 8.1 Pro and Windows 8.1 Enterprise.

By using DISM, you can manage online and offline images of the Windows operating system, including images for deployment and those for virtual machines. Windows Image (.wim) files are used to deploy Windows 8.1. Virtual hard disk (.vhd) files are used with virtual machines. The same commands work on WIM and VHD files.

You can use DISM to:

  • Add and remove packages. Packages can include language packs, updates, and utilities.

  • Enable and disable Windows features.

  • Add and remove third-party device drivers.

You can run DISM at an elevated administrator command prompt by following these steps:

  1. On the Apps screen, Command Prompt is listed in the Windows System category. Or, if you are working with Start, enter cmd.

  2. Press and hold or right-click the Command Prompt shortcut on the Apps screen, and then tap or click Run As Administrator.

  3. If the User Account Control prompt appears, proceed as you normally would to allow the application to run with administrator privileges.

  4. In the Command Prompt window, enter dism /? to view available options for DISM.

  5. To view commands available for working with online images, enter dism /online /?.

Although DISM is designed to work primarily with offline images and images you’ve mounted, you can use some DISM commands to get important information about the live operating system running on a computer. Table 1-1 provides an overview of DISM Online subcommands you can use with live operating systems. For example, if you want to display a list of Windows editions to which a computer can be upgraded, you can enter the following command.

dism /online /get-targeteditions
Table 1-1. DISM Online commands for live operating systems

Subcommand

Description

/Disable-Feature/featurename:FeatureName

Disables a specified feature. Feature names are case sensitive.

/Enable-Feature/featurename:FeatureName

Enables a specified feature. Feature names are case sensitive.

/Get-CurrentEdition

Displays the currently installed edition of Windows.

/Get-DriverInfo/driver:DriverName.inf

Displays information about a specified third-party driver that is installed in the driver store. Driver names are not case sensitive.

/Get-Drivers

Displays information about all third-party drivers that are installed in the driver store.

/Get-FeatureInfo/featurename:FeatureName

Displays information about a specified feature. Feature names are case sensitive.

/Get-Features

Displays the name and state of all features that are available in the online image.

/Get-Intl

Displays information about the default system user interface language, system locale, default time zone, keyboard language, and installed languages.

/Get-PackageInfo/packagename:PackageName

Displays information about a specified package. Package names are case sensitive.

/Get-Packages

Displays information about Windows packages that are installed.

/Get-TargetEditions2

Lists the Windows editions to which the operating system can be upgraded.

DISM Online also is handy when you want to list all available features by their name and status, such as might be needed for PC inventory or to add or remove features. To list available features, enter the following command at an elevated prompt.

dism /online /get-features

To add a feature, use the /Enable-Feature parameter and then set the name of the feature to enable with the /FeatureName parameter. If a feature has related subfeatures, add the /All parameter to enable all the subfeatures. This example enables Hyper-V and all related features.

dism /online /enable-feature /featurename:Microsoft-hyper-v /all

Understanding Windows imaging

When you update Windows 8.1 by adding or removing features, applying hotfixes, or installing service packs, you are simply modifying the set of modules available. And because these modules are independent, you can make these changes without affecting the system as a whole. Because language packs are separate modules as well, you can easily implement different language configurations without needing separate installations for each language.

Microsoft distributes Windows 8.1 on media with WIM disk images. Because WIM is hardware independent, Microsoft can ship one binary file for 32-bit architectures and one binary file for 64-bit architectures. A separate binary file is available for Windows 8.1 RT.

Windows 8.1 can be installed through either automated or interactive setup. You can automate the installation of Windows 8.1 in several ways, including the following:

  • Create an unattended installation answer file. Windows 8.1 uses a standards-based, single-format answer file. This file, called Unattend.xml, is written in XML, making it easier to process by using standard tools. By creating a custom answer file and then running Setup using this answer file, you can perform unattended installations of Windows 8.1. The Setup program can then install the operating system from a distribution share or from media.

  • Use Sysprep image-based installation. This approach requires running the System Preparation command-line tool (Sysprep.exe) on a computer that you want to use as the master deployment computer, and then creating a disk image of this computer’s configuration. Sysprep is stored in the %SystemRoot%System32Sysprep folder. The Windows Automated Installation Kit (Windows AIK) includes Windows System Image Manager and ImageX to help you use Sysprep for deployments. You use Windows System Image Manager to create answer files for unattended installations. You use ImageX to create and manage disk images.

By using WIM as its disk-imaging format and taking advantage of the modular design of Windows 8.1, ImageX significantly reduces the number of disk images that must be maintained. You don’t need to maintain multiple hardware-dependent disk images or multiple language-dependent disk images. Instead, you typically need only a single disk image for each chip architecture used in your organization. You can then use different installation scripts to customize the operating system installation as necessary.

WIM has other advantages over earlier disk image formats as well. WIM enables you to modify and maintain disk images offline, which means you can add or remove optional components and drivers or perform updates without having to create a new disk image. To do this, you mount the disk image as a folder, and then use File Explorer or other tools to update, manage, or remove files as necessary.

Windows System Image Manager, ImageX, and Sysprep provide several different ways to automate deployment. Here are the basic steps:

  1. Set up and configure Windows 8.1 on a computer not being used for normal operations, and then install and configure any necessary components and applications.

  2. Run Sysprep to prepare the computer for capture. Sysprep removes unique identifiers from the computer and designates it as a master deployment computer. At the end of this process, the computer no longer has identifying information that allows it to be logged on to and used within a domain or workgroup.

  3. Use the ImageX /Capture option to capture the disk image and store this image on media or in a distribution share. The image can be maintained offline by using the ImageX /Mountrw option to mount the image in read/write mode so that you can make any necessary changes. Use the ImageX /Unmount command to unmount the image when you are finished making changes.

    You also can mount images by using DISM /Mount-WIM and unmount images by using DISM /Unmount-WIM. DISM provides functionality for manipulating images. You can set product keys, perform upgrades, add or remove drivers, set language and locale information, add or remove packages and features, and clean up images.

  4. Use Windows System Image Manager to create your unattended installation answer files. You can then create deployment scripts that configure the computer, run Setup by using the answer file, and apply the disk image you’ve previously created.

  5. Run your deployment script to configure the computer and install the operating system.

Managing access and prestaging computers

You can manage images by using DISM. To prevent unauthorized users from installing images, you can:

  • Prestage computers and allow only known computers to be deployed.

  • Modify the security settings of image files so that only appropriate personnel can access them.

  • Enable administrator approval for client installation.

Prestaging computers

Prestaging computers involves creating computer accounts in Active Directory Domain Services prior to their use. By prestaging a computer, you control exactly which clients and servers can communicate with each other. Before you prestage computers, you should be sure that Windows Deployment Services is configured to accept requests only from known computers by following these steps:

  1. In the Windows Deployment Services console, expand the Servers node. Press and hold or right-click the server with which you want to work, and then select Properties.

  2. On the PXE Response Settings tab, tap or click Respond Only To Known Client Computers, and then tap or click OK.

To prestage a computer, you need to know the computer’s GUID. A computer’s GUID comes from the active network adapter on the computer and must be entered in the format {dddddddd-dddd-dddd-dddd-dddddddddddd}, where d is a hexadecimal digit, such as {AEFED345-BC13-22CD-ABCD-11BB11342112}.

You can obtain the required identifier in several ways. In some cases, manufacturers print a label with the GUID and attach the label to the computer. However, don’t forget that the GUID is valid only for the network adapter that shipped with the computer. If you replace the adapter, the new adapter will have a new GUID.

To obtain the GUID for the installed network adapter, you can check the computer’s firmware. If a remote computer is started, you can enter the following command at a Windows PowerShell prompt.

get-wmiobject win32_networkadapter | format-list guid

Write down or copy the GUID associated with the network adapter connected to the LAN.

To prestage computers, follow these steps:

  1. In Active Directory Users And Computers, press and hold or right-click the operating unit (OU) or container in which the computer will be staged, tap or click New, and then tap or click Computer.

  2. Enter a name for the computer, and then tap or click Next. Alternatively, tap or click Change to choose the user or group with permission to join this computer to the domain, and then tap or click Next.

  3. On the Managed page, choose This Is A Managed Computer, enter the computer’s GUID, and then tap or click Next. The GUID can be found in the system firmware or it might be posted on the computer case.

  4. On the Host Server page, choose the Windows Deployment Services server that will service this client. Tap or click Next, and then tap or click Finish.

Modifying image file security

To modify the security settings on an image file, open File Explorer. Press and hold or right-click the image file, and then click Properties. In the Properties dialog box, use the options on the Security tab to configure the security settings you want to use. Alternatively, you can configure security settings on the Image Group folder in which the image file is stored. These settings will then be inherited by the images in the Image Group folder.

Requiring administrator approval

Instead of prestaging computers or using image file security, you can require administrator approval before allowing computers to be installed from images. To require administrator approval rather than modify security settings on image files, you can do the following:

  1. In the Windows Deployment Services console, expand the Servers node. Press and hold or right-click the server you want to work with, and then tap or click Properties.

  2. On the PXE Response Settings tab, select Respond To All (Known And Unknown) Client Computers.

  3. Select For Unknown Clients, Notify Administrator And Respond After Approval, and then tap or click OK.

Now computers that are started from the network will enter a pending state. Before the installation can proceed, an administrator can approve or reject the request.

To approve a request, complete the following steps:

  1. In the Windows Deployment Services console, select the server with which you want to work. Next, tap or click the server’s Pending Devices folder to select it and display a list of computers waiting for approval.

  2. Press and hold or right-click the computer, and then tap or click Approve.

To reject a request, complete the following steps:

  1. In the Windows Deployment Services console, select the server with which you want to work. Next, tap or click the server’s Pending Devices folder to select it and display a list of computers waiting for approval.

  2. Press and hold or right-click the computer, and then tap or click Reject.

Customizing Windows images

You can customize a mounted boot or install an image by using the DISM utility. Available options for DISM are summarized in Table 1-2. All components in an image are managed via the component store.

Table 1-2. Key options for the DISM utility

Command Type/Command

Description

GENERAL COMMANDS

 

/Cleanup-Wim

Deletes resources associated with mounted Windows images that are corrupt

/Commit-Wim

Saves changes to a mounted Windows image

/Get-MountedWimInfo

Displays information about mounted Windows images

/Get-WimInfo

Displays information about images in a Windows image file

/Image

Specifies the path to the root directory of an offline Windows image

/Mount-Wim

Mounts an image from a Windows image file

/Online

Targets the running operating system

/Remount-Wim

Recovers an orphaned Windows mount directory

/Unmount-Wim

Unmounts a mounted Windows image

ADDITIONAL OPTIONS

 

/English

Displays command-line output in English

/Format

Specifies the report output format

/LogLevel

Specifies the output level shown in the log (1–4)

/LogPath

Specifies the log file path

/NoRestart

Suppresses automatic reboots and reboot prompts

/Quiet

Suppresses all output except for error messages

/ScratchDir

Specifies the path to a scratch directory

/SysDriveDir

Specifies the path to the system loader file named BootMgr

/WinDir

Specifies the path to the Windows directory

After you mount an image, you are able to work with the mounted image by using the Dism /Image subcommands listed in Table 1-3. These subcommands allow you to upgrade the image to a higher edition (such as from Windows 8.1 Pro to Windows 8.1 Enterprise), add and remove device drivers, specify time zones and language user interface options, display updates and installed message signaled interrupt (MSI) applications, add and remove packages, and more.

Table 1-3. Important subcommands for mounted and offline images

Subcommands

Description

/Add-Driver

Adds driver packages to an offline image

/Add-Package

Adds packages to the image

/Apply-Unattend

Applies an AnswerFile.xml file to an image

/Check-AppPatch

Displays information if the multiple customization updates (MSP files) are applicable to the mounted image

/Cleanup-Image

Performs cleanup and recovery operations on the image

/Disable-Feature

Disables a specific feature in the image

/Enable-Feature

Enables a specific feature in the image

/Gen-LangIni

Generates a new Lang.ini file

/Get-AppInfo

Displays information about a specific installed MSI application

/Get-AppPatches

Displays information about all applied MSP updates for all installed applications

/Get-AppPatchInfo

Displays information about installed MSP updates

/Get-Apps

Displays information about all installed MSI applications

/Get-CurrentEdition

Displays the edition of the specified image

/Get-DriverInfo

Displays information about a specific driver in an offline image or a running operating system

/Get-Drivers

Displays information about all drivers in an offline image or a running operating system

/Get-FeatureInfo

Displays information about a specific feature

/Get-Features

Displays information about all features in a package

/Get-Intl

Displays information about the international settings and languages

/Get-PackageInfo

Displays information about a specific package

/Get-Packages

Displays information about all packages in the image

/Get-TargetEditions

Displays a list of Windows editions to which an image can be upgraded

/Remove-Driver

Removes driver packages from an offline image

/Remove-Package

Removes packages from the image

/Set-AllIntl

Sets all international settings in the mounted offline image

/Set-Edition

Upgrades the Windows image to a higher edition, such as from Windows 8.1 Pro to Windows 8.1 Enterprise

/Set-InputLocale

Sets the input locales and keyboard layouts to use in the mounted offline image

/Set-LayeredDriver

Sets the keyboard layered driver

/Set-ProductKey

Populates the product key into the offline image

/Set-SetupUILang

Defines the default language that will be used by Setup

/Set-SKUIntlDefaults

Sets all international settings to the default values for the specified SKU language in the mounted offline image

/Set-SysLocale

Sets the language for non-Unicode programs (also called system locale) and font settings in the mounted offline image

/Set-TimeZone

Sets the default time zone in the mounted offline image

/Set-UILang

Sets the default system UI language that is used in the mounted offline image

/Set-UILangFallback

Sets the fallback default language for the system UI in the mounted offline image

/Set-UserLocale

Sets the user locale in the mounted offline image

The DISM tool provides commands for working with WIM images. The syntax for mounting images is

dism /mount-wim /wimfile:Path /index:Index /mountdir:MountPath

where Path is the full path to the WIM image, Index is the index position of the image number of the image within the .wim file to apply, and MountPath is the directory location where you’d like to mount the image, such as

dism /mount-wim /wimfile:c:winpe_x86isosourcesoot.wim /index:1 /
mountdir:C:Win8

You can then modify the image as necessary. To commit your changes at any time, you can use Dism /Commit-Wim, as shown in the following example.

dism /commit-wim /mountdir:C:Win8

Here, you commit changes to the WIM images mounted in the C:Win8 directory.

To unmount a WIM file, you can use Dism /Unmount-Wim, as shown in the following example.

dism /unmount-wim /mountdir:C:Win8

Here, you unmount the WIM image that was mounted and committed in the C:Win8 directory. If there are uncommitted changes, you must commit or discard changes when you unmount a WIM image. Add /Commit to commit changes or /Discard to discard changes. This affects only the changes you haven’t previously committed.

Installing Windows 8.1

Windows 8.1 Pro and Enterprise are the main editions intended for use in Active Directory domains. When you install Windows 8.1 on a computer with an existing operating system, you can perform a clean installation or an upgrade. The major differences between a clean installation and an upgrade are the following:

  • Clean installation. With a clean installation, the Windows Setup program completely replaces the original operating system on the computer, and all user and application settings are lost. You should use a clean installation when the operating system cannot be upgraded, the system must boot to multiple operating systems, a standardized configuration is required, or when no operating system is currently installed.

  • Upgrade installation. During an upgrade, user accounts, user files, and user settings are retained, existing applications and their settings are kept, and basic system configuration is not required. An upgrade installation should be used when you have computers running the Windows operating system that support upgrading to Windows 8.1 and you want to minimize disruption by maintaining the existing settings, user information, and application configurations.

The way an upgrade works depends on the operating system being upgraded. When you are upgrading from Windows 7, Windows Setup performs an in-place upgrade that ensures the upgrade works as described previously. With Windows Vista and Windows XP, an in-place upgrade works differently. With Windows Vista, you can retain user accounts, user files, and user settings, as well as basic system configuration, but Windows Setup will not retain applications and their settings. With Windows XP, you can retain user accounts, user files, and user settings, but Windows Setup will not retain applications and their settings or basic system configuration.

Preparing for Windows 8.1 installation

To install Windows 8.1, you can start from the Windows distribution media, run Setup from your current Windows operating system, perform a command-line installation, or use one of the automated installation options.

There are two basic approaches to setting up Windows 8.1—interactively or as an automated process. An interactive installation is what many people regard as the regular Windows installation—the kind in which you walk through the setup process and enter a lot of information. It can be performed from distribution media (by starting from the distribution media or running Windows Setup from a command line). The default Windows setup process when starting from the retail Windows 8.1 DVD is interactive, prompting you for configuration information throughout the process.

There are several types of automated setup, which actually have administrator-configurable amounts of user interaction. The most basic form of unattended setup you can perform is an unattended installation using only answer files. An answer file contains all or part of the configuration information usually prompted for during a standard installation process. You can create unattended answer files by using Windows System Image Manager, which is provided in the Windows Assessment and Deployment Kit (ADK). To take unattended setup a step further, you can use Windows Deployment Services.

The standard setup program for Windows 8.1 is Setup.exe. You can run Setup.exe from the currently running Windows operating system to perform an upgrade, or you can start from the distribution media to perform a new installation of Windows 8.1. When you are working with Windows 8.1 on x86-based systems, you should be aware of the special types of drive sections used by the operating system:

  • Active. The active partition or volume is the drive section for system cache and startup. Some removable media devices might be listed as having an active partition.

  • Boot. The boot partition or volume contains the operating system and its support files. The system and boot partition or volume can be the same.

  • System. The system partition or volume contains the hardware-specific files needed to load the operating system. As part of software configuration, the system partition or volume can’t be part of a striped or spanned volume.

Partitions and volumes are essentially the same thing; however, two different terms are used at times because you create partitions on basic disks and you create volumes on dynamic disks. On an x86-based computer, you can mark a partition as active by using the Disk Management snap-in.

Although the active, boot, and system volumes or partitions can be the same, each is required nonetheless. When you install Windows 8.1, the Setup program assesses all the hard disk drive resources available. Typically, Windows 8.1 puts boot and system files on the same drive and partition, and then marks this partition as the active partition. The advantage of this configuration is that you don’t need multiple drives for the operating system, and you can use an additional drive as a mirror of the operating system partitions.

There are a number of differences when installing to EFI-based hardware. The EFI starts up by loading a firmware-based boot menu. Normally, EFI disks have a partition structure called a GUID partition table (GPT). This partition structure differs substantially from the 32-bit–platform MBR-based partitions.

GPT-based disks have two required partitions and one or more optional (OEM or data) partitions (up to 128 total):

  • EFI system partition (ESP)

  • Microsoft reserved partition (MSR)

  • At least one data partition

The EFI boot menu presents a set of options, one of which is the EFI shell. The EFI shell provides an operating environment supporting the FAT and FAT32 file systems, as well as configuration and file management commands. To view a list of partitions on an EFI-based computer, use the Map command. In the output of the Map command, blk designates partition blocks and fs# designates readable file systems. You can change to a partition by entering the partition block number followed by a colon. Enter dir to view files in the partition. EFI has a boot maintenance manager that allows you to configure the boot menu.

When you install Windows 8.1, the Setup program will automatically create a Windows Recovery Environment (Windows RE) partition and install additional components that can be used for recovery and troubleshooting in that partition. As a result, the Windows recovery tools are always available on computers running Windows 8.1. For more information, see the Recovering from a failed start section in Chapter 10.

As an administrator, you can use these tools to recover computers. If a remote user can’t start Windows, you can talk the user through the process of starting Windows RE and initiating recovery. You do this by having the user access the Advanced Repair Options menu, as discussed in the Recovering from a failed start section in Chapter 10.

Performing a Windows 8.1 installation

Before you install Windows 8.1 on a computer, you should determine whether the underlying hardware meets the requirements for physical memory, processing power, and graphics capabilities. Microsoft provides both minimum requirements and recommended requirements. Requirements for memory and graphics are measured in megabytes (MB) and gigabytes (GB); requirements for processors are measured in gigahertz (GHz).

Windows 8.1 requires:

  • A 1-GHz or faster 32-bit (x86) or 64-bit (x64) processor

  • At least 1 GB RAM (32-bit) or 2 GB RAM (64-bit)

  • A DirectX 9 graphics processor with a Windows Display Drive Model (WDDM) 1.0 or later driver

  • Touch UI requires a tablet or a monitor that supports multitouch.

Note

Microsoft recommends that a computer have available disk space of at least 16 GB (32-bit) or 20 GB (64-bit). Various features in Windows 8.1, such as protection points, which include previous versions of files and folders that have been modified, can quickly increase the size requirements. For optimal performance of the hard disk, you need at least 15 percent free space at all times and adequate space for the paging file, which might be up to twice the size of the system’s RAM. Also, if you are doing an in-place upgrade, the Windows.old folder will contain folders and files from the previous installation.

Any computer that meets or exceeds these hardware requirements can run Windows 8.1. You can perform a new installation of Windows 8.1 by completing these steps:

  1. Turn on the computer and insert the Windows 8.1 distribution media into the computer’s DVD-ROM drive. Press a key to start the Setup program from the DVD when prompted. If you’re not prompted to start from DVD, you might need to modify the computer’s boot or startup options in firmware.

  2. When prompted, choose your language, time, currency format, and keyboard layout, and then tap or click Next. Click Install Now.

  3. With retail versions of Windows 8.1, you typically have to provide a product key. If prompted, enter the product key. Tap the onscreen keyboard button if you are working on a device without a keyboard, and then use the onscreen keyboard to enter the product key. Tap or click Next.

    Note

    If Setup determines that the product key is invalid, make sure that you entered each letter and number correctly. You don’t need to enter dashes. Sometimes it’s easier to reenter the product key than to find the incorrect value in the key sequence.

  4. Read the license terms. If you agree, tap or click I Accept The License Terms, and then tap or click Next.

  5. The Which Type Of Installation Do You Want? page is displayed to ensure that you really want to perform a new installation rather than an upgrade. To continue with the new installation, select Custom: Install Windows Only (Advanced).

  6. When prompted for an installation location, choose the drive partition on which you want to install the operating system, and then tap or click Next.

    Tip

    During installation, on the Where Do You Want To Install Windows? page, you can access a command prompt by pressing Shift+F10. This puts you in the MinWinPC environment used by Setup to install the operating system, and you have access to many of the same command-line tools that are available in a standard installation of Windows 8.1.

  7. If the drive partition you’ve selected contains a previous Windows installation, you’ll get a prompt telling you that existing user and application settings will be moved to a folder named Windows.old and that you must copy these settings to the new installation to use them. Tap or click OK.

  8. Setup will then start the installation. During this process, Setup copies the full disk image of Windows 8.1 to the disk you’ve selected and then expands it. Afterward, Setup installs features based on the computer’s configuration and any hardware that Setup detects. When Setup finishes the installation and restarts the computer, the operating system will be loaded and the system will be set up for first use. After the system is prepared, Setup will restart the computer again.

  9. On the Personalize page, pick a background color for the Start page and desktop. Enter a computer name, and then tap or click Next.

  10. When prompted, choose your country or region, your time and currency format, and your keyboard layout. Tap or click Next.

  11. With wireless connections, you’ll need to select the wireless connection to use. When you tap or click Connect, you’ll be able to enter the password for the wireless network. Then you’ll need to tap or click Connect again. If the computer has a wired connection to the Internet, you shouldn’t need to do this.

  12. On the Settings page, you can tap or click Use Express Settings to accept the express settings or tap or click Customize to customize the settings. Express settings configure the computer and standard defaults, as follows:

    • Turn on sharing and connect devices, which might be suitable for home and work networks, though not necessarily for domain environments.

    • Automatically install important and recommended updates, as well as updates for devices.

    • Help protect the PC from unsafe content, files, and websites by enabling the SmartScreen Filter for Internet Explorer and Windows.

    • Use Windows Error Reporting to check for solutions to problems.

    • Use Internet Explorer compatibility lists to help resolve website compatibility issues.

    • Let desktop apps use your name and account picture.

    • Enable Windows Location Platform so desktop apps can ask users for their location.

  13. If the computer has an Internet connection, the Sign In To Your PC page allows you to set up either a Microsoft Account or a local computer account. Otherwise, only a local computer account can be created. At this point, you’ll typically want to use a local account for the computer, so tap or click Sign In Without A Microsoft Account, and then confirm by tapping or clicking Local Account again. Next, enter a user name. Enter and then confirm a password. Enter a password hint. Finally, tap or click Finish.

    Note

    Chapter 5, discusses Microsoft accounts and provides details on how they can be created and used. When you connect a local or domain account to a Microsoft account, the account becomes a connected local or connected domain account.

  14. Afterward, Windows 8.1 will prepare the computer’s desktop.

You can upgrade a computer to Windows 8.1 by completing these steps:

  1. Start the computer and log on by using an account with administrator privileges. Insert the Windows 8.1 distribution media into the computer’s DVD-ROM drive. The Windows 8.1 Setup program should start automatically. If Setup doesn’t start automatically, use File Explorer to access the distribution media, and then double-tap or double-click Setup.exe.

    Note

    Only the current operating system’s keyboard layout is available during installation. This also means that if your keyboard language and the language of the edition of Windows 8.1 you are installing are different, you might see unexpected characters as you type.

  2. Setup will copy temporary files and then start. If your computer is connected to the Internet, choose whether to get required updates during the installation. Either tap or click Go Online To Install Updates Now or tap or click No, Thanks. Tap or click Next.

    Tip

    You don’t have to get updates during the installation. If you decide not to get required updates, you can update the computer later by using the Windows Update feature. I prefer to install updates as part of the installation to ensure that the computer is ready to go when I finish setting up the operating system.

  3. With retail versions of Windows 8.1, you typically have to provide a product key. If prompted, enter the product key. Tap the onscreen keyboard button if you are working on a device without a keyboard, and then use the onscreen keyboard to enter the product key. By default, the computer will automatically activate Windows the next time you connect to the Internet. Tap or click Next.

    Note

    If Setup determines that the product key is invalid, make sure you entered each letter and number correctly. You don’t need to enter dashes. Sometimes it’s easier to reenter the product key than to find the incorrect value in the key sequence.

  4. Read the license terms. If you agree, tap or click I Accept The License Terms, and then tap or click Accept.

  5. The options that appear on the Choose What To Keep page depend on the version of Windows currently running on your computer. Upgrade options you might get include the following:

    • Windows Settings. If this option is available and selected, Setup attempts to keep basic settings, including settings for your desktop background, display, Internet favorites, Internet history, and Ease of Access. Not all settings will be moved and available in Windows 8.1.

    • Personal Files. If this option is available and selected, Setup saves personal files from the Users folder. This means that the personal files stored in each user’s Documents, Music, Pictures, Videos, and other folders are moved and made available in Windows 8.1.

    • AppsIf this option is available and selected, Setup saves settings for desktop apps and makes them available after upgrade. Desktop programs, and some desktop apps, will need to be reinstalled.

    • Nothing. If this option is selected, Setup moves folders and files for the previous installation to a folder named Windows.old, and the previous installation will no longer run.

    Security Alert

    If you are upgrading and normally log in by using a fingerprint reader or other biometric device, you’ll need to write down your password. You’ll need to enter the user name and password the first time you sign in to Windows 8.1.

  6. Tap or click Next, and then tap or click Install. Continue with steps 8 through 14 of the previous procedure.

You might have trouble installing Windows 8.1 for a variety of reasons. Possible solutions to common problems follow, in problem/solution format.

  • You can’t start from the Windows 8.1 installation media. Although most computers can start from DVD, sometimes this capability is disabled in firmware. Set the boot order in firmware so that the DVD drive appears ahead of hard disk drives and other bootable media.

  • You can’t select a hard disk during setup. Although the Windows 8.1 installation media contains drivers for most disk controllers, you might have a disk controller for which a default driver isn’t available. Insert media containing the required drivers, and then tap or click Load Drivers on the Where Do You Want To Install Windows? page. If the driver is on an internal hard drive, press Shift+F10 to access a command prompt, and then use Xcopy to copy the driver files to a USB flash device or other removable media. You can then tap or click Load Drivers to load the drivers from the media.

  • You forgot to modify the hard disk configuration prior to starting the installation. On the Where Do You Want To Install Windows? page, tap or click Drive Options (Advanced). You can then use the options provided to create, delete, and format partitions as necessary. If you need to shrink or extend a partition (even during an upgrade), press Shift+F10 to access a command prompt, and then use Disk Part to work with the partition. You can extend and shrink partitions without having to delete them. You also can use Disk Part to change the disk type and partition style.

Creating a Windows To Go workspace

Another way to work with Windows 8.1 is to create a Windows To Go workspace. A Windows To Go workspace is a bootable installation of Windows 8.1 that’s installed on a 32-GB or larger USB drive. A Windows To Go workspace operates much like a standard installation of Windows 8.1 except in the following respects:

  • Hibernate is disabled as a sleep option by default, because this helps ensure that you can easily move the workspace between computers.

  • Internal disks are offline by default to ensure that data is stored on the USB drive rather than on the computer into which the Windows To Go drive is inserted.

  • Trusted Platform Module (TPM) is not used; however, a pre-operating system boot password can be configured as part of BitLocker Drive Encryption.

  • Windows Recovery Environment (Windows RE) is not available, and you cannot refresh or reset a Windows To Go workspace.

Unlike in Windows 8, Windows To Go workspaces for Windows 8.1 are able to use Microsoft accounts and access the Microsoft store. Windows To Go discovers available hardware and installs necessary drivers upon first boot on a host computer. The next time you start Windows To Go on that host computer, Windows To Go identifies the host computer and loads the correct drivers automatically. Applications that you want to run from a Windows To Go workspace must support roaming.

Unlike Windows 8, Windows 8.1 includes a Windows To Go creator tool. You can access this tool and create a Windows To Go workspace by completing the following steps:

  1. Insert a 32-GB or larger USB drive into a USB port on your computer.

  2. In Control Panel, tap or click Large Icons or Small Icons as the View By option.

  3. Tap or click the Windows To Go option.

  4. In the Create A Windows To Go Workspace dialog box, tap or click the USB drive on which you want to create the Windows To Go workspace.

  5. Tap or click Next, and then follow the prompts.

Running Windows 8.1

When the operating system starts after installation, you can log on and access the desktop. By default, Windows 8.1 stores user profile data under %SystemDrive% Users\%UserName%. Within the user profile folder, each user who logs on to the system has a personal folder, and that personal folder contains additional folders. These folders are the default locations for storing specific types of data and files:

  • AppData. User-specific application data (in a hidden folder)

  • Contacts. Contacts and contact groups

  • Desktop. The user’s desktop

  • Downloads. Programs and data downloaded from the Internet

  • Favorites. The user’s Internet favorites

  • Links. The user’s Internet links

  • Documents. The user’s document files

  • Music. The user’s music files

  • Pictures. The user’s pictures

  • Videos. The user’s video files

  • Saved Games. The user’s saved game data

  • Searches. The user’s saved searches

Note

%SystemDrive% and %UserName% refer to the SystemDrive and UserName environment variables, respectively. The Windows operating system has many environment variables, which are used to refer to user-specific and system-specific values. Often, I’ll refer to environment variables by using this syntax: %VariableName%. If you’ve upgraded to Windows 8.1 from an earlier version of Windows, the user’s personal folder might also contain symbolic links (which look like shortcuts) to the folders and settings used by that earlier version. A symbolic link is a pointer to a file or folder that often is created for backward compatibility with applications that look for a folder or file in a location that has been moved. You can create symbolic links by using the Mklink command-line utility. At a command prompt, enter mklink /? to learn the available options.

Windows 8.1 uses personal folders and personal libraries. Personal folders are listed in the left pane of File Explorer and displayed in the main pane when you select the This PC node. Libraries are displayed in File Explorer only when you select the Libraries node.

Libraries work differently than they do in Windows 8 and earlier versions of Windows. Although libraries are still collections of files and folders that are grouped together and presented through a common view, the data they collect is different.

In earlier versions of Windows, libraries collected a user’s personal data and a computer’s public data. In Windows 8.1, libraries collect locally stored personal data and cloud-stored personal data. Thus, if a user has a connected local or connected domain account, locally stored data is collected with data stored on SkyDrive. For example, the Documents library collects the data from a user’s locally stored Documents folder and a user’s cloud-stored Documents folder.

When you are working with the Libraries node in File Explorer, you can create new libraries to act as views to various collections of data by pressing and holding or right-clicking an open area of the main pane, pointing to New, and then selecting Library.

Important

When you work with libraries, it’s important to remember that they are only representations of collected data. Windows 8.1 creates views of files and folders that you add to libraries. The libraries do not contain any actual data, and any action that you take on a file or folder within a library is performed on the source file or folder.

Windows 8.1 provides themes that allow you to easily customize the appearance of menus, windows, and the desktop. In Control Panel, tap or click the Change The Theme link under Appearance And Personalization, and then choose the theme you want to use. Windows Default themes such as Earth or Flowers add improved visual design and enhanced dynamic effects to the interface. If you want to use fewer advanced features, choose the Windows theme. Additional themes are available online as well.

It is important to point out, however, that the interface enhancements that can be used on a computer depend on which Windows 8.1 edition is installed and on the computer’s hardware.

Using Action Center and activating Windows

By default, when you log on, the operating system displays an Action Center summary icon in the desktop notification area. This icon has a white flag on it. Action Center is a program that monitors the status of important security and maintenance areas. If the status of a monitored item changes, Action Center updates the notification icon as appropriate for the severity of the alert. If you tap or click this icon, Windows displays a dialog box with a summary listing of each alert or action item that needs your attention. Tap or click an action item link to run the related solution. Tap or click the Open Action Center link to display the Action Center.

If you’ve disabled Action Center notifications on the taskbar, you can start Action Center by following these steps:

  1. In Control Panel, tap or click the System And Security category heading link.

  2. Tap or click Action Center.

Action Center, shown in Figure 1-1, provides an overview of the computer’s status and lists any issues that need to be resolved. After you have installed Windows 8.1, action alerts in Action Center might let you know that device drivers are available and need to be installed. Simply tap or click the action item to begin the driver installation process. For detailed information on working with Action Center, see the Using automated Help and support section in Chapter 8.

The Action Center window shows issues that need user attention.
Figure 1-1. The Action Center window shows issues that need user attention.

Windows 8.1 Pro and Enterprise editions support volume licensing. Although volume-licensed versions of Windows 8.1 might not require activation or product keys, retail versions of Windows 8.1 require both activation and product keys. You can determine whether Windows 8.1 has been activated in Control Panel by tapping or clicking System And Security, and then tapping or clicking System. On the System page, read the Windows Activation entry. This entry specifies whether you have activated the operating system. If Windows 8.1 has not been activated and you are connected to the Internet, select View Details In Windows Activation, and then tap or click Activate.

Running Windows 8.1 in groups and domains

Computers running Windows 8.1 can be members of a homegroup, a workgroup, a workplace, or a domain. A homegroup is a loose association of computers on a home network. Computers in a homegroup share data that can be accessed by using a password common to the users in the homegroup. You set the homegroup password when you set up the homegroup and can modify the password as necessary at any time.

A workgroup is a loose association of computers in which each computer is managed separately. A workplace is a loose association of computers that grants access to certain internal network resources and business apps. A domain is a collection of computers that you can manage collectively by means of domain controllers, which are servers running Windows that manage access to the network, to the directory database, and to shared resources.

Real World

Workplaces are new in Windows 8.1 and so are Work Folders. Don’t confuse these two features. Workplaces are a middle ground between traditional workgroups and domains. Computers that are members of a workplace can access internal network resources, such as internal websites and business applications. Work Folders allow users to synchronize their corporate data to their devices and vice versa. Those devices can be joined to the corporate domain or a workplace. To deploy Work Folders, an administrator adds the File And Storage Services > Work Folders role to a server, and then configures Work Folders by using Server Manager. Because Work Folders make use of the IIS hostable web core, the folders are accessed via a remote web gateway running on IIS.

Homegroups are available when a computer running Windows 8.1 is connected to a home network. Workgroups, workplaces, and domains are available when a computer running Windows 8.1 is connected to a work network.

Some aspects of Windows 8.1 vary depending on whether a computer is a member of a homegroup, workgroup, workplace, or domain. The sections that follow discuss these differences as they pertain to UAC, logon, fast user switching, and password management.

Understanding UAC in Windows 8.1

In a homegroup, workgroup, or workplace, a computer running Windows 8.1 has only local machine accounts. In a domain, a computer running Windows 8.1 has both local machine accounts and domain accounts. Windows 8.1 has two primary types of local user accounts:

  • Standard. Standard user accounts can use most software and can change system settings that do not affect other users or the security of the computer.

  • Administrator. Administrator user accounts have complete access to the computer and can make any necessary changes.

Windows 8.1 has a special type of local user account called a Microsoft account. Microsoft accounts can be thought of as synchronized local accounts and are discussed in detail in the Understanding user and group accounts section in Chapter 5.

Windows 8.1 includes UAC as a way to enhance computer security by ensuring true separation of standard user and administrator user accounts. Because of the UAC feature in Windows 8.1, all applications run by using either standard user or administrator user privileges. Whether you log on as a standard user or as an administrator user, you get a security prompt by default whenever you run an application that requires administrator privileges. The way the security prompt works depends on Group Policy settings (as discussed in the Optimizing UAC and Admin Approval Mode section in Chapter 5) and whether you are logged on with a standard user account or an administrator user account.

When you are logged on with a standard user account, you are asked to provide a password for an administrator account, as shown in Figure 1-2. In a homegroup, workgroup, or workplace, each local computer administrator account is listed by name. To proceed, you must tap or click an account, enter the account’s password, and then tap or click Yes.

This User Account Control dialog box prompts for administrator credentials.
Figure 1-2. This User Account Control dialog box prompts for administrator credentials.

In a domain, the User Account Control dialog box does not list any administrator accounts, so you must know the user name and password of an administrator account in the default (logon) domain or a trusted domain to continue. When Windows prompts you, enter the account name and password, and then tap or click Yes. If the account is in the default domain, you don’t have to specify the domain name. If the account is in another domain, you must specify the domain and the account name by using the format domainusername, such as cpandlwilliams.

When you are logged on with an administrator user account, you are asked to confirm that you want to continue, as shown in Figure 1-3. You can tap or click Yes to allow the task to be performed, or tap or click No to stop the task from being performed. Tapping or clicking Show Details shows the full path to the program being executed.

This User Account Control dialog box prompts for confirmation to continue.
Figure 1-3. This User Account Control dialog box prompts for confirmation to continue.

Elevation of privileges allows a standard user application to run with administrator privileges. You can run applications with elevated privileges by following these steps:

  1. Press and hold or right-click the application’s tile or shortcut, and then tap or click Run As Administrator.

  2. When the User Account Control prompt appears, proceed as you normally would to allow the application to run with administrator privileges.

Note

You must run the command prompt with elevated privileges to perform administration at the command line. If you do not do this, you will get an error when you try to run an administrator utility or perform a task that requires administrator privileges.

Logging on to, shutting down, and restarting Windows 8.1

Windows 8.1 displays a Lock screen at startup. When you click the Lock screen, you get the Welcome screen. The behavior of the Welcome screen depends on Group Policy settings and the computer’s homegroup, workgroup, or domain membership.

Keep the following in mind:

  • In a homegroup, workgroup, or workplace, the Welcome screen shows a list of accounts on the computer. To log on with one of these accounts, tap or click the account and enter a password if required.

  • In a domain, the name of the last user to log on is displayed by default on the Welcome screen. You can log on with this account by entering the required password. You can log on as another user as well by clicking the Switch User button, selecting one of the alternative accounts listed, and then providing the password for that account or clicking Other User to enter the user name and password for the account to use. Note that the Switch User button has a left-pointing arrow in a circle and is to the left of the account picture.

By default, the last account to log on to the computer is listed in computerusername or domainusername format. To log on to this account, you enter the account password, and then tap or click the Submit button. The Submit button is part of the Password box, and shows a right-pointing arrow. To log on to a different account, tap or click Switch User, press Ctrl+Alt+Del, and then tap or click Other User. The logon information that you must provide depends on what type of account you are using:

  • If the account is in the current/default domain, enter the user name and password, and then tap or click the arrow button.

  • If the account is in another domain, you must specify the domain and the account name by using the format domainusername, such as cpandlwilliams.

  • If you want to log on to the local machine, enter .username, where username is the name of the local account, such as .williams.

When you are logged on, you can display the Windows Logon screen by pressing Ctrl+Alt+Del. This screen allows you to lock the computer, switch users, sign out, change a password, or start Task Manager. The Power button is in the lower-right corner of the screen. Tapping or clicking the Power button displays Sleep, Shut Down, and Restart options.

Because Shut down and Restart are options of the Power settings, you also can shut down or restart a computer by following these steps:

  1. Slide in from the right side of the screen or press Windows key + C.

  2. Tap or click Settings, and then tap or click Power.

  3. Tap or click Shut Down or Restart as appropriate.

Note

Windows 8.1 supports fast user switching in domain, homegroup, and workgroup configurations. When a user is logged on to a computer running Windows 8.1, you can use fast user switching to allow another user to log on without requiring the current user to log off. To switch users, press Ctrl+Alt+Del, and then tap or click Switch User.

Managing user account passwords with Windows 8.1

Windows 8.1 provides fast and easy ways to manage user account passwords. You can easily perform the following tasks:

  • Change the current user’s password.

  • Change the password for another domain or local computer account.

  • Create a password reset disk.

  • Reset a user’s password.

These tasks are discussed in the sections that follow.

Changing the Current User’s Password

You can change the current user’s password by completing the following steps:

  1. Press Ctrl+Alt+Del, and then tap or click the Change A Password option.

    Note

    In a domain, the current user’s domain account name is listed in domainusername format. In a homegroup, workgroup, or workplace, the current user’s local account name is listed.

  2. Enter the current password for the account in the Old Password text box.

  3. Enter and confirm the new password for the account in the New Password and the Confirm Password text boxes.

  4. Tap or click the arrow button to confirm the change.

Changing Other Account Passwords

You can change the password for a domain or a local account other than the current user’s account by completing these steps:

  1. Press Ctrl+Alt+Del, and then tap or click the Change A Password option.

  2. Tap or click in the User Name text box, and then enter the name of the account.

    Note

    For a domain account, specify the domain and the account name by using the format domainusername, such as cpandlwilliams. For a local computer account, enter .username, where username is the name of the local account, such as .williams.

  3. Enter the current password for the account in the Old Password text box.

  4. Enter and confirm the new password for the account in the New Password and the Confirm Password text boxes.

  5. Tap or click the arrow button to confirm the change.

Creating and Using a Password Reset Disk

Passwords for domain users and local users are managed in different ways. In domains, passwords for domain user accounts are managed by administrators. Administrators can reset forgotten passwords by using the Active Directory Users And Computers console.

In homegroups and workgroups, passwords for local machine accounts can be stored in a secure, encrypted file on a password reset disk, which is a USB flash drive that contains the information needed to reset your password. You can create a password reset disk for the current user by completing these steps:

  1. Press Ctrl+Alt+Del, and then tap or click the Change A Password option.

  2. Tap or click Create A Password Reset Disk to start the Forgotten Password Wizard.

  3. In the Forgotten Password Wizard, read the introductory message. Insert the USB flash drive you want to use, and then tap or click Next.

  4. Select the USB flash drive you want to use in the drive list. Tap or click Next.

  5. Enter the current password for the logged on user in the text box provided, and then tap or click Next.

  6. After the wizard creates the password reset disk, tap or click Next, remove the disk, and then tap or click Finish.

Be sure to store the password reset disk in a secure location because anyone with access to the disk can use it to gain access to the user’s data. If a user is unable to log on because he or she has forgotten the password, you can use the password reset disk to create a new password and log on to the account by using this password.

Real World

You can use BitLocker To Go to protect and encrypt USB flash devices and other removable media drives. When a user is logged on, protected media can be unlocked by using a password or a smart card with a smart card PIN. However, when a user isn’t logged on, the protected drive cannot be accessed. Because of this, you shouldn’t protect password reset disks with BitLocker To Go.

Resetting a User’s Password

Administrators can reset forgotten passwords by using the Active Directory Users And Computers console. In homegroups and workgroups, you can reset a password by following these steps:

  1. On the Log On screen, tap or click the arrow button without entering a password, and then tap or click OK. The Reset Password option should be displayed. If the user has already entered the wrong password, the Reset Password option might already be displayed.

  2. Insert the disk or USB flash device containing the password recovery file, and then tap or click Reset Password to start the Reset Password Wizard.

  3. In the Reset Password Wizard, read the introductory message, and then tap or click Next.

  4. Select the device you want to use in the drive list, and then tap or click Next.

  5. On the Reset The User Account Password page, enter and confirm a new password for the user.

  6. Enter a password hint, and then tap or click Next. Tap or click Finish.

Power plans, sleep modes, and shutdown

Normally, computers running Windows 8.1 use the Balanced power plan, and this power plan turns off the display and puts the computer in sleep mode automatically after a specified period of time passes with no user activity.

When entering the sleep state, the operating system automatically saves all work, turns off the display, and puts the computer in sleep mode. Sleep mode is a low-power consumption mode in which the state of the computer is maintained in the computer’s memory, and the computer’s fans and hard disks are turned off.

Windows 8.1 saves the computer state before entering sleep mode, and you don’t need to exit programs before you do this. Because the computer uses very little energy in the sleep state, you don’t have to worry about wasting energy.

Tip

Sleep mode works in slightly different ways depending on the type of computing device. Often you can turn off and turn on mobile computers by closing or opening the lid. When you close the lid, the laptop enters the sleep state. When you open the lid, the laptop wakes up from the sleep state. If the laptop is in the sleep state for an extended amount of time, or the laptop’s battery runs low on power, the state of the computer is saved to the hard disk and then the computer shuts down completely. This final state is similar to the hibernate state used in early versions of Windows.

To view or modify the default power options, open Control Panel. In Control Panel, tap or click System And Security, and then, under Power Options, tap or click Change When The Computer Sleeps. The options available depend on the type of computing device. With mobile computers and tablets, as shown in Figure 1-4, you might be able to set On Battery and Plugged In options for turning off the display, putting the computer to sleep, and adjusting the display brightness. With desktop computers, you can only specify when the display is turned off and when the computer goes to sleep. Tap or click Save Changes to save your changes.

You can cause most computers to enter the sleep state by tapping or clicking the Settings charm button, tapping or clicking Power, and then tapping or clicking Sleep. To wake the computer from the sleep state, you can press and hold somewhere on the touch screen, move the mouse, or press any key on the keyboard. Note that some computers have separate power and sleep buttons on their case. The way these buttons work can be set through the power plan options.

Configure power options to optimize power management for the computer.
Figure 1-4. Configure power options to optimize power management for the computer.

There are instances in which a computer can’t use the sleep state. The system hardware, state, and configuration can affect the way the power and sleep buttons work. Some computer hardware doesn’t support the sleep state. In this case, the computer can’t use the sleep state. This is also the case when the computer has updates installed that require a restart or when you’ve installed programs that require a restart. Additionally, if an administrator has reconfigured the power options on the computer and set the power button, the sleep button, or both to alternative actions, the computer will use those actions instead of the default shutdown and sleep actions.

Caution

When working with computers in the sleep state, keep in mind that the computer is still drawing power. You should never install hardware inside the computer when it is in the sleep state. To avoid possible confusion regarding the sleep state and the power off state, be sure to unplug desktop computers running Windows 8.1 before installing internal devices. External devices are exceptions. You can connect USB, FireWire, and eSATA devices without shutting down the computer.

To change the default setting for the power button, open Control Panel. In Control Panel, tap or click System And Security, and then, under Power Options, tap or click Choose What The Power Buttons Do. As before, the options available depend on the type of computing device. With mobile computers, as shown in Figure 1-5, you might be able to set On Battery and Plugged In options that specify what happens when you press the power button, what happens when you press the sleep button, and what happens when you close the lid. Optionally, you can tap or click Change Settings That Are Currently Unavailable, and then do any of the following:

  • Choose Require A Password to require a password to log on after waking the computer from sleep.

  • Choose Turn On Fast Startup to save system information to a file on the system disk when you shut down the computer. This file is then read during startup to enable faster startup. When you restart a computer, Fast Startup is not used.

  • Choose the Power options you want displayed when you click Power.

Save your changes by tapping or clicking Save Changes.

Configure power button options.
Figure 1-5. Configure power button options.

Windows 8.1 architecture

If you want to truly know how Windows 8.1 works and what makes it tick, you need to dig under the hood. Windows 8.1 doesn’t start from an initialization file. Instead, the operating system uses the Windows Boot Manager to initialize and start the operating system.

The boot environment dramatically changes the way the operating system starts. The boot environment was created by Microsoft to resolve several prickly problems related to boot integrity, operating system integrity, and firmware abstraction. The boot environment is loaded prior to the operating system, making it a pre–operating system environment. As such, the boot environment can be used to validate the integrity of the startup process and the operating system itself before actually starting the operating system.

The boot environment is an extensible abstraction layer that allows the operating system to work with multiple types of firmware interfaces without requiring the operating system to be specifically written to work with these firmware interfaces. Rather than updating the operating system each time a new firmware interface is developed, firmware interface developers can use the standard programming interfaces of the boot environment to allow the operating system to communicate as necessary through the firmware interfaces.

Firmware interface abstraction is the first secret ingredient that makes it possible for Windows 8.1 to work with BIOS-based and EFI-based computers in exactly the same way, and this is one of the primary reasons Windows 8.1 achieves hardware independence.

The next ingredient for hardware independence is Windows Imaging (WIM) format. Microsoft distributes Windows 8.1 on media by using WIM disk images. WIM uses compression and single-instance storage to dramatically reduce the size of image files. Using compression reduces the size of the image in much the same way that zip compression reduces the size of files. Using single-instance storage reduces the size of the image because only one physical copy of a file is stored for each instance of that file in the disk image.

The final ingredient for hardware independence is modularization. Windows 8.1 uses modular component design so that each component of the operating system is defined as a separate, independent unit or module. Because modules can contain other modules, various major features of the operating system can be grouped together and described independently of other major features. Because modules are independent from each other, modules can be swapped in or out to customize the operating system environment.

Windows 8.1 includes extensive support architecture. At the heart of this architecture is built-in diagnostics and troubleshooting. Microsoft designed built-in diagnostics and troubleshooting to be self-correcting and self-diagnosing or, failing that, to provide guidance while you are diagnosing problems.

Windows 8.1 includes network awareness and network discovery features. Network awareness tracks changes in network configuration and connectivity. Network discovery controls a computer’s ability to detect other computers and devices on a network.

Network awareness allows Windows 8.1 to detect the current network configuration and connectivity status, which is important because many networking and security settings depend on the type of network to which a computer running Windows 8.1 is connected. Windows 8.1 has separate network configurations for domain networks, private networks, and public networks and is able to detect the following:

  • When you change a network connection

  • Whether the computer has a connection to the Internet

  • Whether the computer can connect to the corporate network over the Internet

Windows Firewall in Windows 8.1 supports connectivity to multiple networks simultaneously and multiple active firewall profiles. Because of this, the active firewall profile for a connection depends on the type of connection.

If you disconnect a computer from one network switch or hub and plug it into a new network switch or hub, you might inadvertently cause the computer to think it is on a different network, and depending on Group Policy configuration, this could cause the computer to enter a lockdown state in which additional network security settings are applied. As shown in Figure 1-6, you can view the network connection status in the Network And Sharing Center. In Control Panel, under Network And Internet, tap or click View Network Status And Tasks to access this management console.

Tip

Through the DirectAccess feature, computers running Windows 8.1 can directly access corporate networks wherever they are as long as they have access to the Internet, and best of all, users don’t need to initiate VPN connections. The feature relies on DirectAccess servers being configured on the corporate network and DirectAccess being enabled in Group Policy.

Determine the network state.
Figure 1-6. Determine the network state.

Windows 8.1 tracks the identification status of all networks to which the computer has been connected. When Windows 8.1 is in the process of identifying a network, the Network And Sharing Center shows the Identifying Networks state. This is a temporary state for a network that is being identified. After Windows 8.1 identifies a network, the network becomes an Identified Network and is listed by its network or domain name in the Network And Sharing Center.

If Windows 8.1 is unable to identify the network, the network is listed with the Unidentified Network status in the Network And Sharing Center. In Group Policy, you can set default location types and user permissions for each network state, as well as for all networks, by using the policies for Computer Configuration under Windows SettingsSecurity SettingsNetwork List Manager Policies.

When you are working with the Network And Sharing Center, you can attempt to diagnose a warning status by using Windows Network Diagnostics—another key component of the diagnostics and troubleshooting framework. To start diagnostics, tap or click Troubleshoot Problems, tap or click Internet Connections, and then tap or click Next. Windows Network Diagnostics then attempts to identify the network problem and provide a possible solution.

The Windows diagnostics and troubleshooting infrastructure offers improved diagnostics guidance, additional error reporting details, expanded event logging, and extensive recovery policies. Although early versions of Windows include some help and diagnostics features, those features are, for the most part, not self-correcting or self-diagnosing. Windows now can detect many types of hardware, memory, and performance issues and resolve them automatically or help users through the process of resolving them. For more information, see the Working with the automated Help and support system section in Chapter 8.

Error detection for devices and failure detection for disk drives also are automated. If a device is having problems, hardware diagnostics can detect error conditions and either repair the problem automatically or guide the user through a recovery process. With disk drives, hardware diagnostics can use fault reports provided by disk drives to detect potential failure and alert you before this happens. Hardware diagnostics can also help guide you through the backup process after alerting you that a disk might be failing.

Windows 8.1 can automatically detect performance issues, which include slow application startup, slow boot, slow standby/resume, and slow shutdown. If a computer is experiencing degraded performance, Windows diagnostics can detect the problem and provide possible solutions. For advanced performance issues, you can track related performance and reliability data in the Performance Monitor console, which is an administrative tool.

Windows 8.1 can also detect issues related to memory leaks and failing memory. If you suspect that a computer has a memory problem that is not being automatically detected, you can run Windows Memory Diagnostic manually by completing the following steps:

  1. From Start, type mdsched.exe, and then press Enter. Normally, text that you type on Start is entered into the Apps Search box by default.

  2. Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart, as shown in Figure 1-7.

    Test memory for problems.
    Figure 1-7. Test memory for problems.
  3. Windows Memory Diagnostic runs automatically after the computer restarts and performs a standard memory test. If you want to perform fewer or more tests, press F1, use the up and down arrow keys to set the Test Mix as Basic, Standard, or Extended, and then press F10 to apply the desired settings and resume testing.

  4. When testing is complete, the computer restarts. The test results will be displayed when you log on.

If a computer crashes because of failing memory and Memory Diagnostic detects this, you are prompted to schedule a memory test the next time the computer is started.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset