tl;dr, verify your targets :-)

On Sunday, May 18, 2014, CESAR.ABREG0 <[email protected]> wrote:

> Verify the number of clients in collection before using to deploy a TS to
> it? Verify that the dynamic collection being use contains the intended
> clients? Verify that the 'all system' collection is not a target?
> There could be more but a couple of that I can think of.
>
> Most this situations happen by human errors and inexperienced as well. I
> think HP consulting did it at a bank a couple of years ago and some that
> colleagues have shared with me that happened in a USA government branch.
> I've been doing imaging over 10 years and I never do mandatory deployments
> to populated collections, only to empty ones and I add clients manually or
> have a process to do so.
>
> This got me thinking of steps that can be taken or be part of a TS to
> prevent this type of situation up to an extend, can't never be prevented
> completely.
>
> 1. Put a step that verify DCs and other critical infrastructure systems
> and have human click yes before moving forward or fail if no response.
> 2. Creat web service/orchestrator to send email or a type of notification
> to a group before continuing. Automated.
> 3. What I've used in the past. Create an empty collection, deploy TS to it
> as mandatory, add required systems manually or by script from a list. Limit
> who can add systems and the type of client, like no DCs or SCCM systems.
>
> Cesar A.
> Meaning is NOT in words, but inside people! Dr. Myles Munroe
> My iPad takes half the blame for misspells.
>
> On May 18, 2014, at 5:31 PM, Ken Schaefer 
> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>>
> wrote:
>
>  I'm assuming someone clicked the wrong button (i.e. "Finished", when
> they should've clicked "Cancel"). How does "process verification" (how do
> you define this?) help?
>
>
>
> Cheers
>
> Ken
>
>
>
> *From:* 
> [email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>[
> mailto:[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>]
> *On Behalf Of *Rankin, James R
> *Sent:* Monday, 19 May 2014 2:59 AM
> *To:* 
> [email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>
> *Subject:* Re: [NTSysADM] A Windows 7 image was deployed to EVERYTHING.
>
>
>
> I think I may use this as an example in an article about the importance of
> process verification.
>
> Sent from my (new!) BlackBerry, which may make me an antiques dealer, but
> it's reliable as hell for email delivery :-)
>  ------------------------------
>
> *From: *"Andrew S. Baker" 
> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>>
>
>
> *Sender: 
> *[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>
>
> *Date: *Sun, 18 May 2014 12:55:37 -0400
>
> *To: 
> *ntsysadm<[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>
> >
>
> *ReplyTo: 
> *[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>
>
> *Subject: *Re: [NTSysADM] A Windows 7 image was deployed to EVERYTHING.
>
>
>
> Automation leads to relaxation...
>
> ...unless something goes horribly wrong.
>
>
>
>
>
>
>
> *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker>
> *Providing Virtual CIO Services (IT Operations & Information Security) for
> the SMB market...*
>
>
>
>
>
> On Fri, May 16, 2014 at 10:40 PM, Richard Stovall 
> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>>
> wrote:
>
> Wowzers. That's just incredible.
>
> On May 16, 2014 8:14 PM, "Kennedy, Jim" 
> <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>>
> wrote:
>
>  So SCCM sent win 7 to everything, including servers.
>
>
>
> http://it.emory.edu/windows7-incident/
>
>
>
>
>
>

-- 
--
Espi (via mobile)

Reply via email to