Client discovered but not installed
- From: "telekom.yu@xxxxxxxxxxxxxx" <telekom.yu@xxxxxxxxxxxxxx>
- Date: Mon, 4 Jul 2005 08:49:01 -0700
I have SMS 2003 sp1 in Windows 2003 domain with AD.
I have one Primary Site server:
- Siemens primergy
- Pentium III Xeon 700 MHz
- 512 MB RAM
- HD1 17GB c:\System 5GB e:\SQL 12GB
- HD2 35GB d:\SMS 35GB
- Mylex Raid Controller
- LAN 100 Mb
I have Hardware and Software inventory, and Advertised program agents enabled.
I have 5215 discovered resources and 646 installed clients.
My network is segmented with VLANS.
My problem is that on some of my subnets (10.4.80.0, 10.10.208.0 etc.) I
have 341 discovered computers and SMS client installed on only 41 one of
them. All of that subnets are in the same building. Some of my SMS clients
need more than a day to show up as clients in collections. When I checked the
application log on one of them I found out this:
-27.6.2005 8:34
Source: MsiInstaller
ID: 11707
Product: SMS Advanced Client -- Installation operation completed successfully
-27.6.2005 12:54
Source: MsiInstaller
ID: 11729
Product: SMS Advanced Client -- Configuration failed.
-27.6.2005 12:55
Source: MsiInstaller
ID: 11728
Product: SMS Advanced Client -- Configuration completed successfully
Why would SMS client installation need more than 4 hours to complete? And
why did the configuration failed first time? Is it possible that my hardware
is not good enough for this number of clients? I plan to add 4 more much
stronger servers in a month, but for now I would like to add 900 clients on
this one that I have.
I will try some performance monitors tomorrow on my server.
--
System Administrator
Telecom Serbia
.
- Follow-Ups:
- RE: Client discovered but not installed
- From: "Lee Li[MSFT]"
- RE: Client discovered but not installed
- Prev by Date: Re: uninstall a patch
- Next by Date: Dynamic Collections and System Performance
- Previous by thread: Raising Alarms with SMS
- Next by thread: RE: Client discovered but not installed
- Index(es):
Relevant Pages
|
