Re: SMS2003 parent with sms 2.0 children and SUS
From: Microsoft (mas_at_mas.com)
Date: 02/11/05
- Next message: Joe Brown: "SP1 upgrade failing"
- Previous message: Deester: ""Install Pending" package on secondary DP"
- In reply to: Adam Welker [MSFT]: "Re: SMS2003 parent with sms 2.0 children and SUS"
- Next in thread: Adam Welker [MSFT]: "Re: SMS2003 parent with sms 2.0 children and SUS"
- Reply: Adam Welker [MSFT]: "Re: SMS2003 parent with sms 2.0 children and SUS"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 11 Feb 2005 17:37:50 -0500
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..
> >> >
> >> >
> >>
> >>
> >
> >
>
>
- Next message: Joe Brown: "SP1 upgrade failing"
- Previous message: Deester: ""Install Pending" package on secondary DP"
- In reply to: Adam Welker [MSFT]: "Re: SMS2003 parent with sms 2.0 children and SUS"
- Next in thread: Adam Welker [MSFT]: "Re: SMS2003 parent with sms 2.0 children and SUS"
- Reply: Adam Welker [MSFT]: "Re: SMS2003 parent with sms 2.0 children and SUS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
