Best Practices using PM/PMC or PSB administered Software update Clients
Let's "fantasize" the following small production environment:
PMS/PMC ver 11.22:
100 F-Secure Client Security Premium 11.60 build 284 w7-w8 clients
100 F-Secure Software Updater 2.00 build 1384
-Software update deployment policy: all possible,overwite WSUS,install every Thursday at 0300 am,force restart
-"Broken-Tuesday MS-patch comes up int the "wilderness",no official MS-solution available yet..
What would be your suggestions of Best-Practice-administration of this?.Try to describe it step by step..
etomcat Posts: 1,319 Superuser
Honestly said, for a 100 computer company, the sysadmin would probably have to face musketry, if he or she rolled out M$ hotfixes without first testing them on a handful of "scapegoat" computer chosen to represent the PC fleet in all departments of the company.
In a school or an underfunded institute, there is probably no full-time sysadmin. In that case, F-Secure support could probably assist in creating a .JAR file out of the Microsoft supplied bad-patch uninstaller tool, which could then be distributed via the PMC or the PSB push-install tool. (Unsigned packages used to be accepted by F-Secure centralized management system if a setting was changed in the config. Maybe this is no longer possible?)
Best Regards: Tamas Feher, Hungary.6 1Like