Client-3.4-4.1.docx

On Windows 8 and newer versions, you have a choice to install either traditional desktop applications or to install apps from the Windows Store. This lesson focuses on managing desktop applications. This lesson covers the following topics: - Desktop application installation process - Desktop...

On Windows 8 and newer versions, you have a choice to install either traditional desktop applications or to install apps from the Windows Store. This lesson focuses on managing desktop applications. This lesson covers the following topics: - Desktop application installation process - Desktop application management - Application registries **Desktop Application Installation Process** **Verify Compatibility**: **Scan for Malware**: **Create a Restore Point**: **Install the Application**: Desktop Application Management Installed applications are most commonly managed through the Apps link found on the homepage of the Windows Settings app. When an application has been selected using this method, you\'ll have one or more of the following options available. Choose where the app goes: Under *Advanced app settings* , there are a few choices to help ensure the safety of application downloads. The choice defines where applications can come from. For example: - Anywhere - Anywhere, but let me know if there\'s a comparable app in the Microsoft Store - Anywhere, but warn me before installing an app that\'s not from the Microsoft Store - The Microsoft Store (recommended) Repair apps: You might run into a situation in which an application is crashing, behaves erratically, or is freezing. If this happens, it's possible that one or more of the application files have been corrupted or accidentally deleted. In this type of situation, you can attempt to fix the application. Some application installers include a repair feature. If selected, the repair feature will search the files used by the application to find any that are missing or corrupt. It will then replace them using the original files from the installer. To repair an app: Some apps don\'t provide the Modify option. So, to attempt to repair this type of app, you can use the Advanced options (if available) after locating the desired app from Installed apps. This gives you the ability to try to repair the app using the Repair or Reset feature. Repair will try to fix the app without affecting your data. The Reset option will try to fix the app, but will delete all its data. Uninstall: At times, you may need to uninstall an application. For example, if you no longer use the app and want to reclaim the disk space that it\'s using. Another situation is if the installer either doesn\'t have a Repair option or the Repair option didn\'t solve the issue. The next best choice may be to uninstall the application and reinstall it. **Uninstall** **Other options:** When working from within the Settings app, there are several other options to help manage your apps, such as: - Advanced app settings -- lets you choose where to get apps, archive apps, and uninstall updates. - Default apps -- lets you determine which app to use when opening files. - Startup -- lets you determine which apps should run automatically when the computer boots. A wealth of information about each application can be found in the application\'s Registry keys. The path to application keys is HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall. In the Registry, you will see a list of the applications that are installed on the system. Each app in the Registry has a key. Within each of these keys are sub-keys that contain helpful information such as: - Display name - Publisher - Install date - Version numbers - A help link from the publisher - An uninstall string **Regedit** **Local Printer Sharing** A printer attached to a computer can be shared with the other computers in your network. Sharing a printer means that users on the network can see and print to a printer physically attached to someone else\'s computer. Sharing a printer helps reduce cost and administration time. To share a local printer, complete the following steps on the computer the printer is attached to: 1. Right-click **Start** and select **Settings** \> **Bluetooth & devices**. 2. Select **Printers & scanners**. 3. Select the desired **printer**. 4. Select **Printer properties**. 5. Select the Sharing tab, select **Change Sharing Options**. 6. Select **Share this printer**. 7. Enter a **share name**. (Use a share name that will make the printer easily identifiable by users.) 8. Click **Apply** and then **OK**. 9. If needed, add additional drivers to support other Windows versions. The additional drivers are downloaded when the client connects to the printer. This prevents users from having to manually install the driver and potentially installing the wrong driver. Before a shared printer can be used by remote users, you must turn on network discovery and file and printer sharing. You must also grant permissions to those requiring access to the printer. - To turn on Network discovery and File sharing, complete the following: 1. Open **File Explorer**. 2. Open **Network**. 3. An error message will display that states, \"Network discovery is turned off\...\". To turn it on, select the **Network discovery is turned off** banner and then select **Turn on network discover and file sharing**. - To change your network sharing settings: 1. Open **Settings** \> **Network & internet**. 2. Click the **Wi-Fi** or **Ethernet** tab. 3. Under *Network profile type* , select **Private**. To grant permissions to use a printer, use the Security tab of the printer properties to add the applicable users/groups and then grant them the required permissions. While configuring security, consider the following permissions: Print: This permission allows users to manage their own print jobs for the print queue. The ALL APPLICATION PACKAGES under Group or user name represents Windows Store apps. By default, the Everyone group is assigned the Print permission for a shared printer. This allows all workgroup users or domain account users to use the printer. You can restrict printer access by manually entering users and groups you want to allow access. Manage this Printer: This permission includes the Print permissions and allows the user to manage the printer\'s configuration settings and permissions. These permissions include Pause a print job, Restart a print job, Change spooler settings, Adjust printer permissions, Change printer properties, and Share a printer. Manage Documents: The Manage Documents permission allows the user to manage all print jobs in the printer queue. A user can have the Manage Documents permission without having the Print or Manage permissions. By default, users can manage their own documents in the print queue. They can manage other users\' documents only if they have the Manage Documents permission. Document management tasks include: Shared Printer Connection After a printer has been shared on the network, each client must connect to the shared printer as follows: Right-click Start and select Settings \> Bluetooth & devices. Select Printers & scanners. Select Add a device. Wait while Windows searches for nearby printers. Select the name of the printer you want to add (connect to). Follow the on-screen instructions to install the printer onto your computer. The printer that I want isn\'t listed Find a printer in the directory, based on location or feature. Select a shared printer by name. Add a printer using a TCP/IP address or hostname. Add a Bluetooth, wireless, or network discoverable printer. Add a local or network printer with manual settings. By default, standard users can install printers. **Default Printer Configuration** When you print a file, Windows begins the print process using a default printer. In most cases, the printer used can be changed, but having the printer you use the most as the default saves time and reduces the chance that you\'ll print to the wrong printer. When Windows is first installed, it automatically determines your default printer. It does so by finding the printer you used most recently at your current location. To manually configure your default printer, complete the following: 1. Right-click **Start** and select **Settings** \> **Bluetooth & devices**. 2. Select **Printers & scanners**. 3. Under printer preferences, uncheck **Let Windows manage my default printer**. 4. Select the desired printer and then select **Manage**. 5. Select **Set as default**. **Print Management Using the Settings App** **Devices and Printers** From Printers & scanners, you can add, delete, and manage the printers for the local computer. If given permissions, you can also add shared printers. **Print Management Using the Print Management App** The Windows Pro and Enterprise editions let you manage printers using the Printer Management app. You can open the Print Management app using any of the following methods: - From the Start button, right-click **Start** and go to **Windows Administrative Tools** \> **Print Management**. - From the Windows search field found on the taskbar, enter **Printmanagement** and run the Print Management app. - Run **Printmanagement.msc** from PowerShell or a Command Prompt. From the Print Management console, you can complete print management tasks for both local and remoter printers, such as: - View all printers and print servers. - Add or delete printers. - Add or remove print servers. - Add, delete, and manage print drivers. - View and manage printer queues. - View and modify the status of your printers. - Migrate printers. - Deploy printers using Group Policy. Once you have opened Printer Management, you can select a printer by right-clicking it. You can select the following tasks: - Open Printer Queue - Pause Printing - Deploy With Group Policy - Set Printing Defaults - Manage Sharing - Print Test Page - Enable Branch Office Direct Printing - Properties - Delete - Rename - Help Printer Management Using PowerShell You can also use PowerShell cmdlets to manage the printer. The following table shows all print management cmdlets and description for each: **Add-Printer** Adds a printer to the specified computer. ---------------------------- ---------------------------------------------------------------------------- **Get-PrinterDriver** Retrieves the list of printer drivers installed on the specified computer. **Add-PrinterPort** Installs a printer port on the specified computer. **Get-PrintConfiguration** Gets the configuration information of a printer. **Get-PrintJob** Retrieves a list of print jobs in the specified printer. **Get-Printer** Retrieves a list of printers installed on a computer. **Get-PrinterDriver** Retrieves the list of printer drivers installed on the specified computer. **Get-PrinterPort** Retrieves a list of printer ports installed on the specified computer. **Get-PrinterProperty** Retrieves printer properties for the specified printer. **Read-PrinterNfcTag** Reads information about printers from an NFC tag. **Remove-PrintJob** Removes a print job on the specified printer. **Remove-Printer** Removes a printer from the specified computer. **Remove-PrinterDriver** Deletes printer driver from the specified computer. **Remove-PrinterPort** Removes the specified printer port from the specified computer. **Rename-Printer** Renames the specified printer. **Restart-PrintJob** Restarts a print job on the specified printer. **Resume-PrintJob** Resumes a suspended print job. **Set-PrintConfiguration** Sets the configuration information for the specified printer. **Set-Printer** Updates the configuration of an existing printer. **Set-PrinterProperty** Modifies the printer properties for the specified printer. **Suspend-PrintJob** Suspends a print job on the specified printer. **Write-PrinterNfcTag** Writes printer connection data to an NFC tag. Creating a reference image is the process of customizing a Windows installation and storing it in a special file that can then be deployed to multiple machines. This lesson covers the following topics: - Image files - Windows Imaging Format (WIM) files - Windows Assessment and Deployment Kit (Windows ADK) - Microsoft Deployment Toolkit (MDT) - Sysprep - Windows Pre-Installation Environment (WinPE) **Image Files** An image file is a copy of the contents of a hard drive, DVD, or other media stored as a single file. There are different types of image files used in computing. For example, an image of a DVD is called an ISO image because it has the file extension.iso. **Windows Imaging Format (WIM) Files** When creating a Windows reference image, Microsoft uses the Windows Imaging Format. This format allows users to create an image of the computer system configuration. This base image of a system\'s configuration is referred to as a reference image. - Reference images are often called WIM files because they have the file extension.wim. - WIM files are file-based images. - Only the files and settings are copied, unlike a standard image file where each sector is copied individually. - Multiple Windows images can be stored in a single file. - Each image is given a unique name. - WIM files use a unique single-instance storage structure. - A file can be used by multiple images but stored only once. - A file can be accessed by all images. - Image size is reduced. **Windows Assessment and Deployment Kit (Windows ADK)** The Windows Assessment and Deployment Toolkit is a collection of tools from Microsoft to simplify the process of creating and deploying Windows images. The following table describes tools within the ADK collection. Windows System Image Manager (SIM): A useful tool that assists in creating answer files. Windows Configuration Designer: Tool used to create provisioning packages. Deployment and Imaging Tools Environment: Customized command line tool that allows any command line tool in the ADK to be run. Deployment Image Servicing and Management (DISM): A command line tool that can manually capture, modify, and deploy a Windows image. **Microsoft Deployment Toolkit (MDT)** The MDT provides a unified collection of tools, processes, and guidance for automating server and desktop deployments. **Sysprep** Sysprep is a tool included with Windows and stored in the System32 folder. Be aware of the following regarding Sysprep. - The main purpose of Sysprep is to strip a Windows installation of its security identifier and make the Windows installation as generic as possible before creating the reference image. This is done to remove conflicts when loading the image onto another computer. - With newer versions of Windows, Sysprep has become less reliable and will often generate error messages. This usually occurs if apps from the Windows Store have been installed on the reference machine. **The Windows Pre-Installation Environment (WinPE)** WinPE is a bare minimum version of Windows that can boot, install, deploy, and repair a system. You can also use WinPE to do the following: - Set up a hard drive before a Windows installation. - Recover data from unbootable devices. - Modify the operating system when it is not running. - Set up automatic recovery tools. There are several benefits to creating customized Windows images. Specific drivers, application, language packs, settings, and more can be pre-loaded, configured, and stored with the image. Before you capture the Windows images intended for mass redistribution, you must complete the appropriate preparation steps. This lesson covers the following topics: - Sysprep preparation - The Microsoft Deployment Toolkit (MDT) process - Deployment share creation and configuration **Sysprep Preparation** A *reference image* is the system image you want to install on other computers. You create it using a reference computer. Keep the following in mind when building a reference image. - Typically, the reference computer is manually built. - Windows, applications, and drivers are manually installed and configured. - Network settings, security settings, and any specific organizational settings are manually configured. - Before a reference image can be deployed to multiple machines, it must be made generic. You can do this with the Sysprep tool. Sysprep removes hardware specific drivers, the computer name, the security identifier (SID), and several other specifics. Sysprep is included with all versions of Windows and is stored in the \\Windows\\System32\\Sysprep folder. Once Sysprep runs and completes its configuration, the reference machine must be shut down and not turned back on. If the machine boots up after Sysprep has been run, it regenerates a computer name and security identifier. If the machine boots before taking the image, you\'ll need to Sysprep it again. Another method of preparing to deploy images to multiple computers is using the Microsoft Deployment Workbench. The Deployment Workbench is one of the tools installed with the MDT. With the Deployment Workbench, you first create a deployment share. A deployment share includes all the information, packages, operating system files, task sequences, and drivers required to install and configure the desired version of Windows. The task sequence is a critical part of the preparation. Task sequences specify the template to use, and a template guides you through the process of specifying the purpose of your Windows deployment. In most cases, you\'ll use the Standard Client Task Sequence. You should specify the following: - The desired operating system to install - The operating system product key - The operating system settings - An admin password When the deployment share has been created and configured, it also includes an ISO file that will be used to boot a Hyper-V machine. This ISO is configured to locate the deployment share on the management machine. To create an image that can be deployed, you boot a new Hyper-V machine from the ISO file. You are then connected to the deployment share, and the new operating system will be installed on the Hyper-V machine based on the settings in your task sequence. An image is then automatically created from the new Hyper-V machine and saved on the deployment share. You can use this image for later deployments. **Deployment Share Creation and Configuration** To capture a reference image using MDT, create and configure a deployment share as follows: 1. Install the MDT, the Assessment and Deployment Kit (ADK), and the Windows Preinstallation Environment Add-on (WinPE files) on a management machine. 2. Run the Deployment Workbench to create a deployment share. 3. Configure the deployment share with the following: a. Load the Windows operating system from installation media for the version of Windows you want to deploy. You can alternately use a previously captured WIM file. b. Go through the options to load applications, drivers, language packs, etc. c. Create a task sequence. The task sequence defines each step that will happen during deployment of the image. - This includes such things as setting the computer name, administrator password, Windows license key, etc. - This also creates the answer file, so you don\'t have to manually create one. d. Edit the properties of the deployment share and configure: - The rules - This creates the CustomSettings.ini file used for unattended installs. - The Bootstrap.ini file - The Bootstrap.ini points the installation to the deploy share. - Windows PE settings - Monitoring (optional) 4. Update the deployment share. This creates everything required to create and capture an image, including creating the ISO image that can be used to boot to a WinPE environment. This completes the preparation required, and you are now ready to use the WinPE ISO to capture your image as described above. After a Windows reference image has been created, it must be captured. Capturing an image is the process of converting it to a Windows Imaging Format (WIM) file or other appropriate image file format that can be deployed. The capture process varies depending on the method you used to create the image in the first place. This lesson covers the following topics: - Reference images - Microsoft Deployment Toolkit (MDT) **Reference Images** If you used a reference machine to create the image, you use the Deployment Image Servicing and Management (DISM) tool to capture the image. DISM is a command line tool that must be run with administrator privileges to function properly. Since the reference machine cannot be booted after Sysprep has been run, you must use the Windows Preinstallation Environment (WinPE) when creating the image. WinPE is a special, minimal version of Windows that is used to install, deploy, and repair Windows. To capture the image from WinPE, complete the following steps: 1. Download and prepare the WinPE environment (USB, DVD). 2. Boot the reference computer to the Windows PE environment. 3. From within the WinPE environment, run the **diskpart** command. 4. Assign drive letters to all partitions to be imaged on the reference system. Do this by selecting the partitions, one at a time, and entering: **assign letter= *letter*** 5. Prepare a storage location for the image to be captured. Do one of the following: - Connect a removable storage device (such as a removable USB drive) to the reference system. - Enter **NET USE** to connect to the network share. 6. Capture an image of each partition using the following DISM command: **dism /capture-image /imagefile: *image\_file\_name* /capturedir: *source\_directory* /name: *image\_name*** **dism /capture-image** - DISM is typically executed from within the WinPE environment on the reference computer to capture an image of an existing Windows volume. - The image is saved as a WIM file. - You can use DISM to modify an existing image, such as adding drivers, without recapturing the entire image from the reference computer. Use the following DISM options to capture an image: - **/Compress** - specifies the type of compression used for the capture operation: - **Maximum** - provides the best compression, but increases the amount of time required to capture the image - **Fast** - provides faster image capture, but does not compress the image as much as the Maximum option - **None** - does not compress the captured image - **/ImageFile *:image\_file\_name*** - specifies the filename of the captured image (the path to the image file must also be specified) - / **CaptureDir: *source\_directory*** - specifies the volume path to be imaged - **/Name: *image\_name*** - specifies a name for the image **Microsoft Deployment Toolkit** To capture the image created with the MDT, it\'s easiest to utilize a virtual machine. Follow these steps to create the image from the MDT. 1. Use the bootable ISO file in the *Boot* folder in the deployment share location. This ISO file is used to boot a virtual machine. 2. The virtual machine boots into a special WinPE environment and loads the Windows Deployment Wizard. 3. In the wizard, specify the UNC path where the image files are stored (this is the deployment share location). 4. The wizard goes through the process of building the image. 5. When the process is completed, the WIM file is created and ready for deployment. Once an image has been created, it can be deployed to machines as needed. There are three categories of Windows deployment methods. This lesson covers the following topics: - Modern deployment - Dynamic provisioning - Traditional deployment **Modern Deployment** Modern deployment methods are the recommended methods used to deploy images unless there is a specific reason to use a different procedure. These methods all use the Microsoft Deployment Toolkit (MDT) or the System Center Configuration Manager (SCCM). **Dynamic Provisioning** Dynamic provisioning methods allow for custom settings and applications in specific use cases. These methods change the OEM Windows that come pre-loaded on a computer system.