locked
UR6 Update Rollup - Agent not updated RRS feed

  • Question

  • Hi Team,

    We have successfully did UR6 update in SCOM 2016 production environment. I could see some 200+ servers agent goes to failed state in pending management. Please let me know what should be done for these servers. 

    Wednesday, May 1, 2019 1:20 PM

Answers

  • Ok, this clearly states that the local SYSTEM account doesn't have enough permissions to perform this action remotely.

    What you could do is to install the agent with a different user (for example a user that belongs to Domain Admins).

    Select the agents that have failed, right-click them and choose Install Agent, then at the "Administrator Account" step, provide a user that has permissions on the agent computers.

    Did you do this and did these agents get updated?

    The Error Code '80070643' is most likely due to connectivity or permission issues, you need to use an action account which has enough permissions on the agent computer.

    If you installed the SCOM Management management pack by Kevin Holman, you could use the Execute any PowerShell task to manually update agents.

    1. Create a share on your SCOM server where you place the MOMAgent.msi in the share.

    2. In the SCOM console, go to Monitoring > SCOM Management > SCOM Agents > select all the agents which have an older agent version.

    3. On the right-hand side click Execute any PowerShell.

    4. You can then define a user account that has permissions on all the agent computers (for example: Domain Admin account).

    5. Then click Override.

    6. In the ScriptBody, type the command to install the SCOM agent manually and define the path to the share where you placed the MOMAgent.msi.

    For installing the SCOM agent manually, you can refer to the following link:

    Examples of installing the agent from the command line
    https://docs.microsoft.com/en-us/system-center/scom/manage-deploy-windows-agent-manually?view=sc-om-2019#examples-of-installing-the-agent-from-the-command-line

    7. Finally click Run.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, May 6, 2019 5:46 PM

All replies

  • Hi,

    Agents should be placed into pending actions by this update for any agent that was not manually installed, you can then simply approve these.

    You can refer to Kevin Holman's blog post below:

    UR6 for SCOM 2016 – Step by Step
    https://kevinholman.com/2018/10/31/ur6-for-scom-2016-step-by-step/

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 1, 2019 1:27 PM
  • Yes, I followed his steps and approved it. Out of 1700 servers, 205 servers failed. What am I to do for these servers. 
    Wednesday, May 1, 2019 1:35 PM
  • I'm aware that these are manually installed agent managed nodes but not sure how to proceed with this. 
    Wednesday, May 1, 2019 1:36 PM
  • Check the errors why they have failed to update.

    I also recommend using the "SCOM Management" management pack by Kevin Holman, with this you can also install/update/uninstall multiple SCOM agents or do various of other things by using the Execute any PowerShell task.

    SCOM Management – MP – Making a SCOM Admin’s life a little easier
    https://kevinholman.com/2017/05/09/scom-management-mp-making-a-scom-admins-life-a-little-easier

    Download here:
    https://gallery.technet.microsoft.com/SCOM-Agent-Management-b96680d5


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 1, 2019 1:46 PM
  • Sure, I shall check on that. I get the below error while approving but I can login to the server using the same account. 

    The Operations Manager Server failed to open service control manager on computer ARSJHPC03.hq.huskyenergy.com.

    Therefore, the Server cannot complete configuration of agent on the computer.

    Operation: Agent Install

    Install account: NT AUTHORITY\SYSTEM

    Error Code: 80070005 

    Error Description: Access is denied. 


    Wednesday, May 1, 2019 1:49 PM
  • Ok, this clearly states that the local SYSTEM account doesn't have enough permissions to perform this action remotely.

    What you could do is to install the agent with a different user (for example a user that belongs to Domain Admins).

    Select the agents that have failed, right-click them and choose Install Agent, then at the "Administrator Account" step, provide a user that has permissions on the agent computers.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 1, 2019 1:54 PM
  • Once I gave a different admin account, it worked but UR version is not updated to UR6(PFA). We have also imported Kevin SCOM management pack; just checked. 
    Wednesday, May 1, 2019 2:02 PM
  • It could just take some time, you could also try clearing the SCOM console cache.

    Also give Kevin's management pack some time to retrieve the information, you can then also check there for the agent versions.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 1, 2019 2:04 PM
  • Sure, thanks for your inputs Leon. 
    Wednesday, May 1, 2019 2:16 PM
  • Hi ,

    Some version change needs restarting. So you can try to restart these agents on a non-business time to see if the version is changed.

    Best regards.

    Crystal


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 2, 2019 1:42 AM
  • Hi Crystal,

    Error Code '80070643'.

    I get this error while approving the agent in pending management. Please help on this. 

    Monday, May 6, 2019 4:24 PM
  • Ok, this clearly states that the local SYSTEM account doesn't have enough permissions to perform this action remotely.

    What you could do is to install the agent with a different user (for example a user that belongs to Domain Admins).

    Select the agents that have failed, right-click them and choose Install Agent, then at the "Administrator Account" step, provide a user that has permissions on the agent computers.

    Did you do this and did these agents get updated?

    The Error Code '80070643' is most likely due to connectivity or permission issues, you need to use an action account which has enough permissions on the agent computer.

    If you installed the SCOM Management management pack by Kevin Holman, you could use the Execute any PowerShell task to manually update agents.

    1. Create a share on your SCOM server where you place the MOMAgent.msi in the share.

    2. In the SCOM console, go to Monitoring > SCOM Management > SCOM Agents > select all the agents which have an older agent version.

    3. On the right-hand side click Execute any PowerShell.

    4. You can then define a user account that has permissions on all the agent computers (for example: Domain Admin account).

    5. Then click Override.

    6. In the ScriptBody, type the command to install the SCOM agent manually and define the path to the share where you placed the MOMAgent.msi.

    For installing the SCOM agent manually, you can refer to the following link:

    Examples of installing the agent from the command line
    https://docs.microsoft.com/en-us/system-center/scom/manage-deploy-windows-agent-manually?view=sc-om-2019#examples-of-installing-the-agent-from-the-command-line

    7. Finally click Run.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, May 6, 2019 5:46 PM
  • Hi

     

    For the following error code. it can be caused by many reasons:

    Error Code: 80070643

    Error Description: Fatal error during installation.

     

    Possible Cause:

    • The account previously specified to perform the agent installation in the discovery wizard will need to have permissions to connect remotely to the target computer and install a Windows service. This requires local administrator permissions due to the requirement to write to the registry.
    • Group policy restrictions on the management server computer account, or the account used for agent push, can prevent successful installation. Group Policy Objects in Active Directory that prevent the Management Server computer account, or the user account used by the Discovery Wizard, from remotely accessing the Windows folder, the registry, WMI or administrative shares on the target computer can prevent successful deployment of the Operations Manager agent.
    • The Windows Firewall is blocking ports between the Management Server and the target computer.
    • Required services on the target computer are not running.

     

    Please try the solutions under the following link to see if it is working:

    https://support.microsoft.com/en-us/help/2566152/troubleshooting-the-installation-of-the-system-center-operations-manag

     

    Hope the information can help. If any question, please let me know.

     

    Best regards.

    Crystal


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 7, 2019 3:30 AM
  • Hi,

    what is that status here? Were you able to resolve this? Appreciate your feedback and thank you in advance!

    Regards,


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Monday, May 13, 2019 12:13 PM