Re: How to configure SCCM 2007 Primary Site with a SMS 2003 (Child

Here if you want I agree with Sherry too. :-) but since I don't read those "crazy forum" (Newsgroups rules) [inside joke]



And don't forget about

- Maintenance windows

- That there are many predefined desire configuration Management pack

- Better and increased licence management



There you have two ConfigMgr MVP on your side.

"Luke" <wililupy@xxxxxxxxxxx> wrote in message news:23bbebd4-b4d4-4729-9295-1d355eaa5276@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Nov 21, 1:28 pm, Sherry Kissinger [MVP-SMS]
<SherryKissingerMVP...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I see you're posting over in the ConfigMgr forums, and John Marcum is taking
excellent care of you (even if occasionally his tongue-in-cheek replies get
lost in translation). Can I just get away with "I agree with John"?

Ok, ok... I understand you might have a bit of a fight to get the $$ for
licensing. The people with the purse strings always want to push back and
say "do you *really* need it?"

One good argument:
- Do they plan to upgrade to a different client operating system.... Ever?
Even the Vista client support on SMS2003 leaves much to be desired; the
configmgr client is much better. And I've heard Windows 7 is in beta.... I
can't imagine too much effort going into making a SMS2003 client for Windows
7.

All the other arguments I can think of are all about making your life (the
admin's life) easier. I know the people with the purse strings don't really
care about how much better your job will be.

Here's a couple more:
With ConfigMgr, Desired Configuration Management: watch for 'drift' from
defined policies.
With ConfigMgr, OSD (especially because of the Task Sequences): once
designed & implemented from top down--you could even have the end user say
"yes, I'd like to reimage my machine over lunch". Reduce tech costs!
With ConfigMgr, Patching: ITMU gone; WSUS-like in.

John also mentioned getting the SA agreement. With Microsoft committed to
every 3 yrs updating their System Center products, the "let's just license it
when we need it" argument just ends up costing the company a big chuck of
money.
--
Standardize. Simplify. Automate.

"Luke" wrote:
> On Nov 21, 5:47 am, Sherry Kissinger [MVP-SMS]
> <SherryKissingerMVP...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > Ok. Well, as I mentioned it is technically possible to do what you > > propose.
> > But I definitely recommend getting your sms2003 sites upgraded to 07 > > as soon
> > as you possibly can. ConfigMgr07 has tons of excellent features; it is > > well
> > worth it!

> > (I'm sorry, I still don't quite buy the "everyone needs their own > > primary
> > because we need to have our own little kingdom". I still recommend > > getting
> > someone in who knows how -- not me, by the way; I'm just a random > > person who
> > is also a configmgr admin, but I'm not a hierarchy designer! -- to > > really
> > look at your hierarchy and recommend the correct 1-3 year plan)
> > --
> > Standardize. Simplify. Automate.

> > "Luke" wrote:
> > > We are running into licensing issues. Our corporate office only > > > bought
> > > a licensing for them, and expect all the remote sites (mine > > > included)
> > > to run SMS 2003 since we are licensed for that.
> > > The hierarchy will be the SMMC 2007 server on top, and then 3-4
> > > primary children SMS 2003 servers for the remote sites so that we > > > can
> > > control our local clients at our sites.

> > > Thanks for the reply, If you have any questions, don't hesitate to
> > > ask.- Hide quoted text -

> > - Show quoted text -

> I am starting to lean more towards using SCCM secondary sites.
> However, now I have concerns about our clients. We aren't licensed for
> our clients at the remote sites for SCCM 2007 but we are for SMS 2003.
> If we install SCCM Secondary sites at the remote sites, won't we run
> into licensing issues for the clients?

Yes, John has been "taking care" of me. If you don't mind, I would
like to quote your post in an email to my supervisors about this
situation. Seeing that you are an SMS MVP will carry more weight than
just my recommendation.

It looks like we are going to move ahead and install SMS 2003 as a
primary child site at the remote sites, and then upgrade to SCCM once
the budget allows for it.
I talked with a Microsoft Licensing Rep. and he told us what it would
cost and sent me a quote for it that I will forward to them as well.
Perhaps with your post and the quote from microsoft, we can go the
right path and just install SCCM.
I don't know how long they will let me put this back, but it looks
like in the next week or two they want to move forward.

I'll keep you posted.

Thanks

.

Relevant Pages

  • Re: How to configure SCCM 2007 Primary Site with a SMS 2003 (Child
    ... Do they plan to upgrade to a different client operating system.... ... With ConfigMgr, Desired Configuration Management: ... a licensing for them, and expect all the remote sites ...
    (microsoft.public.sms.admin)
  • ConfigMgr Site Assignment Prb. with OSD through WDS at Secondary S
    ... Everything seems to work fine besides client ... because of the assignment problem). ... secondary site instead of the primary site. ... Since ConfigMgr ...
    (microsoft.public.sms.setup)
  • Re: How to configure SCCM 2007 Primary Site with a SMS 2003 (Child
    ... ConfigMgr, don't forget to line up budget for www.mms-2009.com, the best ... Do they plan to upgrade to a different client operating system.... ... a licensing for them, and expect all the remote sites (mine ... primary children SMS 2003 servers for the remote sites so that we ...
    (microsoft.public.sms.admin)
  • Re: How to configure SCCM 2007 Primary Site with a SMS 2003 (Child
    ... I see you're posting over in the ConfigMgr forums, ... Do they plan to upgrade to a different client operating system.... ... a licensing for them, and expect all the remote sites ...
    (microsoft.public.sms.admin)
  • RE: Clients at secondary sites
    ... This is for SMS2003 Advanced Clients (not ConfigMgr), ... secondary sites that report to one of the primaries. ... In the primary that holds the secondaries, all agents are enabled, ... The client deployment is working fine. ...
    (microsoft.public.sms.admin)
Loading