Hi,

I have here a network with 6 computers in a domain. On the domain controller
I have installed the MS SQL Server and the SMS 2003. After I set all the
stuff I can see the computers (discovering method worked). However for all
my computers (in Collections->All Systems) the "Site code" is empty and for
some computers the "Assigned" is "No" for some computers is "Yes".

On the Domain controller computer (the one that runs the SQL server and SMS
2003) I installed manually the Advanced client (using client.msi). I see the
client in Control Panel, and all seems to be OK (in Components tab it says
all components are installed and in Advanced tab if I click "Discover" it
says "Automatic site code discovery was successful". In the currently
assigned to site ecode I have my site code (the one and only one site code).

However in management console in SMS I cannot see my client. The "Client" is
set to "No" all the time and of course Hardware + Software Inventory are not
working. If I do Install Client form "All Tasks" from context menu nothing
happens. I go thru all dialogs but a client is not installed.

I have set the site boundaries to something like IP subnet 192.168.1.0, but
no client is visible in SMS Management Console.

Any ideas?

--------------------------------------------------------------------------
Dorel Sturm
Germany

Hi Dorel,

why don't you use the german sms newsgroup (microsoft.public.de.sms) ? ;-)

- assigned: "yes / no" depends on the site boundaries of your sms site and
the subnet/ad site your clients are in
- did you refresh the collection(s)? Right klick, all tasks, update
collection membership, then refresh. This happens only once every 24h by
default; you'll see the changes only after the collection is refreshed
- check ccm.log on the site server if the server was able to push the
client(s)

Regards,
Torsten (Germany)


"Dorel Sturm" schrieb:
[..]

Hi Torsten,

After I changed the sms site boundaries I got now for all computers the
status Assigend = YES for all computers.

The problem I still have is the client: the status is still set to "No" for
all computers, and the "Site Code" is empty!

For "All Systems" collection I changed in the properties dialog in
"Membership Rules" TAB the update to occur every minute (and not once in 24
hours). After I do a refresh I see the changes. However still no client!

In the ccm.log I have something like this (after I did Install Client in All
Tasks context menu):

================================================== ===========================================
======>Begin Processing request: "RBSQRWFP", machine name: "MULTI-OS"
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.802 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Trying each entry in the SMS Client Remote Installation account list~
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.802 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Attempting to connect to administrative share '\\MULTI-OS\admin$' using
account 'pps-testdomain\Administrator'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu
Sep 15 10:02:09.802 2005 W. Europe Daylight Time><thread=1616 (0x650)>
---> WNetGetProviderName for LANMAN returned Microsoft Windows Network~
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.802 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Failed to connect to \\MULTI-OS\admin$ using account
pps-testdomain\Administrator (1219) $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep
15 10:02:09.802 2005 W. Europe Daylight Time><thread=1616 (0x650)>
---> Attempting to connect to administrative share '\\MULTI-OS\admin$' using
account 'pps-testdomain\SMSService'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep
15 10:02:09.802 2005 W. Europe Daylight Time><thread=1616 (0x650)>
---> Connected to administrative share on machine MULTI-OS using account
'pps-testdomain\SMSService'~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15
10:02:09.802 2005 W. Europe Daylight Time><thread=1616 (0x650)>
---> Attempting to make IPC connection to share <\\MULTI-OS\IPC$> ~
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.802 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> System OS version string "5.2" converted to 5.20
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Could not retrieve the heartbeat time from the client (2)~
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Unable to retrieve a sites list from machine "MULTI-OS".
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Unable to retrieve travel mode switch from machine "MULTI-OS".
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Unable to retrieve pending command value for sms client base components
from machine "MULTI-OS". $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15
10:02:09.818 2005 W. Europe Daylight Time><thread=1616 (0x650)>
---> Could not retrieve the site config timestamp from the client (2)~
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Client type to be installed on MULTI-OS: Advanced client
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
Advanced client version detected on target machine MULTI-OS
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Mobile client on the target machine has the same version, and 'forced'
flag is turned on.~ $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818
2005 W. Europe Daylight Time><thread=1616 (0x650)>
---> Copying client files to \\MULTI-OS\admin$\system32\ccmsetup.~
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Copying file "C:\SMS\bin\I386\MobileClient.tcf" to
"\\MULTI-OS\admin$\system32\ccmsetup\MobileClient.tcf"
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Created service "ccmsetup" on machine "MULTI-OS".
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:10.130 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Started service "ccmsetup" on machine "MULTI-OS".
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:10.193 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
---> Completed request "RBSQRWFP", machine name "MULTI-OS".
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:10.208 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
Deleted request "RBSQRWFP", machine name "MULTI-OS"
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:10.208 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
<======End request: "RBSQRWFP", machine name: "MULTI-OS".
$$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:10.208 2005 W. Europe
Daylight Time><thread=1616 (0x650)>
================================================== ================================================== =====

As I see here the already installed client was detected and updated. However
no client (and no Hardware Inventory) in SMS Management Console!

Any ideas?


Another question: how do I uninstall (manually) the SMS client? There is no
entry in Add/Remove Programs for it.

Thanks for your support.

Dorel Sturm
(Germany, but not a good german speaker :-) )

"Torsten [MVP]" <torsten.meringer> wrote in message
news:e073
[..]

In article <dgba5a$i7f$1>, dodo
says...
[..]
> ---> System OS version string "5.2" converted to 5.20
> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
> Daylight Time><thread=1616 (0x650)>
> ---> Could not retrieve the heartbeat time from the client (2)~
> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
> Daylight Time><thread=1616 (0x650)>
> ---> Unable to retrieve a sites list from machine "MULTI-OS".
> $$<SMS_CLIENT_CONFIG_MANAGER><Thu Sep 15 10:02:09.818 2005 W. Europe
> Daylight Time><thread=1616 (0x650)>
> ---> Unable to retrieve travel mode switch from machine "MULTI-OS".
Do you see any errors in ccmsetup.log on the client?

Uninstalling the client manually can be done use msiexec /x client.msi
or by using ccmclean from the sms 2003 toolkit.
http://www.microsoft.com/smserver/do...3/default.mspx

Dorel

I experience the same problem; I put in the client push installation my site
code and force reinstall of the entire client.

It seems like a DNS problem or something that prevent the active directory
publishing the site code to the clients.




Ilan

Hi,

I found somewhere on the Internet that SMS 2003 requires Internet
Information Server on the same computer. Is this true?
I don't have IIS on the computer that runs the SMS server and this may be
the problem why the clients are not recognized.

Dorel


"Elan Chekroun PO" <elan_chk> wrote in message
news:4037
[..]

Dorel

You don’t need iis on the workstations !!!
All you need is to configure your client push installesion with your site
code.

"SMSSITECODE=XXX"

Try it now…

Hi Dorel,

not having IIS on the Management Point is the key! The MP requires IIS.
Check out the "mp troubleshooter" from the "SMS 2003 Toolkit 2". This tools
checks
the prerequisites for installing or running a MP. Additionally have a look
at this doc
http://www.microsoft.com/technet/pro...t/default.mspx

Regards,
Torsten

"Dorel Sturm" schrieb:
[..]

Hi,

I found the problem: it was the IIS and the Background Inteligent Transfer
Service (BITS) not being installed. After installing them the stuff seems to
work.

I found this errors (e.g. not having BITS installed) somewhere deep in the
management console. It would be nice is SMS tells you at install time that
this and that are missing and in may not work correctly.

Is that common for SMS that after installing (apparently without problems)
you have to search for errors because something may went wrong?

Thanks for your support.

Dorel

"Torsten [MVP]" <torsten.meringer> wrote in message
news:1e39
[..]

Sms does a pretty good job of verifying prerequisites. Unfortunately the
iis prerequisites are for site systems that you add afterwards, and we
want those installations to be silent, because they don't happen
necessarily immediately, and they usually don't happen from the console
where we enable them. So it is kind off difficult to make this an in
your face dialog box that you missed a required component.

The status message system in sms (under system status) is your best
location to check for issues.

Furthermore sms doesn't install a mp by default during setup (otherwise
we could analyze the iis req then) because we can't be sure that you
need an mp in every single site (you could have sites that don't have
advanced clients assigned or roaming to it.)

Kim Oppalfens
MVP SMS
In article <dgedjf$4ht$1>, dodo
says...
[..]