With New-WindowsDiscoveryConfiguration it's possible to specify credentials
by the -ActionAccountCredential parameter, but there's no such parameter for
install-agent.
This causes the following error:
The MOM Server failed to open service control manager on computer
dc2.tad.loc. Therefore, the MOM 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.
Anyone has a workaround to do a scripted install of agents with the
non-default action account ?
I'm not a specialist of powershell but maybe something like this shoud
work with good parameters ?:
$discoveryconf = New-WindowsDiscoveryConfiguration + parameters
$discovery = Start-Discovery <MS> -Windowsdiscoveryconfiguration
$discoveryconf
Install-Agent -ManagementServer <MS> -AgentManagedComputer
$discovery.CustomMonitoringObjects
"François Dufour [Exakis]" wrote:
As far as I know I used the correct parameters. You can add credentials to
New-WindowsDiscoveryConfiguration cmdlet for discovering hosts. This works
fine, but those credentials aren't used with install-agent (and not possible
to specify)
Install-Agent does not let you specify action acount credentials. You need
to define those credentials when callin New-WindowsDiscoveryConfiguration
cmdlet. And provide result of discovery to Install-Agent cmdlet.
Following is a link to a sample on how to discover and install agent
computers.
http://blogs.msdn.com/scshell/archive/2007/02/09/discovering-windows-computers.aspx
Thanks
--
Ercan Turkarslan [MSFT]
Ercan.Tu...@at.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wim-ms" <Wi...@discussions.microsoft.com> wrote in message
news:6775A692-F398-46CD...@microsoft.com...
I tried it, doesn't work, install-agent doesn't seem to use those
credentials I supply to New-WindowsDiscoveryConfiguration
So i did some digging, really alot of the stuff you will fool around with in SCOM needs you to understand classes and objects.
The class you are trying to deal with is the "InstallAgentConfiguration Class" Notes on it can be found here:
http://msdn.microsoft.com/en-us/library/microsoft.enterprisemanagement.administration.installagentconfiguration_members.aspx
Also to instantiate this object you would want to do the following.. Instantiating an object just makes it available for use in your code.
$InstallAgentConfiguration = New-Object Microsoft.EnterpriseManagement.Administration.InstallAgentConfiguration
From there you can do the following..
$InstallAgentConfiguration.<put method or property here>
Example:
$InstallAgentConfiguration.InstallPath = "D:\Program Files\System Center Operations Manager 2007"
The above code just makes it so your install directory is changed from the default and is now pointing to D for every agent you install via script.
There are a few methods in that class that may be of some use to you :)
Wimm wrote:
Hi,I tried it, doesn't work, install-agent doesn't seem to use those
08-Apr-08
Hi,
I tried it, does not work, install-agent does not seem to use those
credentials I supply to New-WindowsDiscoveryConfiguration
"Ercan Turkarslan [MSFT]" wrote:
Previous Posts In This Thread:
On Thursday, January 17, 2008 12:02 PM
Wim-m wrote:
install-agent with credentials
I'm trying to use install-agent but it seems there is no way to specify
credentials for the actionaccount ?
With New-WindowsDiscoveryConfiguration it's possible to specify credentials
by the -ActionAccountCredential parameter, but there's no such parameter for
install-agent.
This causes the following error:
The MOM Server failed to open service control manager on computer
dc2.tad.loc. Therefore, the MOM 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.
Anyone has a workaround to do a scripted install of agents with the
non-default action account ?
On Friday, January 18, 2008 3:20 PM
Wimm wrote:
Re: install-agent with credentials
"Fran??ois Dufour [Exakis]" wrote:
As far as I know I used the correct parameters. You can add credentials to
New-WindowsDiscoveryConfiguration cmdlet for discovering hosts. This works
fine, but those credentials aren't used with install-agent (and not possible
to specify)
On Saturday, January 19, 2008 8:27 PM
=?ISO-8859-1?Q?Fran=E7ois_Dufour_[Exakis]?= wrote:
Re: install-agent with credentials
On 17 jan, 18:02, Wim-ms <Wim...@discussions.microsoft.com> wrote:
s
or
ent
I'm not a specialist of powershell but maybe something like this shoud
work with good parameters ?:
$discoveryconf =3D New-WindowsDiscoveryConfiguration + parameters
$discovery =3D Start-Discovery <MS> -Windowsdiscoveryconfiguration
$discoveryconf
Install-Agent -ManagementServer <MS> -AgentManagedComputer
$discovery.CustomMonitoringObjects
On Wednesday, March 12, 2008 4:12 PM
Ercan Turkarslan [MSFT] wrote:
Hi,Install-Agent does not let you specify action acount credentials.
Hi,
Install-Agent does not let you specify action acount credentials. You need
to define those credentials when callin New-WindowsDiscoveryConfiguration
cmdlet. And provide result of discovery to Install-Agent cmdlet.
Following is a link to a sample on how to discover and install agent
computers.
http://blogs.msdn.com/scshell/archive/2007/02/09/discovering-windows-computers.aspx
Thanks
--
Ercan Turkarslan [MSFT]
Ercan.Tu...@at.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wim-ms" <Wi...@discussions.microsoft.com> wrote in message
news:6775A692-F398-46CD...@microsoft.com...
On Tuesday, April 08, 2008 8:14 AM
Wimm wrote:
Hi,I tried it, doesn't work, install-agent doesn't seem to use those
Hi,
I tried it, does not work, install-agent does not seem to use those
credentials I supply to New-WindowsDiscoveryConfiguration
"Ercan Turkarslan [MSFT]" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Reflection Effect
http://www.eggheadcafe.com/tutorials/aspnet/8cc84aa8-3b44-4037-beab-49bd76e20b9b/wpf-reflection-effect.aspx