The CO version needs to match the agent afaik. you should not need to distribute this particular CO though. have you tried running a USP job against the target ?
We have created new Distribute Configuration Objects job by selecting New > Administration Task > Distribute Configuration Objects.
And applied the Hardware information V6 to the target agents 184.108.40.2062 and 220.127.116.111
Please help me I want Hardware Information in my all managed servers as like below.
Thanks in Advance.
Thanks and Regards,
Jeyaprakash Rajan | Enterprise Tools & Automation
SEZ - DLF Technology Park 6th Floor 1/124 Mount Poonamalle Road Manapakkam Chennai 600089 | India
VOIP: +44 20 700 36118 | Mobile: +91 87544 63680
image002.png 65.7 K
can you try this:
-decomission the target
-run a Update Server Properties Job against it
- see if all the COs show up.
Not worked out.. ☹
You must ensure that the Connection object instance for the vCenter host and the Virtualization object instance of the vCenter host are permissioned using the client’s ACL template (like you would permission a server).
Jayendra - what jeyaprakash is doing has nothing to do w/ the vcenter object or vmware at all.
what options did you run the USP with? did you specify the 'update configuration objects registration' option?
we may or may not be able to pull that. if you go on the target you can run the NSH/nativetool/bin/mcsysinfo and see if the serial number shows up in there. if not, then the sysinfo tool may not be able to pull this info. you could open a ticket w/ bmc support about that.