Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Firday Night Lights Migration... VMBES, OWA, Smartphone issues found.
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
Firday Night Lights Migration... VMBES, OWA, Smartphone... - 28.Jul.2008 10:16:09 AM
|
|
|
joeya
Posts: 17
Joined: 30.Dec.2006
Status: offline
|
I went to migrate all my mailboxes starting at 8pm friday night and figured they'd all be moved by midnight or so. nope. we only have 38 mailboxes, and only about 6 of them were over 1.5 gigs in size, and I didn't finish until about 5am. The issues I ran into were probably run of the mill but I wanted to share them. 1. Blackberry - we use professional software, not Enterprise Server, but 2007 does NOT work properly on 32bit so you have to download the MAPI item for the Blackberry server ( ExchangeMapiCdo.MSI ), and then properly set up the MAPI client to work and point at the 2007 server. (I used the Legacy Blackberry Manager MMC snap in to do it.) And then I rebooted the server after all the mailboxes were on the new exchange server and tested. (also verified they were showing the proper server attachment.) 2. OWA access looks so much nicer and seems to work so much better ... UNLESS the user has somehow blocked inherited permissions, and can't log into OWA. I found the fix for that here. Not sure how they managed to block inherited permissions in AD, but it happens. 3. Smartphones using activesync was my biggest problem in the beginning, but after I reloaded the websites, installed the proper certs and made sure that my "outside" owa server had an internal and external, and my mailbox server ONLY had an internal address, they all came up like champs. The final lesson learned was that you can manage mailbox sizes at the USER LEVEL or you can manage them at the Server Configuration / Mailbox / Storage Group LEVEL. I found out that only ONE of my users had broken the default limits set there, and his mailbox was completely LOCKED DOWN. he could access, but no send, no receive and no SYNC since it was over its limit. so he cussed me out until I found the settings. needless to say I will be following his progress closely with his plan to shrink his mailbox size down as I lower the limit down tighter and tighter... Boy I'm glad THAT is over with.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|