Migrate SBS 2008 with exchange 2007 to office365

Hi, we have a sbs 2008 with exchange 2007 the boss got the idea to move the E-mail to office 365, i have done some research but still have some questions, now i am not an expert on exchange, could some one tell me if this is a straight operation going from
exchange 2007 to office 365, is it supported or do we have to move to exchange 2010 and then to office 365?
Thank you very much in advanced.

Yes, going from Exchange 2007 to Office 365 is supported. You want to run a Migration.
Check out this link for exact instructions on what to do for the migration:
http://help.outlook.com/en-US/140/ms.exch.ecp.emailmigrationwizardexchangelearnmore.aspx
Then, when you are ready to setup Outlook with Office 365, check out this link to make Outlook use the public Autodiscover rather than SBS Autodiscover:
http://www.mcbsys.com/techblog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/
I just did a cutover migration from SBS 2008 to Office 365 using both these websites and it went off very nicely.
Good luck on your migration.
Oh, and if you only use Office 365 for email, it is $4 a month per user.

Similar Messages

Migrate SBS Server 2008 with Exchange 2007 to Exchange 2013

I have looked at the documentation to co exist 2007 and 2013. However I am concerned as it talks about changing the dns name to something like legacy, as the dns name that is used for outlook to connect is the name of the server. So here
is my question. Would I have to change the name of the actual server itself? and if I choose not to, and use a new name for the 2013 server, such as mail, would the users that get migrated, would they automatically update the
name change? Also note the SBS server with exchange 2007 is also their file server at present but will be changing.

Hi ,
Thank you for posting your question in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback
on our support quality, please send your feedback here.
Andy Qi
TechNet Community Support

SBS 2008 and Exchange 2007 intermittent Email Issues

Hello
I am having an issue with my SBS 2008 Server and Exchange 2007. After setup, the mail seems to work great for about a week, then the mail just quits working. To get it working again, all I have to do is reboot the server and mail starts working
again. When looking in the event logs, all I come across is transport.exe errors. Any ideas on why it works for 5-10 days, then just quits working? Any help or insight would be much appreciated.
Thanks All

Larry
Here are some of the errors that i am getting:
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\NETWORK SERVICE; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: edgetransport.exe
Client ProcessId: 0
Client ApplicationId: Client=Transport
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\SYSTEM; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVERNAME/cn=Microsoft System
Attendant.
Error: -1069
Client Machine: SERVERNAME
Client Process: Microsoft.Exchange.ServiceHost.exe
Client ProcessId: 0
Client ApplicationId: Microsoft System Attendant Service Let
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account WIS\JLange; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: w3wp.exe
Client ProcessId: 0
Client ApplicationId: Client=ActiveSync;UserAgent=Apple-iPhone5C1/1002.329;Action=User=jlange&DeviceId=ApplF18KM7FHFH1C&DeviceType=iPhone&Cmd=Sync
These are a few errors that i get when the mail isn't working. When it stops of the server, the outlook clients show the exchange server disconnected, and active sync will not work either. I can still remote to the server, so i dont think its
an internet connectivity issue. Let me know if you have any other questions. Again, the mail seems to work for about 5-7 days, then i have to reboot the server to get the mail flowing again. Any help or direction would be appreciated.
Thanks for Looking

Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

HI, i need help here
I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
flow went back to normal. We then remove the program from the control panel.
Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
Much Appreciated

Symantec's support group should be able to tell you what happened.
--- Rich Matheisen MCSE&I, Exchange MVP

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

Anyone done SBS 2008 to Exchange 2013 migration - disable IPv6 on SBS?

IPv6 enabled on ours without any problems. THanks for the links Anil, had not heard of those problems before

Well, considering over the scenario you have mentioned, I would like to refer you on this informative article that covers few parts of causes when disabling IPV6 on Exchange 2013 Server installation : http://mike-graham.co.uk/blog/2013/08/12/disabling-ipv6-on-exchange-2013-servers-causes-problems/Here is a well documented technet resource that also provides step-wise instructions when proceeding to migrate from Exchange 2007 to 2013 by checking all the required prerequisites : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migra...Moreover, while need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on LepideMigrator for Exchange tool that provides a hassle-free environment to get this job done without having downtime or any further interruption.

Migrate SBS 2008 to Server 2012 R2 Std

Thank you for your reply. The Setup is a 2012 HV with three VM's = DC, Exchange and Terminal Server. The Exchange will be 2010. It was decided to stay with Emails on the Server by the company director, we don't require office 365
I think the migration of 2008 to 2012 dc should be fine, but it was migrating the exchange 2007 to exchange 2010 that I was not sure about, my notes I have were actually for 2003 sbs's that were going to use office 365 so that's why I was enquiring after the email migration
thanks

Hello
We have a SBS 2008 Server that is going to be migrated to Server 2012 R2. The 2012 has two virtual machines - one for the new Domain and the other is for email exchange. We have instructions for migrating a SBS 2003 Server to 2012 Server that we were told was successful - can I apply these same steps to a SBS 2008 Server? IT involves promotion 2012 to DC, migrating AD (FSMO, scheme master global catalog) and migrate dhcp.
for the emails, is there a MS guide to migrating SBS 2008 mailboxes to the 2012 R2 email server?
Thanks
This topic first appeared in the Spiceworks Community

Outlook 14.4.8 not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox"

Outlook 14.4.8 on iMAC Retina and Yosemite 10.10.2 is not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox".
Accessing Mails with Webbrowser and from Windows Outlook is working correctly.
All Macs (also the ones with OS 10.6.8) do not anymore show any new messages in inbox.
Restarted Server, tried to disable autodiscover on macs and deleting/adding account and repairing database does not fix the problem. Also restarted server several times.
We have the same problem on 2 imacs retina with yosemite and on 2 mac pro with 10.6.8 and different office 2011 versions.
i tried to configure the exchange account in apple mail on yosemite and it also states "connected" and does list some folders but no new mails are getting in.
Windows clients and outlook on them works and syncs fine, and also when connecting via webbrowser at owa it must be a mac-specific/webdav issue.
exchange 2007 Sp3 Version 8.3 (bild 83.6) and Update Rollup 15 for sp3 (automatic updates "HIGH" for server and clients)
there is one update popping up again and again even after everytime successull installation: Windows Mlicious Software Removal Tool x64 - October 2010.
i tried to configure a new user with empty mailbox and configured it with microsoft mail (mac - yosemite) as exchange and was able to send a mail from there (even if quite delayed).
but there are not coming in any mails.
same exchange accounts triggered by imap do work and also via owa.
Exchange Accounts in Outlook for MAC and also in Mail (Yosemite) do show the folder structures but there is no mails showing up. I can send mails from the exchange accounts created but they seem to be processed with a delay of like 15minutes and outlook
is giving error "end of file reached" but messages are send after some time.
Does seem like EWS is extremely slow, to slow perhaps to sync and therefore ending in timeout.
Also i cannot reach the server from externally over ssl https 443. if testing port 443 of exchange from outside the port seems closed even firewall settings of sbs 2008 and sonicwall ports are correctly open.
could it be there is something in regarding webdav which is very slow and leading to timeouts ?
in application log i do have the following two information events every few minute:
The Exchange Web Services started successfully. Event ID 1
and
Process STORE.EXE (PID=3688). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SERVER.org.local CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
Errors in Application log:
The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section
The entry <C:\WSUS\WSUSCONTENT\CONTENTFOLDERACLSCHECK.TXT> in the hash map cannot be updated.
An exception Microsoft.Exchange.Data.Storage.ConversionFailedException occurred while converting message Imap4Message 69447
Also outlook 2011 clients are asked by time to time to reenter pwds and errors like "connection is closed. 13"
Faulting application taskeng.exe, version 6.0.6002.18342, time stamp 0x4cd34898, faulting module ntdll.dll, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc000071b, fault offset 0x0000000000082445, process id 0x3288
Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.
Backup Exec:
FULL_BACKUP -- The job failed with the following error: A failure occurred querying the Writer status.
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The
error returned from CoCreateInstance
Exchange VSS Writer (instance 2d932ef8-6319-4ab8-a45f-1242480b44ad:15) failed with error code 1295 when processing the backup completion event.

Hi,
Since Outlook running on Windows works well, it seems an issue on the Mac side. I suggest ask Mac for help so that you can get more professional suggestions.
More information for your reference:
Please try to verify whether there is any expired certificate from the computer personal store.
If it is the case, please remove them.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

ICal still does not sync with exchange 2007 in Lion

Dear,
In Snow Leopard, iCal was not syncing with Exchange 2007. I read a lot of things on this and it all led to recurring events. Indeed, after deleting them, things started to work. But I cannot delete recurring events! I need them!
Seeing that there was soo much talk on this all over on apple, I assumed that Apple would fix it. Instead, all we're seeing is some enhanced UI.
Can somebody at Apple please make sure that this thing finally gets fixed? Really, how hard can it be, knowing that the hardware based i devices can sync without any trouble?
Just for extra information, so you know what direction to look for:
I have Windows SBS 2008 in Dutch language. Timezone is Brussels. Exchange 2007 and all updates.
The system is running a self signed certificate
Outlook works fine on the Mac. I don't want to use Outlook on the Mac but am forced to at the moment.
Mail/Addressbook sync fine. Only Outlook doesn't!
I did try deleting recurrent events and this worked for a day. Basically stopped working I think when I added again those recurring events.
There are some errors in the console:
21/07/11 11:42:36,563 iCal: Couldn't find an NSTimeZone to match the SerializableTimeZone
21/07/11 11:42:36,563 iCal: WARNING: Failed to find TimeZone Identifier for Windows MeetingTimeZone: (GMT+01:00) Amsterdam, Berlijn, Bern, Rome, Stockholm, Wenen
21/07/11 11:42:36,580 iCal: error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken." UserInfo=0x7fbe94adb8b0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7fbe94102d40>, NSLocalizedDescription=iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken., NSLocalizedFailureReason=De account 'Exchange' kan momenteel niet worden bijgewerkt.}
Please fix this,
Guido
Message was edited by: guido4096. Added error message

Hi all,
I do have exactly the same problem.
But I am adding a new flavor, but I can not understand it.
I've setup two Exchange calender connections. Both servers are inhouse. The setup of the Exchange servers are most likely the same.
But one works and one not! How could this be explained?
I like to express my deep disappointment about iCal and partly Apple Mail. It is unbelievable for me, that years after Apple's cooperation with Microsoft there are still such problems.
I like my Macbooks and I certainly have the absolutely full bandwidth of all Apple products in my household and companies. But I think I have to go back to Microsoft and Sony Laptops in the near future.
Although this kind of bugs are small one's, but the hurt constantly. Apple - please fix that.
Here just for the interested reader is my console error message:
3/15/12 11:51:29.819 AM iCal: error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal can’t refresh events in the calendar “Kalender”." UserInfo=0x7f856d4bddb0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7f856c5ca060>, NSLocalizedDescription=iCal can’t refresh events in the calendar “Kalender”., NSLocalizedFailureReason=The account "DR InfoDyn" currently can’t be refreshed.}

Problems doing activesync with Exchange 2007 on AT&T Centro

I have an AT&T Centro and a PC laptop. I recently changed jobs and now have a Mac OS X (10.5.8) at work. I immediately was able to set up ActiveSync on my Centro in order to obtain emails and update contacts and datebook. However, last week, I was migrated over to the Exchange 2007 server, and even after changing the mail server name, I keep getting the message "You are attempting to access a web page that has an invalid security certificate (server name mismatch)."
I have contacted our technical support people, who tried to tell me that they only support Blackberries and iPhones. However, they did agree to review the documentation I found online, which indicated that the certificate would need to be reissued to the correct site name, or that the server should be aliased externally and internally.
When I sent this link to them, instead of following these directions, they replied that another employee had a similar problem and was able to solve it by downloading the Build 86 VersaMail update on smartphone. However,when I looked into this, it was only for Sprint users, not AT&T.
I have spent many hours trying to solve this problem and don't know where else to turn. I have reviewed many of the forum items and can't quite find my situation.
By the way, the laptop stopped syncing with the phone when I began doing ActiveSync with the Mac. Now that ActiveSync no longer works with the Mac, I am able to sync again with the laptop. However, I'm less worried about that and more worried about being able to sync with the Exchange server, since that is the only way to access emails when I am away from the office and don't have a wireless connection on my laptop.
Can anyone help?
Thanks.
Post relates to: Centro (AT&T)

You will need to have your IT folks provide you with the cert & you can create your own palmos version with this tool http://kb.palm.com/wps/portal/kb/common/article/43375_en.html
At that point, sync the newly created palm compatible certs.pdb to the handheld (not to the memory card) and when you go to your mail website in blazer, you should be able to go to https:// & have a blue lock symbol.Give your versamail EAS sync another shot as well. Also, while not supported, I have seen people have luck installing the versamail 401 update on verizon 755p even, so could give it a shot on your at&t centro.
Note that the latest osx (10.6 is it?) release has removed the palmos sync conduits from their isync program.

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
Client Connectivity in an Exchange 2013 Coexistence Environment
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Coexistence with Exchange 2007 and 2013

Hi everyone ,
i migrated this week to exchange 2013 in coexistence with exchange 2007 ,,,, is it normal that i cannot create anymore a mailbox on the exchange 2007 server even with the console (ecp) in 2013 ??
thanks

Provided an answer on your other thread
https://social.technet.microsoft.com/Forums/en-US/393a2406-5202-4d21-9583-2e4beed574be/create-mailbox-on-2007?forum=exchangesvrgeneral
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Migrate SBS 2008 to new hardware

We have an SBS 2008 installation and are testing a disaster recovery solution by re-installing in Migration Mode.
Step 5 in the migration document from Microsoft discusses;
Demote and remove the Source Server from the network
We'd like to fully test this and get the backup box up and running before signing it off as a working solution.
Our concern is that, even if we isolate the test machine on a difference subnet from our production LAN, there is some kind of licensing consequence for our running box - via some kind of de-activation signal sent over the net, perhaps - should we continue
through the final steps.
Can anyone confirm or deny whether any kind of de-activation occurs? Perhaps paranoia, but thought best to check since we really can't have our live systems shut down.

Hi,
Before going further, would you please provide more detailed information about your concern? It’s difficult to understand your needs for me with the information you mentioned. For details about
how to migrate SBS 2008 to new hardware, please refer to the following articles.
Migrate Windows Small Business Server 2008 to New Hardware
http://technet.microsoft.com/en-us/library/cc664208(v=ws.10).aspx
Moving SBS to new hardware
http://msmvps.com/blogs/kwsupport/archive/2005/06/18/53958.aspx
Hope it helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Does anyone know how to get apple mail in Lion to connect with Exchange 2007?

Does anyone know how to get apple mail in Lion 10.7.2 to connect with Exchange 2007? It worked perfectly with Snow Leopard... upgraded to lion and it won't work. We use Exchange 2007 with SP 3 and Rollup 4. Won't connect... and I can't get Apple to give me any direction.

We finally got it to work today. We had to call and pay for the microsoft support service, but the issue was on the server end. We had to go into the iis manager... went to sites... when to default website...and changed the SSL settings for Auto Discover, EWS Exadmin, echange, exchweb, owa... and the rest..
Change the settings to ignore client certificates.
Problem solved. Can finally send and receive.

Has anyone managed to create an email account on the OS X mail client with Exchange 2007?

Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen

jthurner wrote:
Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen
No workaround needed, open Mail, Contacts and Calendars (in System Preferences) select Exchange, enter your email address and password, opt to setup Contacts and Calendars as well as mail and hit enter. That should set it up (assuming your apparently witless IT dept has setup the autodiscover record correctly at their end)

Migrate SBS 2008 with exchange 2007 to office365

Similar Messages

Maybe you are looking for