Prev | Current Page 55 | Next

Joezer Cookey-Gam, Brendan Keane, Jeffrey Rosen, and Jonathan Runyon

"Professional Windows PowerShell for Exchange Server 2007 Service Pack 1"


Figure 1-23
Chapter 1: Getting Started with Windows PowerShell
29
To change this behavior, add the AutoSize parameter to force Format-Table to change column widths
to make the most of the console screen width, and the Wrap parameter to wrap long values that won ??™ t fit
on a single line to the next line. The addition of these two parameters to the previous example yields the
results shown in Figure 1 - 24 .
Figure 1-24
Running Scripts
As you learn to use Exchange Management Shell to manage your Exchange organization you will most
likely identify several command sequences that you run on a regular basis to accomplish some task.
Store these commands in a Windows PowerShell script file so you can run them all by simply executing
the script file. Use your favorite text editing software to create and edit script files. Windows PowerShell
script files use .ps1 as the file extension name.
To run a script, type its name at the command line. You do not have to include the .ps1 file extension.
However, you do have to pay attention to the drive location where the script is stored and the current
location from which the script is being run. You must supply the full path to the script file even if the
script is stored in the current location. To tell Windows PowerShell the script is in the current directory,
either type the full path or use a dot and backslash (.


Pages:
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67
nowoczesne meble prezenty Golec uOrkiestra 3 pieniny noclegi ABBA