spnkzss Posted February 8, 2017 ID:1100086 Share Posted February 8, 2017 Since I do not have NetBIOS installed on my network, I cannot do a push install. I originally installed the Management Console and the created an Installation package that is delivered via group policy. This has worked for 80+ installations without issue. I just upgraded from 1.6.1.x to 1.7.0.3208. I created a new .msi installation package. I then created a new folder under the same location as the old .msi and put the new ClientSetup.msi into that folder. I then went into the gpo, added the new .msi file and told it to upgrade the other installation package. On the client I get this in the Event Viewer: Event ID: 109 Description: Application Malwarebytes' Managed Client (2) from policy Malwarebytes Install was configured to upgrade application Malwarebytes' Managed Client from policy Malwarebytes Install. The assignment or installation of the upgrade application Malwarebytes' Managed Client (2) from policy Malwarebytes Install failed with error : %%2 The upgrade will be stopped. I recreated the installation package as an .exe so that I could manually run it on one machine that had the installation from the previous .gpo, just to make sure the upgrade just doesn't fail out, and that upgrade worked. Thoughts? Rob Link to post Share on other sites More sharing options...
djacobson Posted February 8, 2017 ID:1100109 Share Posted February 8, 2017 Deploying via the offline installer through third party tools requires that the previous install be removed before installing the newer version. The third party install cannot upgrade over the top of an existing install. Link to post Share on other sites More sharing options...
spnkzss Posted February 8, 2017 Author ID:1100113 Share Posted February 8, 2017 So, if I did an ungrouped install via group policy, moved all the computers to their appropriate new Group, nwo have to uninstall and reinstall to do an upgrade, I will have to regroup them again? Link to post Share on other sites More sharing options...
djacobson Posted February 8, 2017 ID:1100175 Share Posted February 8, 2017 The groups the clients are held in within the console are determined by a file on the endpoint, a group GUID in a file tells the clients where they belong. As long as this file doesn't change, the client will report right back to where they were before after the upgrade is complete. The file is C:\ProgramData\sccomm\sccomm.xml on the endpoint. Link to post Share on other sites More sharing options...
spnkzss Posted February 9, 2017 Author ID:1100350 Share Posted February 9, 2017 I think there is something else going on, as overnight, I had a handful of machines actually upgrade via the policy. Most machines still aren't updating this morning, but I will watch it for a couple days. Rob Link to post Share on other sites More sharing options...
djacobson Posted February 9, 2017 ID:1100422 Share Posted February 9, 2017 In some instances, the endpoint will need to restart to finish its upgrade. Let us know how your observations go and if you need any more help. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now