Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: AnnetteMon
New Today: 66
New Yesterday: 63
Overall: 149740

People Online:
Visitors: 43
Members: 4
Total: 47 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Server Patching and Change Mgt
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Server Patching and Change Mgt

 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
birdman
Newbie
Newbie


Joined: May 06, 2008
Posts: 9

PostPosted: Thu May 29, 2008 7:21 am    Post subject: Server Patching and Change Mgt Reply with quote

Looking for concensus on how companies handle Change for MS Server Patching. Since server patching is done monthly do companies use Standard Changes? Are they handled through maintenance windows - how would that work? Or are these Normal Changes that require an RFC every month? We patch a few hundred servers per month so how would Change Mgt control this activity of which servers being patched when? The main problem we have is the lack of visibility as to which servers are being patched when so there ends up being collisions. Lack of awareness is the other major problem.
Back to top
View user's profile
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Thu May 29, 2008 5:16 pm    Post subject: Reply with quote

Hi birdman

In my manual process, I handle these through Standard Changes - Change is tied to Machine type & O/S - Initial Release document is effectively a procedure for applying patches. This is agreed by CAB to be accurate & effective. I then require a Standard Release Notification for each instance. This gives details of device patched, patch id, time, date, duration,implementer, etc. All this info is then fed into the Forward Schedule of Change, and E-Mail notification is sent to interested parties. I will accept multiple instances of the same patch on different devices on one SRN. This then gives an overall view of what is happening and when.

Maybe not perfect, but effective. Smile
_________________
Regards

Ed
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3319
Location: London, UK

PostPosted: Thu May 29, 2008 5:45 pm    Post subject: Reply with quote

YEp, same here

We defined the monthly patching in the policy document as standard change

and applied it
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
asrilrm
Senior Itiler


Joined: Oct 07, 2007
Posts: 441
Location: Jakarta, INA

PostPosted: Thu May 29, 2008 6:25 pm    Post subject: Reply with quote

Hi,

My company entirely uses Linux (Susse) for O/S. Patches are not as often as MS, but in many occasions have caused problems.
I treat them as normal change and definitely must go through CAB.

Cheers,
Asril
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Thu May 29, 2008 6:53 pm    Post subject: Reply with quote

HI,

same as above - if you can though define a maintenance window for patching but still require change control before implementing the change.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3319
Location: London, UK

PostPosted: Thu May 29, 2008 7:45 pm    Post subject: Reply with quote

i think we all agree that the periodic patching of systems - servers, workstations, systems - should go throguh the change management process - to include tickets, approval, FSC, etc etc

However, as noted each company has to make their own decisions as to where these chanegs fall under

do they fallunder standard change model - pre-approved etc etc etc
do they fall under normal change model - approval, cab etc etc
do they fall under ...... etc etc etc

It depends on what your CM policy is about this as well as the RM and CfM policy say about this

If the CfM tracks the patches - a major headache - their requirements may say normal change process so that they get tracked ...etc
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Skinnera
Senior Itiler


Joined: May 07, 2005
Posts: 121
Location: UK

PostPosted: Thu May 29, 2008 11:14 pm    Post subject: Re: Server Patching and Change Mgt Reply with quote

birdman wrote:
Looking for concensus on how companies handle Change for MS Server Patching. Since server patching is done monthly do companies use Standard Changes? Yes.

Are they handled through maintenance windows - how would that work? Yes - and very well. Wink

Or are these Normal Changes that require an RFC every month? - Yes, a set of Standard Change RFCs are populated in the FSC every month

We patch a few hundred servers per month so how would Change Mgt control this activity of which servers being patched when? We get the support team to pacth them in known batches of, say, 25 a night, carefully arranged to cause minimum disruption if they go wrong.
One RFC per batch.


The main problem we have is the lack of visibility as to which servers are being patched when so there ends up being collisions. Lack of awareness is the other major problem. The solution above works for us and gets over these issues.

_________________
When I say 'CCR', please read 'RFC'.
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.