20688BC: Microsoft Windows 8: Module 1: Planning and Implementing Management of Windows 8

The flashcards below were created by user LarryBudMelman on FreezingBlue Flashcards.

  1. 1.1. The Tools for Troubleshooting Stability and Performance:
    • 1. Event Viewer
    • 2. Task Manager
    • 3. Resource Monitor
    • 4. Performance Monitor
    • 5. Reliability Monitor
  2. 1.1.1. Tool: Event Viewer
    • Used to view and manage event logs
    • 1. System even Log
    • 2. Application Event Log
    • 3. Security Event Log
  3. 1.1.2. Tool: Task Manager
    • Monitors the use of resources on a local computer.  
    • 1. Processes: The list of processes includes information about CPU, memory, disk, and network utilization for each process.
    • 2. Performance: provides a graphical overview of resource utilization
    • 3. App history: provides a cumulative accounting of the CPU time, network, and metered network usage by individual applications. 
    • Metered network is data transferred on networks such as wireless providers.
    • 4. Startup: applications that start automatically when you sign in.
    • 5. Users: users that are logged on, the processes they are running, and the resources used by each of user and process.
    • 6. Details: process names, process IDs, CPU utilization, and memory utilization.
    • 7. Services:
    • the services installed and the status of each service. 
    • You can start and stop services
  4. 1.1.3. Tool: Resource Monitor
    • View detailed information about resources being used, such as:
    • 1. CPU
    • 2. Memory
    • 3. Disk
    • 4. Network
  5. 1.1.4. Tool: Performance Monitor
    • Used to view performance information by the use of performance monitors that a tech/user can choose.  These can be written to a file for later analysis.  
    • System Diagnostics and System Performance tools are preconfigured.
  6. 1.1.5. Tool: Reliability Monitor
    provides a graphical display of system stability over time, based on failures of applications,Windows 8, and drivers. 

    You can identify the point in time at which system stability was reduced, and view the changes software or driver updates that occurred at that point in time.

    To review reliability history at a later time, save the reliability history to a file.
  7. 1.2. Remote Management
    An easy way to manage remote computers without having to be physically present at the computer itself.
  8. 1.3. RPC: Remote Procedure Call
    • Allows remote PC management.  Requires:
    • 1. RPC service to run on client PC
    • 2. RPC Endpoint Mapper service 
    • 3. Configuration of Windows Firewall to allow remote management.  It is turned off by default.
  9. 1.4. WinRM
    • A web service that allows remote management through the Internet.  
    • 1. Must be manually configured on client PC's or setup via Group Policy
    • 2. A listener must be setup for port 5985.
  10. 1.5. Remote Desktop
    • 1. Provides a private session on a remote PC.
    • 2. Use to troubleshoot problems on remote PC's. 
    • 3. Use to provide remote access to PC's to users
    • 4. Allows for printer and hard drive re-direction.
  11. 1.6. Remote Assistance
    • 1. Connects to an existing user session
    • 2. Use to view user actions
    • 3. Use to troubleshoot issues
    • 4. Can be offered or requested
    • 5. It is turned-off by default, must be enabled
  12. 1.7. RSAT: Remote Server Administration Tools
    • 1. a collection of server administration tools that can be installed on a PC.  
    • 2. Can be used by server admins to remotely configure Win 2012 servers.
  13. 2. Windows Powershell
    A command line interface used to manage computers running Win8.
  14. 2.1. Cmdlets
    • 1. Uses the verb (action) noun (subject) relationship.  
    • 2. Ex: Start-Service –Name “Application Identity”
  15. 2.2 Windows Powershell Pipeline
    • 1. Windows Powershell is object based
    • 2. Piping passes objects from one cmdlet to another
  16. 2.3 Windows Powershell Scripts
    • 1. Scripts are text files with a *.ps1 extentsion
    • 2. Contains one or more cmdlets
    • 3. Requires a full or relative path to run
    • 4. Execution Policy restricts script execution
  17. 2.3.1 Execution Policy: Restricted
    • 1. Default policy for Win8
    • 2. Does not allow scripts to be run
  18. 2.3.2. Execution Policy: AllSigned
    This policy requires that a trusted publisher sign all scripts and configuration files, including scripts created on your local computer.
  19. 2.3.3. Execution Policy: RemoteSigned
    • This policy requires that a trusted publisher sign all scripts and configuration files downloaded from the Internet. 
    • This execution policy is useful because it assumes that local scripts are ones that you create yourself, and that you trust them. 
    • It does not require those scripts to be signed. 
    • Scripts that are downloaded from the Internet or received via email are not trusted, unless they carry an intact, trusted digital signature.
  20. 2.3.4. Execution Policy: Unrestricted
    • 1. loads all configuration files and runs all scripts
    • 2. Not suitable for production environments
    • 3. Warnings given for scripts downloaded from the Internet, but they still can be run.
  21. 2.3.5. Execution Policy: Bypass
    • 1. loads all configuration files and runs all scripts
    • 2. No warnings given for scripts, despite their origin.
    • 3. Not suitable for production environements
Card Set
20688BC: Microsoft Windows 8: Module 1: Planning and Implementing Management of Windows 8
20688BC: Microsoft Windows 8: Module 1: Planning and Implementing Management of Windows 8
Show Answers