MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  February 2008

MSUNAG February 2008

Subject:

Re: MSU Exchange Thoughts on Central Active Directory and no more "Islands"

From:

Troy Murray <[log in to unmask]>

Reply-To:

Troy Murray <[log in to unmask]>

Date:

Thu, 14 Feb 2008 09:17:24 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (136 lines)

Thanks Chris.

-t

On Feb 14, 2008, at 8:41 AM, Harper, Chris wrote:

> Listserves were ADFUTURE and EMAILFUTURE, just a small correction  
> there. But yes will be a good platform for this discussion.
>
> Christopher M. Harper
> MANAGER OF INFORMATION TECHNOLOGY
> University Relations / Michigan State University
> 401 Olds Hall, East Lansing, MI 48824-1047
> Email: [log in to unmask] / Direct: 517.355.9980
> Web: http://ur.msu.edu / Cell: 517.290.5496
>
>
> --
>
> From: MSU Network Administrators Group [mailto:[log in to unmask]]  
> On Behalf Of Troy Murray
> Sent: Wednesday, February 13, 2008 8:36 PM
> To: [log in to unmask]
> Subject: Re: [MSUNAG] MSU Exchange Thoughts on Central Active  
> Directory and no more "Islands"
>
> A good thread to start the list setup for that discussion, I think  
> it was by using "adfuture" and or "mailfuture" in the subject and  
> body to the list serve address.
>
> --
> Troy Murray
> Sent from my iPhone
>
> On Feb 13, 2008, at 7:25 PM, Esther Reed <[log in to unmask]> wrote:
> I left today’s IT Exchange a bit early so perhaps my following  
> comments have been discussed:
> (This is a bit long to provide background to those who did not  
> attend.)
>
> When I left, the discussion about options for MSU Email was  
> revolving around MS Exchange and a central AD.  The idea of a single  
> sign-on using just the centrally authenticated and maintained  
> account was included in this.  Tom Davis asked, “If we built it,  
> would you come?”  I must add that some of the discussion seemed (to  
> me) to wander from a central email system to an entirely central  
> computing system -- no more “islands”.
>
> The responses, that I heard, discussed the pros and cons from IT and  
> business viewpoints:  What is reasonable or convenient to create and  
> maintain?  I heard no one mention a major component:  the needs of  
> individual colleges, units, departments and programs.  Aren’t  
> computing systems supposed to serve and mesh with a unit’s workflow  
> (as much as possible given their budget)?
>
> MSU has over 240 graduate programs -- most have different needs,  
> priorities and workflows.  Add to that undergraduate programs,  
> research grants, centers, extension services and satellite  
> operations.  It is easy to see that many pieces of MSU have vastly  
> different needs and workflows that will not fit a standard business  
> model.
>
> The problems with a central Exchange and AD are (1) one-size-fits- 
> all configuration, (2) inability to nimbly change, and (3) long  
> response times.  These are NOT criticisms; these are the nature of  
> the beast.
>
> (1) One-size-fits-all:   A central system can not match its AD to  
> the workflow of every unit on campus.  It just can’t.  A “best fit”  
> middle-of-the-road configuration will have to be used.  Units, who  
> do not quite match, will have to adjust their workflows to fit.  A  
> unit with its own child domain will have more flexibility, but some  
> limitations will have to exist to ensure that all domains play  
> nicely together.
>
> (2) Nimble changes:   How long does it take for a single unit to  
> upgrade its servers -- once the chairman or dean gives their  
> blessing  ;^)  ?  How long for a central system?  How long have we  
> just been *discussing* changing MSU email?  Again, no criticism --  
> thorough preparation is critical.  It  just takes a long time to  
> change a behemoth.
>
> (3) Response times:   If my Dean wants an account created or a  
> global Exchange group changed right now, I can do that in minutes.   
> How long will it take for a central system to respond to this  
> request?  4 hours?  24 hours?  1 week?
>
> I do agree that a centrally maintained system will be attractive to  
> some units, such as (a) units who have no IT person; (b) units who  
> want their IT person to do something other than Exchange or AD; (c)  
> units whose IT person is not interested in doing Exchange or AD; (d)  
> units whose workflow will be minimally impacted; or (e) units who  
> want a central feature such as a globally shared calendar (BTW, not  
> everyone wants this.).
>
> However, I believe that many units need a specialized configuration,  
> nimble changes, quick response times and an IT person who intimately  
> knows their workflow.  These units will continue to maintain their  
> separate “islands” as long as they can afford to do so.  These units  
> pay for this because it makes sense for how they need to do business  
> -- it strengthens whatever service or course they provide.  To tell  
> them “too bad” and force them to a central system will weaken them  
> -- compared to competing programs or services -- and, in turn,  
> weaken MSU.
>
> It would be far better to have central *policies* of what is needed  
> (security, encryption, disaster protection, email services, etc.).   
> Then each unit would be allowed to choose how to comply -- either  
> join the central system or make sure that their “island” follows the  
> rules.
>
> I believe that MSU will continue to need both:  a central system and  
> “islands”.
>
> What are your thoughts or opinions?
>
> ~ Esther
>
> Esther V. V. Reed
> IT Systems Administrator
> MSU Graduate School
>

-- 
Troy Murray
Developer
Michigan State University
Biomedical Research and Informatics Center (BRIC)
100 Conrad Hall
East Lansing, MI 48824
Phone: 517-432-4248
Fax: 517-353-9420
E-mail: [log in to unmask]
Calendar
HTML - http://www.icalx.com/html/troymurray72/month.php?cal=BRIC+Work
iCalendar - http://www.icalx.com/public/troymurray72/BRIC%20Work.ics

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager