Reset Software Update Plug-in Policy

I need a solution

Good evening,

I have encountered an issue on a server which is running on Windows 2008 R2 OS with Altiris Management Agent 8.1. The issue i have is the fact that it failed to install a bunch of updates and it have reached the maximum default number of “reinstallation attempts after task failure” of 3. 

I’ve searched high and low and tried to locate the Altiris registry key on the server which contains this fact and try to delete, but with no luck.

Could you kindly let me know where is this key located so i can manually purge it and have the server retry the failed updates? 

Thank you for your time.

0

Related:

Enrollment statistics shows Endpoints with ‘Authentication Pending’ status

I need a solution

Hi, I configured my EDR and SEPM on 19/04. Mix of Windows 7 and Windows 8.1. Only 3 endpoints have been enrolled (2 Windows 7 and 1 Windows 8.1); the rest (31) still Endpoints with ‘Authentication Pending’ status. How can I troubleshoot this or should I wait longer? My understanding is that if some has been enrolled, then eventually all will be enrolled. Thanks to help! 

0

Related:

KB4487011 and KB4487006 fix unresponsive app issues

Microsoft recently released Windows 10 cumulative updates KB4487006, KB4487011, KB4487021, and KB4487029 addressing non-security bugs in the operating system. The company aims to enhance the reliability of the OS with bug fixes, stability enhancement and quality improvements.

KB4487011 improvement and fixes

KB4487011 offers four major improvements and fixes that we’ll list below:

1. IE Fails To Load Images Bug Fix

The update addressed the problems related to loading images having a backslash () in their relative source path. The issue was reported in the previous releases.

2. Microsoft Access Bug Fix

The Microsoft Access bug was responsible for randomly stopping those apps that are using Microsoft Jet database along with the Microsoft Access 95 file format. Just like the previous issue, this bug was also reported in KB4487044.

3. Application Not Responding Bug Fix

This issue was reported by the users that the issue arose when the same input queue is used by its two threads.

4. Device Compatability Issue Fix

This fix addresses a bug that existed in the evaluation of the compatibility status of the entire ecosystem of Windows. It is done to ensure device and application compatibility for all Windows updates.

KB4487011 Known Issues

As of now, Microsoft has not acknowledged any known issues in the update. The blog post will be updated if the tech giant confirms any potential bugs.

KB4487006 Improvement & Fixes

Apart from the device compatibility and issues and Microsoft Access bug fix, the update comes along with a series of bug fixes. Some of the major features are discussed below.

1. Remote Desktop Protocol (RDP) Client Bug

The release of KB4487006 resolved a major issue that existed in the previous build. The users got black screen at the login in the Remote Desktop Protocol (RDP) client application.

2. win32kfull.sys Reliability Issue

The update fixes a reliability issue with win32kfull.sys, that existed in the previous versions. The bug was initially introduced in KB4487026.

3. Microsoft Outlook “The operation failed” error

When a user tried to open the Microsoft Exchange Address Book, “The operation failed” used to appear. The issue was introduced after the installation of KB4457127 on Active Directory domain controllers.

KB4487006 Known Issues

1. Startup Issues in Specific Laptops

Specific Lenovo and Fujitsu laptops that currently have less than 8 GB RAM may face startup issues. The bug is created as a result of KB4467691installation.

One of the easiest ways to resolve the issue is restarting your machine with the help of Unified Extensible Firmware Interface (UEFI). Make sure to disable Secure Boot before restarting the device.

2. Cluster Service Start Fail

If the “Minimum Password Length” of the group policy uses more than 14 characters then the users can face cluster service start fail error. The following error message is displayed to the user “2245 (NERR_PasswordTooShort)”. The installation of KB4467684 triggers the error.

Microsoft is currently working to resolve the issue and the workaround is expected to be available in the coming weeks. Till now the company suggests the users to set the default minimum password length policy to equals to or less than 14 characters.

3. IE 11 Authentication Issues

Some authentication issues are reported in Internet Explorer 11 right after the installation of IE11. As soon as the same account is used by two or more users for various concurrent login sessions on the same Windows Server machine.

Microsoft recommends the users to create unique user accounts. Moreover, multiple RDP sessions should be disabled for each user account.

System Center Virtual Machine Manager (SCVMM) fails to manage the logical switches that have been deployed on the host that is managed by SCVMM. Also, a stop error is raised in vfpext.sysif you fail to follow the best practices.

A quick workaround is to access the affected host machine to run mofcomp files for running two mof files named as Scvmmswitchportsettings.mof and VMMDHCPSvr.mof. Microsoft recommends that users can avoid a stop error by following the best practices.

Download KB4487011/KB4487006 for Windows 10

The KB4487011/KB4487006 patch can be automatically downloaded through the Settings menu. If you have not yet received the update you need to open the Settings menu by pressing Win+I. Now you need to navigate to Update & Security >>Windows Update >> Check for updates.

You can enhance the consistency of the update process by installing the latest servicing stack update (SSU) just before installing the LCU KB4487011.

Microsoft has followed its tradition to specify third Tuesday of the month for the release of the non-security cumulative update. Although these updates are termed as non-security, it is yet not clear that either security components are included in the update or not. 

Comment down below if you have faced any pre and post-installation issues while installing KB4487011 and KB4487006.

Completely Remove Altiris Agent

I need a solution

I couldn’t find anything recent in the knowledgebase (i.e. whatever articles I came across specified versions less than 8.1) so thought I’d post my query here.  So if I have a computer with SMA 8.1 that no longer has network connectivity to my SMP server, what’s the current thought on commands to manually and most thoroughly remove the Altiris Agent from the workstation?  Are commands for, say, 7.5 still applicable for 8.1?

0

Related:

ServiceDesk 8.5 RU1 – New Features

I do not need a solution (just sharing information)

Symantec™ ServiceDesk 8.1 RU1 Release Notes
DOC10487
https://support.symantec.com/en_US/article.DOC10487.html

New Features

Feature Description
Updated the theme of all the forms. The Themes of all the forms is now updated to match the new Process
Manager format.
0

Related:

“Windows could not connect to the System Event Notification Service service”

I need a solution

Hello all,

Our company has been dealing with a nagging issue for the last week or two. I have tried multiple fixes but ultimately I believe it has to do with our recent Symantec Endpoint Protection Manager migration to a new server and client SEP upgrades from v12 to v14.2.

Upon logging on in the morning, users will get an error: “Windows could not connect to the System Event Notification Service service”

After a reboot (usually just one, sometimes 2 or 3), they will be able to log in again. This only affects Windows 7 and 8.1 users, not Windows 10. It does not seem tied to Group Policy as users are spread across various OU’s and no changes have been made recently.

We have tried: 

  • Symantec update to 14.2.1031.0100
  • Patching windows
  • Rejoining domain
  • Forcing group policy update
  • Netsh winsock reset
  • Phone reboots (Act as switches for the PC’s)
  • Reg key edits: https://appuals.com/fix-windows-could-not-connect-to-the-system-event-notification-service/
  • Setting Group Policy Service (gpsvc) to Automatic startup type
  • Setting DHCP Client service to Automatic startup type
  • Uninstalling KB2952664
  • Rafeeq’s registry edit suggestion (Didn’t find these keys at all): https://www.symantec.com/connect/forums/symantec-endpoint-protection-blocks-system-event-notification-service-starting

So ultimately I am wondering if there are any settings within Symantec Endpoint Protection that could be causing this issue. I greatly appreciate any and all input.

Thanks,

Matt

0

1547218740

Related:

8.1 Failure updating to RU7

I need a solution

Good evening!

I am preparing to install updates to my existing 8.1 RU5 installtion in preparation for upgrading to 8.5.

The updates finished, but I had an error.

A critical error occurred:

Product failed to install.  See log for details.

Configuration failed while attempting: Configure Symantec Virtual Machine Management 8.1 RU7…

Has anyone seen anything similar?  

0

Related:

Receiver for Windows 4.11 | Error “Unable to connect to the server. error SSL Error 4”

Microsoft introduced new set of ciphers, in their update KB2919355, which is applicable to Windows 8.1 and Windows Server 2012 R2 operating systems.

The following cipher suites are enabled and in this priority order by default by the Microsoft Schannel Provider:

Cipher suite string Allowed by SCH_USE_STRONG_CRYPTO TLS/SSL Protocol Versions
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 Yes TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 Yes TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 Yes TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 Yes TLS 1.2
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 Yes TLS 1.0, 1.1, 1.2
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 Yes TLS 1.0, 1.1, 1.2
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 Yes TLS 1.0, 1.1, 1.2
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 Yes TLS 1.0, 1.1, 1.2


Receiver for Windows 4.7, Receiver for Mac 12.5, Receiver for Android 3.12.2/3.12.3 and Receiver for Linux 13.6 introduce these ECDHE ciphers which trigger this defect.

• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

Install KB2919355 on all Windows 8.1 client machines.

Related:

Data Protection Advisor DPA Upgraded TSM to 8.1 Spectrum Protect 8.1 (formerly TSM) and data collection stopped working.[1]

Article Number: 501371 Article Version: 3 Article Type: Break Fix



Data Protection Advisor,Data Protection Advisor Family,Data Protection Advisor 6.3,Data Protection Advisor 6.2,Data Protection Advisor 6.1,Data Protection Advisor 6.0

Data Protection Advisor DPA Site upgraded TSM 7.1 to 8.1 Spectrum Protect 8.1 (formerly TSM) and data collection stopped working.

DPA version prior to DPA 6.4

DPA versions prior to DPA 6.4 are not compatible with Spectrum Protect 8.1 (formerly TSM).

Upgrade the DPA Server and Agents to DPA 6.4 or newer.

Related:

  • No Related Posts