Exchange Admin IP: Office 365 Connectivity

Hi,
I'm trying to use the Exchange Admin integration pack to manage Office 365 objects. I'm having some difficulty setting up the Exchange Admin Connection. I've setup the following:
Exchange Server Host: outlook.office365.com
Port: 443
PowerShell Application: powershell-liveid
User Name: [email protected]
Exchange Environment: Online
If I run a simple Get Mailbox activity I get the following error:
Error(s) executing PowerShell command: System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name
is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers
within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.. Inner exception: . Command info: Command name: New-PSSession. Parameters: [ConfigurationName:Microsoft.Exchange],[ConnectionUri:https://outlook.office365.com/powershell-liveid],[Credential:System.Management.Automation.PSCredential],[Authentication:Basic],[SessionOption:System.Management.Automation.Remoting.PSSessionOption]..
Exception: ExchangeGatewayException
Target site: ExchangeGatewayBase.CheckErrors
Stack trace:
   at SystemCenter.IntegrationPack.ExchangeAdmin.Gateway.Core.ExchangeGatewayBase.CheckErrors(String commandText, ICollection`1 errors)
   at SystemCenter.IntegrationPack.ExchangeAdmin.Gateway.Core.ExchangeGatewayBase.Execute(ExchangeRequest request)
   at SystemCenter.IntegrationPack.ExchangeAdmin.Gateway.Core.LocalExchangeGateway.CreateRemoteSession(PSObject sessionOptions)
   at SystemCenter.IntegrationPack.ExchangeAdmin.Gateway.Core.LocalExchangeGateway.ImportRemoteSession()
   at SystemCenter.IntegrationPack.ExchangeAdmin.Gateway.Core.LocalExchangeGateway.OpenRunspace()
   at SystemCenter.IntegrationPack.ExchangeAdmin.Domain.ExchangeGatewayFactory.CreateLocal(ExchangeConfiguration configuration, IActivityLogger logger, Boolean importRemoteSession)
   at SystemCenter.IntegrationPack.ExchangeAdmin.Domain.ExchangeGatewayFactory.CreateGateway(ExchangeConfiguration configuration, IActivityLogger logger)
   at SystemCenter.IntegrationPack.ExchangeAdmin.Activity.ExchangeActivity.Execute(IActivityRequest request, IActivityResponse response)
I've run these commands from this article:
http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx
And can connect successfully using the same credentials used above.
Has anyone else got this working?
Thanks,
Tim

Hi,
Take a look,
http://community.office365.com/en-us/f/156/t/227656.aspx

Similar Messages

How to use Powershell to set delegate for user mailbox in Exchange 2010 and Office 365

Hello,
Can you please tell me if I can set delegate for user mailbox in Exchange 2010 or Office 365 using Powershell?
If I can, then how can I do that? (which Powershell commands for setting the delegate?)
Many thanks, and have a good day!

Hi,
If you wanted to add a delegate to possiblly a large number of users or you do this during mailbox provisioning. So the following script will use
impersonation to access another users mailbox and add a delegate.
$mbtoDelegate = "[email protected]"
$delegatetoAdd = "[email protected]"
$dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.0\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)
$service = new-object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)
$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$sidbind = "LDAP://<SID=" + $windowsIdentity.user.Value.ToString() + ">"
$aceuser = [ADSI]$sidbind
$service.AutodiscoverUrl($aceuser.mail.ToString())
$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress,
$mbtoDelegate);
$mbMailbox = new-object Microsoft.Exchange.WebServices.Data.Mailbox($mbtoDelegate)
$dgUser = new-object Microsoft.Exchange.WebServices.Data.DelegateUser($delegatetoAdd)
$dgUser.ViewPrivateItems = $false
$dgUser.ReceiveCopiesOfMeetingMessages = $false
$dgUser.Permissions.CalendarFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Editor
$dgUser.Permissions.InboxFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Reviewer
$dgArray = new-object Microsoft.Exchange.WebServices.Data.DelegateUser[] 1
$dgArray[0] = $dgUser
$service.AddDelegates($mbMailbox, [Microsoft.Exchange.WebServices.Data.MeetingRequestsDeliveryScope]::DelegatesAndMe, $dgArray);
Hope this helps.

Exchange 2007 to Office 365.

Hello,
We're upgrading our Exchange 2007 to Office 365. We can't store a small portion of our emails in office 365 (cloud) due to contract obligations that says storing data outside of the UK is not allowed.
I can see there is a way to create a pst on a network location to store this small portion of data but when my pc is away from the office network, i receive an error saying it can't find the PST. Is there a way to stop the error appearing? I only want the pst folder to appear if they are on the office network? Or do you have a different solution i mind to solve our problem?
Thanks
This topic first appeared in the Spiceworks Community

Hi
http://blogs.technet.com/b/canitpro/archive/2013/11/20/step-by-step-migrating-from-exchange-2007-to-office-365.aspx
Hope this helps. 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 Exchange 2003 to Office 365

Dear all,
We are going to migrate Exchange 2003 to Office 365. Because of the large number of mailboxes and mail databases, we decide to build hybrid to support coexistence during the migration period.
According to "Exchange Server Deployment Assistant" I found that we can build more Exchange 2010 for that requirement
http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-BwAIAAAAQAAAAAEAiFIAAAA~
I just wonder that after deploying the Exchange 2010, can we move directly the mailboxes from Exchange 2003 to Office 365 or we need to move to Exchange 2010 first (as a "buffer") before moving to Office 365
Thanks a lot !!!

Hello,
The main goal of a staged migration is to migrate Exchange on-premises servers when:
1. You have more than 2000 mailboxes.
2. You plan to migrate over a few weeks and months rather than in a single batch.
3. You want to migrate to the Cloud completely and remove your on-premises Exchange deployment.
Hybrid scenarios are useful when you do not want to remove your on-premises deployment. In some cases there is no technical possibility, it is not cost-effective etc. to move a whole organization to Office 365. In these situations you may decide that moving
only some mailboxes to Office 365 is a good option and create a hybrid deployment.
You need to consider all pros and cons, especially when Exchange 2003 has gone out of support lifecycle and then choose the better option for your organization.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Exchange 2010 to office 365 migration lab

I am looking out for free migration lab if any available online from Microsoft or any vendor related to migrate from exchange 2010 to office 365 . Please suggest ?
Aditya Mediratta

Hi,
Unfortunately, there’s no related lab for use.
We can Microsoft Exchange Server Deployment Assistant to generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios. For your reference:
https://technet.microsoft.com/en-us/office/dn756393.aspx
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]
Allen Wang
TechNet Community Support

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

No Office 365 connections via Outlook 2013

I am usually able to connect via Outlook 2013 to mny Office 365 Exchange accounts for email etc. But sinice Saturday 18th July have been unable to do this. Outlook truies to connect andcannot ending up in a "disconnected" status. I have re-installed Office from scratch, no dice.I have disabled Windows Firewall, no diceI have flushed my DNS, no dice. I can pull mail via Outlokk for POP and IMAP no problem. I can also tether my laptop to my phone and pull Office 365 mail etc with no issues. So I know the laptop is fine, the Outlook app is fine and Microsoft hosting Exchange is fine. The issue has to be the network I am connecting over. I cannot ping the 365 addrerss eitherC:\Users\JDarling>ping sky.comPinging sky.com [90.216.128.5] with 32 bytes of data&colon;
Request timed out.Ping statistics for 90.216.128.5:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:\Users\JDarling>ping outlook.comPinging outlook.com [132.245.113.194] with 32 bytes of data&colon;
Reply from 132.245.113.194: bytes=32 time=132ms TTL=241
Reply from 132.245.113.194: bytes=32 time=136ms TTL=241
Reply from 132.245.113.194: bytes=32 time=135ms TTL=241
Reply from 132.245.113.194: bytes=32 time=131ms TTL=241Ping statistics for 132.245.113.194:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 131ms, Maximum = 136ms, Average = 133ms Failed pinging: C:\Users\JDarling>ping outlook.office365.comPinging outlook-emeawest.office365.com [2a01:111:f400:9850::2] with 32 bytes of
data&colon;
Request timed out.
Request timed out.Ping statistics for 2a01:111:f400:9850::2:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\JDarling>tracert outlook.office365.comTracing route to outlook-emeawest.office365.com [2a01:111:f400:9850::2]
over a maximum of 30 hops:1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
I can use the OWA to get mail, but as I have several mail accounts configured in Outlook and you can only sign in to one 365 account at a time, this is not a workaround I can use. Any ideas what the problem is?

I'm getting this too; I have an Office 365 account that is provided by my employer. Around Thursday last week I started to have issues connecting to the mailbox using the Outlook 2016 for Windows Desktop at home. It would show as disconnected and attempting to reconnect would get errors regarding authenitcation. Being an IT professional I did some investigation and also having talked to Microsoft themselves we've narrowed it down to some form of Sky IPv6 configuration, as the Microsoft Exchange expert I spoke too reckons that it's some for of IPv6 Proxy setup at Sky's end, reasons; Around the same time I was having issues with connecting to my O365 mailbox I noticed my Sky Hub has received a firmware update adding several IPv6 related features (Ping, LAN setup, Firewall).I also have Outlook for Android and can connect to my O365 account at home no problem; my Smartphone (Galaxy S4 running Android Lollipop) does not support IPv6.There is nothing wrong with my O365 account and mailbox, Microsoft checked whilst I was looking over their shoulder and I can connect to it via the Web Portal at home.Outlook 2016 can connect to my O365 mailbox via other networks; my employer's wifi network and also whilst at a friend's, their BT Internet wifi network; this indicates that the IPv6 configuration on my laptop is good.I've found a work around; you need to disable IPv6 on your PC's network card until Sky sort out what they are doing regarding IPv6! Navigate to the Control Panel.Go to the Network and Sharing Centre.On the left click "Change Adapter Settings".This will bring up the "Network Settings" form.Right click the connection that is being used (you will probably see two connections if your PC has both an ethernet and wifi card. The one that is NOT being used will have a RED "X" against it).Choose Properties.Within the "This connection uses the following items" list of items, scroll down until you find "Internet Protocol Version 6 (TCP/IP)" and uncheck it (remove the tick from the box) and click "OK".Restart Outlook; the mailbox should now connect. The question I have what is Sky doing regarding IPv6 introduction/configuration as so far I haven't seen much about it!

Exchange connector to Office 365

Dears,
I am beginner to SCSM, so please forgive my non professional questions.....
I am trying to connect my Service Manager to Office 365, and I have below questions
In general settings > Enter one or more active directory: I added my local domain (John.Lab)
Is this correct?
In server settings > Use Auto discovery: I did not check it Is this correct?
In server settings > Exchange Server URL, I added: "https://pod51036.outlook.com/EWS/Exchange.asmx" is this correct or do I have to add:
https://pod51036.outlook.com/owa?
In server settings > User impersonation can I use this settings to link it with my IR since I am using office 365? "actually this is the main reason for my exchange connector?
In server settings > Run as account:
can I use a domain user account which does not have Mailbox and
mail address?
Thank you

Hi,
1. This is correct
2. This is correct
3. This looks good. Otherwise, try
https://outlook.office365.com/EWS/Exchange.asmx
4. No. You must not check this option.
5. You have to create a separate Run As account. The username would be [Office 365 Domain]\[Office 365 User Name], and the Password. SCSM will not be able to validate the credentials, however you can still accept it.
HTH,
Dieter

Migrating Exchange 2013 to Office 365 Transient Error

So I setup an Exchange Hybrid Environment in an attempt to migrate mailboxes to Office 365. I'm performing my first test migration and so far it's running, very slow but it's running. I keep seeing this error in the migration job and I'm guessing it's slowing
me down. I'm hoping someone can point me in the right direction as to what's causing this.
1/10/2015 2:28:37 AM [BN1PR05MB357] Transient error DataExportTransientException has occurred. The system will retry (1/60).
1/10/2015 2:29:55 AM [BN1PR05MB357] The Microsoft Exchange Mailbox Replication service 'BN1PR05MB357.namprd05.prod.outlook.com' (15.1.53.16 caps:1FFF) is examining the request.
1/10/2015 2:29:55 AM [BN1PR05MB357] Connected to target mailbox 'client.onmicrosoft.com\b00fdbce-03e6-4d85-ad21-28a8c60055c5 (Primary)', database 'NAMPR05DG023-db142', Mailbox server 'BN1PR05MB357.namprd05.prod.outlook.com' Version 15.1 (Build 53.0).
1/10/2015 2:29:56 AM [BN1PR05MB357] Connected to source mailbox 'client.onmicrosoft.com\b00fdbce-03e6-4d85-ad21-28a8c60055c5 (Primary)', database 'Mailbox Database', Mailbox server 'EX13.client.local' Version 15.0 (Build 995.0), proxy server 'EX13.client.local'
15.0.995.28 caps:017FFFFFCB07FFFF.
1/10/2015 2:29:58 AM [BN1PR05MB357] Request processing continued, stage LoadingMessages.
Vincent Sprague

Do you have any firewall appliance or TMG between Exchange Onpremises and Online? I've seen this issue multiple times with TMG.
http://technet.microsoft.com/en-us/library/dd441028.aspx, with other firewall appliances look for the same kind of configuration.
Also be sure you have enough resources (cores and memory) available.

Bypass Proxy for Local Addresses - Office 365 connection/ Outlook 2010

This is a strange one. Connectivity to Office 365 within our netwotk works fine although very slow for outlook 2010 client to initially connect. Once connected, it works ok. I have done a netwotk trace using netmon to see if i can identify
the reason for the slow startup (2 mins minumum for profile to load and for outlook to connect to exchange). The trace tell me that my local pc tries to make a direct connection to the office365 external IPs first, then tries the TMG proxy. Once it hits the
proxy, it kicks into life and works.
So it looks to me like it thinks the external IP address of office 365 is an internal address and spends it time trying all the ip addresses until it trys the proxy. At this point, the
Bypass Proxy Server for Local Addresses is ticked.
As soon as i untick this box, all traffic heads directly to the proxy and of course it connects like lighting. The exchange settings proxy is set in outlook for "on fast networks, connect using HTTP first, then connect using TCP/IP" (tick
is on) and the same for slow networks.
I cant for the life of me work out why it tries to connect directly to the external IPs first and not connect via TMG until i untick the
Bypass Proxy Server for Local Addresses
Would love any ideas that may assist.

We have been in discussions with Microsoft over the last few days on this issue - which is seen with Outlook 2007 versions onwards. Extract from resolution communication from Microsoft:
The issue you have raised is known as it has been reported and when you have a proxy set in Internet Explorer and “Bypass proxy settings for local addresses”, Outlook will attempt to connect to Office 365 directly – like the bypass rule would apply.
Because the direct connection is blocked in the Firewall, Outlook needs to have the connections going in Timeout before attempting to connect using the Proxy.
Your network trace proves the issue.
Microsoft have scheduled a fix for Outlook 2010 in February 2014 cumulative update. A fix for Outlook 2013 will also follow, but Outlook 2007 will not be addressed because it is in Extended Support.
There are two possible workarounds for this behaviour:
First, and I wouldn’t recommend it, is to allow Direct traffic through the Firewall to Office 365.
The advantage of this approach is that it will be done centralized and it will impact everyone immediately.
Information about the O365 IP addresses
There are two downsides to this behaviour:
1. First you need to maintain the Firewall exceptions as IP from O365 server can change without notice
2. Second, winhttp traffic may go through both proxy and direct and this can cause unforeseen behaviour.
The second approach is to use a proxy pac instead of manually setting in the proxy and the exceptions.
The advantage is that you will have centralized method to control how winhttp traffic goes and the issue will not be experienced anymore.
If a single pac does not be fit, you can configure proxy pac files for each site requirements and use an IIS server to store it.

Multiple Legacy Exchange Forests - Single Office 365

I currently have 2 legacy Exchange forests:
legacysales.com
legacyservices.com
Both of these organisations are being migrated to a consolidated Active Directory:
newsalesservices.com
The new organisation will use Office 365. There will be no On-Premise Exchange in this organisation.
My challenge is to migrate to new AD and Office 365.
I can't find much info on this so here is my proposed plan:
Configure hybrid deployment in legacysales.com with newsalesservices.com Office 365 and migrate mail.
Configure hybrid deployment in legacyservices.com with newsalesservices.com Office 365 and migrate mail.
Migrate AD user objects from legacysales.com to newsalesservices.com on-premises AD (use ADMT, retain SIDs etc.)
Migrate AD user objects from legacysales.com to newsalesservices.com on-premises AD (use ADMT, retain SIDs etc.)
Use new Azure Active Directory Sync (AADS) to sync from new AD user objects in newssalesservices.com AD to newsalesservices.com Office 365 (match on different attribute e.g. legacy mail address).
Does anyone have any experience with a similar scenario? Any caveats? Any feedback?
Should I maybe migrate the AD objects first (although the mail sync will always have to occur from legacy forests to Office 365 anyway).

Hi SupCra,
Your proposed plan seems technically right, but has some risks.
Will aadsync actually match the dirsync objects
Are all required attributes available in the new forest, probably you will still need to extend the AD schema to have some required Exchange properties (like
ms-Exch-Hide-From-Address-Lists properties).
If you can create a test setup I would be very interested in the results!
A more safer approach will be the use of an external migration tool.
Setup AADSync with the new forest and Office365
Create user mailboxes
Incremental sync of mailboxes
Cut-over
Although there are limitations with this approach too!
How many users do you have? Is a batched migration required?

Can I migrate users from a hosted Exchange 2010 to Office 365 Enterprise E1 without the need of third party software?

I am hoping I am posting to the correct forum. We are currently using a hosted Exchange 2010 service through Intermedia and due to continuing issues with them and the pricing, we are getting ready to migrate to Microsoft’s Office 365 Enterprise
E1 platform. My question is this, besides the fact that we will need to set up ADFS for SSO, will I be able to migrate our existing mailboxes from Intermedia to Office 365 without having to purchase additional software?
The current configuration we have with Intermedia allows for us to use OWA and our OST files for our current users are cached locally on the workstations.
We also do not have any public folders in use. I have searched the web, but I have not been able to find a definitive answer or steps that I should take to prepare for this type of migration.
Any suggestions on this matter would be appreciated. Thank you.

It looks as I should be able to from reading that article. Not sure why the company that want to set this all up for me wanted $12,000 for something I can do with 6 steps.
Thank you

Exchange 2010 and Office 365

Haven't been able to find a definitive answer from our friends at Microsoft or Google, so here goes!I have a client (lets call the Client A) with onsite SBS Server (Exchange 2010 SP3) of 50 seats. The client has multiple meeting rooms, defined as resource mailboxes and makes extensive use of free/busy info for booking staff and resources for meetings.That part is all good!Recently, a related organization (who we'll call Client B) moved into the same office with them. The second organization (who has IT support provided by another company) uses Office 365 for their email services and has a completely different domain name etc.Because they are related, Client A has requested that they and Client B integrate their calendars so that staff from clients A & B can see each others free/busy info, invite each other to meetings and staff from...
This topic first appeared in the Spiceworks Community

Hi,
If you wanted to add a delegate to possiblly a large number of users or you do this during mailbox provisioning. So the following script will use
impersonation to access another users mailbox and add a delegate.
$mbtoDelegate = "[email protected]"
$delegatetoAdd = "[email protected]"
$dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.0\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)
$service = new-object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)
$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$sidbind = "LDAP://<SID=" + $windowsIdentity.user.Value.ToString() + ">"
$aceuser = [ADSI]$sidbind
$service.AutodiscoverUrl($aceuser.mail.ToString())
$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress,
$mbtoDelegate);
$mbMailbox = new-object Microsoft.Exchange.WebServices.Data.Mailbox($mbtoDelegate)
$dgUser = new-object Microsoft.Exchange.WebServices.Data.DelegateUser($delegatetoAdd)
$dgUser.ViewPrivateItems = $false
$dgUser.ReceiveCopiesOfMeetingMessages = $false
$dgUser.Permissions.CalendarFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Editor
$dgUser.Permissions.InboxFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Reviewer
$dgArray = new-object Microsoft.Exchange.WebServices.Data.DelegateUser[] 1
$dgArray[0] = $dgUser
$service.AddDelegates($mbMailbox, [Microsoft.Exchange.WebServices.Data.MeetingRequestsDeliveryScope]::DelegatesAndMe, $dgArray);
Hope this helps.

Old Exchange Script to Office 365 Exchange

Previously, I was using the script (on our old Exchange server) below to create a report on all emails sent to a different domain name aside from our company's registered domains. Now, we are using Office 365 and I don't know how to make this work.
Here is my script for collecting emails not sent to our company's registered domains:
Get-MessageTrackingLog -ResultSize Unlimited -EventID "SEND" | where{$_.recipients -notlike "*@company.com, *@company-1.com"} |select-object Timestamp,Source,EventId,Sender,{$_.Recipients},MessageSubject | Format-Table -Wrap -AutoSize|
Out-File -FilePath "X:\EmailLogs\EmailLog $(get-date -f yyyy-MM-dd).txt" -width 1000
Now this is the second script I use to "pull" the logs and send emails for notification:
$date = Get-Date -Format d.MMMM.yyyy
$source = "X:\EmailLogs\EmailLog $(get-date -f yyyy-MM-dd).txt"
$destination = "\\Company-Shared\EmailLogs\"
$path = test-Path $destination
$smtp = "EXCH01"
$from = "Sender <[email protected]>"
$to = "Recipient <[email protected]>"
$body = "This is a scheduled-automated e-mail message. Exchange Log file copied to \\Company-Shared\EmailLogs shared folder: $date"
$subject = "Exchange Log Backup on $date"
if ($path -eq $true) {
copy-Item -Path $source -Destination $destination
$backup_log = Dir -Recurse $destination | out-File "$destination\backup_log.txt"
$attachment = "$destination\backup_log.txt"
send-MailMessage -SmtpServer $smtp -From $from -To $to -Subject $subject -Body $body -BodyAsHtml
send-MailMessage -SmtpServer $smtp -From $from1 -To $to1 -Subject $subject1 -Attachments $attachment -Body $body1 -BodyAsHtml
write-host "Copy Sucessfull"
How can I make this work for our new Office365?
Thank you.

I tried converting it with Get-MessageTrackingLog but I get this error. Can someone help me out on the conversion of this script:
A parameter cannot be found that matches parameter name 'ResultSize':
+CategoryInfo : InvalidArgument: <:> [Get-MessageTrace], ParameterBindingException
+ FullyQualifiedErrorID: NamedParameterNotFound, Get-MessageTrace
+ PSComputerName: xxxxxxxxx.outlook.com
Thank you.
Look at the link I posted for Get-MessageTrace.
It does not have the same parameters as Get-MessageTrackingLog.
You cannot specify an Event type, and Sender and Recipient addresses can only be filtered by either a list of addresses or a single wildcard string (you can't use multiple wildcards), so if you have multiple accepted domains you're either looking at late
filtering or getting multiple traces, each one filtered on one accepted domain.
Here's an example using late filtering.
$O365_SessionParams =
ConfigurationName = 'Microsoft.Exchange'
ConnectionUri = 'https://ps.outlook.com/powershell/'
Authentication = 'Basic'
AllowRedirection = $true
# ErrorAction = 'Stop'
# Credential = $Credential
$O365_Session = New-PSSession @O365_SessionParams
Import-PSSession $O365_Session -CommandName Get-MessageTrace
$TraceParams =
StartDate = (Get-Date).AddDays(-1).ToShortDateString()
EndDate = (Get-Date).ToShortDateString()
PageSize = 1000
# ErrorAction = 'Stop'
$AcceptedDomains = '@company\.com$|@company-1\.com$'
$TraceResults =
Get-MessageTrace @TraceParams |
Where-Object { ($_.SenderAddress -match $AcceptedDomains) -and
($_.RecipientAddress -notmatch $AcceptedDomains) }
That was copied from script I have message tracing, and those Credential and ErrorAction parameters are for accepting alternate credentials and error handling in the script, and I left that code out for the example, so they've been commented.
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Exchange 2010 to Office 365 federation trust

I'm trying to setup a federated trust between two companies on different domains (Exchange 2010 SP2 on premise/Office 365). We are trying to share calendar information and contacts. I've gone through the steps to setup a federated trust and created
the TXT file for the (Exchange 2010) on premise domain. When I try creating the trust from the Exchange 2010 on premise domain to Office 365 I receive an error.
COMMAND:
Set-FederatedOrganizationIdentifier –AccountNamespace <some_domain> –DelegationFederationTrust “Microsoft Federation Gateway”
ERROR:
Proof of domain ownership has failed. Make sure that the TXT record for the specified domain is available in DNS. The format of the TXT record should be "example.com IN TXT hash-value" where "example.com" is the domain you want to configure
for Federation and "hash-value" is the proof value generated with "Get-FederatedDomainProof -DomainName example.com".
Do I need to create a TXT file for the Office 365 side?
Thanks
Stephen

You need to add this TXT record for your domain and publish it EXTERNALLY, so that the MFG can verify it. For example, check the TXT records for Microsoft.com:
PS C:\> Resolve-DnsName -Type TXT microsoft.com
Name Type TTL Section Strings
microsoft.com TXT 2346 Answer {FbUF6DbkE+Aw1/wi9xgDi8KVrIIZus5v8L6tbIQZ
kGrQ/rVQKJi8CjQbBtWtE64ey4NJJwj5J65PIggVY
NabdQ==}

Exchange Admin IP: Office 365 Connectivity

Similar Messages

Maybe you are looking for