Re: SMS2003 parent with sms 2.0 children and SUS

From: Adam Welker [MSFT] (adamwel_at_online.microsoft.com)
Date: 02/13/05


Date: Sat, 12 Feb 2005 20:21:04 -0800

Software Update status messages come from two sources, patchinstall and the
scan package. If your central site is an upgrade from SMS 2.0 you'll need
to update the scan tool with the 2003 version. If you have existing update
packages created at or by a 2.0 site, you'll need to update the patchinstall
version in those packages. The easiest way to do that is to run the Wizard
against those packages.
If you do all of that, then your 2.0 clients at the child sites will
generate all of the new 2003 status messages and they will be processed and
sent back to the 2003 Central site where you can view reports. All of the
scan tools currently available, except for the Dell Update scan tool will
work when advertised from a 2003 site to clients of a child 2.0 site.
The Dell Update scan tool will only work on SMS 2003 SP1 advanced clients.
There are other scan tools coming in the future which will likely have the
same requirements.

-- 
Adam Welker
This posting is provided "AS IS" with no warranties, and confers no rights.
"Microsoft" <mas@mas.com> wrote in message 
news:%23RWSTpIEFHA.4052@TK2MSFTNGP09.phx.gbl...
> I'm a little confused so let me explain what I want to do and you can tell
> me if it will help
>
> We only have SUS FP installed on the parent site (which has 0 clients) 
> and
> its advertised from there to a collection containing all of our 
> workstations
> from all of the child sites . Each child site gets the replicated
> advertisement and sends it to its clients and they run the package that 
> was
> created on the parent.
>
> When I run the report on the parent server that is SMS 2003 sp1.  Will the
> report accurately reflect the patch status of the clients that ran the
> package from a sms 2.0 site?
>
>
> "Adam Welker [MSFT]" <adamwel@online.microsoft.com> wrote in message
> news:ed1RRCIEFHA.936@TK2MSFTNGP12.phx.gbl...
>> I believe the status messages are generated by the clients.  They won't 
>> be
>> visible at the 2.0 sites.  You'll need to update any of your patch
> packages
>> with the new 2003 files.  This can be done by running DSUW against those
> old
>> packages.  You'll also want to install the 2003 versions of the scan
> tools.
>>
>> I believe all scan tools currently available, except the Dell Update scan
>> tool will work on SMS 2003 legacy and advanced clients and 2.0 clients.
>>
>> The Dell Update scan tool requires SMS 2003 SP1 advanced clients I 
>> believe
>> and I'd expect that to be a requirement for any new scan tools released 
>> in
>> the future.
>>
>> -- 
>> Adam Welker
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>>
>>
>> "Microsoft" <mas@mas.com> wrote in message
>> news:uQQrqqHEFHA.3972@TK2MSFTNGP15.phx.gbl...
>> > So just to clarify.. When I run my reports from the 2003 parent server
> on
>> > patching status I'll get all the benifits of 2003 sp1 and be able to 
>> > see
>> > which machines, installed, failed and were rebooted?
>> > "Jeff Harbaugh [MSFT]" <jeffharb@online.microsoft.com> wrote in message
>> > news:eJK$SXHEFHA.560@TK2MSFTNGP15.phx.gbl...
>> >> Upgrading to SMS 2003 should have no affect on the child sites and
>> >> communication. The information flow will continue the same way as if
> you
>> >> were all SMS 2.0.
>> >>
>> >> -- 
>> >> Thanks,
>> >> Jeff Harbaugh [MSFT]
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >> "Microsoft" <mas@mas.com> wrote in message
>> >> news:%23$KR19GEFHA.1396@tk2msftngp13.phx.gbl...
>> >> >I have 7 sites over 7 wan links that are child sites to one parent in
>> >> >our
>> >> > 2.0 setup.  I have SMS sus setup on the parent and its packages get
>> >> > replicated to the child sites and run.
>> >> >
>> >> > Once I upgrade the parent site to sms2003, will the child sites 
>> >> > still
>> >> > be
>> >> > able to run the package even though they will be still 2.0 and the
>> >> > packages
>> >> > will be created using SMS 2003?
>> >> >
>> >> > Will my child sites still be able to add new clients until I get 
>> >> > them
>> >> > to
>> >> > 2003?   No AD at this company yet..
>> >> >
>> >> > Thanks..
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Re: SMS 2.0 to SMS 2003 Upgrade
    ... > exisiting packages and information that relates to the child site. ... > you remove it from the SMS 2.0. ... > collections and clients from the child site. ... >> Installation Wizard you mentioned)? ...
    (microsoft.public.sms.setup)
  • Re: SMS2003 parent with sms 2.0 children and SUS
    ... I believe the status messages are generated by the clients. ... You'll need to update any of your patch packages ... The Dell Update scan tool requires SMS 2003 SP1 advanced clients I believe ... >>> replicated to the child sites and run. ...
    (microsoft.public.sms.setup)
  • Re: MP, DP or new Site???
    ... Advertise very small packages. ... I want to set these servers up as distribution points to help me ... making these locations SMS secondary sites, then for each activate them as ... or where you centrally admister these clients the Central site. ...
    (microsoft.public.sms.admin)
  • RE: software distribution issue
    ... My SMS logs are clean and the package apears to be ... ready to go, but no clients have requested, i suspect its a policy problem ... > - Created multiple packages for testing ... but I can not see the applicaiton advertisements in the ...
    (microsoft.public.sms.swdist)
  • No status messages from child site clients
    ... Running SMS 2003 SP1, parent site with 4 remote child sites. ... the clients from the problem site sent any status messages. ...
    (microsoft.public.sms.admin)