1 / 180

Module 0

Module 0. Outline & Introduction . Session Overview. Day 1 Built-In Tools Deployment Options File Server Resource Manager (FSRM) Home Directory Group Policy Windows Server Update Services (WSUS) Windows Deployment Server (WDS)

airell
Télécharger la présentation

Module 0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Module 0 Outline & Introduction

  2. Session Overview Day 1 • Built-In Tools • Deployment Options • File Server Resource Manager (FSRM) • Home Directory • Group Policy • Windows Server Update Services (WSUS) • Windows Deployment Server (WDS) • Windows Automated Installation Kit & Assessment and Deployment Kit (WAIK / WADK) • Windows Deployment Tool kit

  3. Session Overview Day 2 • System Center Configuration Manager • Overview • Manage Software Deployments • Create and Deploy Applications • Deploy and Manage Software Updates • Managing Operating System Deployments • Managing Compliance Settings

  4. Module 1 File Server Resource Manager (FSRM)

  5. Module Overview • Issues Surrounding Workstation Management • Overview of FSRM Using FSRM to Manage Quotas, File Screens, and Storage Reports

  6. What Is an In-Place Deployment? • In-place upgrade: upgrade existing computers to Windows 7 and maintain their configurations • Source and destination computer • Wipe-and-load: replace the computers’ current configuration with new ones, selectively migrating portions of their previous configurations • Upgrade • Restore user state • Collect user state • Intermediate store • Existing computer

  7. What Is a Side-by-Side Deployment? • Deployment scenario where source and destination computer are two different computers • Destination computer • Source Computer • Intermediate store • Collect user state • Restore user state

  8. Determining a Deployment Scenario When will you use the following deployment scenarios? In-place (upgrade) 1 Wipe-and-load (refresh) 2 Side-by-side (replace) 3

  9. Determining a Deployment Scenario When will you use the following deployment scenarios? In-place (upgrade) 1 Wipe-and-load (refresh) 2 Side-by-side (replace) 3

  10. What Is Lite-Touch Deployment? What is Lite-Touch Deployment?

  11. What Is Zero-Touch Deployment? What is Zero-Touch Deployment?

  12. What Is FSRM? • FSRM Enables the following functionality: • Storage quota management • File screening management • Storage reports management • Classification management • File management tasks

  13. What Is File Screening Management? File screen management provides a method for controlling the types of files that can be saved on file servers • File screen management consists of: • Creating file screens • Defining file screen templates • Creating file screen exceptions • Creating file groups

  14. What Are Storage Reports? Storage reports provide information about file usage on a file server • Types of storage reports include: • Duplicate Files • File Screening Audit • Files by File Group, Owner, or Property • Folders by Property • Large Files • Quota Usage • Least and most recently accessed files

  15. Module 2 Deploying and Maintaining Images

  16. Module Overview • Overview of Windows Deployment Services Implementing Deployment with Windows Deployment Services Administering Windows Deployment Services

  17. Tools Used to Support the Planning Phase Enterprise Learning Framework (ELF) System Center Configuration Manager 2007 Microsoft Assessment and Planning Toolkit (MAP) 4.0 Microsoft Application Compatibility Toolkit (ACT) 5.5 Microsoft Desktop Optimization Pack (MDOP) for Asset Inventory Planning 1.0 P L A N Microsoft Deployment Toolkit (MDT) 4.2

  18. Tools Used to Support the Building Phase MDT Deployment Workbench Windows Automated Installation Kit (WAIK) User State Migration Tool (USMT) B U I L D

  19. Tools Used to Support the Deploying Phase MDT Deployment Workbench Windows Deployment Services (WDS) User State Migration Tool (USMT) System Center Configuration Manager D E P L O Y

  20. What Is Windows Imaging File Format? • A file-based disk image format that contains compressed files used to install operating systems Windows Image (.wim) File WIM Header Metadata Resource (Image 1) Metadata Resource (Image 2) File Resource File Resource File Resource File Resource Lookup Table XML Data Integrity Table File Resource File Resource Lookup Table XML Data Integrity Table Image 1 Image 2

  21. How Windows Uses Modularization Modularization allows you to: Add multiple device drivers and updates to the image files ü • Customize optional Windows features ü Update individual elements in the image files ü • Deploy multiple language versions of Windows using a single image file ü

  22. The Imaging Process The Deployment processes

  23. Types of Images Three different type of images: • Thick images • Core application • Language packs • Other files • Thin images • Few applications • Few language packs Hybrid images Mix thin and thick image strategies

  24. What Is an Image Strategy? An image strategy defines the standard configuration of each common operating system image that is created by an organization. An image strategy must include the following elements: Type of images ü Number of images ü Number of WIM files ü Pre-configured settings in an image ü Additional operating system elements ü

  25. Image Strategy Flowchart Are Multiple Builds Required? Yes SCCM Available? No No Yes Is Storage Cost a Factor? Is Network Traffic a Factor? Yes No Yes No Hybrid Image Thin Image Thick Image

  26. Onsite Image Engineering Process Create New Deployment Share MDT Initial Setup Add Operating System (for master image) Add Applications (for master image) Create and stock the Deployment Share Add Packages (for master image) Add Drivers (for master image) Task Sequence Add Task Sequence to Build and Capture Master Image Configure Deployment Properties in CS.ini Configure Master Image Settings Build Reference Machine, Sysprep and Capture WIM Build Master Image and Capture

  27. Sharing Best Practices for Designing Images Identify and discuss several best practices for image-based deployment.

  28. Sharing Best Practices for Designing Images • The following list outlines several best practices for image-based deployment: • Use a single image strategy to reduce the number of images to maintain and service. • Use a multilingual strategy to add multiple language packs to your image to reduce the number of language-specific images that you support. • Run the sysprep /generalize command when preparing the Windows image to be captured, even if all computers have the same hardware configuration. • Do not deploy the default image (install.wim) file that is included with the Windows product DVD directly by using ImageX. You can use the default image only with Windows Setup (setup.exe). • Use the imagex /flags option when capturing a Windows image to create the metadata to apply to the image that you are capturing. • Do not duplicate features for different architecture types in an answer file, if you are performing cross-platform deployments. • Create architecture-specific settings for each configuration pass in an answer file for cross-platform deployments.

  29. What Is Windows Deployment Services? Windows Deployment Services is a server role that is provided with Windows Server 2012 • Windows Deployment Services: • Enables you to perform network-based installations • Simplifies the deployment process • Supports deployment to computers with no operating system • Provides end-to-end operating system deployment • Uses existing technologies, such as Windows PE, .wim and .vhd files, and image-based deployment.

  30. Windows Deployment Services Components Windows Deployment Services provides several functions through these components: • Windows Deployment Services PXE Server • Windows Deployment Services Client • Additional Server Components • TFTP server • Shared folder • Image repository • Multicasting Engine

  31. Why Use Windows Deployment Services? Consider the following scenarios: • In a small network consisting of a single server and around 25 Windows XP computers, you want to expedite the upgrade process of the client computers to Windows 8 • A medium-sized organization wants to deploy multiple servers in branch offices that are geographically dispersed. It would be time-consuming and expensive to send experienced IT staff to each location to deploy the servers

  32. Understanding Windows Deployment Services Components Windows Deployment Services prerequisites include: • AD DS • DHCP • DNS • NTFS volume Use Windows Automated Deployment Tool Kit to create answer files for automated deployment

  33. Installing and Configuring Windows Deployment Services • Install and configure Windows Deployment Services by: • Installing the Windows Deployment Services server role • Install the Deployment Server or Transport Server role service • Perform post-installation configuration of Windows Deployment Services by: • Specifying an image store location • Configuring the DHCP server options, if required • Configuring PXE server configuration

  34. Managing Deployments with Windows Deployment Services To service client computers with Windows Deployment Services, you must: • Configure boot settings • Configure install settings • Configure transmission settings • Configure drivers

  35. Common Administration Tasks There are several common administrative tasks and tools for Windows Deployment Services • Tools • Windows Deployment Services console • WDSUtil.exe • Dism.exe • Sysprep.exe • ImageX.exe • Windows SIM • Tasks • Configure DHCP • Create and service images • Manage the boot menu • Prestage client computers • Automate deployment • Configure transmission

  36. Automating Deployments To automate the Windows Setup process: • Create the Unattend.xml file • Copy the file to the Windows Deployment Services server • View the properties of the appropriate install image • Enable unattended mode and select the answer file

  37. Demo • Install the Windows Automated Installation Kit • Identify resources and tools included with the Windows Automated Installation Kit • Build a custom Answer File by using Windows SIM • Install a reference computer from a DVD using a custom Answer File • Generalize a reference computer by using Sysprep • Add packages to Windows PE • Create a bootable Windows PE ISO image • Start the Windows PE Operating System environment • Capture an image using ImageX • Apply an image using ImageX • Service an offline WIM image

  38. Module 3 Implementing Update Management

  39. Overview of WSUS • What Is WSUS? The WSUS Update Management Process Server Requirements for WSUS

  40. What Is WSUS? Microsoft Update website Automatic updates Server running Windows Server Update Services Test clients LAN Internet Automatic updates

  41. The WSUS Update Management Process Assess Deploy Identify Update Management Evaluate and Plan

  42. Configuring Automatic Updates • You must configure the client computers to use the WSUS server as the source for updates • You can use Group Policy to configure clients, including the following settings: • Update frequency • Update installation schedule • Automatic restart behavior • Default computer group in WSUS

  43. WSUS Administration You can use the WSUS Administration console to: • Manage updates • Configure computer groups • View computer status • View synchronization information • Configure and view WSUS reports • Configure WSUS settings and options In Windows Server 2012, WSUS also includes Windows PowerShell cmdlets for administration

  44. What Are Computer Groups? • You can use computer groups to organize WSUS clients • The default computer groups include: • You can create custom computer groups to control how updates are applied All Computers Unassigned Computers

  45. Approving Updates • Updates can be approved automatically, but it is not recommended • Updates should be tested before they are approved for production • Updates can be declined if they are not needed • Updates can be removed if they cause problems

  46. Module 4 Overview of System Center 2012 Configuration Manager

  47. Overview of the System Center 2012 Family of Products

  48. Overview of Configuration Manager 2012 Asset Management Deployment Compliance Management Security Hardware and Software Inventory Application Management Compliance Settings Role-based Administration Software Update Management Power Management NAP Asset Intelligence ClientHealth Endpoint Protection Operating System Deployment Software Metering Reporting Remote Management Content Management Monitoring

  49. Benefits of Implementing System Center 2012 Configuration Manager in an Organization Key Benefits of Configuration Manager 2012 • Empower user productivity • Using the application catalog to allow users to request software when they need it • Unify management and security infrastructure • Compliance settings allows you to ensure your clients are configured in a secure manner • Simplify IT administration • Provides a unified infrastructure that gives a single pane of glass to manage physical, virtual, and mobile clients

  50. Overview of the Configuration Manager 2012 Hierarchy SQL Database Central Administration Site Primary Site Primary Site Primary Site SQL Database SQL Database SQL Database Secondary Site • Each site is identified by a a unique 3-character code • Central administration site can be used for reporting and management only • Primary sites can only be parents of secondary sites • Secondary sites now have their own database SQL Database

More Related