And for Install Exchange, maybe note: Install Exchange with slipstreamed sp2 or 3. Then no issues with PowerShell v2 at all.
On Sat, Jul 10, 2010 at 7:39 AM, Michael B. Smith <mich...@smithcons.com> wrote: > Exchange 2007 sp2 and Exchange 2007 sp3 both support PowerShell 2.0. > > Regards, > > Michael B. Smith > Consultant and Exchange MVP > http://TheEssentialExchange.com > > > -----Original Message----- > From: Damien Solodow [mailto:damien.solo...@harrison.edu] > Sent: Friday, July 09, 2010 8:55 PM > To: MS-Exchange Admin Issues > Subject: Re: Server install checklist > > Because 2007 is built on 1.0. > > -------------------------- > Sent using BlackBerry > > > ----- Original Message ----- > From: Kurt Buff <kurt.b...@gmail.com> > To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> > Sent: Fri Jul 09 20:41:26 2010 > Subject: Re: Server install checklist > > Why powershell 1.0? Why not 2.0? I have not touched Exchange past 2003, so > this is an ignorant question... > > On Fri, Jul 9, 2010 at 13:01, Steve Hart <sh...@wrightbg.com> wrote: >> I'm going to be installing a new Exchange 2007 server into an existing E2007 >> org. In the process of refreshing my plan (I haven't done this in a couple >> of years), I was struck by the absence of a real checklist. I'm not talking >> the basics that are available on Microsoft's site; I'm thinking of all of >> the little changes necessary to make an Exchange install function the way we >> want it. Since many members of the list do this often, I thought maybe we >> could waste a little Friday afternoon time creating a list of things to do >> and check. The list I have here is driven by my project, but spinning the >> thing out more generic is fine too; then it will be more useful to the >> community at large. >> >> Nothing here should be taken as gospel by anyone. I'm a network admin that >> has Exchange as a small part of my job. Corrections are welcome. >> >> Here's my starter for discussion purposes (This is assuming adding an E2007 >> server to an E2007 org, so the AD prep is done. We're a small company with >> 60 mailboxes on one server): >> >> Install Windows server (64 bit) >> Patch windows >> Configure networking w/ Static IP >> Add server to the domain >> Configure Page file on C Drive to total RAM + 10MB Install .net 2.0 >> Install MMC 3.0 Install Powershell 1.0 Install IIS Install Exchange >> Enter Exchange key Patch Exchange Change IS Store cache time to 15 >> minutes (to shorten "send as" change delays) Install RPC over HTTP >> Proxy for Outlook Anywhere Enable Exchange Powershell scripting Copy >> all scripts from any existing servers to the local drive for handy use >> Increase max mailbox size Increase max attachment size Enable deleted >> item retention Move Exchange logs Move Exchange database Create 2nd >> database for Spam Quarantine Get 3rd party certs for OWA, OA Install >> certs Set up certs for CAS Set up ActiveSync Configure additional >> email domains Create/Modify outside send and receive connectors Create >> test mailbox in new database, verify mail flow Test Outlook, OWA, >> Outlook Anywhere, Mac Connectivity... >> Configure backups >> Rehome public folders, if used >> Move Outlook Address Book generation >> Create inside specialized receive connectors for anything that sends >> email >> Multifunction Printers/Scanners >> Monitoring computers >> Backup devices >> Homegrown apps >> Commercial packages Repoint all internal devices to new email server >> (see above list) Move mailboxes Redirect NAT rules to point to new box >> Repoint internal DNS record for "mail" and "autodiscover" >> Stop all services on old server >> Test for one week >> Remove public folders from old server >> Remove mailbox stores from old server >> Uninstall Exchange from old server >> Remove old server from the domain >> Jack and Coke~ >> >> >> > > > > > > >
