I have just installed Powershell on a Win2003 sp2 server.
When I want to invoke a script in the PowerShell console I get the error
message: "the term 'test.ps1' in not recognised as a cmdlet, …".

What should I do and where should I look for similar problems in the future.
I have three PowerShell books but I couldn't find this topic in any of them.



Thank you very much.

If youre console current directory shows c:\scripts then you can type
PS c:\scripts> .\script.ps1

If you want to invoke a script from another directory try
PS c:\scripts> & d:\temp\script.ps1


Shay
http://scriptolog.blogspot.com



> I have just installed Powershell on a Win2003 sp2 server.
> When I want to invoke a script in the PowerShell console I get the
> error
> message: "the term 'test.ps1' in not recognised as a cmdlet, …".
> What should I do and where should I look for similar problems in the
> future.
> I have three PowerShell books but I couldn't find this topic in any
> of them.
> Thank you very much.
>

Thank you very much Shay, it works

I wonder why on Vista it works without .\

Thanks again, Dan

"Shay Levi" wrote:

> If youre console current directory shows c:\scripts then you can type
> PS c:\scripts> .\script.ps1
>
> If you want to invoke a script from another directory try
> PS c:\scripts> & d:\temp\script.ps1
>
>
> Shay
> http://scriptolog.blogspot.com
>
>
>
> > I have just installed Powershell on a Win2003 sp2 server.
> > When I want to invoke a script in the PowerShell console I get the
> > error
> > message: "the term 'test.ps1' in not recognised as a cmdlet, …".
> > What should I do and where should I look for similar problems in the
> > future.
> > I have three PowerShell books but I couldn't find this topic in any
> > of them.
> > Thank you very much.
> >
>
>
>

"Dan" <dan@discussions.microsoft.com> wrote in message
news:71806669-E036-4172-83E8-C4AF6C3EA24F@microsoft.com...
> Thank you very much Shay, it works
>
> I wonder why on Vista it works without .\

Either your current directory happens to be in your PATH, or you added << .
>> to your PATH which automatically looks for executables in whatever
current directory you are in (not recommended for safety reasons). You can
verify that by typing:

PS> $envath

Hope that helps,
Jacques

In message <71806669-E036-4172-83E8-C4AF6C3EA24F@microsoft.com>, Dan
<dan@discussions.microsoft.com> writes
>I wonder why on Vista it works without .\

Powershell should work the same on Vista.

--
Thomas Lee
doctordns@gmail.com
MVP - Admin Frameworks and Security

"Dan" wrote:

> where should I look for similar problems in the future.

The PowerShell newsgroup (you already found it) is a good place to ask
questions like this. ;-) Also don't forget that you can search through
the newsgroup using google groups (many common questions have been answered
before):
http://groups.google.com/group/micro...topics?lnk=srg

> I have three PowerShell books but I couldn't find this topic in any of them.

Strange. May I ask which books you are refering to?
I can recommend Bruce Payette's book "Windows PowerShell in Action" (ISBN
1-932394-90-7). I'm quite sure this topic is also covered in his book.

--
greetings
dreeschkind

The behavior you described is a default security feature in PowerShell and
should work the same across the board (tested on Windows XP, 2003 and 2008)
i.e.

C:\>.\Myscript.ps1

C:\>D:\folder\Myscript.ps1

HTH.

--
............... All new, all fresh ..............
http://www.leedesmond.com/weblog/



"Dan" wrote:

> I have just installed Powershell on a Win2003 sp2 server.
> When I want to invoke a script in the PowerShell console I get the error
> message: "the term 'test.ps1' in not recognised as a cmdlet, …".
>
> What should I do and where should I look for similar problems in the future.
> I have three PowerShell books but I couldn't find this topic in any of them.
>
> Thank you very much.