Can't install Endpoint 10.6.1 on WIndows 10 -1903

[seattlemicro]

This has us putting a halt on a handful of new PC installs because the PCs already have 1903 on them.  We just renewed about a half a dozen McAfee subscriptions.  We went all McAfee with most of our clients years ago because Symantec Endpoint was a resource hog on the servers.  We have one client on ESET with no issues at all.  Time to look at another product?

[spdif]

If you aren't using ENS Firewall you can deploy Virusscan Patch 13.  Depending on your licencing the on-premise version of mvision endpoint might also be an option  while you search for a replacement. 

Just remember the Universal Rule of Endpoint Security Administration.  The AV product you hate the most is the one your organization bought last year. 

[Sys_Admin]

@seattlemicro

I have to explain to one of my bosses why he cant get his shiny new 1903 machine, and to the other two why they can't upgrade to 1903.

As an added complication all three happen to be the OWNERS also.

We have EPO cloud so nothing can be done.

Wanted to move to an on-premises EPO but was told they can't transfer the licenses!

So stuck until end of August for now, but won't be stuck when our renewal comes around early next year.

[Former Member · Accepted solution]

@Sys_Admin  @Former Member @seattlemicro 

Just to clarify. There is a supported version of ENS for fresh builds of 1903.

This is the July Update > which is a full installer.

The release can be obtained through support. Please check KB91642 before deploying the July Update though.

[spdif]

@Former Member offering a version of the product with a critical known issue is not a solution.

from KB82450, copied 7/22/2019:

Critical:

Reference Number	Related Article	Found in ENS Version	Resolved in ENS Version	Issue Description
ENSW-26688	KB91642	10.6.1 July Update		Issue: A reboot loop can occur after installing or upgrading to ENS 10.6.1 July Update. The issue occurs only if other Subject Interface Package (SIP) providers are present. McAfee is working to provide a solution. Customers using the ENS 10.6.1 July Update package are advised to carefully test before wider adoption. Test for the presence of the symptom when it is unknown whether a third-party SIP provider is present on systems. For instructions to recover a system in a reboot loop, and for more information, see the related article.

---

[Sys_Admin]

Well clearly your departments don't communicate with each other - .

From the email sent to me LAST WEDNESDAY...

Quote..

"Please be informed that the July update which was rolled out to on-prem customers had certain issues wherein a reboot loop occurs after installing or upgrading to ENS 10.5.5 July Update or ENS 10.6.1 July Update. Hence out of caution, this ENS 10.6.1 and 10.5.5 July Updates has been pulled back for on-prem customers."

Then further down...

Quote

"Note: It is also not possible to provide the RTS of this patch as our engineers are in the process of re-building it."

[Former Member]

I'm sorry to hear you've been misinformed. The build is very much available via support, if you are still having trouble obtaining it, please feel free to send me the SR number and I will provide it to you if you wish.

[Former Member]

Fully understand your concerns however as the KB states only certain customers are impacted hence the release was not fully pulled.

[brentil]

We can confirm that they are available from support still.  We accidentally deleted the extensions zip files for this release but we're in the middle of migrating to a new ePO 5.10 server and needed them to bring extensions into sync between systems.  We put a support request in and had the files within 30 minutes.

[twenden]

Does support have the standalone installer for July update also? We are in a university environment and provide EndPoint Security as a standalone product to students. 

Does the update that support provides include a fix for this SIP boot loop issue? I am in need of providing ENS to students as they are not ePO managed. All our ePO managed systems are OK as they received the May patch that support 1903. 

I am trying to avoid releasing a ENS that has issues and also don't want to resort to having to issues VirusScan 8.8i patch 13 as we have migrated to ENS over a year ago.