Adv Clietn install probs 1

[mrmovie]

Upgrading from SMS2.0 client to Adv Client using the following command line

iReturn = objShell.Run("\\" & arrcfg(4) & "\SMSClient\i386\ccmsetup.exe /retry:5 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=2000000 CCMLOGMAXHISTORY=2 SMSSITECODE=" & arrCfg(3) & " SMSCACHESIZE=" & sCacheSize & " SMSCACHEFLAGS=MAXDRIVE;COMPRESS SMSCACHEDIR=" & Chr(34) & "SMSCACHE" & Chr(34), 1, True)

arrCfg and sCacheSize are correct, can see this from ccmsetup.log and client.msi.log

on about 25% of clients the client does not end up with a Site assigned and the Cache info is greyed out.
the only actions available are Machine Retrival and User Retrev. The components list is full of the right stuff with no errors.
I can find no errors in log files with ref to assigning to site.
The ClientLocation.log shows a couple of entries saying there is no site assigned.
i have manually and through script discovered the site and then assigned it and the client updates and doesnt complain. however the client doesnt actually seem to do anything and the SMS servers still dont show the client.
I have tried to re-install the client but it just ends up in the same state.
Site boundaries are defo ok, cant see any errors at all.
Is there anything else i can check? anything else i can kick off to get the client to register itself? or perhaps some log on the server???
thanks,
richard

 

[tbrennans]

I would guess that if 25% are not getting assigned it would indicate a boundary issue. Are the the clients not getting assignments not in the same subnet? Are they xp? nt?

Computers that are not running Windows XP or operating systems in the Windows 2000 and Windows Server 2003 families cannot belong to Active Directory sites. Those computers cannot be assigned to SMS sites based on membership in Active Directory sites. They can be assigned based only on IP address.

so if they are legacy clients and they are not in a boundary you can force them into one:

by using the Forced Sites tool (Site4c.exe). For information about using this tool, run the Forced Sites tool with the /? switch. The Forced Sites tool is available for download with the SMS 2.0 Support Tools at

http://go.microsoft.com/smserver/downloads/20/default.asp.

more info!!

 

[mrmovie]

all machines are either XP or W2k fully SP'd up (sp1 and sp4 resp)
i dont think it is a site boundary issue as i have a machine right next to mine in the same subnet with the problem

 

[tbrennans]

hmmm if you go to the control panel sys man icon and tell it to discover the site does it do it?

 

[tbrennans]

Check these logs if you'd be so kind

LocationServices.log
ClientLocation.log

 

[mrmovie]

dont have a locationservice.log, the only entry in the clientlocation.log says that there isnt a site assigned.

i think i am getting closer, the eventlog on 3 machines are identical.

lots of DCOM evtid 10002 access denies and

The SMS Agent Host service terminated unexpectedly. It has done this 167 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

events!! great. might log a call with MS

 

[tbrennans]

You cannot install the Systems Management Server 2003 Advanced Client on a computer that has Internet Information Services installed

Only thing I know of that causes that error

http://support.microsoft.com/?kbid=884870

 

[tbrennans]

For what its worth......

/mp: Ccmsetup.exe /mp:[server] SMSSITECODE=[KEYWORD]
Provides a management point as an installation source. This source is added to the source list as \\[server]\SMSclient\i386. You can specify this switch multiple times to provide more than one management point.

/service Ccmsetup.exe /service SMSSITECODE=[KEYWORD]
Forces Ccmsetup.exe to run in the local system account context. The Client.msi file download and the client installation are both performed in the local system context. Use this option only when you are using Active Directory and the client computer account has access to the SMSClient\i386 shared folder on the management point. If the user does not have administrative credentials, the operation will fail. ********


/source: Ccmsetup.exe /source:[folder] SMSSITECODE=[KEYWORD]
Provides a local or remote location where Ccmsetup.exe locates Client.msi and any language-specific files or folders, such as Client.mst. You can specify this switch multiple times to provide more than one possible installation source.


/useronly Ccmsetup.exe /useronly SMSSITECODE=[KEYWORD]
Forces Ccmsetup.exe to run in the logged-on user's security context. Be careful when using this option. If the user does not have administrative credentials, the operation will fail.


Dont know what else to tell ya,

 

[mrmovie]

thank you tbrennans for your efforts. i will post something back once we have found the issue!