Re: Client push works but doesn't...
From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 03/15/04
- Next message: Micke B: "Re: SMS 2003 and Secondary Sites"
- Previous message: Andrew Meikle: "Re: Extending the Schema for SMS 2003"
- In reply to: Jørn Jørgensen: "Re: Client push works but doesn't..."
- Next in thread: Jørn Jørgensen: "Re: Client push works but doesn't..."
- Reply: Jørn Jørgensen: "Re: Client push works but doesn't..."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 14:02:29 -0800
Are you in an AD environment? If so have you extended the schema for SMS?
This will allow you clients to search AD for the Site and MP that they
belong to.
--
Thanks
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jørn Jørgensen" <jorn@hotmail.com> wrote in message
news:%23VeIQXrCEHA.2556@TK2MSFTNGP12.phx.gbl...
> Hi again!
>
> After reassigning all resources to the primary site I can now make all
> machines at the secondary site connect to SMS by manually entering the
site
> code in Control Panel -> Systems Management on each machine.
>
> Thanks a lot for your patience and advice!
>
> However, I still cannot get SMS to assign a site code automatically, I
need
> to enter the site code manually. Any idea what this might be caused by?
> Trying to discover the site from the client fails with "Automatic site
> discovery failed". Am I right in assuming that the same discovery
mechanism
> is used here as is used for assigning the correct site code within SMS?
>
> Again, thanks for all your help!
>
> Regards,
> Jørn
>
> "Mark Scott [MSFT]" <marksc@online.microsoft.com> wrote in message
> news:#CLihmqCEHA.2888@TK2MSFTNGP09.phx.gbl...
> > Jørn,
> >
> > Advanced clients cannot be assigned to a secondary site. They must be
> > assigned to a primary site. If you have assigned them to a secondary
> site,
> > then they are orphans. That said, you can have advanced clients within
> the
> > boundaries of your secondary and they can get policy and all that, but
> they
> > must be assigned to your primary. I'd recommend reading Chapter 4,
Client
> > Deployment of the Concepts, Planning and Deployment Guide located on
your
> > SMS 2003 cd.
> >
> > "Jørn Jørgensen" <jorn@hotmail.com> wrote in message
> > news:OIZpaORCEHA.240@tk2msftngp13.phx.gbl...
> > > Hi again,
> > >
> > > An update:
> > > * I have managed to have the secondary site communicate with the
client
> > > running on the secondary site SMS server (to communicate with 'itself'
> > that
> > > is).
> > > * I cannot for the life of me get SMS to connect to the clients
running
> on
> > > the other machines in the secondary domain/site¨.
> > >
> > > Further description of the problem:
> > > * If I delete the computers from the All Systems collection and run a
> new
> > > discovery, the SMS secondary site server comes up with Client=No, even
> if
> > it
> > > had Client=Yes before I deleted it. I don't know if this is normal
> > > behaviour.
> > > * Whereas Control Panel -> Systems Management previously did not allow
> an
> > > SMS site code to be entered (gave error message when clicking OK) this
> is
> > > now possible. It is still not, however, possible to discover the site
> > code.
> > > * In the Console, when viewing a collection, regardless of whether it
is
> > > indicated that a client is installed or not, the site code is blank -
> > > although all machines are assigned.
> > > * When I try to push clients manually to all computers in a collection
> > (this
> > > includes machines from the primary site and the secondary site), the
> > primary
> > > site seems to try to handle pushing the client to the machines in the
> > > secondary site as well (only ccm.log on the primary site SMS server is
> > > updated).
> > > * The CCM.log displays the same messages as described below ("Unable
> > > to..."), but it has now started to include:
> > > * Unable to retreive travel mode switch from machine "T4h-S001"
> > > * Unable to retrieve pending command value for sms client base
> > > components from machine "T4h-S001"
> > >
> > > Is this beginning to make sense to anyone?
> > >
> > > For the record, the management point in the secondary site seems to
have
> > no
> > > problems. There is no overlap of the site boundaries (which I assume
> might
> > > have accounted for the resources being assigned, but not to a specific
> > > site).
> > >
> > > Thanks for any input!
> > > Jørn
> > >
> > >
> > > "Jørn Jørgensen" <jorn@hotmail.com> wrote in message
> > > news:uXKdGWGCEHA.2164@TK2MSFTNGP10.phx.gbl...
> > > > Hi,
> > > >
> > > > Testing client installation I have a problem with pushing clients
> > > >
> > > > The scenario::
> > > > * A primary site and a secondary site
> > > > * Within the secondary sites resources are discovered and assigned
> > > correctly
> > > > * All resources assigned to the secondary site are on the same
subnet
> > and
> > > in
> > > > the same domain (this includes the secondary site server)
> > > > * Automatic push does not work for any computers, including the site
> > > server
> > > >
> > > > When I try to manually push a client to a computer at the secondary
> > site,
> > > it
> > > > seems to both work and not work:
> > > > * CCM.log seems to think the client installs correctly
> > > > * CCM.log confirms that the connection to admin$, IPC$ works
> > > > * Subsequent attempts at manual push show CCM.log opting not to
> install
> > > the
> > > > client because it's already installed.
> > > > * On the client computer the client is definitely installed
> (everything
> > is
> > > > present in \Windows\System32\CCMsetup, the client.msi.log seems to
> have
> > no
> > > > errors and the icons show up in the Control Panel).
> > > >
> > > > However:
> > > > * CCM.log always complains about the following:
> > > > - Could not retrieve the heartbeat time from the client
> > > > - Unable to retrieve a sites list from machine "T4H-S001"
> > > > - Unable to retrieve travel mode switch from machine "T4H-S001"
> > > > - Unable to retrieve pending command value for sms client base
> > > > components from machine "T4H-S001"
> > > > * The SMS console does not see the computers as having the client
> > > > "installed"
> > > > * At the client computer, in the Control Panel -> Systems Management
> the
> > > > site code is blank, and the SMS site cannot be discovered (neither
the
> > > > secondary nor the primary)
> > > >
> > > > The site server (which is also the DC) acts just as the other
> resources
> > in
> > > > the site - the client is installed, but SMS thinks it isn't.
> > > >
> > > > What am I doing wrong?
> > > >
> > > > Thanks in advance!
> > > > Jørn
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Micke B: "Re: SMS 2003 and Secondary Sites"
- Previous message: Andrew Meikle: "Re: Extending the Schema for SMS 2003"
- In reply to: Jørn Jørgensen: "Re: Client push works but doesn't..."
- Next in thread: Jørn Jørgensen: "Re: Client push works but doesn't..."
- Reply: Jørn Jørgensen: "Re: Client push works but doesn't..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
