Office 365 Deployment w/Decommissioned Exchange 2003 environment

Hello,
I'm having an issue creating Office365 mailboxes. Here's my situation:
In 2011 we we migrated off of an on-premise Exhange 2003 server and on to Google Apps (Gmail). To my knowledge the on-premise Exchange 2003 server was fully decommissioned and removed from our network. Now we're try to move from Google Apps (Gmail)
to Office365. I've set up AD synchronization and all my AD accounts synchronize as expected. However, only some of my synchronized accounts are provisioning mailboxes correctly. After some troubleshooting on the Office365 community we were
able to narrow down the issue: http://community.office365.com/en-us/f/156/t/252194.aspx. It appears that the only accounts that are successully provisioning mailboxes are accounts that DID NOT previously have a mailbox associated on the on-premise
Exchange 2003 server...Accounts that DID hold a mailbox on the on-premise Exchange 2003 server are NOT being successfully provisioned with an Office365 mailbox. My understanding is that this is actually expected functionality...Per MS support techs:
If an AD account has attributes indicating an on-premise Exchange server, then Office365 will not provision a mailbox until the on-premise mailbox is migrated. The issue I have is, I do not have an on-premise mailbox to migrate or an on-premise Exchange
server at all.
My on-premise Exchange 2003 server no longer exists. What attributes do I need to remove and/or reset on my accounts for Office365 to be able to provision a mailbox correctly?
Thank you in advance!

Hi,
What’s the error message do you receive when trying to create the mailbox?
You can check the user’s AD properties by:
ldifde -f c:\<Name of User>.txt -d "distinguishedName of User"
Here is the detailed steps for getting the
distinguishedName of a user:
a. Run the Adsiedit.msc from a command prompt.
b. Expand “Domain”->”DC=domainName,DC=com”->”CN=Users”
c. Right click on ”CN=the problematic user name”, click “Properties”.
d. Find the attribute “distinguishedName” attribute. Double click copy the value of it.
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

Exchange 2010 deployment in Exchange 2003 Environment

Hello,
I have recently installed Exchange 2010 in an Exchange 2003 environment. I need some help migrating all my settings over to Exchange 2010
-- mailboxes, recipient policies, offline address book, free/busy, etc.
I have looked at these following TechNet sheets for assistance, but getting a bit confused:
http://technet.microsoft.com/en-us/library/aa996719.aspx (Exchange 2013 System
Requirements)http://technet.microsoft.com/en-us/library/ee332348.aspx (Upgrade
from Exchange 2003 Client Access)http://technet.microsoft.com/en-us/library/aa998186.aspx
(Exchange 2003 - Planning Roadmap for Upgrade and Coexistence)http://technet.microsoft.com/en-us/library/ee681662.aspx (Install
Exchange 2010 in a Mixed Exchange 2003 and Exchange 2007 Organization)
I have two domain controllers. Exchange 2010 is not installed on a DC, but Exchange 2003 is on one of them. I want to eventually decommission
the Exchange 2003 environment and implement and Edge Server in its place. Exchange 2010 is installed on a Virtual Machine. It's running SP3, the latest service pack. Exchange 2003 is on a physical machine and it's running SP2.
Please help me simplify what exactly I need to do to migrate 2003 configurations over to 2010.
Thank you for you much appreciated assistance.

Hi
I would install a new DC and seize the MSO roles to the highest server. Remember you can install server 2012 but not R2 yet.
You can setup your connectors on exchange 2010 to send/receive mail to the internet. make sure your ISP allows the new server.
You can also setup a routing group connector so that mail flows from EX2003 to EX2010 and vice versa during your transition period.
Remember to replicate your public folders to the new server and if you have a lot of data be patient. Once you happy with everthing then decomission the old DC.
Hello,
All FSMO roles are transferred (not seized) on my Windows 2008 R2 Standard Domain Controller. I transferred all the roles off my Windows 2003 Domain Controller. The W2K3 DC is also my Exchange Server 2003 SP2. I specifically did not want to
install Exchange 2010 on a DC. It's on its own member server.
Should I make the Exchange 2003 Server a Front-End Server when I create a routing group for mail flow to Exchange 2010? I want to eventually implement an Edge. Also, can I have mail flow from the Internet directly to the Hub and bypass the Exchange
2003 mail flow?

Anti-Virus Software Needed @ Work in a Windows/Exchange 2003 Environment?

I'm taking delivery of a new 24" iMac, and will be using it at work in a Windows/Exchange 2003 environment. I'll be using VMWare Fusion, and Win XP Pro 32 bit to run our business-critical applications. Also, until Office for Mac 2007 is released in January, I'll be using Office 2007 (including Outlook 2007) from the Windows partition. I'm the "pioneer" (the first) Mac user at our company and want to get this right. Regarding antivirus sofware (which I've never had to worry about on my home G5):
1.) Do I need it at all?
2.) Do I need to get it for the Windows partition? the OSX partition? both?
3.) If I need anti-virus software for either or both, what is recommended, given my workstation/network setup? will the same product work for both OSX and XP? or do I need separate programs for each?
Thanks!

For the windows antivirus software I would avoid Norton. I've had problems with every version of it that I've used, both on my own pc and others. I've also had problems with Mcafee. Go with either ZoneAlarm Internet Security Suite, Kaspersky Antivirus, or AVG from Grisoft. AVG has caught things that norton doesn't. I use the free version in conjunction with ZoneAlarm on my XP machine, but they have business versions. Zonealarm's firewall works very well. The inbound/outbound program control is hard to beat. Their anti-spyware/adware solution leaves a little to be desired though. For the ultimate antivirus protection on a PC, you really need to run redundant programs.
However for Mac, I can't recommend anything, since I'm not yet a mac user. Not yet.

Office 365 Deployment Verification

I've been tasked with identifying which users have office 365 deployed. I've found a great license spread sheet that queries against the tenant and pulls back licensing details such as provisioning status: success, disabled, pending input, disabled. I don't
think that this just tells me the status of the license but not the status of the deployment.
Does anyone know how to run a report that will give me installation status? Is this possible?
Thanks in advance.

Hi,
Do you mean you'd like to audit the status of Office installs each user has installed? Based on my research, at the moment there isn't a way to create or pull such a report.
Anyway, this is the forum to discuss questions and feedback for Microsoft Office client. There is not so much about Office 365
Admin/hosted aspect here, I would suggest you to post in the dedicated forum of
Office 365 Community, where you can get more experienced responses:
http://community.office365.com/en-us/f/default.aspx
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Decommissioning Exchange 2003 after Office 365 Migration

Hello,
My company recently migrated from Exchange 2003 to Office 365 and are working on decommissioning our on-premises Exchange 2003 server. We believe everything is ready to go, however this Microsoft article: http://help.outlook.com/en-us/140/ff959224.aspx#nextsteps has
a big Caution box warning of "unintended consequences" and recommending I contact Microsoft Support:
I've tried my Office 365 support options, but they only tell me that Exchange 2003 is no longer supported and they can't help me, despite the fact that I'm trying to remove it, not maintain it. So
I'm allowed to pay for a new service, but shouldn't expect assistance in safely moving from my old service...
Regardless, they directed me here, so I was hoping someone might be able to advise about what these "unintended consequences" actually are so I can feel fully prepared to decommission.
Thanks in Advance,
Jim

Hi,
After you’ve verified that all e-mail is being routed directly to the cloud-based mailboxes, completed the migration, and no longer need to maintain your on-premises e-mail organization or don’t plan on implementing a single sign-on solution, you can uninstall
Exchange from your servers and remove your on-premises Exchange organization. For more information, see the following:
How to Uninstall Exchange Server 2003
http://technet.microsoft.com/en-us/library/bb125110(EXCHG.65).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Decommissioning Exchange 2003 Server

Follow the Exchange Deployment Assistant to the letter and you will not have issues.
http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspx
(after the migration it shows you how to decommission it properly.)

Hello All,
My Exchange server setup is in coexistence mode (1 Exchange 2003 server entp and 2 Exchange Severs 2010 DAG is in place)
only 2 mailboxes are left on Exchange 2003 and will be moving them soon.
So I wish to know the what all precautions I should be take and what all action items are there.Recommended link will do
regards
Atul A
This topic first appeared in the Spiceworks Community

Exchange 2010 System Public Folders trying to replicate to decommissioned Exchange 2003

I was checking the mail queue on Exchange 2010 and noticed several hundred messages in retry. Looking at the messages I found that they were all destined for an old 2003 exchange that has been decommissioned. I looked at the System Public Folders and found
replication is set up on "events root, OWAScatchpad, SchemaRoot, and Store Events. They are set to replicate to the old mail server. When I try to remove the old server from replication it gives me an error;
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Set-PublicFolder
Failed
Error:
You must specify a value with the Replicas parameter.
OK
Not sure where to go with this error. Could someone point me in the right direction?
Thank you,
Wade Harris

Hi,
For this issue, I recommend you add an Exchange 2010 public folder database to the replica list and then remove Exchange 2003 server from this list to check result.
I tested in my lab, and I got the same error with yours, we need to keep at least one public folder database in the replica list.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

How do you connect a PowerBI report to SharePoint in my Office 365 deployment

Hi
I'm trying to find details on connecting a SharePoint Survey in Office 365 to PowerBI in the same site in order to enable automated reporting of the survey results over time by each responder
Thanks
Paul

Hi Paul,
Power BI for Office 365 is a self-service business intelligence (BI) solution delivered through Excel and Office 365 that provides information workers with data analysis and visualization capabilities to
identify deeper business insights about their data. With Power BI for Office 365, you can connect to data in the cloud or extend your existing on-premises data sources and systems to quickly build and deploy self-service BI solutions hosted in Microsoft’s
trusted enterprise cloud.
You can have a look at a demonstration of Power BI for Office 365, showing you how all the various tools and technologies work together: Power Query, Power Pivot, Power View, Power Map, Power BI sites, Data
Management, Power BI Admin center, Power BI for mobile, Power BI Q&A:
http://www.youtube.com/watch?v=_WprkRAq6BQ
For more information, you can refer to these blogs:
http://social.technet.microsoft.com/Forums/en-US/17244a02-06f3-4a1d-b9b2-49a40d99294e/if-i-use-sharepointonline-list-as-my-data-store-how-do-i-do-the-datarefresh-in-power-bi-for-office?forum=powerbiforoffice365
http://sharepointpromag.com/office-365/power-bi-office-365-what-you-need-know
http://office.microsoft.com/en-us/excel-help/power-bi-for-office-365-faq-HA104219793.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Office 365 Shared Mailbox in Exchange Admin

I am creating shared mailboxes in my Office 365 account and I want all the users on my domain to have access to all of the mailboxes. Is there any way I can set this up automatically, instead of manually adding each user to each shared mailbox and
then having to remember to add all new users into each shared mailbox?
Also is there anyway I can only allow them to have View-Only permissions on these mailboxes?
Thanks

Hi Lauren,
the cmdlet add-mailboxpermission is avaliable for Exchange Online, too.
http://technet.microsoft.com/de-de/library/bb124097(v=exchg.150).aspx
So you can receive a list for all your users mailboxes, and then you run add-mailboxpermission to all of them.
$mymailboxlist = get-mailbox -resultsize unlimited
$mymailboxlist | foreach-object {
                 $resourceMailbox = $_
                 $mymailboxlist | foreach-object {
                         $permittedMailboxAccess = $_
    add-mailboxpermission -identity $resourceMailbox -user $permittedMailboxAccess -accessRights FullAccess -InheritanceType All
In that example script you may ignore warning messages that a user already had access to her own mailbox.
You may add logic to the code to avoid that :)
If you do not know how to connect to Exchange online (required to run that code) please see
http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx
Regards,
Martin

Connect Lync 2013 online (office 365) to on prem exchange 2010

Not sure which forum this belongs in, exchange 2010, office 365 or here so I'll start here.
I want to connect my lync 2013 clients to my on prem 2010 exchange server. I'm not exactly sure where to start because there is so much information out there I'm kind of confused as to where to start.
Thanks!

A good place to start: http://technet.microsoft.com/en-us/library/jj945633.aspx & http://technet.microsoft.com/en-us/library/jj205403.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Office 365 Deployment with new local domain

I just started working for a company that has somewhat implemented Office 365 to about 100 users. They are mostly using it for Exchange Online. No ADFS or AD Sync has been done between the on-premise domain and Office365.
The same user accounts do exist in the local domain.
Once we get ADFS and AD Sync working what will happen between the Office365 accounts and the local accounts. For instance, in Office365 we have
[email protected] and locally we have a user
[email protected] Will the accounts just sync together and use the information from the local domain since the IDs are the same.

Hi,
This is the forum to discuss questions and feedback for Microsoft Office client. There is so much about Office 365
Directory integration aspect here, I would suggest you to post in the forum of Office Community, where you can get more experienced responses:
http://community.office365.com/en-us/f/613.aspx
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Migrate Office 365 To On-Premise Exchange 2013

hello
My client attempts to migrate the mailboxes hosted from Office 365 to Exchange 2013 on-premise hosted in the client's company.
However, despite all attempts , it appears that no procedure works correctly. All's time , something wrong appears Inside the process.
Indeed, on Office 365 we don't see the servers in our on-premise exchange 2013.
the Exchange Hybrid are set correctly and to exchange 2013 migration attempts to run Office 365. (MRS proxy select)
All servers are in the same Update. My client can't update with the last CU6 all server and want to stay with the CU3
Thanks for your read and for your help
Best regard
Alexis

Bonjour,
J'ai deja réalisé ce type de mission, si celle-ci est tout à fait possible en utilisant uniquement les outils intégrés à Exchange, elle nécessite beaucoup de préparation, notament en terme d'AD, et selon la configuration dans laquelle vous êtes, peut etre
*non* transparente pour vos utilisateurs.
" My client can't update with the last CU6 all server and want to stay with the CU3"
C'est par contre un point plus que géneant, le CU3 n'est plus supporté par MS, la compatibilité avec O365 n'est donc pas garantie.
Si vous souhaitez un echange plus sérieux sur ce sujet, vous pouvez me contacter.
Bruce Jourdain de Coutance - Consultant MVP Exchange http://blog.brucejdc.fr

Office 365 Hybrid Setup With Exchange 2010

I have onpremis exchange 2010 which is configured as hybrid with o365.some of my users are in o365 cloud.Now when im checking on the o365 admin portal dns settings, its saying we need to add some dns records in my public dns hoster.But since im having hybrid
setup, i cant understand that thing.
Darshana Jayathilake

Hi Darshana,
Since your question is more related to Office 365, I'd recommend you post it to the Office 365 Community forum:
http://community.office365.com/en-us/f/default.aspx
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Shutting Down Exchange 2003 System after move to Office 365

We recently moved our entire exchange 2003 environment via a consultant to Office 365. The migration went fine but now i am trying to shut down my old Exchange 2003 servers. I know i cant shut down the individual 2003 servers without
removing the old mailboxes themselves from the stores. I have attempted to remove some mailboxes from some of my accounts to do this but it removes the proxyaddress field on the user objects themselves. Is there a way to delete the mailboxes
without the proxy address being deleted in ad? Without that all my users email addresses are defaulting to the onmicrosoft address, which is really annoying We are using dirsync for user updates and groups, so im losing the default email address
when it syncs up to office 365. And yes I know about adsi edit to put it back it but that's not viable for 500+ user accounts individually.
Tried asking this on office 365 forums but they shuffled me off to here.

When your mailboxes were moved to Office 365, your directory should have been updated so it pointed to the mailboxes in Office 365, not to your local Exchange 2003 mailboxes. Just thinking this through, I think your consultant didn't do a complete
job. With the Exchange 2013 PowerShell tools, you should be able to update your 500 accounts so they point to the proper system for the mailboxes.

Office 365 Deployment w/Decommissioned Exchange 2003 environment

Similar Messages

Maybe you are looking for