Vista - same beginners questions

hello,

i just begin with learning ms powershell. no i'm first by reading the
whitepapers. but now i have i few questions.

1.) can i use ms powershell also with .net 3.0 or only with .net 2.0
2.) how do i start ms powershell outside the powershell - i mean how
do you start "ps-batch" script from a cmd.exe ?
3.) need i a englisch ms powershell for english OS, and a german ms
powershell for german OS, or is that not important what language i
have ?
4.) can i use ms powershell on my computer, to control other computers
in the network, which have .net 2.0 / 3.0 but no the ms powershell
installed ?

kind regards

Hassan

To answer your questions in order:

1) PowerShell uses .NET 2.0 .NET 2.0 must be installed before PowerShell
can be installed. You may be able to use functionality from .NET 3.0
depending on what it is and loading the assembly into PowerShell

2) if you want to run a powershell script from the cmd prompt then you use

powershell.exe -Command "path to script"

you can see the full syntax by using powershell /?

3) You can download PowerShell from here
http://www.microsoft.com/windowsserv.../download.mspx
There are versions available in languages other than English. I would use
the appropriate language for your machine.

4) PowerShell cannot control other computers directly at the moment. You
can use WMI and .NET functionality to control remote machines. There are
some remoting add ons available for PowerShell
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"HassanMullah" wrote:

HassanMullah wrote:Welcome!
You can use it with 2.0+. Installing a higher version, will still
install older versions of the framework. For example, 3.0 only contains
a limited number of updates, while 2.0 gives you the entire "base".
From DOS, type for information:
C:\>powershell /?

Yes, get the proper package for your OS.
Yes, you can remotely "manage" other computers with other technologies
like WMI and ADSI. You call these from your PowerShell installation.

Marco


--
----------------
PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

But they still require that PowerShell be installed on the remote machine.

Marco

--
----------------
PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

Marco Shaw wrote:Sorry to nitpick Marco but while your second sentence is true, the first is not,
at least not for pre-2.0 versions. You still have to install 1.0, 1.1, 2.0,
individually, independent of the order in which you install them. I have
installed .NET many, many, many times and ran into this.

--

Hal Rottenberg
Blog: http://halr9000.com
Webmaster, Psi (http://psi-im.org)
Co-host, PowerScripting Podcast (http://powerscripting.net)

Regarding your question #3 I have to disagree with Rich & Marco. I live in
Germany and work for a global company, so I have the pleasure to enjoy
localization hell since the early days of Windows. PowerShell is an
administrative automation tool, it's not targeting on office users. Running a
corporate environment requires that your administrative tools behave in a
uniform manner everywhere, regardless of the local end user's language
preference, so our experience is to better stay away from localization
(whenever possible, but at least for administrative tools).

Gerd



"HassanMullah" wrote:

Hal Rottenberg wrote:Nitpick away... Perhaps my memory is failing me though. Anything is
possible.

Marco


--
----------------
PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

I'm confused. I have this command that I'm using in Powershell that works
(type C:\temp\computers.txt | % { $_; gwmi -computername $_
win32_logicaldisk -filter "drivetype=3" | % { $_.deviceid; $_.freespace/1GB }
} | out-file c:\temp\FreespaceResults.txt) What I would like to do is
schedule a task to run it and then e-mail me a copy of the results. However,
if I set this up as a scheduled task, it doesn't work. I setup the task with
this command calling a text file with the above mentioned command line.
Powershell -Command c:\temp\freespace.txt. It just pops up the text file and
then a cmd prompt window pops up and goes away. I see no errors. Any
suggestions appreciated. thanks

"RichS" wrote:

Hi Chuck,

In your example below, PowerShell is doing just what you tell it to. When
you execute nothing but a path to a text file, that text file will open in
its default editor, which is why you see the file in notepad. The console
then closes because you didn't tell it to stay open.

There are a few things you should know about running PowerShell scripts
through PowerShell.exe:
1. If you don't want the console to close, you need to specify -NoExit on
the command line.
2. If you want PowerShell to run a script, script files should be saved with
the .ps1 extension.
3. (only important if your script file path has spaces) If your script file
path has spaces, you need to pass it in differently.

Here are two examples:

powershell -noexit C:\Test.ps1

and

powershell -noexit "& ""C:\Documents and Settings\kmunro\My
Documents\Test.ps1"""

-
Kirk Munro
Poshoholic
http://poshoholic.com

"chucksweety" <chucksweety@xxxxxx> wrote in message
news:A2CAB1D6-EC28-4D8E-9571-4F692D16D1DC@xxxxxx