Quantcast
Channel: Exchange Online migration and hybrid deployments - Recent Threads
Viewing all 2330 articles
Browse latest View live
↧

SharePoint online - tag images so it can be searched

August 2, 2012, 5:26 am
$
0
0

Hi, We have 100s of images, CAD drawings that we want to upload and maintain the sharepoint online. Each drawings may have 15 to 20 tags by which we identify the parts/components etc., Its the way, we use it internally so that we can locate a correct drawing.

 

Now, i know we can create a image library in sharepoint and tag the images. How can we search on by the tags?  Can someone provide a steps or link for us?  I tried to do that few months ago - my experience was that it took sometime for the sharepoint cloud to index and show the results. or perhaps I am missing something. Therefore if someone could point out or state the steps that will be great.

 

 

↧
Search

Re: Send as ability

August 2, 2012, 5:36 am
↧
↧

Hybrid deployment with Barracuda spam firewall?

August 2, 2012, 5:58 am
$
0
0

Hi Everyone,


I'm in the middle of working through a hybrid setup between our Exchange 2010 servers and Office 365. We currently use a Barracuda for our internal Exchange servers. All external mail is delivered to the Barracuda, and all internal mail is sent outbound through the Barracuda.


Currently we only use one domain with the Barracuda and all of our internal users, domain.org. With Office 365, we're mainly using it for a subdomain - students.domain.org. I would like the ability to migrate our internal domain.org users to Office 365 at some point, and also keep the possibility of moving the students.domain.org users back into the internal server as well. 


How can all of this work with our Barracuda? None of MS' documentation seems to mention using anything besides FOPE. I wouldn't mind having the Barracuda deal with all email for both domains, but it seems like that probably won't work. I am definitely not interested in purchasing FOPE licenses for all of our internal users and bagging the Barracuda, which is what MS seems to suggest doing with the "MX to the cloud" deployment option. 


Thanks!


-MRCUR

↧

Hybrid Configuration Wizard: ValidateConfiguration execution failed: Configure Legacy Exchange Support

August 2, 2012, 5:59 am
$
0
0

I am posting this in new thread in case anyone find it useful. I did post this as a possible answer to someone elses thread but i think i want to put this in its own thread, as my situation is quite specific

 

Problem: HCW failed with error "ValidateConfiguration execution failed: Configure Legacy Exchange Support"

 

We have a native Exchange 2010 environment with 9 Exchange 2010 servers, (all exchange SP2 UR3). Roles are split and seperated

 

Site A

2x Mailbox, 2x CAS/HT, 2x Edge

 

Site B

1x Mailbox, 1x CAS/HT, 1x Edge

We have Public Folder DB's on each Mailbox Server. All PFs are fully replicated to all the DB's

The public folders were originally migrated/replicated from exchange 2003
There is no exchange 2003 in the environment anymore.
There are no problems with the public folder infrastructure. Everything is working fine.
There is no trace of any 'legacy' exchange 2003 leftovers in AD. Everything was removed after we finished moving to 2010 about 12 months ago. We were following the MS documentation, and exchange 2003 was removed cleanly. Public folder hierarchies were correctly 're-homed' off the 2003 servers, and the CN=SERVERS container was removed from the 'first administrative group' using ADSI edit after we removed the last exchange 2003 server. We made sure that public folder replica's were all problem free before we retired that

 

We have done all the preparation for hybrid configuration using 'exDelopy' steps. We spent a long time making sure the environment was ready. Office 365 deployment readiness tools showing no issues. But when we finally tried to setup hybrid coexistence: I was unable to run HCW, it would fail with: "ValidateConfiguration execution failed: Configure Legacy Exchange Support"

 

Log files show the HCW trying to 'get-publicfolders' on my mailbox servers.
It succeeds on the first server, and then fails on the next one it tries

[7/30/2012 21:36:42] INFO:Running command: Get-PublicFolderDatabase -Server 'MBX-A-00'
[7/30/2012 21:36:42] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 30/07/2012 22:36:42.
[7/30/2012 21:36:42] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 30/07/2012 22:36:42.
[7/30/2012 21:36:42] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 46.884.
[7/30/2012 21:36:42] INFO:Running command: Get-PublicFolder -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'MBX-A-00' -Recurse ''
[7/30/2012 21:36:42] INFO:Cmdlet: Get-PublicFolder --Start Time: 30/07/2012 22:36:42.
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolder --End Time: 30/07/2012 22:36:43.
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolder --Processing Time: 906.424.
[7/30/2012 21:36:43] INFO:Running command: Get-PublicFolderDatabase -Server 'VEXMBX-A-01'
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 30/07/2012 22:36:43.
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 30/07/2012 22:36:43.
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 62.512.
[7/30/2012 21:36:43] INFO:Running command: Get-PublicFolder -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'MBX-A-01' -Recurse ''
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolder --Start Time: 30/07/2012 22:36:43.
[7/30/2012 21:36:43] ERROR:System.Management.Automation.RemoteException: No existing 'PublicFolder' matches the following Identity: '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolder --End Time: 30/07/2012 22:36:43.
[7/30/2012 21:36:43] INFO:Cmdlet: Get-PublicFolder --Processing Time: 62.512.
[7/30/2012 21:36:43] INFO:Disconnected from On-Premises session
[7/30/2012 21:36:43] INFO:Disconnected from Tenant session
[7/30/2012 21:36:43] ERROR:Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Legacy Exchange Support at Microsoft.Exchange.Management.Hybrid.Engine.ExecuteTask(TaskBase taskBase, TaskContext taskContext)

I could - as an administrator - run the same get-publicfolder command in powershell on any exchange server, or my administrative workstation and confirm the foders exist and can be enumerated on this same server on which the failure was occuring

Get-PublicFolder  -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'MBX-A-01' -recurse

 

This command would return the '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' folder and its children. It would work fine when targeting ANYof my exchange mailbox servers. No problem. Nonetheless, the HCW would not get past this point.

 

I tried to run that same 'get-publicfolder' powershell command, by running powershell as the 'on-premise' user account specified during the HCW. It would work on 2 of my PF DB's but consistently fail on the same server mentioned in my logs. Output was as follows:

 

<powershell running as the HCW on-premise user, (with org management rights)>

Get-PublicFolder -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'MBX-A-01' -Recurse

 

No existing 'PublicFolder' matches the following Identity: '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], MapiOperationException
    + FullyQualifiedErrorId : 1ACB800A,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder

 

I confirmed the user account was a member of 'organisational management'
It didnt matter what additional rights this user was granted - i tried domain admin, enterprise admin, builtin administrators... - it would always fail.

 

Further testing revealed that this user account could not actually enumerate ANY public folders on this specific PF database on this 1 mailbox server

 

Get-PublicFolder -Identity '\' -Server 'MBX-A-01' -Recurse

No existing 'PublicFolder' matches the following Identity: '\'. Make sure that you specified the correct 'PublicFolder'  Identity and that you have the necessary permissions to view 'PublicFolder'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-PublicFolder], MapiOperationException
    + FullyQualifiedErrorId : C0789D04,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder

As it started to look like permissions, i checked and compared all of the administrative permissions on ALL the public folder DB's with each other:

 

Get-PublicFolderAdministrativePermission -Identity "\" -server MBX-A-00 | fl

Get-PublicFolderAdministrativePermission -Identity "\" -server MBX-A-01 | fl

Get-PublicFolderAdministrativePermission -Identity "\" -server MBX-B-00 | fl

 

The permissions were identical on all my public folder db's on all my mailbox servers. There were no differences at all. There were no explicit deny rights. There was nothing that would explain why i cant get-publicfolders on this one database, when running as this user.

 

In the end - out of sheer desperation - i mailbox enabled the user - just to see what would happen.
This user was not previously mailbox enabled. There was nothing in any of the documentation that indicated that it should be

 

After i mailbox enabled the user, the commands were able to execute. I could enumerate all public folders in all DB's on all servers when executing the powershell as this user.

 

I dont understand whats going on here at all. From my perspective it should not be necessary to be mailbox enabled user in order to be able to enumerate public folders...
...and, even if that were the case, why would it fail only on 1 specific PF DB on one specific server?. Surely it should fail on all of them?

 

I do not have answers to these questions.

 

but for anyone out there having a similar problem - if you need to get the HCW to work, and you have the same problem as me, try to mailbox-enable the on-prem user account thats configured during the HCW, to see if it clears your problem.

Hope this might help someone else. I had a week of hell because of this problem.

 

↧

Re: Autodiscover works for on-premise users but not for Office 365 cloud users

August 2, 2012, 6:33 am
$
0
0

Hello Ben,

How are the things going?
In addition, do you need further assistance on the issue?

Best regards,
Claud

↧
↧

Re: Hybrid Email migration Through Batch file

August 2, 2012, 8:22 am
$
0
0

Hi arsaleng82,

Take a look at this script, I use it to migrate large batches of users. You will need to create a CSV file and set the first row to 'UserPrincipalName' then list out your users full UPN down the column. remember your users have to be licensed before doing this. This particular scipt keeps the username and password in the file, I have seen other scripts that can hide this, you'll notice though that this script encrypts the password before it sends it to Office 365. You also need to add two credentials, in the first set you should put an account that is a Global admin in UPN form, the second one should be in DOMAIN\username format and needs to have permissions to move mailboxes from the On-prem solution.

$powerUser = "administrator@domain.com"

$powerPass = "Password"

$password = ConvertTo-SecureString $powerPass -AsPlainText -Force

$Cred = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $powerUser,$password

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection

Import-PSSession $Session

$powerUser = "domain\administrator"

$powerPass = "Password"

$password = ConvertTo-SecureString $powerPass -AsPlainText -Force

$Cred = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $powerUser,$password

$Users = Import-Csv c:\Users.csv

$Users | ForEach-Object {

new-MoveRequest -identity $_.UserPrincipalName -Remote -RemoteHostName 'mail.domain.com' -RemoteCredential $cred -TargetDeliveryDomain 'domain.mail.onmicrosoft.com' -BadItemLimit 10 -LargeItemLimit 20

}

Remove-PSSession $Session

↧

Re: IMAP Migration Issues

August 2, 2012, 9:53 am
$
0
0

The users do exist on the imap server.

EmailAddress,UserName,Password

paula@sueclarkrealestate.com,paula@sueclarkrealestate.com,password

↧

RE: second hybrid server

August 2, 2012, 10:17 am
$
0
0

I also need an answer to this.

I too would like to add a second hybrid server (my primary is fine, I would like to load balance my migrations to the cloud and my mail routing.

If someone has some help to give I would be grateful.

↧
Search

Re: Calendar sharing

August 2, 2012, 10:59 am
$
0
0

Hi Crock,

You can't do this in a hybrid mode. If you want to delegate control of a mailbox or any item within a mailbox such as a calendar, both parties have to be on the same side of the fence cloud/cloud or on-prem/on-prem.

Thanks,

↧
↧

Installing a second hybrid server for high availability of the hybrid configuration

August 2, 2012, 11:42 am
$
0
0
Hello,

I am creating a new thread for this as I haven't managed to find any other information on this anywhere else. There are other threads which mention it but they have no definitive responses.

I have a hybrid co-existance environment consisting of a single 2010 hybrid server holding the CAS, HT and MBX roles alongside a on-premise Exchange 2007 environment. I have ADFS (which is clustered in both ADFS proxy and ADFS server) and a DirSync server. Everything is working well.

However, we have a large amount of work to do to migrate up our on-premise mailboxes to the cloud and we are concerned that our hybrid server (which is routing mail to the cloud because we cannot change our MX records as we are in co-existance and the HT role also routes internal mail from the cloud) will be overloaded with the work of migrating mailboxes (even though it is a meaty server with regards to RAM and processors). As such we would have purchased a second server of the same spec which we would like to move into the hybrid role and user to make our hybrid structure highly available.

I can find no information anywhere which discusses the installation of the second hybrid server and configuration of it to make, specifically the CAS and HT, but also the MBX, roles highly available. Even my resources at Microsoft are not aware of any.

Let me say at this point that we have no desire to use a hardware load balancer to do any of this work and I have read much on using hardware load balancing for Exchange 2010. Our MBX role is extremely under-utilised, but our CAS and HT roles are very necessary. I would imagine we're talking about a CAS array of some kind or even a NLB for one or both of these roles.

If someone could help me with providing some documentation on the high availaility of a hybrid environment (and I have read much already on configuring hybrid - I mean specifically about adding a second hybrid) it would be much appreciated.

Thanks


↧

Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 5:18 am
$
0
0

I cannot get Exchange Server 2003 to relay through Office 365.  Let's presume I've correctly configured the SMTP Virtual Server (and I believe I have) and concentrate on the 'moral' issue, in a SMTP relay sense.

If my mailbox is User-B@company.com and I've configured my Exchange Server settings to use User-A@company.com for relay authentication, then I get a "#5.7.1 smtp;550 5.7.1 Client does not have permissions to send as this sender" error.  Of course, I can't overcome this error by using a User-A@company.com local mailbox because of the Office 365 relaying guidelines:  That is, that the relay authentication address cannot exist as a local Exchange organisation mailbox.

But I can test this using a mail testing tool (Chilkat SendMail Tester).  I've changed the names but you'll get the idea:

The above test succeeds and I receive the message into my Gmail account.

Now, if all I change is the "From" field to User-B@company.com, the send fails.

How can I configure Exchange Server 2003 to allow relaying for all users without getting the "#5.7.1 smtp;550 5.7.1 Client does not have permissions to send as this sender" error.

Thanks,

↧

Re: Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 5:36 am
$
0
0

Hi Rod,

I understand you prefer to use SMTP Relay.

You can refer to this link for more information of SMTP relay.
http://support.microsoft.com/kb/2600912

And the ‘From’ address must be a valued address of the Office 365 tenant. If the User-B@company.com doesn’t exist, you will receive the 5.7.1 report.

Thanks,
Ray Yang

↧

Re: Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 6:23 am
$
0
0

User-B@company.com does indeed exist in the Office 365 Exchange Online domain; as do all of the local mailbox accounts I tested this with, and all are licensed .  My configuration was as per support.microsoft.com/.../2600912.


Is there something else I should check for?

↧
↧

Re: Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 6:34 am
$
0
0

what's the meaning of local mailbox?

what's the user-b't type?

If it is exist, it won't say lient does not have permissions to send as this sender

↧

Re: Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 6:53 am
$
0
0

'FromMars' I am relaying from my on-premise Exchange Server 2003.  A local mailbox is one on the on-premise system.

User-B is on both systems. The Mailbox type is "User" on Office 365.  User-B has a mailbox on the on-premise system.

The only unusual condition I can think of is that I have removed all mailbox accounts on this Exchange server from appearing in the GAL ("Hide from Exchange address lists" setting).  In have done this because I'm running a batch migration and mailboxes are spread over two Exchange servers.

↧
Search

Re: Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 6:56 am
$
0
0

How to make a box on both system? It is impossible.

If the user B is in local, O365 won't think they have this user. So you will get this error.

you can try again after the migration finished.

↧

Re: Hybrid deployment with Barracuda spam firewall?

August 5, 2012, 7:22 am
$
0
0

Hi MRCUR,

I'm thinking there are the different. FOPE provides service for every user in Office365, but it's different with delicated FOPE license. If you want to find out the detail different, you can call our sales and billing team g.microsoftonline.com/.../280

Thanks, Neo Zhu

↧
↧

Re: Cannot relay Exchange Server 2003 through Office 365.

August 5, 2012, 7:49 am
$
0
0

You can certainly create a mailbox on both systems (on-premise and O365) because each are different Exchange Organizations - but I see what you're saying:  You can but it won't work for the scenario I'm describing.

Well that's a bummer.  It's a shame that http://support.microsoft.com/kb/2600912 doesn't mention that as you say, "O365 won't think they have this user".

On the positive side, my relaying requirements are only a temporary measure.  I'll reconfigure Exchange.

'FromMars', thanks for this really helpful piece of information.

↧

Re: Identify skipped messages

August 5, 2012, 10:40 pm
$
0
0
Hi Simon,
 
How are things going? Do you need any further assistance?
 
If you have any questions, please feel free to post here. We are happy to assist you.
 
Thanks,
Jolin Qiao
↧

pls verify my setup is normal

August 5, 2012, 11:10 pm
$
0
0

We had a consultant configure coexistence and I've just run into an issue which makes me question if the setup is correct / normal best practice:

 

O365 Tenancy = XX.onmicrosoft.com

Free/Busy sharing configured using domain XX.mail.onmicrosoft.com (also set as Tenancy domain in Org config in Hybrid server)

 

I've been told I need to allocated each mailbox both the above domain names.

 

My testing indicated:

tenancy domain is handling mail flow (this domain is added automatically as an SMTP address when mailbox migrated to cloud)

and

XX.mail.onmicrosoft.com must be set as the mailboxes routing domain for Free/Busy to work.

 

If the users routing domain is defined as O365 tenancy domain name of XX.onmicrosoft.com email flow works fine but Free/Busy information not available.

 

Is this a "normal" setup?

 

thanks

↧
Viewing all 2330 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>