Task Sequence and Powershell

[KuifJe]

Hello all,

 

I have an OSD task sequence deploying Windows Server 2008 R2. All is well, SCCM client gets installed, SCOM agent gets installed, drivers get injected.

 

Now there's also a Powershell script which fails with errorcode 1. For the life of me I haven't found a clue as to where the problem lies.

 

Running SCCM 2007 SP2 R2.

 

The scripts is packed inside a program which will call the following commandline (as administrator):

 

"%windir%\SysWOW64\WindowsPowershell\v1.0\Powershell.exe" -command ".\Script.ps1".

 

Manually running this command in a powershell prompt everything works.

 

I've also incorporated a sytem reboot to the new OS in the Task Sequence so the powershell execution policy gets set to "RemoteSigned" and the program is also copied locally before execution...

 

Any ideas anyone?

[Peter van der Woude]

What is the location of the script? A package, a networkshare?

[KuifJe]

It's a package. The TS is configured to download packages before they are run.

 

The script itself will adjust the Execution Policy to RemoteSigned so it can execute local scripts.

 

edit: spelling

[Peter van der Woude]

And your script is in the root of the package? I don't think you need to use ".\" then in front of your script.

 

To be sure take a look here: http://technet.microsoft.com/en-us/library/ee176949.aspx

[KuifJe]

The script is at the root of the package. The eventual error I got is 0x80070001 which is a file missing error (IIRC).

 

This led me to believe the command wasn't executed directly from the package dir but from System32 or somewhere else. I reconfigured the package to include the complete path to the script (C:\_TaskSequence\etc..) see if that works.

[Peter van der Woude]

You also might want to take a look at this post: http://blogs.technet.com/mniehaus/archive/2009/09/22/running-powershell-scripts-as-part-of-a-task-sequence.aspx