App-V prereqs install: .NET is asking for reboot but Powershell installs meanwhile(?!)

Hi,

I want to deploy App-V 5.0 SP3 to some W7 client which don't have .NET 4.5.1 or Powershell 3.0 (.NET 4.5 is already installed).
Created a dependency to Powershell 3.0 application and  .NET 4.51 application (in that order) but .NET 4.5.1 installs first. No problem BUT the fact it asks for a reboot and AT THE SAME TIME Powershell 3.0 installs. That's pretty confusing for an enduser (it asks for a reboot but another install starts).
Howto make sure Powershell install starts after reboot (or it can start before 4.5.1 or it can install after 4.5.1 but then the reboot should only be asked AFTER install of Powershell 3.0). Can't remove the reboot after 4.5.1 and set it after Powershell since for .NET on itself a reboot is really needed.

Please advise.

May 19th, 2015 9:38am

How is the reboot triggered? How are the deployment types configured? There is no way to determine the order of dependencies (exception: AppX -> AppY -> AppZ which would work. Whereas AppX -> [AppY and AppZ] not).
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2015 9:57am

Microsoft App-V 5.0 SP3 application has 1 deployment type that has a dependency to Powershell 3.0 AND .NET 4.5.1.
I don't see the point creating a dependency on .NET 4.5.1 to Powershell since there is no dependency.

.NET 4.5.1 has on "user exprience" tab "determine behaviour on return code", that results in install .NET 4.5.1 then green icon in taskbar asking for reboot but Powershell installing also.

May 19th, 2015 10:20am

I am sure I  had an issue recently where powershell would not install properly and it was down to not having the dotnetframework installed. Will have a look.

Edit: My issue was with V4, not V3.

http://blogs.msdn.com/b/powershell/archive/2013/10/29/wmf-4-0-known-issue-partial-installation-without-net-framework-4-5.aspx

Does suppressing the reboot of .netframework help at all?

NDP451-KB2858728-x86-x64-AllOS-ENU.exe /q /norestart /msioptions ALLUSERS="1" ROOTDRIVE="C:\" REBOOT="ReallySuppress"

Couldn't you change the dependency of the APPV application to be just one of the applications and then make that applications dependency the other application. that would make sure they go on in the order you want.  

Free Windows Admin Tool Kit Click here and download it now
May 19th, 2015 11:13am

I am sure I  had an issue recently where powershell would not install properly and it was down to not having the dotnetframework installed. Will have a look.

Edit: My issue was with V4, not V3.

http://blogs.msdn.com/b/powershell/archive/2013/10/29/wmf-4-0-known-issue-partial-installation-without-net-framework-4-5.aspx

Does suppressing the reboot of .netframework help at all?

NDP451-KB2858728-x86-x64-AllOS-ENU.exe /q /norestart /msioptions ALLUSERS="1" ROOTDRIVE="C:\" REBOOT="ReallySuppress"

Couldn't you change the dependency of the APPV application to be just one of the applications and then make that applications dependency the other application. that would make sure they go on in the order you want.  

  • Edited by Richard.Knight Tuesday, May 19, 2015 3:24 PM
  • Marked as answer by janhoedt Tuesday, May 26, 2015 2:27 PM
  • Unmarked as answer by janhoedt 20 hours 10 minutes ago
May 19th, 2015 3:12pm

Making Powershell dependent on Dotnet did the trick at first, changed the detection script of Powershell to

if ($psversiontable.psversion.Major -ge '3.0') {Return $True} and detection of dotnet 4.5.1

to check on regvalue for SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full ge 3

Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 5:11am

Since then (update above), problem reappeared.
Please advise.
June 3rd, 2015 5:21am

So what happens: .NET 4.5.1 is installed, then Powershell that works fine but then App-V 5.0 installs also whereas it should wait for a reboot and it does not.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 5:25am

Maybe I should change the detection script(s)?
June 3rd, 2015 5:34am

I guess, if I would change the detection of Powershell to

hotfix KB2506143 (PS 3) or hotfix KB2819745 (PS 4) then it will only be deteced after reboot and that could make my setup work?

Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 5:40am

Something like Get-HotFix | Where-Object {$_.HotfixID -eq 'KB2506143 ' or 'KB2819745 '}
June 3rd, 2015 5:53am

That's a question for scripting guys forum.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 5:56am

This works, but result is still the same: all applications install one after the other without a reboot.

if (Get-HotFix | Where-Object {$_.HotfixID -eq 'KB2506143' -or $_.HotfixID -eq 'KB2819745'}) {Return $True}

June 3rd, 2015 7:39am

It DOES go in the order I want, though the App-V client starts installing @ the end and fails because Powershell/Dotnet need a reboot after install.
Free Windows Admin Tool Kit Click here and download it now
June 3rd, 2015 8:16am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics