Thank you Peter for replying….
Am afraid that this didn’t work either. I put the updates in an accessible share folder on the server and surely changed to our server name, when I ran the script it triggered the update on the x64bit machine and created that folder “2f707890fd73bf7dfcfb0e43f5dcc3ae” which is the extraction of the package but no installation I even removed the /quite switch to see what exactly what is happening but actually no installation for the update, about the .Net Framework I made sure that it’s already installed before hand and am running 4.5 ver. About the x86 machine it bounced back by an error ” Connecting to the remote server $computer failed ” even though I ran the “winrm quickconfig” to receive requests.
I can get it working on single machine and it works perfectly fine as I want, but when it comes to multiple it stuff up specially during the check of the (x64 and x86) but on one single machine it copied the file and ran the batch.cmd file and installed the update and works fine. So any more suggestions ??
PS C:\> $cmd={
Switch ($env:PROCESSOR_ARCHITECTURE){
“AMD64″ {Start-Process -FilePath wusa.exe -ArgumentList “\\myserver\dfs\Update\Windows6.1-KB2819745-x64-MultiPkg.msu” -Wait}
“x86″ {Start-Process -FilePath wusa.exe -ArgumentList “\\myserver\dfs\Update\Windows6.1-KB2819745-x86-MultiPkg.msu” -Wait}
}
}
Invoke-Command -ComputerName $(Get-Content “F:\WindowsManagementFramework4.0\Computer Lists\Test List.txt”) -ScriptBlock $cmd
[Delllap16010] Connecting to remote server Delllap16010 failed with the following error message : The WS-Management service cannot process the request. Cannot find the Microsoft.PowerShell
session configuration in the WSMan: drive on the Delllap16010 computer. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (Delllap16010:String) [], PSRemotingTransportException
+ FullyQualifiedErrorId : InvalidResourceUri,PSSessionStateBroken