Showing posts with label AGENT. Show all posts
Showing posts with label AGENT. Show all posts

Saturday, 15 October 2016

SCCM 2012 R2 Log File for Windows Update Agent and WSUS Server issues

SCCM 2012 R2 Log File for Windows Update Agent and WSUS Server issues


Windows Update Agent

The following table lists the log files that contain information related to the Windows Update Agent.
Log name
Description
Computer with log file
WindowsUpdate.log
Records details about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.
Client

WSUS Server

The following table lists the log files that contain information related to the WSUS server.
Log name
Description
Computer with log file
Change.log
Records details about the WSUS server database information that has changed.
WSUS server
SoftwareDistribution.log
Records details about the software updates that are synchronized from the configured update source to the WSUS server database.
WSUS server

Saturday, 21 May 2016

How to Enable Logging for Linux agent in SCOM 2012 r2

How to Enable Logging for Linux agent in SCOM 2012 r2

    • Linux agent is one of the most challenging to monitor in SCOM. As is cross platform monitoring it does not give clear error when there is error.
    • So you should enable Loging on Agent to see whats happening.
    • Once loging is enabled you can see log created in /var/opt/microsoft/scx/log.log
    • To see the current state of loging type scxadmin -log-list
    • To set loging to Troubleshooting type scxadmin -log-set all verbrose

    • This will set the loging to TRACE and will start recording all events.
    • Once your troubleshooting is compeleted you have to reset the log back/
    • To do this use the command scxadmin -log-reset
    • This will reset the logs back to info level from Trace level

Wednesday, 1 July 2015

Install SCOM 2012 R2 agent on Servers Hosted in Microsoft Azure Cloud

Install SCOM agent on Servers Hosted in Microsoft Azure Cloud


  • Microsot Azure is the Cloud Solution from Microsoft. You can Install SCOM agents and Monitor them using your Existing SCOM environment.
  • To Install SCOM agent on Windows Serve hosted in Microsoft Azure Cloud
  • Logon to Your Azure Portal
  • Then Click on Operation Insight Tab on the left






  • Then Click on the Workspace that you see 









  • Now You will be taken to the Dashboard Page,Now Click on SERVERS Tab



  • Now Click on "Enable OP INSIGHTS"

      • And Install SCOM agent on the Server. This will install SCOM agent on server automatically.


       




      • Now Login to Your Server and Go to Control Panel and Open Microsoft Monitoring Agent. YOu can see that the agent ins installed.If you have In house SCOM server then configure you Management server and your SCOM management group. in Operations Manager Tab. By Default it Connects to Microsoft Operaions Manager

      • You can see that after some time MP's get downloaded and Monitoring Start.

      Monday, 25 May 2015

      PowerShell Command to repair SCOM agent

      PowerShell Command to repair SCOM agent


      • There are many different ways to repair a SCOM agent.
      • Most preferred way is to Use SCOM console Right Click and select repair option.
      • Another way is to Use Command Shell command
      • "REPAIR-SCOMAGENT" is the command you have to use to repair the SCOM agent.
      • By default it uses the SCOM action account to repair the agent.So make sure it have sufficient rights on the server

      Wednesday, 13 May 2015

      Upgrade SCOM 2012 R2 agent using SCCM for latest UR upgrade



      Upgrade SCOM 2012 R2 agent using SCCM for latest UR upgrade



      • Follow the below command to upgrade SCOM agents using SCCM



      msiexec /i path\Directory\MOMAgent.msi /qn /l*v %temp%\MOMAgentUpgrade.log
      
      
      • This will upgrade the agent using the latest UR4 or UR5 upgrade

      Tuesday, 12 May 2015

      Install SCOM 2012 R2 agent using SCCM or command line

      Install SCOM 2012 R2 agent using SCCM:

      Inorder to install SCOM agent using SCCM, we have to follow the belwo procedure. Please use the below command line script which you use to install the SCOM agent from command line or SCCM



      %WinDir%\System32\msiexec.exe /i path\Directory\MOMAgent.msi /qn USE_SETTINGS_FROM_AD={0|1} USE_MANUALLY_SPECIFIED_SETTINGS={0|1} MANAGEMENT_GROUP=MGname MANAGEMENT_SERVER_DNS=MSname MANAGEMENT_SERVER_AD_NAME =MSname SECURE_PORT=PortNumber ACTIONS_USE_COMPUTER_ACCOUNT={0|1} ACTIONSUSER=UserName ACTIONSDOMAIN=DomainName ACTIONSPASSWORD=Password AcceptEndUserLicenseAgreement=1

      USE_SETTINGS_FROM_AD={0|1}:

      Indicates whether the management group settings properties will be set on the command line. Use 0 if you want to set the properties at the command line. Use 1 to use the management group settings from Active Directory.

      USE_MANUALLY_SPECIFIED_SETTINGS=={0|1}:

      If USE_SETTINGS_FROM_AD=1, then USE_MANUALLY_SPECIFIED_SETTINGS must equal 0.

      MANAGEMENT_GROUP=MGname:

      Specifies the management group that will manage the computer.


      MANAGEMENT_SERVER_DNS=MSname:


      Specifies the fully qualified domain name for the management server. To use a gateway server, enter the gateway server FQDN as MANAGEMENT_SERVER_DNS.


      MANAGEMENT_SERVER_AD_NAME=ADname:

      Use this parameter if the computer's DNS and Active Directory names differ to set to the fully qualified Active Directory Domain Services name.


      SECURE_PORT=PortNumber:
      5723

      ACTIONS_USE_COMPUTER_ACCOUNT={0|1}:

      Indicates whether to use a specified user account (0) or the Local System account (1).

      ACTIONSUSER=UserName:

      Sets the Agent Action account to UserName. This parameter is required if you specified ACTIONS_USE_COMPUTER_ACCOUNT=0.

      ACTIONSDOMAIN= DomainName:

      Sets the domain for the Agent Action account identified with the ACTIONSUSER parameter.

      ACTIONSPASSWORD= Password:

      The password for the user identified with the ACTIONSUSER parameter.

      AcceptEndUserLicenseAgreement=1:

      Used to specify that you accept the End User License Agreement (EULA).




      Tuesday, 20 January 2015

      SCOM Agent is not installed but still showing in Pending State in SCOM 2012 r2-Resolved

      SCOM Agent is not installed but still showing in Pending State in SCOM 2012 r2-steps to resolve


      • We recently had a issue where there is no SCOM agent on the server.But When we try to Install SCOM agent from Console its says there is already agent pending to be managed and doesn't allow to install.
      • Then when we check the pending agent state it shows up there ,but if i go and check the server there is no SCOM agent.
      • So we where puzzled how its coming in pending management. Then we reject in pending management it goes from there.But if i try to install agent again it comes in pending management.
      • So its stuck in pending management,So this time i rejected it and its gone from there.
      • Then i Ran the Command shell command
                     GET-SCOMPendingManagement | where {$_.AgentName -eq "FQDNServername"

      • And the server was showing pending in command shell but not in console.
      • To fix it you need to login to Operations Manager database server and run the below store procedue on query window on the operations manager database
                     p_AgentPendingActionDeletebyAgentName 'FQDNServername'

      Wednesday, 31 December 2014

      SCOM Agent Uninstall error : The patch Package could not be opened

      SCOM Agent Uninstall error : The patch Package could not be opened



      • SCOM agent uninstall was always a piece of Cake. Jut right click and select uninstall from console



      • But recently i was migrating from SCOM 2007 to SCOM 2012 and i have to uninstall SCOM 2007 R2 agents.Most went wellBut few failed with error


      "The patch Package could not be opened. Verify that the patch package exists and that you can access it.Or contact the application support."


      • First reaction was shocked. Haven't seen this error.I have access and all the msi to uninstall.



      • Later i found out that issue is because of fact that the agent creates a reg entry of while installing with unique patch number.And if this conflicts or if there multiple of them then it will fail.


      So to fix It follow the below steps,


      • Click Start
      • In Search type Regedit
      • Click on HKEY_CLASSES_ROOT\Installer\Products\07779052F1B26F94BAD9C107B8
      • Then double click on "Patches"
      • Delete all the Values in it and Close it.
      • Now go and try to uninstall it and it will work fine.