Hi,

I am trying to migrate Users from Acquired domain to Office 365 and also migrate users from On premises to Office 365 on same tenant.  Current Simplet Exchange Migration or Staged Exchange Migration is not suitable in our situation (Do not have control on acquired domain and we have some resistance on access to the domain).  Current acquired domain messaging environment is Exchange 2010.  I am planning to export the acquired domain users mail data into PST and inject to Office 365.

My concern is how to set co existence untill we complete Export and Import mailbox on to cloud?  

a. Set forward address on acquired domain users to forward it to cloud email ID.  But how forwarded email appear on Cloud mailbox?

b. If I set targetaddress attribute value on acquired domain then it will not drop email on on-premises mailbox.  This is going to be issue untill we say user to access their cloud mailbox.

C. How X500 email ID set on acquired domain for coexistence being a period till I complete export/Import process.

Thank you in advance.

Murali

This is one of the most stupid and dumbest things that I ever seen or heard of.   You have to use something called PowerShell to perform some admin task on your account.  

They told me that this was for small business owners that don't need and IT staff, yet you are trying to make me a programmer to perform some simple account management task.  I seen phrases like "Easy to use...", "No training needed", "Get the value and simplicity of Microsoft® Office 365 for small businesses"

There is an outstanding Office 365 User Guide (337 pages) but no where does it talk about PowerShell commands.

Microsoft is great in coming up with new technology but terrible in making it usable.

Ken,

I would suggest that 80-90% of what needs to be done with the Small Business Office 365 product can be done without ever needing to know Powershell. However Office 365 is a common product that needs to support both enterprises as well as small business. This article is more aimed at the enterprise users who probably want to get much deeper into the configuration of Office 365.

Powershell is available on most modern Microsoft platforms including those on premise like Windows Server and Small Business Server. It is not something unique to Office 365.

I doubt there is any technology that does not come with a certain level of technical complexity. That is why it is important to use the services of a good IT provider in your area, of which I'm sure there are plenty.

Failing all that don't forget there are plenty of free resources available to you for assistance and if you need a greater level of support then enterprise plans may be a better option as they include support.

You need to remember that Office 365 products like Exchange, SharePoint and Lync are enterprise versions that are being made available down to a single person for less than $10 per month. That is excellent value for the power that you receive and much more when compared to what you could do on site and with other providers in my opinion.

So in summary, if you make a product too basic you loose some of the granularity to customize it, if you make it too complex people struggle to configure it. You can't have it both ways unfortunately in general. You need to strike a balance and that is what Office 365 provides between with all its different offerings I believe.

Thanks

Very good answer.  It is not what I wanted to hear but a it is a good responce containing some good advice.

Ken: where do you get a copy of "Office 365 User Guide (337 pages)"?

I can't remember where I got it from on this site.  But here is a link to my copy:

dl.dropbox.com/.../O365UserGuide.pdf

Thanks much!