Important! Release of patches to address security vulnerabilities in SafeGuard Windows Clients (SGN/SGE/SGLC)

Many thanks for this additional point which I raised last time about the patch...

"Additionally the version in the SafeGuard about box has been updated and the clients report the new version using the machine inventory, which can be displayed in the SafeGuard Management Center."

This is much appreciated - I'm sure an easy/small thing to implement but makes a huge difference to management and compliance.

I performed the update on my first Windows 7 Pro machine and got this.  What assurance will I have this won't happen on the next.  Also, is there a way to script this in Labtech? 

I also wanted to stop and give kudos on changing the behavior and having this release show the new build in the management center after successful installation and first check in. It really will make it easier to ensure clients have successfully installed the latest update.

Hi Jeffrey, 

Sorry to hear about the issue you had earlier, We have not received any complaints so far since this patch was released, so am sure you shouldn't be having any issues.

I haven't rolled it out yet, but I have a LabTech script for this.

I've used ZenWorks as the client is installed on each of my laptops. I've rolled it out to a handful now and no issues yet?

I've used some switches to make it silent so that it doesn't impact the end user. Works well so far!

"SGN8005Patch1804_x64.msp" /qn REBOOT=ReallySuppress /norestart

Hi Jeffrey,

on W7 it is vital to have the security updates from MS on a current level (especially KB3033929 is important). 

https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929.

Hope that helps

F.

I have just received this error upon my first attempt at the 1804 patch, with a Windows 7 Pro 64bit, Sophos SafeGuard 8.00.0.251.  I have full access to the 3915d.msi in the location it says has the error, and I even ran it separately to make sure it opened, and it did.  I've logged on as the domain admin and also made sure security permissions were accurate, and they are.   I also did verify that KB3033929 is installed on the PC, as mentioned in the above comment.

Should I open a ticket with your support?

Hey,

I may be mistaken here, however, I think these files are .MSP, not .MSI files. Windows handles .msp files as 'transforms' to msi's. Try renaming to an .msp and see if you continue to have issues.

AWilson said:

Hey,

I may be mistaken here, however, I think these files are .MSP, not .MSI files. Windows handles .msp files as 'transforms' to msi's. Try renaming to an .msp and see if you continue to have issues. 

That helps proceed past the first step, renaming to MSP......but then it failed for a second step (below).  I tried the same trick, but it never continued.  I even copied the file, leaving the .MSI and then renamed the copy identically, having .MSP as well.  Still nothing.   Definitely seems like a bug of some sort with the installer.