SCOM Agent install \ deployment query?

Hi All
I have a query regards best practices. Within our environment we will have a number of Build Environments (all within the same domain), which will involve servers being built, decommissioned and rebuilt for application testing teams.
Query is how best to handle the install\life-cycle of the SCOM Agent with regards to this scenario?
Just looking to see if others have had experience of this type of scenario and best practices \ experiences etc
Any thoughts much appreciated.
Kind Regards
Andrew

Just have a couple of questions/suggestions:
Do the different servers have some sort of naming convention ie:
Prod servers have: PRD in the name
dev servers have: DEV in the name
ect.... If so then my suggestion is to create a number of groups ie Prod Servers, Dev Servers, Test Servers ect. and have these groups auto populate. You can then configure overrides for these groups for alerts
to manage alert volume/escalations.
As for install are these servers windows server/ unix servers or a mix?
Number of ways you could try managing installs is to script the install (Google SCCM SCOM agent deployment script for some hints)
Consider if you want to auto approve agents or manually approve them so you know when servers are being added or removed.
If servers are being removed you could look at scripting a removal of the server from SCOM (have a look at http://social.technet.microsoft.com/Forums/en-US/c4dcfce6-b241-4435-8f8b-1276814c455e/scom-2012-powershell-command-to-remove-agent)
If you could detail what your setup is or what you would like to be able to do we could make more suggestions.
Cheers,
Martin
Blog:
http://sustaslog.wordpress.com
LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

SCCM Agent Install \ Deployment query?

Hi All
I have a query regards best practices. Within our environment we will have a number of Build Environments (all within the same domain), which will involve servers being built, decommissioned and rebuilt for application testing teams.
Query is how best to handle the install\life-cycle of the SCCM Agent with regards to this scenario?
Just looking to see if others have had experience of this type of scenario and best practices \ experiences etc
Any thoughts much appreciated.
Kind Regards
Andrew

Thank you for your replys Jason and Wally,
I guess 'best practice' was the wrong phrase to use in this case. However across the other System Center applications a number of best practices have become established for a certain scenarios\processes, and I was looking to see if a similar
approach had become established for the scenario outlined. However on reflection I appreciate SCCM is a product that has enormous flexibility with regards to the variety of environments and the complexity of scenarios it is able to accommodate\handle. Thus
as you say, 'best practices' are not that realistic in general.
With regards to the scenario mentioned, we have 'x' number of development environments which will be provisioned via VMM Service Templates, via SCSM and SCORCH automation. With the first number of rebuilds the Server names will not be the reused, but
after 'x' number of rebuilds the server names will be cycled\reused. After further digging\reading I believe a scripted approach would be best, along with a separate method of cleaning out old server names from within SCCM itself. The main concern
is when a server names get reused, it may still be in the SCCM database, but the new Server (with same name) has a new SID; which I believe would\could introduce issues.
Although I guess, with all that said, the most elegant\simple approach would be to have a clean uninstall of the SCCM agents whenever a development environment is decommissioned?
Kind Regards
Andrew

Find out what servers have a SCOM agent installed

Hello,
With a list of approx 1400 servers, I am after a quick way to see which ones have SCOM agent installed on them?
This is over one domain .
Thanks in advance
Tubble with Microsoft

You can get all servers with SCOM agents and export to a CSV fileGet-Agent | select-object PrincipalName,ComputerName,Domain | export-csv c:\allServerlist.csv
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical

SCOM agent install fails Error 80070035 - the network path was not found

I have deployed SCOM 2012 agents to most servers (2008, 2008 R2, 2012, 2012R2) in our estate but some either fail to install or are not monitored. I assume the two problems are related, but for now I am concentrating on the servers that fail completely.
Installation is from the Discovery Wizard and I have about 20 servers that fail of various server versions.
So looking at one specific server that is failing to install the agent - a 2008 standard service pack 2
The firewall in on and file and printer sharing is enabled for domain, remote administration is enabled for domain
I added a specific rule to allow TCP 5723 and 5724
DCOM is enabled
I can Ping the target server from the SCOM server by both name and FQDN - both return the same IP and our DNS server has only one entry for this server
I can browse to the admin share \\server\C$ from the SCOM Server, using the same account that I specify for the agent install that is a domain admin with rights on this server (and on the other servers the agent
did install to) and the server has plenty of disk space available
I am not sure what else to look at so would welcome any ideas
Thanks

Hi Petro,
I have a Agent installation failure cheat sheet, For your error 80070035 it is said to perform a manual installation.
So i would like to understand which version of SCOM is this ? 2007 R2 or 2012 or 2012 r2 ?
Also check if your agents have the WMI service started and enabled ?
Also if yours is a SCOM 2007 R2 do you have a RMS & MS in your management group ? If yes then Pushing the agent installation from MS may cause such issue. So would suggest you push the installation from RMS.
Also check if your Network connectivity meets the minimum requirement as recommended by SCOM. Below is applicable for Both SCOM 2007 R2 & SCOM 2012 & 2012 R2.
Component A
Component B
Minimum Requirement
Root management server or management server
Agent
64 Kbps
Root management server or management server
Agentless
1024 Kbps
Root management server or management server
Database
256 Kbps
Also check if you have any Anti virus / Firewall which is blocking the install / communication. If yes disabe or add the "Monitoringhost.exe to the safe list or what your feature is.
Check if you have another IP assigned to the NIC card and remove it tempraurly andchecl.
Also post the event logs of the Agents which are in not monitored state for analysis.
SCOM Agent installation failure error codes
Error
Error Code(s)
Remediation Steps
The MOM Server could not execute WMI Query "Select * from Win32_Environment where
NAME='PROCESSOR_ARCHITECTURE'" on computer server.domain.com
Operation: Agent Install
Install account: domain\account
Error Code: 80004005
Error Description: Unspecified error
80004005
1. Check the PATH environment variable. If the PATH statement is very long, due to lots of installed third party software - this can
fail. Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary.
2. The cause
could be corrupted Performance Counters on the target Agent.
To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command
prompt. Press ENTER after each command.
cd
\windows\system32
lodctr /R
Note /R is uppercase.
Windows Server 2003 rebuilds all the counters because it reads all the .ini files in the C:\Windows\inf\009 folder for the English operating system.
How to manually rebuild Performance Counter Library values
http://support.microsoft.com/kb/300956
3. Manual agent install.
The MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access
3. Inspect WMI health and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
The MOM Server failed to open service control manager on computer "servername.domain.com". Access is Denied
Operation: Agent Install
Install account: DomainName\User Account
Error Code: 80070005
Error Description: Access is denied.
80070005
80041002
1. Verify SCOM agent push account is in Local Administrators group on target computer.
2. On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin.
Disable McAfee antivirus during push
The MOM Server failed to open service control manager on computer "servername.domain.com".
Therefore, the MOM Server cannot complete configuration of agent on the computer.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
800706BA
1. Firewall blocking NetBIOS ports
2. DNS resolution issue. Make sure the agent can ping the MS by NetBIOS and FQDN. Make sure the MS can ping the agent by NetBIOS
and FQDN
3. Firewall blocking ICMP
4. RPC services stopped.
The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding
on this computer, please retry the Push Agent operation after some time.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 80072971
Error description: Unknown error 0x80072971
80072971
This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer:
%windir%\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2
When you install or remove a management agent, the Operations Manager 2007 management server copies temporary files to the remote computer. One
of these files is named LockFileTime.txt. This lock file is intended to prevent another management server from performing a management agent installation at the same time as the current installation. If the management agent installation is unsuccessful and
if the management server loses connectivity with the remote computer, the temporary files may not be removed. Therefore, the LockFileTime.txt may remain in the folder on the remote computer. When the management server next tries to perform an agent installation,
the management server detects the lock file. Therefore, the management agent installation is unsuccessful.
http://support.microsoft.com/kb/934760/en-us
The MOM Server detected that the following services on computer "(null);NetLogon" are not running. These services are required for push
agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Remote Computer Name: servername.domain.com Install account: DOMAIN\account
Error Code: C000296E
Error Description: Unknown error 0xC000296E
C000296E
1. Netlogon service is not running. It must be set to auto/started
The MOM Server detected that the following services on computer
"winmgmt;(null)" are not running
C000296E
1. WMI services not running or WMI corrupt
The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer "servername.domain.com". This service is
required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to "Manual" or "Automatic", or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: C0002976
Error Description: Unknown error 0xC0002976
C0002976
1. Windows Installer service is not running or set to disabled – set this to manual or auto and start it.
The Agent Management Operation Agent Install failed for remote computer servername.domain.com.
Install account: DOMAIN\account
Error Code: 80070643
Error Description: Fatal error during installation.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameAgentInstall.LOG
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameMOMAgentMgmt.log" on the Management Server.
80070643
1. Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired.
Call was canceled by the message filter
80010002
Install latest SP and retry. One server that failed did not have Service pack installed
The MOM Server could not find directory \\I.P.\C$\WINDOWS\. Agent will not be installed on computer "name". Please verify the required
share exists.
80070006
1. Manual agent install
Possible locking on registry?
http://www.sysadmintales.com/category/operations-manager/
Try manual install.
Verified share does not exist.
The network path was not found.
80070035
1. Manual agent install
The Agent Management Operation Agent Install failed for remote computer "name". There is not enough space on the disk.
80070070
1. Free space on install disk
The MOM Server failed to perform specified operation on computer "name". The semaphore timeout period has expired.
80070079
NSlookup failed on server. Possible DNS resolution issue.
Try adding dnsname to dnssuffix search list.
The MOM Server could not start the MOMAgentInstaller service on computer "name" in the time.
8007041D
80070102
NSlookup failed on server. Possible DNS resolution issue.
Verify domain is in suffix search list on management servers.
The Agent Management Operation Agent Install failed for remote computer "name"
80070643
1. Ensure automatic updates service is started
2. Rebuild WMI repository
3. DNS resolution issue
The Agent Management Operation Agent Install failed for remote computer "name". Another installation is already in progress.
80070652
Verify not in pending management. If yes, remove and then attempt installation again.
The MOM Server detected that computer "name" has an unsupported operating system or service pack version
80072977
Install latest SP and verify you are installing to Windows system.
Not discovered
Agent machine is not a member of domain
Ping fails
1. Server is down
2. Server is blocked by firewall
3. DNS resolving to wrong IP.
Fail to resolve machine
1. DNS issue
The MOM Server failed to perform specified operation on computer "name". Not enough server storage…
8007046A
1. This is typically a memory error caused by the remote OS that the agent is being installed on.
There are currently no logon servers available to service the logon request.
8007051F
1. Possible DNS issue
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version
of the Windows Installer service.
8007064D
1. Install Windows Installer 3.1
The network address is invalid
800706AB
Possible DNS name resolution issue.
Tried nslookup on server name and did not get response.
Verify domain is in suffix search list on management servers.
The MOM Server failed to perform specified operation on computer servername.domain.com
80070040
1. Ensure agent push account has local admin rights
The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com.
80072979
1. Correct DNS/WINS issue.
2. Try pushing to NetBIOS name
Gautam.75801

SCOM agent install on Unix/Linux

Hi, trying to install agent on RHEL. Here is the case:
- Hosts file added with FQDN name on Linux server
- IPtables off for IPv4 & IPv6(I've a doubt here. Even turned off, do they need exception entry in iptables for both v4 & v6)
- Replying for ping from both SCOM management servers by hostname and IP address.
- nslookup pointing to same IP & server
- DNS resolution ok (both forward & reverse)
- WinRM qc showing WinRM already set to listen.
- Getting discovered while agent install, failing at certificate signing validation - the last step.
- Sudoer file modified perfectly
- Port 1270 is open over network (confirmed by n/w team)
Still receive below error :(
- Agent verification failed.
Error detail: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination,
most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". When verifying winrm, it is already configured to receive requests.
-Thanks, Satya

Certificate does not include the FQDN so it fails. You can do a few things here to fix it.
Run the following on the Linux agent and try discovery again. This will overwrite the old certificate and create a new one with the FQDN.
/opt/microsoft/scx/bin/tools/scxsslconfig -h <Linux hostname> -d <domain name> -f -v
Update the /etc/hosts file on the Linux computer and add the FQDN:
x.x.x.x myLinux.mydomain.com myLinux
or update the /etc/resolv.conf:
domain mydomain.com
If you do either of the last 2 you will want to delete everything under
/etc/opt/microsoft/scx/ssl and then re-run discovery as it will still try to use the old certificate if it exists.
-Steve

Running SCOM Powershell cmdlets on SCOM Agent Server

Hello,
I have to run some SCOM cmdlets on SCOM Agent Server. But I am getting the below error.
"Get-SCOMClass : The Data Access service is either not running or not yet initilized. Check the event log for more information."
In the Agent Server, there is no "Data Access service".
Please help me in running the SCOM cmdlets on SCOM Agent Server.
Thanks in advance.
Regards,
Mahadevan.G

Hi Mahadevan:
On a SCOM management server, the SDK service name is "System Center Data Access Service". If you don't see that service listed then you are not on a SCOM management server.
Not sure what you mean "SCOM Agent Server"? The SCOM cmdlets won't run on a computer with just the SCOM agent installed unless you also install the SCOM console/powershell features from the SCOM install media.
The Get-SCOMClass cmdlet (or Get-SCClass) should run on a management server with no problems. Recommend check again that you are really logged into a SCOM management server.
John Joyner MVP-SC-CDM

SCOM 2012 Agent Deployment query

Hello,
I have tried to deploy the agent remotely to a Windows Storage Server Standard - SP1 server but it failed,
I have checked the compatible OS list and it makes reference to Server 2008 SP2 but not Storage Server.
If I upgrade to SP2 will the agent install on the OS or will it fail anyway.
THanks
Nick

Hello,
I have tried to deploy the agent remotely to a Windows Storage Server Standard - SP1 server but it failed,
I have checked the compatible OS list and it makes reference to Server 2008 SP2 but not Storage Server.
If I upgrade to SP2 will the agent install on the OS or will it fail anyway.
THanks
Nick
I had raised a ticket with Microsoft as this was quite unclear no matter where we looked.
This was their response,
I can confirm SCOM 2012 SP1 agent can be installed on the server “Windows Storage Server Standard –
SP2” as per the below technet link.
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_WindowsAgents
Operating Systems: Windows Server 2003 SP2,
Windows Server 2008 SP2, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows XP Professional x64 Edition SP2, Windows XP Professional SP3, Windows Vista SP2, Windows
7, POSReady, Windows XP Embedded Standard, Windows XP Embedded Enterprise, Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems, Windows 7 Ultimate for Embedded Systems, Windows 8 Pro, Windows 8 Enterprise, Windows 8.1 Pro, or Windows
Embedded 8.1 Industry.
Hope this answers your question. Kindly let me know if you have any queries regarding this case further if not I will proceed with the case closure.

Reporting doesn't show the newly installed SCOM Agents

Hello,
I am running SCOM 2012 SP1 on Win2008 R2.
I recently deployed scom agent to couple of machines the agents are showing up healthy and i can see the performance and health data from Monitoring tab but when i try to run report i can't find these new agents in the objects to add to report.
Report
it doesn't even query the agents.
and on the SCOM manamgent server i see this error in event viewer not sure if it is related.
Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.
Exception 'SqlException': Sql execution failed. Error 2627, Level 14, State 1, Procedure ManagedEntityChange, Line 368, Message: Violation of UNIQUE KEY constraint 'UN_ManagedEntityProperty_ManagedEntityRowIdFromDAteTime'. Cannot insert duplicate key in object
'dbo.ManagedEntityProperty'. The duplicate key value is (528, Aug 25 2013 8:52AM).
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.ManagedEntity
Instance name: 08eb00a2-e227-4472-a368-a6e42a2bc502
Instance ID: {EEFCB078-6517-97CD-FA4F-8FCAB54E4930}
Management group: OPSMGR
Regards,
Maqsood
Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

Ok, so at this point, without enabling logging and going to the extremes, I would attempt an uninstall and reinstall of the agents. One at a time. So remove the agents. Reinstall one, and monitor what is happening on that server, and investagate
it in the ops console.
If you know what applications are on the box, and being discovered, look for the server in discovered inventory for those classes, etc.
Before you do that, you can try to run this against the DW to see if there are any alerts associated with these two servers, that is if they ever raised alerts:
USE OperationsManagerDW
SELECT Alerts.AlertName, SUM(1) AS 'Alert Instances', SUM(Alerts.RepeatCount + 1) AS 'Alert + Repeat Count',
CASE Alerts.MonitorAlertInd WHEN 1 THEN vMonitor.MonitorDefaultName WHEN 0 THEN vRule.RuleDefaultName ELSE 'Not found' END AS 'Rule or Monitor Name',
CASE Alerts.MonitorAlertInd WHEN 1 THEN 'Monitor' WHEN 0 THEN 'Rule' ELSE 'Not Found' END AS 'Rule or Monitor', vManagedEntity.Path,
vManagedEntity.DisplayName
FROM Alert.vAlert AS Alerts INNER JOIN
vManagedEntity ON Alerts.ManagedEntityRowId = vManagedEntity.ManagedEntityRowId LEFT OUTER JOIN
vRule AS vRule ON Alerts.WorkflowRowId = vRule.RuleRowId LEFT OUTER JOIN
vMonitor AS vMonitor ON Alerts.WorkflowRowId = vMonitor.MonitorRowId
WHERE (Alerts.RaisedDateTime BETWEEN DATEADD(day, - 180, GETDATE()) AND GETDATE()) AND
(Alerts.AlertName like '%Hub Servers In Retry Error%') and path like '%servername%'
GROUP BY Alerts.AlertName, Alerts.MonitorAlertInd, vMonitor.MonitorDefaultName, vRule.RuleDefaultName, vManagedEntity.Path, vManagedEntity.DisplayName
ORDER BY 'Alert Instances' DESC
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

SCOM 2012 SP1 Agent install issue

Dear all,
Wheni try to push SCOM client , getting below error. Any idea what would be issue ?
The Operations Manager Server could not execute WMI Query "Select * from Win32_OperatingSystem" on computer XXX.XXX.XXX
Operation: Agent Install
Install account: XXXXXX
Error Code: 800706BA
Error Description: The RPC server is unavailable.

Looks Firewall issue only , i have opened below ports , is there any mandatory ports required for SCOM agent installation ?
443
TCP
445
TCP
135
TCP

Identify where to install SCOM Agent on SCCM Site hierarchy.

Hello..
We have a SCCM Site environment where there is one CAS site, other 5 Primary site servers and one DB server .All are in different machines (7 VMs).i need to monitor complete SCCM site hierarchy.Next on which machines i need to install SCOM Agent on both CAS
and all Primary Site Server.
Thanks
RICHA KM

Hi RICHA,
Hope it helps:
http://blogs.technet.com/b/kevinholman/archive/2012/12/11/monitoring-configmgr-2012-with-opsmgr.aspx
http://blogs.catapultsystems.com/cfuller/archive/2012/01/26/opsmgr-2012-scom-and-configmgr-2012-sccm-q-a.aspx
http://msandbu.wordpress.com/2012/04/23/monitoring-sccm-2012-via-scom-2012/
Natalya

C# SCOM SDK agent install works fine from debug mode but disconnects when built from installer

My team is writing a C# application that installs SCOM agents on the fly. I used the code in :
http://msdn.microsoft.com/en-us/library/hh329037.aspx
as a template. Which works fine and will consistently install agents when I run it in debug from Visual Studio. But when I build an installer (using InstallShield), calls to:
"AgentTaskResult results = adminServer.InstallAgents(agents, configuration);"
always result in a Microsoft.EnterpriseManagement.Common.ServerDisconnectedException. The agent install even shows up in pending management on the SCOM server (but this sits in pending management forever and is never processed). Calling managementGroup.Reconnect();
and retrying the agent install still results in a ServerDisconnectedException. The application has no problem doing other things with the managementGroup object (from debug or running from an installer). It can create MonitorConfigurationOverrides and
gets events out of an outbound connector. So it seems like the disconnect problem is localized just to agent install requests.
I looked in the Windows Event Log and found an OpsMgr SDK Service Error:
An exception was thrown while processing InstallAgents for session ID uuid:71d39b19-f9a7-4d4a-82ee-5043480af635;id=41.
Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 778.
Full Exception: System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 778.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
at System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType)
at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
at System.Xml.XmlTextReaderImpl.ParseText()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlReader.ReadString()
at System.Xml.XmlReader.ReadElementString(String name)
at Microsoft.EnterpriseManagement.RuntimeService.TaskRuntimeService.CreateRemoteJobXml(JobDefinition jobDefinition, ManagementPackTask task, Guid hsId)
at Microsoft.EnterpriseManagement.RuntimeService.TaskRuntimeService.SubmitJobs(IList`1 jobDefinitions, Guid batchId, JobCategory category)
at Microsoft.EnterpriseManagement.RuntimeService.TaskRuntimeService.SubmitTasksInternal(IList`1 jobDefinitions, Guid batchId, JobCategory category, PrepareResultSet prepareTaskResultCallback)
at Microsoft.EnterpriseManagement.ServiceDataLayer.AdministrationService.InstallAgents(Guid batchId, IList`1 jobDefinitions)

Hello,
You might ask in the
Visual C# Language forum on MSDN.
Otherwise, perhaps the Operations Manager - Extensibility forum:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/home?forum=operationsmanagerextensibility
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Power-shell script to install scom agent to multiple servers

Hi
we are trying to upgrade/install scom 2012 r2 agents to our windows servers (300+) server via powershell script.
we are wanting the result to be written to csv file but we are facing difficulty in trying to find the object/value to look at to the put the condition against.
we found the script that does for ping(below part script) result but we want to capture any failure. is there anything we can use to achieve what we ant to do?
Thank you in Advance.
-------------------Sample script--------------------------
# Ping the computer
$pingStatus = Get-WmiObject -Class Win32_PingStatus -Filter "Address = '$computer'";
if($pingStatus.StatusCode -eq 0)
#If computer is up, write message and launch agent install
InstallSCOMAgent $Computer
"Success , $computer." | out-file "D:\output.csv" -Append -NoClobber
#Write-Host -ForegroundColor Green "Reply received from $computer.";
else
#Else, just write a message indicating computer unreachable
"Failed , $computer." | out-file "D:\output.csv" -Append -NoClobber

Just in case Newbie like me wondering how it can be done
Here is the code (of course i got the help) simple but does what i want at this stage. Next I am looking at how I can push the agents in parallel, this script will take fairly long time when trying to push to huge number of servers.
#Import PowerShell Modules
import-module OperationsManager
#Variables
$InstallAccount = Get-Credential domainname\username
$PrimaryMgmtServer = Get-SCOMManagementserver -Name <managementservername>
#Connect to OpsMgr Management Group
Start-OperationsManagerClientShell -ManagementServerName: <managementservername> -PersistConnection: $true -Interactive: $true;
$list = Import-Csv -Path 'D:\temp\serverlist.csv'
foreach ($entry in $list)
$computer = $entry.ServerName
try
Install-SCOMAgent -Name $computer -PrimaryManagementServer $PrimaryMgmtServer -ActionAccount $InstallAccount -ErrorAction Stop
#Write Success message into file
"$computer, Success." | out-file "D:\temp\result.csv" -Append -NoClobber
Catch
#just write a failure message into file
"$computer, Failled." | out-file "D:\temp\result.csv" -Append -NoClobber
--------------------------End---------------------------------------------------------------------------

Installing scom agent shows error on HP unix

Hello ,
i am trying to install the scom agent on HP unix , getting below error , i tried manually also not able to succeed ..can anyone help on this .?
       * Installing fileset "scx.core,r=1.4.1-270" (1 of 1).
       * Beginning the Configure Execution Phase.
mv: /etc/opt/microsoft/scx/conf/cimserver_planned.conf.swsave: cannot access: No such file or directory
mv: /etc/opt/microsoft/scx/conf/cimserver_current.conf.swsave: cannot access: No such file or directory
mv: /etc/opt/microsoft/scx/conf/scxlog.conf.swsave: cannot access: No such file or directory
mv: /etc/opt/microsoft/scx/conf/scxrunas.conf.swsave: cannot access: No such file or directory
Generating certificate with hostname="server1", domainname="server1.abc.in"
Starting Microsoft SCX CIM Server
cimserver not started: SSL Exception: Seed file '/var/opt/microsoft/scx/cimserver.rnd' does not exist.
EXIT CODE: 1
ERROR:   The "configure" script for "scx.core" failed (exit code "1").
         The script location was
         "/var/tmp/BAA023557/catalog/scx/core/configure".
       * This script had errors and the execution of this fileset
         cannot proceed until the problem is fixed. Check the above
         output from the script for further details.

Hi, We did some investigation into this and have determined that this occurs when “RAND_status” (an OpenSSL routine) returns 0, which means that the PRNG on this system does not have enough entropy to perform properly. When this happens, Pegasus will look
for a file in the location specified by the error as a source of entropy to seed the PRNG with. We actually didn't catch that this was the case, sorry about that!
Note that, in OM 2012R2, this was already fixed (since Pegasus is no longer used in that version).
A solution is for you to generate a series of files that contain random bits (on a fast and highly used system, one with high entropy). There should be one file generated per system that is experiencing this problem, for security reasons (i.e. each generated
file should be placed on only one system). Once these files are generated, they should be placed in the location specified in the error: '/var/opt/microsoft/scx/cimserver.rnd'.
Permissions should also be set such that only root can read from this file.
This should allow the agent to start. Note that we're unable to test this because we do not have a system that fails RAND_status, unfortunately. However, if you continue to have problems, please let us know, and we'll look into this further.
In any case, a command that can be used to generate random bits is:
openssl rand 2048 > cimserver.rnd
Where 2048 is the number of bits generated. Let me know how this works out for you, thanks so much, and thanks for your patience.
/Jeff

Need to Automate the installation of SCOM agent through Script on workgroup machine in my Environment

Hi Guys,
Please advise me as i need to install SCOM agent on all workgroup machine automatically and not through Copying certificate and all which is quite hectic process, your help will be Appreciated,
Thanks
Amit Singh

More info:
How to deploying SCOM Agents to the Workgroup clients
http://blogs.technet.com/b/csstwplatform/archive/2012/05/28/how-to-deploying-scom-agents-to-the-workgroup-clients.aspx
Installing SCOM 2012 agent on a non-domain workgroup Windows Server
http://himmetyildiz.blogspot.com/2013/11/installing-scom-2012-agent-on-non.html
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM Agent installation Issue

Dear all,
We have SCOM 2012 r2 , when we install agent through discovery . We got the below error
The Operations Manager Server cannot process the install/uninstall request for computer xxxxx due to failure of operating system version verification.
Operation: Agent Install
Install account: XXXXX
Error Code: 80070035
Error Description: The network path was not found.
Any idea what would be the issue here ?
Gone through some forum , but no luck
http://www.scapaot.de/blog/?p=291
Thanks,
74KMS

Hi
Kevin Holman has a great blog on troubleshooting agent install issues here:
http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
The error you state has "Manual Agent Install" as the "fix".
Could you confirm:
1. The agent is in the same domain as the SCOM Management Server?
2. Can you do an NSLookup from the Management Server to the agent FQDN?
3. If you try and install the agent manually, do you get an error or does it complete?
Cheers
Graham

SCOM Agent install \ deployment query?

Similar Messages

Maybe you are looking for