Team or solo? (was Re: We need your feedback)

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Cathy Moya [MS] (camoya_at_online.microsoft.com)
Date: 09/30/04 

Date: Thu, 30 Sep 2004 12:28:19 -0700

That brings up an interesting tangent - how many of you have teams and how
many of you are out there on your own as SMS admins? Just curious . . . 

-- 
Cathy Moya, MCSE: Security, MCT
Technical Writer, Enterprise Management Content Group
Check out the SMS Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided AS IS with no warranties and confers no rights.
"Scott Townsend" <scott-i@.-N0-SPAMplease.enm.com> wrote in message
news:u7bXhswpEHA.516@TK2MSFTNGP09.phx.gbl...
> "<...snip...>hold on I'll pass it over to the patch management
> team.<...snip...>"
>
> Team??  No wonder I cant figure it out. I'm just trying to do all of this
> myself...
>
> I'll take a look at the document and see if it helps.
>
> Scott<-
>
>
> "Rory Niland" <RoryNiland@discussions.microsoft.com> wrote in message
> news:23BC2884-6740-435D-A572-DA9882CF92AA@microsoft.com...
> > Quote : "which is a long title for a very complicated subject"
> >
> > Feedback - why did MS make it so complicated?, then you wouldn't be
> > worried
> > about the books so much.. hold on I'll pass it over to the patch
> > management
> > team.
> >
> >
> > "Cathy Moya [MS]" wrote:
> >
> >> X-posted to microsoft.public.sms.misc,
> >> microsoft.public.sms.software_updates, microsoft.public.sms.swdist
> >> followups set to microsoft.public.sms.misc
> >>
> >> This week we released a beta version of a new book in the Scenarios and
> >> Procedures series of SMS documentation. The full title for this one is
> >> "Scenarios and Procedures for SMS 2003: Software Distribution and Patch
> >> Management", which is a long title for a very complicated subject. The
> >> doc
> >> is only available for download at this time.
> >>
> >>
http://www.microsoft.com/downloads/details.aspx?FamilyID=32f2bb4c-42f8-4b8d-844f-2553fd78049f&DisplayLang=en
> >>
> >> We are considering the document a "beta" because there is still some
> >> content
> >> missing and still some features that aren't complete. And there is
always
> >> room for improvement. As with any beta, we need beta testers. What we
> >> need
> >> to know is:
> >>
> >> 1) If you were (or are) new to SMS, could you take this document and
> >> deploy
> >> a package and/or a software update?
> >> 2) What could we add to a document like this to make it more helpful to
> >> someone who is new to SMS?
> >> 3) What could we add to a document like this to make it more helpful to
> >> you
> >> personally, regardless if your experience level with SMS?
> >> And anything else you'd like to add!
> >>
> >> When giving us feedback, we would like it sent to smsdocs@microsoft.com
> >> and
> >> with "Software Distribution and Patch Management" in the subject line
so
> >> we
> >> can sort it out from the usual smsdoc emails. Thank you!
> >>
> >> I've put together a bit of a summary, for those who want to know some
of
> >> the
> >> thought process behind it:
> >> ------------------
> >> Target Audience:
> >> ------------------
> >> This document is primarily intended for newer SMS administrators,
though
> >> if
> >> you are an experienced SMS Administrator, you may find the planning
> >> worksheets to be helpful if you do not have your own yet. If you are
> >> experienced with SMS package deployment, we hope the document will be
too
> >> basic for you, but we hope you can give us feedback on topics you think
> >> are
> >> important but are not currently included.
> >>
> >> -----------
> >> Structure:
> >> -----------
> >> Like the other S&P guides, we have tried to focus on the sequence you
> >> need
> >> to perform all the tasks - start at A, then go to B, then decide
between
> >> C
> >> or D, and eventually get to Z. Like the S&P for Planning and
Deployment,
> >> there are several flow charts to guide you through the way and there
are
> >> planning worksheets to help you write down everything before you start
> >> configuring. (Added bonus, you end up with hard copy doc of your
> >> environment.) Also like the Planning and Deployment S&P, we tried to
keep
> >> the main part of the doc fairly short but include lots of appendices if
> >> you
> >> want more detail.
> >>
> >> Unlike the S&P for Planning and Deployment, I did the planning docs in
> >> Word
> >> format and annotated all of the lines. If you started by filling out
> >> every
> >> line of every form, you would approach the user interface knowing every
> >> entry you need to make in every dialog box. And if you don't know what
> >> option to choose, you can read the annotations to help you decide. Some
> >> of
> >> the planning forms, like boundary planning, use logic that moves you
from
> >> line to line like the US tax forms.
> >>
> >> ------------
> >> Content:
> >> -----------
> >> The content is about 90% complete. Much of the content comes from
> >> Chapters 5
> >> & 6 in the current SMS Operations Guide but there is also quite a bit
of
> >> new
> >> content with the planning worksheets, and new material related to SP1
is
> >> included. You can find the SP1 material by searching for *SP.
> >>
> >> Thanks for helping make our docs better!
> >>
> >> -- 
> >> Cathy Moya, MCSE: Security, MCT
> >> Technical Writer, Enterprise Management Content Group
> >>
> >> Check out the SMS Technical FAQ:
> >>
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
> >> This posting is provided AS IS with no warranties and confers no
rights.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>
Quantcast