-
Notifications
You must be signed in to change notification settings - Fork 81
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
[BUG] Upgrade - Downloader still 2.9.1.0 #260
Comments
I think it is not ok. Windows EventLog:
However, if I update with the same command (!!) via the command line (eg via psexec) everything updates fine. What is additionally doing OCS now that updating via the OCS package (deployment package) is now impossible? |
I'm doing the upgrade now with a workaround. Not pretty, but works.
But here it needs a real solution! In the past there was also the parameter /upgrade, why is this no longer available? |
Having the same Problem with version > 2.9 Also having the problem, that the client isn't launching automatically according to the PROLOG_FREQ settings. |
Hi, how can i upgrade the agent version on only few PC to test? There is a wiki to follow to update the agent? |
Is there anything new on this topic? I also distributed the upgrade to 2.10.1 via workaround (see above). Surely there should be a clean solution here? |
Hi, can you provide a howto to complete without problem an upgrade of the agent? |
Hi, I have built a batch file as already written above (#260 (comment)) with which I perform the upgrade. It's not pretty, but it works. |
General information
Operating system : WIN10 64, WIN11 64
OCS Inventory information
Windows agent version : 2.10.0.0 (Upgrade vom 2.9.2.0)
Problem's description
After the update (according to the instructions here) the agent is on version 2.10.0.0, but the download service remains on 2.9.1.0 (it was not touched with 2.9.2.0).
Here is the script I use for the upgrade package:
So Agent ist OK:
Downloader NOT:
Here we finally need a reliable solution on how to deal with the problem. There is currently no clean, 100% working solution to update the OCS agent cleanly via OCS.
In the last versions there was at least the command line option "/upgrade", but this is no longer available.
The text was updated successfully, but these errors were encountered: