I am trying to install MS Powershell 1.0 on all of our new machines as they are deployed.  We currently have both vista and xp operating systems and they have a different software install for each OS.  I am currently trying to install by setting up both installs in the applications part of the deployment workbench and then adding an application group with both applications in the group.  I set each indivual application powershell xp to only install in windows xp and the powershell vista to only install in vista.  I then add the powershell application group to the application list for the role the pc is in.  The correct app is running but it keeps getting an unexpected error in the deployment log for the vista install.  I am running a XP install know to check and see if I get the same results.

1:  Is there a better way to deploy applications that have different install packages for each os?

2:  Has anybody gotten a silent install to work for powershell 1.0 in vista?

Thanks

Dan

The xp install works fine I'm just having problems with the vista install so it looks like my method might be working just not the app.

Anybody been able to install powershell 1 in vista

Hi Dan

By any chance, does your BDD.LOG or ZTIAPPLICATIONS.LOG indicate what error you are receiving when you run WUSA.exe to install the PowerShell 1.0 MSU file?

If it's 0x80070002, then this translates to "The System cannot find the file specified" and occurs even when you run it from a command prompt. If it is this, then you need to specify the exact path to the MSU file. For example:

wusa.exe "C:\Updates\Windows6.0-KB928439-x86.msu" /quiet /norestart

Obviously this is difficult when installing an application via the MDT, however you could get round this using the . For example:

wusa.exe "\\server\Distribution$\Applications\PowerShell_Vista\Windows6.0-KB928439-x86.msu" /quiet /norestart

Anyway, having typed all that, why don't you use the 'OS Packages' node in Deployment Workbench. This is an ideal facility for installing Vista/2008 MSU files so it would solve your Vista niggles without having to resort to installing it as an application. The 'Install Packages' step in the Task Sequence will take care of installing this update.

More info: http://blogs.technet.com/deploymentguys/archive/2008/05/19/managing-windows-updates.aspx

As for your other query, there are two easy ways to ensure an application only installs on one particular platform:

1) In the properties of the application, select the Details tab and select the option for "This can run only on the specified client platforms". Select the applicable operating system(s).

2) Install the application via the 'Install Application' task in a Task Sequence. Using the 'Options' tab, add a criteria to the task where "Operating System Version" is equal to a particular operating system. You can specify multiple criteria for different versions of a single operating system.

Let me know how you get on.

Mark

The only error I get for the following command is 

error LOG[Return code from command = 1326]
command wusa.exe "%wdsserver%\vistadeploy\applications\powershell_vista\Windows6.0-KB928439-x86.msu" /quiet /norestart 

If I add it to the packages it puts the pc/laptops into a reboot loop applying patches.  I was finally able to get it to work by writing a script that copies it local from the server it is running from and then running the following command Windows6.0-KB928439-x86.msu" /quiet /norestart and this installs the product. 

Ended up being more work than I thought it would be but in the long run the script might prove to be usefull.

Thanks for your help

Dan