Page 1 of 1

Powershell Manager

Posted: Thu Aug 13, 2020 12:40 pm
by ccalverley
I keep getting into this loop where i try to update powershell on some of my machines, I see in Powershell manager that .net4.5 is installed however it keeps looping me back to the error that .net is not installed and tries to install it but never verifies properly that it's installed and therefore we can not update powershell on any machines. I have updated to the latest version and still see this issue.

Re: Powershell Manager

Posted: Thu Aug 13, 2020 1:44 pm
by Cubert
Which plugin are you in? Powershell manager or Habitat? Both have this tool in it.

Can you send us some logs / screenshots of what your seeing?

Re: Powershell Manager

Posted: Thu Aug 13, 2020 3:19 pm
by ccalverley
powershell manager.

log says
Powershell update to 4 has been stopped due to DotNet Version not at least at 4.5, Installing dot.NET 4.5 now, you will need to reboot or allow reboot and then try again to install powershell 4 after 4.5 is installed.

Image

this device has been rebooted as well with the same results

i am not sure but is your search not looking for .net4.8

Re: Powershell Manager

Posted: Mon Aug 17, 2020 2:15 pm
by Cubert
Yeap, its look no higher than 4.6 so that is an issue. here is how to fix the issue quickly.

Open script and edit the else section at line 55. Copy line 55 and save as line 56, edit line 56 to now reflect 4.8 as the value.

Capture.PNG
Capture.PNG (60.49 KiB) Viewed 9939 times

Re: Powershell Manager

Posted: Tue Aug 18, 2020 6:52 pm
by ccalverley
I also added another line for .net 4.7
Thanks for pointing me in the right direction, tested it and it works now

Re: Powershell Manager

Posted: Wed Aug 19, 2020 2:45 pm
by ccalverley
Ok so That worked wonderfully just have a bit of a big issue
After making the changes to the script about 50 percent of my managed servers automatically rebooted after getting this command
cmd.exe!!! /c "wusa %windir%\LTSvc\PoSh\Powershell-5.0.msu /quiet /noreboot"
Which seems really bad considering we are using the /noreboot switch.
Any idea of why that happened

Re: Powershell Manager

Posted: Wed Aug 19, 2020 2:55 pm
by Cubert
Some powershell installs will ignore the reboot switch and force a reboot anyways. That's a Microsoft thing outside the control of Automate or the plugin.

Its not that we didn'y pass the switch to the upgrade command, it choose to ignore it.

Re: Powershell Manager

Posted: Wed Aug 19, 2020 4:33 pm
by ccalverley
Fun... is there a way to schedule the p4l maintenance so it coorelates with patch windows?