User Profile
Cabarrus300
Copper Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Script execution problem for migration of exchange 2016 public folders to office365
Raphael_Veauvy I was hoping to go through this https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/migrate-to-exchange-online?view=exchserver-2019%20 yesterday and move our Exchange 2013 on-premises Public Folders to Exchange Online. Unfortunately I came across the same issue which is item 1 under Step 3: Generate the .csv files. I did successfully run the script back in June this year but never did finish this migration. The article mentions: To run the migration scripts in this article, you must use an account that has basic authentication enabled. Accounts that use multi-factor authentication (MFA) are currently not supported. Here is a link but it pertains to Exchange Online and we're running the script against our on-premises server but I'm wondering if it will impact any of the other scripts? Thanks * Update - I ran Powershell as an admin on my Exchange 2013 server, ran this command Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn and was able to run the script without error. I was using Exchange Powershell and it wasn't working.3.3KViews4likes2CommentsRe: Exchange Hybrid - Outlook 2013 Autodiscover Issue
Some additional notes: -We’re using E1 -No MFA is enabled on a test account, still in 14 day grace but have another account with MFA, neither work. -I’ve tried Outlook 2013 and 2016 but neither can connect to an email account migrated from on-prem to exchange online. -I think issue is fully related to the test connectivity site failing on wrong username/password on autodiscover-s.outlook.com Thanks4.3KViews0likes0CommentsExchange Hybrid - Outlook 2013 Autodiscover Issue
Hello Everyone, I've spent many hours googling trying to figure this one out and Im stuck. We're new to Office 365 and in the process of getting our on-premise Exchange 2013 server to work with Exchange Online. We ran through the Microsoft Office 365 Hybrid Configuration Wizard and migrated a couple of email boxes from onpremise to the cloud. We have Azure AD Connect setup to replicate users from specific OU's and have Exchange Hybrid Deployment selected. Any feedback would be appreciate, thanks -Public DNS Autodiscover record points to on-premises Exchange 2013 Server - Same public ip as OWA -Internal DNS Autodiscover record points to internal IP of on-premises Exchange 2013 Server -In a perfect world we'd have our on-premise server send email to Zix for threat prevention but for these accounts im bypassing this by using the send connector that the hybrid wizard setup. This is domainorg.mail.onmicrosoft.com deliver to MX record associated with recipient domain. -This quote is where the issue appears to be occuring, where the redirect isn't taking place properly. "For On-premise mailbox, it remain use previous autodiscover lookup behavior to find endpoint and access to Exchange. For migrated mailbox, autodiscover service will redirect On-premise autodiscover record to Office 365 (autodiscover-s.outlook.com), and access to Office 365." -Microsoft Support and Recovery Assistant - Selecting "I need help setting up my Office 365 email in Outlook" comes back with a username / password is incorrect error message. -Microsoft Remote Connectivity Analyzer comes back with "The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user XXXX The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response. -I don't have MFA enabled for this test user -Here is more info from Microsoft Remote Connectivity Analyzer below: Additional Details An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN). HTTP Response Headers: request-id: 35ec9589-1d16-478a-84e6-a073e631548e X-CalculatedBETarget: BLAPR15MB4068.namprd15.prod.outlook.com X-BackEndHttpStatus: 401 X-RUM-Validated: 1 X-AutoDiscovery-Error: LiveIdBasicAuth:InvalidCreds:<UNH:228594863><RequestId=eacd7875-5817-4fca-b2b1-b8acc7dc0e28><UIPH:957273394><X-forwarded-for:957273394><PTS:False><HRD-Business-0ms-61ms-ppserver=><HRDCached:False><UP:0><BlockStatus:3><RST2-Business-0ms-24ms-0ms-ppserver=PROD-EST-011.ProdSlices rid:2a0b2260-88fe-4894-976c-c0fbcb1a0300-puid=>LiveIdSTS-LogonFailure-'0x80048821'<UserType:ManagedBusiness><LogonFailed-BadPassword><AS:BadPassword><Tid=>; X-DiagInfo: BLAPR15MB4068 X-BEServer: BLAPR15MB4068 X-Proxy-RoutingCorrectness: 1 X-Proxy-BackendServerStatus: 401 X-FEServer: DM5PR15CA0049 Content-Length: 0 Cache-Control: private Date: Fri, 05 Jun 2020 01:52:31 GMT Server: Microsoft-IIS/10.0 WWW-Authenticate: Basic Realm="" X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET4.4KViews0likes1Comment
Recent Blog Articles
No content to show