Sysaid is a fine solution, as many people have said. And, if you hunt down an out-of-print book (I believe it was Outlook 2003 for Developers) there is a ECM (Engineering Change Management) application developed using public folders and the Outlook Object Model.
System Center Service Manager is Microsoft's entry in the space. It's a "big" solution. But if you already have System Center licensing, you should take a look at it. By the way, email is not sufficient because it doesn't have any "change management" capabilities. No approval, no search, no mechanism for looking at earlier ECNs, no database, no backup, no reversion - it's email. :) From: [email protected] [mailto:[email protected]] On Behalf Of Dave Lum Sent: Tuesday, October 28, 2014 1:10 PM To: [email protected] Subject: [NTSysADM] Change Management process and documentation We are defining a new change management process at %dayjob%. The current consensus is to do it all via email, which for reason's I can't fully explain gives me fits. I've been asked why not email and I can't come up with anything more useful than "new engineer starts and has no way to review previous changes". Kind of a weak argument... %dayjob% is a smallish company (~250 employees) that does have to worry about HIPAA but currently shows no interest in following ITIL guidelines. What do you guys use and if not email, why not? Dave Lum \\ I.T. Garage [email protected]<mailto:[email protected]> \\ 503.267.9764 (voice/text) www.theitgarage.com<http://www.theitgarage.com>
