Thursday, June 24, 2010

Re: Exchange 2007 - management/maintenance workload

Dan,
I'm=20a=20one-person=20show=20also.=20=20We=20run=20Exchange=202003=20for=
=20about=2050=20mailboxes
and=20I=20have=20little=20maintenance=20to=20do.=20=20We=20run=20shared=
=20calendars,=20MANY
distribution=20lists,=20and=20have=20added=20parents=20as=20contacts=20so=
=20that=20we=20can
use=20DLs=20to=20email=20parents=20of=20classes,=20divisions,=20whole=20s=
chools,=20etc.=20=20So
far,=20it's=20been=20good,=20although=20we=20are=20looking=20at=20impleme=
nting=20an=20online
parent=20portal=20next=20summer=20to=20alleviate=20some=20of=20the=20work=
load=20in=20updating
and=20setting=20up=20the=20lists=20each=20year,=20plus=20the=20online=20f=
eatures=20that=20come
with=20the=20portal.

Bernadette=20

-----Original=20Message-----
From:=20A=20forum=20for=20independent=20school=20educators
[mailto:ISED-L@LISTSERV.SYR.EDU]=20On=20Behalf=20Of=20Ademola=20Popoola
Sent:=20Thursday,=20June=2024,=202010=201:08=20PM
To:=20ISED-L@LISTSERV.SYR.EDU
Subject:=20Re:=20Exchange=202007=20-=20management/maintenance=20workload

If=20the=20server=20is=20beefy=20enough=20and=20the=20the=20Exchange=20co=
nfiguration=20is
solid,
it=20pretty=20much=20runs=20itself.=20Besides=20adding=20new=20users,=20w=
hich=20is=20mostly
taken
care=20of=20when=20you=20add=20the=20users=20to=20AD;=20and=20creating=20=
DL's,=20there=20really=20is
not
much=20of=20a=20maintenance=20issue=20or=20workload=20with=20an=20Exchang=
e=20box.

A.

On=20Thu,=20Jun=2024,=202010=20at=201:03=20PM,=20JPDS=20Tech=20<techpurch=
ases@jpds.org>
wrote:

>=20We=20are=20a=20small=20school,=20with=20under=20100=20email=20account=
s.=20=20We=20are
considering=20a
>=20shift=20from=20POP3=20to=20Exchange=202007=20but=20I=20am=20concerned=
=20about=20adding=20a
great
>=20deal=20of=20administrative=20overhead.=20=20The=20proposed=20new=20se=
t-up=20would=20be
Exchange
>=202007=20running=20on=20(VMWare-virtualized)=20Server=202008;=20we=20wo=
uld=20continue=20to
use
>=20Postini=20to=20reduce=20our=20spam=20load.=20=20We're=20hoping=20to=
=20achieve=20universal
access
>=20for=20staff=20and=20shared=20calendars=20and=20distribution=20lists.=
=20=20I=20also=20hope
that
>=20the
>=20SIS=20described=20in=20the=20thread=20below=20will=20reduce=20our=20s=
torage
requirements.
>
>=20I'm=20aware=20that=20Google=20Apps=20and=20Microsoft=20Live=20offer=
=20these=20things=20but
I'm
>=20specifically=20asking=20about=20Exchange=202007.=20=20One=20techie=20=
tells=20me=20that
2007=20is
>=20so=20stable=20that=20there=20is=20little=20maintenance=20work.=20=20W=
ould=20I=20be=20taking=20on
a
>=20nightmare=20of=20administrative=20tasks?=20=20I=20am=20a=20one-person=
=20tech=20office.
>
>=20With=20trepidation,
>
>=20Dan=20Berger
>
>

*****
This=20email=20and=20any=20files=20transmitted=20with=20it=20are=20confid=
ential=20and=20intended=20solely=20for=20the=20use=20of=20the=20individua=
l=20or=20entity=20to=20whom=20they=20are=20addressed.=20If=20you=20have=
=20received=20this=20email=20in=20error=20please=20notify=20the=20system=
=20manager.=20This=20message=20contains=20confidential=20information=20an=
d=20is=20intended=20only=20for=20the=20individual=20named.=20If=20you=20a=
re=20not=20the=20named=20addressee=20you=20should=20not=20disseminate,=20=
distribute=20or=20copy=20this=20e-mail.=20Please=20notify=20the=20sender=
=20immediately=20by=20e-mail=20if=20you=20have=20received=20this=20e-mail=
=20by=20mistake=20and=20delete=20this=20e-mail=20from=20your=20system.=20=
If=20you=20are=20not=20the=20intended=20recipient=20you=20are=20notified=
=20that=20disclosing,=20copying,=20distributing=20or=20taking=20any=20act=
ion=20in=20reliance=20on=20the=20contents=20of=20this=20information=20is=
=20strictly=20prohibited.

[ For info on ISED-L see https://www.gds.org/podium/default.aspx?t=3D128874 ]
Submissions to ISED-L are released under a creative commons, attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L