Windows Vista Powershell

[DeMario]

Hi,

What is the minimum system requirements for installing PowerShell. I have a laptop which now runs on Windows XP. I am going upgrade the same to Windows Vista for the Powershell option. What are the requirements to run it. Second thing I want to clear the queue of the printer. I also need a sample to create a script from the command prompt. Thanks in advance.

[Doroteo]

Before you start to learn PowerShell, you will need to install the following components. PowerShell is sufficient in itself if you're running Windows Vista. Service Pack 2 if you're running Windows XP. The Service Pack 1 if you have Windows Server 2003 (334 MB), . NET Framework 2.0 (22MB) and Microsoft PowerShell (1.7 MB). If your system does not meet the minimum requirement then you can run the application in Vista.

[opaper]

Tired of the printer that is an eternity to print. From this queue you block your impression. Ok, so this script is for you: $obj = get-wmiobject -query "select * from win32_printer where name='Printer NB'" $obj.CancelAllJobs(). Here's a little script that allows you to connect a network drive. You can include it in a logon script example Wink so on you have PowerShell installed on all machines on your network. $obj = New-Object -com Wscript.Network $obj.MapNetworkDrive("x:", "\\serveur\system").

[MindSpace]

To get them, enter the interior from the standard command prompt in Windows (the good old cmd.exe what!): Powershell.exe /. You get: powershell[.exe] [-PSConsoleFile <file> | -Version <version>] [-NoLogo] [-NoExit] [-NoProfile] [-NonInteractive] [-OutputFormat {Text | XML}] [-InputFormat {Text | XML}] [-Command { - | <bloc_script> [-args <tableau_arguments>] | <chaîne> [<paramètres_commande>] } ] powershell[.exe] -Help | -? | /? ?. The parameter list is impressive you might say! But rest assured, in interactive use is not used any of these settings as you enter commands directly within the console. However it is useful to know that you can run PowerShell script directly without entering interactive mode. Imagine that you have developed a PowerShell script called Exemple1.ps1. Well you can run it by typing the following command: C:\> powershell -command "& {c:\exemple1.ps1}". This mode is interesting to integrate? Bits of code? PowerShell within your scripts. Bt existing. As for example in the logon script for users or even to start a scheduled task. Also note that in this way, PowerShell returns only text and not objects. You can also, instead of calling a script to execute the commands of your choice with the-command and well respecting the following syntax: C:\> powershell -command "&{get-command}"