?
Solved

Move to Office365 from SBS 2008

Posted on 2013-05-26
3
Medium Priority
?
498 Views
Last Modified: 2013-11-20
Hello,

I'm having a rather confusing problem.

I've moved a clients exchange server to Office 365 from SBS 2008 (Exchange 2007) as we'll shortly be migrating to a Server 2012 environment.  

The problem is that when I set up an account from a users desktop (using autodiscover) the mailbox is found but the password will not except.  This only happens from within the local network.  If I create a profile on my personal computer (not attached to any domain) everything works just fine.  

I've since shut all the exchange services and IIS services related to exchange off.

still no luck.

Any help would be greatly appreciated.

thanks.
0
Comment
Question by:Bullfrog28
3 Comments
 
LVL 1

Expert Comment

by:SylvainSSiri
ID: 39198101
Might sound stupid but did you check whether you got administrator rights on that account?Even on the network account?And what about the firewall?
0
 

Author Comment

by:Bullfrog28
ID: 39198109
Yes I've cover that so far.  

it looks like the exchange 2007 system on sbs 2008 is still trying to take over the settings.  I'm not sure how to get past that.
0
 
LVL 26

Accepted Solution

by:
ronnypot earned 1500 total points
ID: 39198625
Hi,

there are indeed some configuration settings that need to be changed otherwise autodiscover will always try to connect to the local SBS server.

See this blog post for details: http://www.mcbsys.com/techblog/2011/08/using-office-365-in-an-sbs-2008-environment/
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
In my humble opinion (IMHO), TouchDown from Symantec is the best in class for this type of application, but Symantec has end-of-lifed it and although one can keep using it, it will no longer be supported or upgraded.  Time to look for alternatives t…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
The video will let you know the exact process to import OST/PST files to the cloud based Office 365 mailboxes. Using Kernel Import PST to Office 365 tool, one can quickly import numerous OST/PST files to Office 365. Besides this, the tool also comes…
Suggested Courses

588 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question