Any particular reason to run Outlook Anywhere? What is the type of connection between the satellite office and your main office? Public Internet? A private network of some sort? If I'm asking too many questions please say so.
On Wed, Jun 30, 2010 at 12:02 AM, sdewilliman <[email protected]> wrote: > No, the idea is that the local tech will be > > 1. installing office 2k7 so its standardized across the board as > currently some users are using OL2k3, some 2k7 and some, gasp, Outlook > Express. > 2. joining machines to the domain (so it can be centrally managed) > > > There’s currently a 2mb link to the hub & OL will be configured for > RPC/https using Cached Mode. > > thanks > > > On 6/29/10 9:04 PM, "Richard Stovall" <[email protected]> wrote: > > So this is actually interesting information vis-a-vis the original > question. The users will have accounts in a Windows AD domain you manage, > but the machines they use are external and will not be domain members? Am I > interpreting your latest post correctly? How will the users' accounts be > setup in their Outlook 2007 profiles? RPC over HTTPS (Outlook Anywhere)? > POP3? IMAP? MAPI over VPN (ugh)? > > What type of Exchange environment do you have? SBS or stand alone > Exchange? > > On Tue, Jun 29, 2010 at 6:12 PM, De Williman, Shih <[email protected]> > wrote: > > Many thanks for all the input. Yes, the local admin will have to do some > sneakernet as these machines are not domain-bound, ergo no proper migration. > > > > *From:* Richard Stovall [mailto:[email protected] <[email protected]>] > *Sent:* Sunday, June 27, 2010 9:19 AM > > *To:* MS-Exchange Admin Issues > *Subject:* Re: Migration : pop3 to Exchange > > > On the off chance that the OP is moving the customer to SBS 2003, there is > a POP3 connector baked in to that product. For a 20 user setup I'd probably > do it the way Steve suggested even if a POP3 connector was available for > free. He almost certainly has to touch each client machine anyway to move > messages and contacts from Outlook Express or whatever client they're using > now. > > On Sun, Jun 27, 2010 at 5:41 AM, Steve Szabo <[email protected]> wrote: > > I had not heard of POPbeamer before, but $199 for a few days use vs. about > 30 minutes hands on getting to know the users and a chance t inspect their > machines for possible problems with a quick follow-up a week later? I’d > choose the latter. > > > \\Steve// > > > *From:* HELP_PC [mailto:[email protected] <[email protected]>] > *Sent:* Sunday, June 27, 2010 1:04 AM > > > *To:* MS-Exchange Admin Issues > *Subject:* R: Migration : pop3 to Exchange > > > Why not popbeamer for Exchange ? > > > *GuidoElia > HELPPC > * > > > > ------------------------------ > > > *Da:* Steve Szabo [mailto:[email protected] <[email protected]>] > *Inviato:* domenica 27 giugno 2010 5.20 > *A:* MS-Exchange Admin Issues > *Oggetto:* RE: Migration : pop3 to Exchange > The way I would do it would be to get everyone on 2007 first, with the > current POP settings, adding Exchange to the profile. Use cached mode and > drop the POP mail into the OST file. Make Exchange the default account. You > do not mention if they will be taking on your own domain name for mail, or > if they will be retaining their own. In either case, you should give them > both addresses, making the appropriate address the primary. > > Make your necessary DNS changes. > > Wait about a week, ensuring everything is running as it should be. At that > time, you should be able to remove the POP account from their profiles, and > have all the mail flowing through your Exchange server. > > It is a bit of work, but it will ensure that they do not miss a single joke > e-mail coming into their addresses. > > > \\Steve// > > > *From:* De Williman, Shih [mailto:[email protected] <[email protected]>] > > *Sent:* Saturday, June 26, 2010 10:26 PM > *To:* MS-Exchange Admin Issues > *Subject:* Migration : pop3 to Exchange > > Hi , > We are in the process of bringing on a small company to our exchange 2003 > network. 20 users currently using pop3 to download mail from their current > internet provider to various mail clients (OE/Office2k3/Office2k7) > > I don’t believe there’s any concenrs re: public folders or shared > calendaring as such with pop3, but I want to make sure that its not just > lowering MX TTL on the provider side, redirecting their mx records to ours > (Postini) & completing the set up of OL2k7 clients to look to > Exhcnage/convert-mounting their dbx-pst files to their OL clients. > > Slapstick recommends pop3-exchange connectors but I think that’s only if we > intend on keeping the ISP mail & not performing a clean cutover. > > Any gotchas I have to worry about? Thanks in advance, > > > > >
