| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 07/22/2005 3:56 PM |
|
| We implemented asset management, software delivery, and remote control back in April, but we still don't have some machines showing in the UAM Admin console. There are almost 1400 machines in software delivery but only half are reporting to asset management, they show an asset management agent in their installation history, but they aren't listed in the asset management console. I've tried to do a run agent activation job on some of the installations in software delivery with no luck. What else can I do? |
|
|
|
SuperUser
Posts:26
|
| 07/23/2005 9:46 PM |
|
You may have 1 of the 3 issues I am having. First, what OS are these machines? If it is unix you need to create a sector server just for them (I'll explain later), If the OS is Windows XP SP2, you may have internal firewall settings to contend with.
Second, if you delivered the AMO agent with SDO then it may not have been configured to send updates regularly, at least that is what CA told me... I will copy the info they had me try:
Issue #1: AMO Agents have been deployed to 80% of our environment using software delivery. In some instances the asset is NOT visible in Asset Management. It shows up in software delivery and shows that it has been installed with the AMO agent. Logging onto the asset, it is possible to run the agent but it never shows up in Asset Management.
Resolution #1: Checked the console found that the all sectors are configured to use "Auto online sector". Unix and other Non Windows assets require a "sector server controlled" sector. A new server was brought online and configured as a "sector server controlled" sector. The AMO agent was redeployed and pointed to the newly installed sector server box. The Asset was visible in 3 hours.
Issue #2: In some instances when the asset shows up in Asset Management it has a name like WS-1, WS-2, WS-3, etc... This name is not on the desktop computer anywhere nor is it in DNS. Where is AMO picking up this Name? How do we correct it?
Resolution #2: Login to the Asset. In the AGENTS directory / ncc31com.ini and edit the following to yes:
DefaultOSLogOn=Yes
DefaultOSLogOnYes/No, Default is Yes
If yes is selected, and the network drivers are properly installed, the Agent will use the user name for the user part, and the Computer Name for the workstation part.
Issue #3: The agents appear to have updated once the agent was installed and have not shown any run activity since.. What would be the best way to force the agents to do a scan and update at least once per week?
Resolution #3: Login to the Asset. In the AGENTS directory, edit the umcstub.ini file. The parameter Interval in umcstub.ini defines the interval between each scan and period defines the time frame in which it has to run and machine must be turned on for this to work through out the week.
Ex: If you define interval = 1440 and period = 0700 - 0800, the agent scan will be performed between 7am and 8am everyday provided the machines are not turned off.
To scann at least once a week then you need to add the following settings in umcstub.ini
Period = 10080
Allowedtimeinterval=0000-2400
I made these changes Friday, and hopefully will see results by Monday.. Let me know if any of this helped... |
|
|
|
SuperUser
Posts:26
|
| 07/24/2005 1:21 AM |
|
You might try to troubleshoot first.
I have experience only with PC based platforms and for troubleshooting it you need to start the agent with debug option.
default path is :
c:\program files\ca\unicenter assset management\agents\umcliwnt.exe /DEBUG
it trigers agent to run in debug mode where you can see results. |
|
|
|
|