Client Installation problems at one site (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003



Message

kangwnl -> Client Installation problems at one site (6/8/2008 6:33:51 PM)

We have a Primary SMS Server with a number of Secondary Servers at different sites. I am having trouble with the client installation at one specific site (which has an SMS secondary Server) and it is driving me a little crazy. Any resolution suggestions would be welcomed.

When I install the SMS client on computers at the site e.g. using the console, highlight the computer and select All Tasks -> Install Client, the SMS client seems to install OK. When I look at Systems Management in Control Panel on the workstation, everything looks fine and the logs on the workstation look OK. However, in the Admin console on the primary SMS Server, it says that the client is not installed. I have installed the console extension “SMS Tools” and when I run a task such as “Policy Evaluation and Update (Machine)” it displays the error “No Advanced Client Found”

I have temporarily turned off the Windows Firewall and the same things happen. There are no errors under System Status > Site Status

Kanga



kangwnl -> RE: Client Installation problems at one site (Secondary Server Issue) (6/10/2008 11:24:46 PM)

The source of my problems seems to stem from the fact that the Secondary site server is not sending any information back to the Primary Server. When I run a query "All Status Messages from a Specfic System" and specify the Secondary site server then NO messages are returned. If I run the same query for other secondary Servers then a get a lot of messages listed.

There is good WAN communication between the sites and no Firewall installed.

The Secondary Server computer object is a member of SMS_SiteSystemToSiteServerConnection, SMS_SiteSystemToSQLConnection and SMS_SiteToSiteConnection groups on the Primary Server.

Where could I look for some clues on what is going wrong?



bmason505 -> RE: Client Installation problems at one site (Secondary Server Issue) (6/10/2008 11:36:51 PM)

Does that secondary have an MP?  Also, what about permissions to the despoolr.box on the primary.  Whatever group that is that has permissions (like site to site), is the secondary in it?



jnelson993 -> RE: Client Installation problems at one site (Secondary Server Issue) (6/10/2008 11:41:41 PM)

Do you have sender addresses set up on parent to child and on child to parent?

Also, just because messages aren't being replicated up doesn't necessarily mean NOTHING's getting replicated.  If you have the REPLICATE ALL SMS CLIENT MESSAGES AT LOW/MEDIUM PRIORITY status filter rule disabled then the status messages won't trickle up,
SITE SETTINGS
  - STATUS FILTER RULES
     - REPLICATE ALL SMS CLIENT MESSAGES AT LOW PRIORITY
     - REPLICATE ALL SMS CLIENT MESSAGES AT MEDIUM PRIORITY

Or if you have REPLICATE TO PARENT SITE unchecked in any of the status summarizers, the status summaries won't trickle up.
SITE SETTINGS
  - STATUS SUMMARIZERS
     - <pick your> STATUS SUMMARIZER
        GENERAL TAB - REPLICATE TO PARENT SITE

Then you can just check the inboxes.  If you don't have a script or MOM/SCOM monitor watching over the inboxes, I like to run DiskDetective or something that will enumerate all of the files/folders and show you what's taking up the most space.  If you have a backlog then perhaps a component or service isn't running or something's clogged.

http://www.disktective.com/

And there's always the SMS logs   ?:\SMS\Logs\



kangwnl -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 1:27:37 AM)

Thanks for the feedback.

To Brian - The secondary is configured under Site Systems > Site Settings as a MP (Use this site system as a management point " is ticked. The SMS_SiteSystemToSiteServerConnection_XXX group on the Primary has rights to the despoolr.box and the site server is in that group.



bmason505 -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 1:39:28 AM)

OK, do you see only site to server or do you also see site to site on the despoolr.box\receive folder?  Can you compare with another working site?



kangwnl -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 2:55:20 AM)

To John – Thanks for the feedback also.

I have a standard sender configured at the parent and child sites. The “rogue” site is configured the same as the other child sites which are working Ok.

The Status Filter rules are set to enabled for low and medium priority messages
The Summarizers are all configured to replicate to parent site

I looked at the inboxes. One area where there is a big build-up is the schedule.box on the Secondary Server. There are 600 files with a SRQ extension in \SMS\Inboxes\schedule.box\requests and also a large number of files with various extensions in \SMS\Inboxes\schedule.box\tosend

I had searched through the logs but didn’t find anything significant errors or warnings. However, after seeing the build-up in the schedule.box I looked at sched.log on the Secondary Server.

I get messages like the following:

There is a direct address to site ADL, no need for routing to send request 3058RSYD.

Later in the log there is:

Scheduling send request 3058RSYD
No addresses available for site ADL
No backup addresses available for site ADL



kangwnl -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 3:12:44 AM)

Brian - The rights to the despoolr.box\receive folder are the setup the same for the rogue secondary site as for the woirking secondary sites. SMS_SiteToSiteConnection_XXX has full rights to despoolr.box\receive.



jnelson993 -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 3:20:42 AM)

quote:


There is a direct address to site ADL, no need for routing to send request 3058RSYD.

Later in the log there is:

Scheduling send request 3058RSYD
No addresses available for site ADL
No backup addresses available for site ADL


Well, that could be a problem...so perhaps try removing the sender address and recreating it on the secondary?  It's a standard sender address, not courier, right?



bmason505 -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 11:23:22 AM)

Wow #2, old SMS 2.0 tricks!  I remember having to do that.  Then again, I remember having to reinstall a secondary just about every day.  Long live Nomad.



jnelson993 -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 2:01:13 PM)

Yeah, this was supposed to be fixed in SMS 2.0 SP4 :)



kangwnl -> RE: Client Installation problems at one site (Secondary Server Issue) (6/11/2008 5:00:01 PM)

Success!!!!! After I deleted the Standard Sender and recreated it, messages started to flow from the Secondary to the Primary. Thanks for all the help.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.234375