Good Afternoon!
I've been struggling to get Powershell versions upgraded using the PoSH plugin. Most of the servers that I have tried pushing the update through the plugin have not updated.
Two entries are generated under Scripts on the endpoint:
Information: Powershell update to 4 has been started.
Result: The Script(6169) was successful in the Else section.
Script: S6169 - Starting at Server Time: Monday, September 17, 2018 12:15:47 AM
Script step logging has been disabled. Please set @ScriptEngineEnableLogger@ = True in your script to enable function logging.
The endpoint that I am testing against is running the follow:
Windows OS - Server 2012 Standard
.Net:
DELETE FROM `plugin_sw_powershell_dotnet_versions` WHERE ComputerID = '3714' ; INSERT IGNORE INTO `plugin_sw_powershell_dotnet_versions` (ClientID,ComputerID,NetName,NetVersion,NetRelease) Values ('2', '3714', 'Client (4.6.1)', '4.6.01055', '394271')
,('2', '3714', 'Full (4.6.1)', '4.6.01055', '394271')
,('2', '3714', 'Client', '4.0.0.0', '')
Powershell:
REPLACE INTO `plugin_sw_powershell_versions` (ClientID,LocationID,ComputerID,Major,Minor,Build,Revision,LastScan) Values (2,316,3714,'3','0','-1','-1',NOW())
Our environment has a lot of Powershell version 2 and 3 installed in it that we need to get to version 4 at a minimum. Getting this to work will save me a tremendous amount of time.
Thank you
- Robert
Updating Powershell with PoSH
Re: Updating Powershell with PoSH
Robert, Can you send us the results of the commands tab during the script run. We need to see the return.
Re: Updating Powershell with PoSH
Is this what your looking for? I ran the upgrade to Powershell 4 against a machine that the plugin is showing as Powershell 3. After the script completed the server did not reboot and Powershell still reports at being on version 3.
Execute Command - Success - 12/11/2018 9:21:01 AM
Parameter:
cmd.exe!!! /c "@powershell -NoProfile -ExecutionPolicy unrestricted -Command $PSVersionTable.PSVersion.Major"
Output: 3
Scripting KeepAlive - Success - 12/11/2018 9:21:17 AM
Parameter:
15
Output:
OK
Invoke Script - Success - 9/21/2018 9:21:19 AM
Parameter:
1|t+3W7tDAxeTWTQn5C/bVxZDKGwLrfLBoJfIQY1BoKWy4PxqGj9BC1w7zG4XQJkCtOeLHdL4XUB8iOAo9a897LWByVE2tOPQ8AIu59mBmbaII1gYQjg9F1cxqKeenGXRuLzKzztmlp4bKzDa1OOA2D8ubghOu2ly5Q3QkkW+H6dcR84QOn67vwRv0yAecpfhXGJpRcN0JuDD/XwNvyJw6pFCsbL8iYxTYWTayVt9m7LRj0O8iCAxGQ5Mhlk0/g8bE9d/lFCZ0gMkIo6wc7tsSeI8QetNvAs7AW3dQe9hj7RSirWRM0q5W2xorVmY4r0XKG7HwI6dYg10TYnFuYjkban+1VeLmrm/r|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw
Output:
4.6.01055|4.6.01055|4.0.0.0|
DownLoad URL - Success - 12/11/2018 9:21:31 AM
Parameter:
https://download.microsoft.com/download ... 819745.msu
Output:
OK Downloaded File https://download.microsoft.com/download ... ltiPkg.msu and saved as %windir%\ltsvc\Windows6.1-KB2819745.msu
Execute Command - Success - 12/11/2018 9:21:36 AM
Parameter:
cmd.exe!!! /c "wusa %windir%\ltsvc\Windows6.1-KB2819745.msu /quiet /forcereboot"
Output:
OK
Scripting KeepAlive - Success - 12/11/2018 9:21:47 AM
Parameter:
15
Output:
OKIs this what your looking for? I ran the upgrade to Powershell 4 against a machine that the plugin is showing as Powershell 3. After the script completed the server did not reboot and Powershell still reports at being on version 3.
Execute Command - Success - 12/11/2018 9:21:01 AM
Parameter:
cmd.exe!!! /c "@powershell -NoProfile -ExecutionPolicy unrestricted -Command $PSVersionTable.PSVersion.Major"
Output: 3
Scripting KeepAlive - Success - 12/11/2018 9:21:17 AM
Parameter:
15
Output:
OK
Invoke Script - Success - 9/21/2018 9:21:19 AM
Parameter:
1|t+3W7tDAxeTWTQn5C/bVxZDKGwLrfLBoJfIQY1BoKWy4PxqGj9BC1w7zG4XQJkCtOeLHdL4XUB8iOAo9a897LWByVE2tOPQ8AIu59mBmbaII1gYQjg9F1cxqKeenGXRuLzKzztmlp4bKzDa1OOA2D8ubghOu2ly5Q3QkkW+H6dcR84QOn67vwRv0yAecpfhXGJpRcN0JuDD/XwNvyJw6pFCsbL8iYxTYWTayVt9m7LRj0O8iCAxGQ5Mhlk0/g8bE9d/lFCZ0gMkIo6wc7tsSeI8QetNvAs7AW3dQe9hj7RSirWRM0q5W2xorVmY4r0XKG7HwI6dYg10TYnFuYjkban+1VeLmrm/r|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw
Output:
4.6.01055|4.6.01055|4.0.0.0|
DownLoad URL - Success - 12/11/2018 9:21:31 AM
Parameter:
https://download.microsoft.com/download ... 819745.msu
Output:
OK Downloaded File https://download.microsoft.com/download ... ltiPkg.msu and saved as %windir%\ltsvc\Windows6.1-KB2819745.msu
Execute Command - Success - 12/11/2018 9:21:36 AM
Parameter:
cmd.exe!!! /c "wusa %windir%\ltsvc\Windows6.1-KB2819745.msu /quiet /forcereboot"
Output:
OK
Scripting KeepAlive - Success - 12/11/2018 9:21:47 AM
Parameter:
15
Output:
OK
Execute Command - Success - 12/11/2018 9:21:01 AM
Parameter:
cmd.exe!!! /c "@powershell -NoProfile -ExecutionPolicy unrestricted -Command $PSVersionTable.PSVersion.Major"
Output: 3
Scripting KeepAlive - Success - 12/11/2018 9:21:17 AM
Parameter:
15
Output:
OK
Invoke Script - Success - 9/21/2018 9:21:19 AM
Parameter:
1|t+3W7tDAxeTWTQn5C/bVxZDKGwLrfLBoJfIQY1BoKWy4PxqGj9BC1w7zG4XQJkCtOeLHdL4XUB8iOAo9a897LWByVE2tOPQ8AIu59mBmbaII1gYQjg9F1cxqKeenGXRuLzKzztmlp4bKzDa1OOA2D8ubghOu2ly5Q3QkkW+H6dcR84QOn67vwRv0yAecpfhXGJpRcN0JuDD/XwNvyJw6pFCsbL8iYxTYWTayVt9m7LRj0O8iCAxGQ5Mhlk0/g8bE9d/lFCZ0gMkIo6wc7tsSeI8QetNvAs7AW3dQe9hj7RSirWRM0q5W2xorVmY4r0XKG7HwI6dYg10TYnFuYjkban+1VeLmrm/r|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw
Output:
4.6.01055|4.6.01055|4.0.0.0|
DownLoad URL - Success - 12/11/2018 9:21:31 AM
Parameter:
https://download.microsoft.com/download ... 819745.msu
Output:
OK Downloaded File https://download.microsoft.com/download ... ltiPkg.msu and saved as %windir%\ltsvc\Windows6.1-KB2819745.msu
Execute Command - Success - 12/11/2018 9:21:36 AM
Parameter:
cmd.exe!!! /c "wusa %windir%\ltsvc\Windows6.1-KB2819745.msu /quiet /forcereboot"
Output:
OK
Scripting KeepAlive - Success - 12/11/2018 9:21:47 AM
Parameter:
15
Output:
OKIs this what your looking for? I ran the upgrade to Powershell 4 against a machine that the plugin is showing as Powershell 3. After the script completed the server did not reboot and Powershell still reports at being on version 3.
Execute Command - Success - 12/11/2018 9:21:01 AM
Parameter:
cmd.exe!!! /c "@powershell -NoProfile -ExecutionPolicy unrestricted -Command $PSVersionTable.PSVersion.Major"
Output: 3
Scripting KeepAlive - Success - 12/11/2018 9:21:17 AM
Parameter:
15
Output:
OK
Invoke Script - Success - 9/21/2018 9:21:19 AM
Parameter:
1|t+3W7tDAxeTWTQn5C/bVxZDKGwLrfLBoJfIQY1BoKWy4PxqGj9BC1w7zG4XQJkCtOeLHdL4XUB8iOAo9a897LWByVE2tOPQ8AIu59mBmbaII1gYQjg9F1cxqKeenGXRuLzKzztmlp4bKzDa1OOA2D8ubghOu2ly5Q3QkkW+H6dcR84QOn67vwRv0yAecpfhXGJpRcN0JuDD/XwNvyJw6pFCsbL8iYxTYWTayVt9m7LRj0O8iCAxGQ5Mhlk0/g8bE9d/lFCZ0gMkIo6wc7tsSeI8QetNvAs7AW3dQe9hj7RSirWRM0q5W2xorVmY4r0XKG7HwI6dYg10TYnFuYjkban+1VeLmrm/r|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw|t+3W7tDAxeS+6CYhhD1YbVhOHsuyZygw
Output:
4.6.01055|4.6.01055|4.0.0.0|
DownLoad URL - Success - 12/11/2018 9:21:31 AM
Parameter:
https://download.microsoft.com/download ... 819745.msu
Output:
OK Downloaded File https://download.microsoft.com/download ... ltiPkg.msu and saved as %windir%\ltsvc\Windows6.1-KB2819745.msu
Execute Command - Success - 12/11/2018 9:21:36 AM
Parameter:
cmd.exe!!! /c "wusa %windir%\ltsvc\Windows6.1-KB2819745.msu /quiet /forcereboot"
Output:
OK
Scripting KeepAlive - Success - 12/11/2018 9:21:47 AM
Parameter:
15
Output:
OK
Re: Updating Powershell with PoSH
Ok A couple of more questions.
What is the OS we are working with? Win 7 Win 10 Etc...
Next if you execute manually on the same agent as before that reports version 3. Log in to the desktop and open a admin command line console on desktop. Copy the following into the command window and run it.
What does DOS report back?
What is the OS we are working with? Win 7 Win 10 Etc...
Next if you execute manually on the same agent as before that reports version 3. Log in to the desktop and open a admin command line console on desktop. Copy the following into the command window and run it.
Code: Select all
wusa %windir%\ltsvc\Windows6.1-KB2819745.msu /quiet /forcereboot
Re: Updating Powershell with PoSH
OS Versions are Windows Server 2008, 2008 R2, and 2012.
When I ran the command from that server using an elevated command prompt there was no message and nothing happened.
When I ran the command from that server using an elevated command prompt there was no message and nothing happened.
Re: Updating Powershell with PoSH
Really, ok lets run just this part..
wusa %windir%\ltsvc\Windows6.1-KB2819745.msu
Does anything get reported? Looking for a Microsoft error like version mismatch or update does not apply warnings.
wusa %windir%\ltsvc\Windows6.1-KB2819745.msu
Does anything get reported? Looking for a Microsoft error like version mismatch or update does not apply warnings.
Re: Updating Powershell with PoSH
Got an error that time.
Windows Update Standalone Installer
Installer encountered an error: 0x80096002
The certificate for the signer of the message is invalid or not found.
Windows Update Standalone Installer
Installer encountered an error: 0x80096002
The certificate for the signer of the message is invalid or not found.
Re: Updating Powershell with PoSH
Interesting..
Let me see if they have a new installer posted.
Let me see if they have a new installer posted.
Re: Updating Powershell with PoSH
Interesting..
Let me see if they (Microsoft) has a new installer posted.
Let me see if they (Microsoft) has a new installer posted.
Re: Updating Powershell with PoSH
Good Afternoon,
I was wondering if you had an update on this?
Thank you!
I was wondering if you had an update on this?
Thank you!