Windows PowerShell is inspired by the best administrative tools and processes from Windows and non-Windows operating systems, and offers a uniquely Windows-centric administration model. For perhaps the first time, Windows PowerShell offers a truly administrator-focused means of automating repetitive or time-consuming administrative tasks, without the need for the same complex programming or system scripting that was required by older technologies. Module 2: Understanding and Using the Formatting System. However, the formatting subsystem offers a great deal of additional power and flexibility that you can use to create exactly the output you need.
|Published (Last):||13 April 2007|
|PDF File Size:||13.41 Mb|
|ePub File Size:||5.6 Mb|
|Price:||Free* [*Free Regsitration Required]|
Windows PowerShell is inspired by the best administrative tools and processes from Windows and non-Windows operating systems, and offers a uniquely Windows-centric administration model. For perhaps the first time, Windows PowerShell offers a truly administrator-focused means of automating repetitive or time-consuming administrative tasks, without the need for the same complex programming or system scripting that was required by older technologies.
Module 2: Understanding and Using the Formatting System. However, the formatting subsystem offers a great deal of additional power and flexibility that you can use to create exactly the output you need. By learning how the formatting system works, you can take advantage of its power and flexibility. Instead, these cmdlets work in conjunction with other, more task-focused cmdlets to help you accomplish specific tasks, put data into a different order or format, and so forth.
At first, it seems that these cmdlets are less interesting, but they are really some of the most important Windows PowerShell cmdlets you can learn. These cmdlets will prove useful no matter what products or technologies you are managing through Windows PowerShell. In many ways, Windows PowerShell may offer the easiest and most approachable means for administrators to work with WMI. Automation can also help improve security and consistency because it is less prone to repeated human error than manual administration.
Windows PowerShell scripts provide you with a way to run a sequence of commands many times with less typing. Scripts can also provide an easier way to automate lengthy sequences of commands or to automate tasks that require logical decisions, repetitive work, and so forth.
Windows PowerShell script execution is controlled by a set of features that, by default, are configured in a secure state. As you begin to work with scripts, you may need to reconfigure some of these features, taking into account your script execution needs as well as the security policies of your environment. Module 7: Background Jobs and Remote Administration. These features each add a level of maturity to the administrative capabilities of Windows PowerShell, helping you to accomplish more complex tasks and enabling you to extend an administrative reach across your enterprise.
None of the topics covered in this module are critical to using Windows PowerShell—but they do make using it easier and more effective in many ways.
Module 9: Automating Windows Server Administration. Learning to use these modules and snap-ins provides you with the ability to automate additional Windows Server R2-related tasks, and also provides additional experience using Windows PowerShell itself, core cmdlets, and other techniques covered earlier in this course. These scripts may be written by someone within your organization, or by individuals from outside your organization.
You might, for example, obtain scripts from an online script repository, from a book, training video, and so on. Therefore, a key skill in Windows PowerShell is being able to read scripts, interpret the commands in them, and develop an expectation of what the script does and how it works. Doing so can also be a good way to learn more advanced Windows PowerShell features, such as scripting constructs.
In this module, you will review a completed example script, and use that script as a way to learn selected scripting constructs. This type of script is similar to the batch files or batch scripts used by most other shells, including the Cmd. Also, you want to create scripts that can anticipate and handle certain errors, and you may need to spend time debugging your scripts to get them working perfectly.
You want to modularize your scripts, as well, so that you can more easily use portions of them in different scenarios. You will learn to use these more complex scripting elements in this module. Although all of these features are very useful in the right scenario, some are very advanced features that may only be of interest to developers, or to administrators who are more comfortable with system programming and scripting.
The purpose of this Appendix is to give you a starting point and examples for some of the additional shell features that might be of interest to an administrator. You can take these examples and starting points and discover more about these features on your own, by reading help topics within Windows PowerShell, by exploring additional examples on the Internet, and so forth. Even these additional features do not, however, constitute the full set of shell capabilities.
Some shell features— such as writing cmdlets in a. NET Framework language, or embedding the shell inside another application, or creating restricted runspaces—require advanced software development skills.
Windows PowerShell offers a number of different features to a number of different audiences. If you find that you have a need for, or an interest in, other shell features, consider purchasing a book that covers those features in more detail. All rights reserved. Legal Notices. Module 1. Lesson 1. Many of the things you can do in Windows PowerShell will seem immediately familiar, such as listing the contents of a directory on disk. However, Windows PowerShell is usually doing something very different under the hood.
Lesson Objectives. After completing this lesson, you will be able to:. Windows PowerShell is not a scripting language, or at least it is not just a scripting language.
Windows PowerShell is an engine designed to execute commands that perform administrative tasks, such as creating new user accounts, configuring services, deleting mailboxes, and so forth. Windows PowerShell actually provides many ways in which you can tell it what commands to execute. You can, for example, manually type command names in a command-line console window. You can also type commands in an integrated scripting environment, ISE that offers a more graphically-rich command-line environment.
If you are a software developer, you can embed Windows PowerShell within your own application, telling it to execute its commands in response to user actions such as clicking buttons or icons. You could also type a series of commands into a text file, and instruct the shell to execute the commands in that file. In an ideal world, Windows PowerShell is a single, central source for administrative functionality. Ideally, you could use a graphical user interface GUI with buttons, icons, dialog boxes, and other elements that execute Windows PowerShell commands in the background.
Some products, like the Windows Server operating system, are not built in that way yet, although some specific components are. This choice, to use commands directly, or to have commands run for you as part of a GUI, is part of what makes Windows PowerShell so compelling.
A GUI can guide you through complex operations, and can help you understand your choices and options more easily. However, Microsoft also recognizes that a GUI can be inefficient for tasks that you need to perform repeatedly, such as creating new user accounts.
By building as much administrative functionality as possible in the form of Windows PowerShell commands, Microsoft. Over time, Windows PowerShell may replace other low-level administrative tools that you may have used. For example, Windows PowerShell can already supplant Visual Basic Script Edition VBScript , because the shell has access to the same features that VBScript does, although in many cases the shell provides easier ways to accomplish the same tasks.
While WMI remains very useful, it can also be complex to use. All of these things are happening now, and will continue to improve in the future as Windows PowerShell itself evolves. Windows PowerShell v2 is included in the Windows Management Framework Core, which also includes other related management technologies.
The download can be found here ; separate versions are available for different operating systems and architectures bit and bit. Windows PowerShell v2 can be installed on the following operating systems:. Windows Embedded for Point of Service 1. Windows PowerShell v2 requires Microsoft. NET Framework 2.
NET Framework 3. Note that Windows PowerShell can expose additional functionality and features from newer versions of Microsoft. NET Framework. Ideally, you should install the highest available version of the Framework to gain the most functionality. Windows PowerShell also exposes new functionality in newer versions of Windows.
That means you may have a slightly reduced feature set on older versions of Windows, simply because those older versions do not contain the underlying functionality that a feature requires. Note: The information in this course applies to Windows PowerShell v2 running on all supported versions of Windows, unless specifically stated otherwise. What Else Will You Need? You are probably aware that the MMC, by itself, is not useful for very many tasks. In order to make the MMC useful, you have to add one or more snap-ins.
Those snap-ins provide product-specific and technology-specific functionality, such as enabling you to administer Active Directory or Exchange Server. Windows PowerShell is similar.
While it does include a number of useful capabilities, it is designed to be extended through snap-ins and modules. Windows PowerShell itself does not provide these modules or snap-ins; they are provided along with whatever product, role, feature, or technology that they relate to.
Some modules may also be installed along with the Windows Remote Server Administration Toolkit RSAT , making it possible to obtain server-related modules on a client operating system like Windows 7. Some modules ma y be available as standalone downloads. For example, the CodePlex Web site at www. Modules may require a specific version of Windows, or a specific version of Microsoft.
Windows PowerShell is used within a number of Microsoft and third-party products. This list is constantly growing, and both Microsoft and third-party software developers often announce Windows PowerShell compatibility with new product versions. Here is a partial list of current products that use Windows PowerShell. Note that this list does not include Windows Server R2 features that can be managed via Windows PowerShell; those features are discussed in Module 9 of this course. For example, using Windows PowerShell commands with Exchange Server might allow you to get the largest mailboxes on a messaging server and move those to a new server.
Such a command might look something like this:. This type of command is much more readable, and much easier to construct, than the complex scripts that were required with previous versions of Exchange Server prior to the introduction of Windows PowerShell.
Demonstration steps:. Alternatively, the same file is also available as part of the companion content and you can refer to the steps and explanations there. Discussion: Benefits of Having the Shell Everywhere. The goal behind this decision was to ensure that Windows PowerShell v2 is available on every computer in your environment. Windows PowerShell v2 contains built-in remoting capabilities, allowing it to contact instances of Windows PowerShell on remote computers to perform management tasks.
Some of the benefits of having Windows PowerShell on all of your client and server computers include:.
Course 10325A Automating Administration with Windows PowerShell® 2.0.pdf
Please complete the form below and a TrainUp. Our staff typically responds to your requests within 30 minutes or less. You can also reach us toll-free at Bring On-Site:.
Automating Administration with Windows PowerShell 2.0 Training Course
Embed Size px x x x x Be sure to access the extended learning content on your Course Companion CD enclosed on the back cover of the book. Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user.