Re: Advanced client installed on the client, but not displaying as such on the Admin Console?
- From: "DW" <imnottellin@xxxxxxxx>
- Date: Fri, 20 Apr 2007 02:15:18 -0400
Thank you greatly for the reply. I checked the heartbeat discovery, and it
was set at 6 hours. I changed it to two weeks. The two tasks you
referenced were not enabled, but both were set to run on data over 90 days
old, and our SMS site is about (at most 50 days old). I'm wondering if the
Heartbeat Discovery interveral being set so short may have had anything to
do with it... I guess I'll see in the morning!
Thank you again for the help,
~Dave
<sherrylkissinger@xxxxxxxxx> wrote in message
news:1177046153.847701.76530@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Apr 19, 2:34 pm, "DW" <nob...@xxxxxxxxxxx> wrote:
Greetings all,
I have a new SMS 2003 SP2 site (previous 2.0 site was removed, clients
ran
the 2.0 client clean utility). The site sits on the same box as the SQL
server. I've opened up all the requisite ports per KB article 826852,
and I
have the following problem: I have about 14 of 100 machines on which the
client components appear to install (the various icons show up in the
Control Panel and the components below show installed/enabled):
CCM Framework - Installed
CCM Policy Agent - Installed
CCM Status and Eventing Agent - Installed
SMS Client Core Components - Installed
SMS Client Shared Components - Installed
SMS inventory Agent - Enabled
SMS Remote Tools Agent - Enabled
SMS Software Distribution Agent - Enabled
SMS Software Metering Agent - Enabled
SMS Software Update Agent - Installed
SMS Source List Update Agent - Enabled
The site code is appropriately identified, and from the Admin Console, I
can
use the remote tools, but the console still refuses to show these
machines
as *clients*. I've manually initiated data collection and inventory
cycles
to try to force a refresh (not that I know if it would work...) to no
avail.
the Client_Config_Manager log isn't giving me any errors, and I have
repeatedly updated the collection membership.
As a frustrated troubleshooting attempt, I deleted one of the troubled
machines from the "All Systems" collection, ran an ASAP AD System
Discovery,
updated the collection membership, and refreshed the display. Now I have
two instances of that system in "All Systems"- one listing the client
installed, one without...
Now, I've been here before. Within 4 hours (now), the machine entry
/with/
the client showing 'installed' has disappeared.
Seriously- What. The. Hell.... I'm completely frustrated and ready to
light
the server on fire- can anyone help? I thank in advance all the gracious
people that volunteer their time and expertise here!
~Dave
I'm by no means sure of this... but check some things: what is your
Heartbeat Discovery interval, and check (and this is where I'm not
sure) under Site Maintenance, Tasks, either delete inactive client
discovery data, or the delete obsolete client discovery data. I think
if you have one of those tasks set too short, it'll evaluate the
client as obsolete, and delete it(?) Sorry I'm vague here...
.
- Follow-Ups:
- References:
- Prev by Date: Re: Advanced client installed on the client, but not displaying as such on the Admin Console?
- Next by Date: How to pass custom properties to a SMS install
- Previous by thread: Re: Advanced client installed on the client, but not displaying as such on the Admin Console?
- Next by thread: Re: Advanced client installed on the client, but not displaying as such on the Admin Console?
- Index(es):
Relevant Pages
|
Loading
