-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install-LabSoftwarePackage and an MSI file #42
Comments
PowerShell 2 issue with WIndows 7. I will look into it, thank you for reporting this! |
For your information the source ISO for the Windows 7 Machine was en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso. |
I already have an idea what's going wrong. It sounds suspiciously like the -in operator has been used. I am at my customer at the moment, but a fix will be coming this evening. We transfer a script block to the remote machine, which means that -in will fail on a plain Win7/2008R2 machine and we need to use -contains instead. |
Hi @asparrowhawk , please do an It really was -notin, as well as the type accelerator pscredential which was also incompatible. After that, install-LabSoftwarePackage works again with PowerShell 2. |
Sorry for the slow response. Many thanks for looking at this issue so promptly. I have updated the AutomatedLab.Common to the latest version but I am seeing a new issue:
I suspect this due to the MSI failing with the message that Application requires the .NET Framework 4.6.1 to be installed. Although it is recorded in the PowerShell output that there was a Fatal error during installation, it would be good to see the exit code of the process. Also the message VERBOSE: Job ID '' with name '' finished would be better if it included the correct Job ID and name. Many thanks again for the fix. |
Sorry that it hit you again. Is the file you share the file "OemMgmtSetup.msi" or a download link. Reproducing the issue is the easiest way to troubleshoot. |
Attached is an MSI file, while not same one used before, exhibits the same issue:
|
I have update the function and added a new exception class. This is how you get the error code if the code runs remotely: Install-LabSoftwarePackage -Path C:\Users\randr\Downloads\SetupWpfInstaller.msi -CommandLine /qn -ComputerName Client7
$Error[0].Exception.SerializedRemoteException.ErrorCode The verbose display issue is fixed in AL. |
I updated to the latest version of AutomatedLab.Common:
I am seeing the following when trying to install the problem MSI:
|
Following a successful run of Install-Lab with a single Windows 7 Machine I am getting the following error when trying to install an MSI file:
The host is Windows 10 Pro, 1803 PowerShell 5.1.17134.228, AutomatedLab 5.1.0.115
Lab details:
The text was updated successfully, but these errors were encountered: