Re: Any SMS consultants out there to answer a question?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Geoff Walker (geoffw_at_m-v-t.com)
Date: 02/19/04


Date: Thu, 19 Feb 2004 10:13:51 -0700

The very first question I would ask is "What do you want to accomplish with
Systems Management Server?"

If they say patch management, ask them if they have tried the free Software
Update Services. If they say no, but they don't like what they've heard,
they're probably a good candidate for SMS2k3, as it provides a more granular
control level for patch management.

Ask if they are ready for a system that has an initial software investment
of ~3500$ (os,sql,sms).

I would want to walk away from that conversation with the knowledge that
this company is clear on it's objectives, and also that they have a strong
network implementation (WAN links, vpn, etc.) and whether they are going to
support certain clients. When my company made the switch to SMS, i made the
suggestion that we not support legacy clients (i.e. win98 & nt4). The
company was already phasing them out, but i pushed them harder and received
over 100 workstations one day to accomplish the phase out (my company was
originally doing it in lots of 5 workstations every 2 weeks)

There are alot of things to cover, but i would read the first chapter of the
Concepts, Planning, & Deployment guide located @
http://www.microsoft.com/downloads/details.aspx?FamilyId=784838B3-34E0-4122-B3E2-17C5B4EEF8F4&displaylang=en,
and then i would read (or skim for refresher) PART 3: Planning.

If you need more help, feel free to mail me at geoffw@m-v-t.com

"adfreak" <anonymous@discussions.microsoft.com> wrote in message
news:12e6501c3f701$36a53310$a001280a@phx.gbl...
> Ok, I've been an AD Architect for the past 4 years solely
> concentrating on AD Design/Migration along with Exchange
> design/migration. Now, all of a sudden, my company is
> sending me out to a client next Tuesday who is 80% through
> with their AD migration. They are also deploying SMS (no
> idea if it's an upgrade from 2.0 to 2003, not much info)
> Anyways, this client has been trying to accomplish the SMS
> rollout in house and have run into issues. They need an
> SMS subject matter expert to come in and perform an
> audition.
>
> My problem is, after telling my company "Hey, I haven't
> touched SMS in over 2.5 years", they say "don't worry
> about it".
>
> My question is....anyone have suggestions on what type of
> questions I should ask when I sit down with this client?
> I'm going to spend the next 3 days becoming familiar with
> SMS 2003
>
> Thanks



Relevant Pages

  • Re: sms 2003 patch management is brutal!
    ... > In regards to patch management, all of my customers bought SMS 2003 mainly ... Inventory and everything else was an added bonus. ... > client and I right click and select Install Client, I have no idea what is ...
    (microsoft.public.sms.admin)
  • Re: sms 2003 patch management is brutal!
    ... In regards to patch management, all of my customers bought SMS 2003 mainly ... Inventory and everything else was an added bonus. ... client and I right click and select Install Client, I have no idea what is ...
    (microsoft.public.sms.admin)
  • Re: SMS Distribution to remote Sites
    ... Obvious SMS provides most of the functionality (patch management could be ... The reason for creating a protected distribution point is simply to make ... SMS tasks for these remote sites. ...
    (microsoft.public.sms.misc)
  • RE: SMS 2003 Patch Management
    ... I would say "Patch Management SMS 2003 Solution Accelerator.doc" by ms ... > that we can push out security patches via SMS. ... > have added a couple of test machines to those collections so that I ...
    (microsoft.public.sms.admin)
  • Re: sms 2003 patch management is brutal!
    ... patch management piece of SMS 2003 as soon as posibble, ... it just isn't called a synch host in the setup interface. ... There may be slight improvements ...
    (microsoft.public.sms.admin)