I probably should have known better, but as I've received a notification in my inbox this morning, I've downloaded (using Software Manager in EPO) and updated both the Hotfix and the Service Patch 3.
Hotfix is deploying nicely, however the Patch 3 just does not want to deploy. I've checked my Agent Update Tasks and there are checks against the VSE 8.8 entry under updates and patches.
Rather interestingly, in software manager the Patches have in the Additional Check In Information column it says "Current Branch, Unknown Distribution Type" and looking at the Master Repository both Patches 2 and 3 were checked in as Current?!!!
Anyone else seeing similar issues?
Message was edited by: mwebb on 09/01/13 04:53:03 CST
Message was edited by: mwebb on 09/01/13 04:58:18 CSTMessage was edited by: mwebb on 09/01/13 05:00:16 CST
we are now useful to this.
A new patch is available after testing period into the epo
the patch is incorrect
then the patch is deleted and after some weeks, sometimes, a new try.
Sorry to say that but seing this a few times during the last monthes makes me thinking that our own internal change procedure is not so bad
I suppose we should all note that Patch3 is for Windows 8 and Windows 2012 Servers ONLY - so it will not deploy out to XP, Vista or Win7....
VirusScan Enterprise 8.8.0 Patch 3 package — Updates VirusScan Enterprise 8.8.0 Patch 2 clients on Windows 8 and Windows Server 2012 systems only.
VirusScan Enterprise 8.8.0 Repost Patch 3 package for Windows — Includes full installation for new systems only.
The Repost Patch 3 package installs:
1. trouble is, if you look my capture that the package has been imported into my evaluation repo but stay like it's still missing
2. i've tried to distribute it on an W8 computer (tagged for me as an alpha mcafee computer )without success.
I'll retry everythning from the start.later
First let me say, We are _never_ going to release a patch like this one again. And by _never_ I mean, unless we have to again for some crazy unexpected reason .
This patch 3 package is unique because it's only intended to be installed on Windows 8 and Server 2012.
Also, with respect to the full install package, we have an ePO limitation that only allowed having 1 single full install package in the repository.
Because of these items we had to craft a single package that could be used in ePO that would deploy the Patch 3 files for Win8/Server2012 systems, and the Patch 2 files for non-Win8/non-Server2012. Consequently, MID is incapable of understanding what this package is.
We will be returning to the regular 1-patch for all OS's in the Patch 4 release (if it will be called that; schedule still to be determined).