https://www.quest.com/community/notes-to-exchange-migration/en-USTelligent Community 13https://www.quest.com/community/notes-to-exchange-migration/f/forum/36646/huge-mail-queues---hcl-router-error-searching-mailbox-file-mail3-box-insufficient-queue-space-router-queue-is-fullFri, 25 Jul 2025 13:40:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:6e9313c7-1b6c-4d92-b5fc-34c7d86e04dehelen rochemail is queuing and the only error in the hcl notes log.nsf is HCL router error searching mailbox file mail3.box insufficient queue space. Router queue is full this is for all 4 mail.boxes cant see any errors on the quest server - any ideas?https://www.quest.com/community/notes-to-exchange-migration/f/forum/32114/convert-nsf-into-pst/85244Wed, 23 Jul 2025 12:56:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:dae3ed41-84f9-417a-898e-52742750f762justJamieIf you are looking for the most efficient and reliable solution to convert NSF files to PST in bulk without hassle, then you have come to the right place. Then use the third-party solution, GainTools NSF to PST Converter tool. It has various advanced features that make it unique from the others. It can export Lotus Notes NSF files into Outlook PST with data like emails, notes, contacts, calendars, etc. Before the conversion process, it is also shown a preview to check all the NSF data. The Graphical User Interface is also very easy and simple, so novice users will never face issues while operating. It also supports all versions of Windows and Outlook. If you have any queries/doubts regarding this tool, then contact its technical support team. They are available 24/7.https://www.quest.com/community/notes-to-exchange-migration/f/forum/32114/convert-nsf-into-pst/84950Fri, 27 Jun 2025 12:56:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:0fe3c4d2-3c02-48a9-9ec8-0e8db4b9601fchandelamit00007Thank you for the information.https://www.quest.com/community/notes-to-exchange-migration/f/forum/36266/notes-to-exchange-connector-does-not-create-contacts-for-domino-groupsMon, 28 Apr 2025 12:01:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:7f558676-9b14-4748-8025-7c0a6b519901pavel marinovI have the Directory sync module enabled for transferring accounts from Domino to Exchange AD. All mailboxes were transferred as contacts in Exchange AD, however I have selected Domino Groups to be transfered as well, but they do not. No error messages, it is like they are not included in the syn. I looked for errors, but they are no errors what so ever. I can see in the domino Directory that the groups reside in a container name Other, which I don't see on the connector for selection. What am I missing? How can I create contact for the groups as well.Coexistence Manager for Noteshttps://www.quest.com/community/notes-to-exchange-migration/f/forum/36257/proxyaddress-for-an-already-created-contact-in-exchange-does-not-change/84285Fri, 25 Apr 2025 14:04:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:609d8c58-036e-41a5-bf90-0f4ffb6633edpavel marinovWell with a Domain Admin it works, but I can't seem to find what exactly are the permissions needed. I would think, that Domain Admin is a bit much, so the user had everything short of Full Control. Can you point me to the part where the permissions for the AD account are listed?https://www.quest.com/community/notes-to-exchange-migration/f/forum/36257/proxyaddress-for-an-already-created-contact-in-exchange-does-not-change/84284Fri, 25 Apr 2025 13:37:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:1fad0728-8903-4869-beea-59c8975ae8abJeff ShahanReview the product documentation around permissions, you have to be missing something.https://www.quest.com/community/notes-to-exchange-migration/f/forum/36257/proxyaddress-for-an-already-created-contact-in-exchange-does-not-change/84283Fri, 25 Apr 2025 13:33:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:a2d08ef4-87a1-420e-9fa3-33bd7094ef61pavel marinovYes, however we have checked the service account in AD and it has everything putside Full Control. Maybe something in the Advanced features in the connector?https://www.quest.com/community/notes-to-exchange-migration/f/forum/36257/proxyaddress-for-an-already-created-contact-in-exchange-does-not-change/84282Fri, 25 Apr 2025 13:20:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:80b649e5-2076-47e1-9d3b-af2b49b811b8Jeff ShahanThe tool is trying to delete and is being denied by the platform. This is a permissions issue.https://www.quest.com/community/notes-to-exchange-migration/f/forum/36257/proxyaddress-for-an-already-created-contact-in-exchange-does-not-changeFri, 25 Apr 2025 13:16:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d037df29-43bc-4f9c-805d-ef2d045d1a67pavel marinovWe are running a migration from Domino to M365. We created a pilot program with about 20 users. Customer decided to migrate with third party tool, so when they migrate the data to M365 mailboxes we disable the notes .nsf file and when we run the directory sync we do not get the contact deleted in AD. We also tried to modify the address of the source .nsf and update the contact in exchange to the new one, but this also fails with ERROR SyncRunner [Connector:notes to exch] [22] - Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))Coexistence Manager for Noteshttps://www.quest.com/community/notes-to-exchange-migration/f/forum/35345/please-wait-while-connections-to-configured-servers-are-tested-this-could-take-several-minutesTue, 26 Nov 2024 00:56:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:f1233d87-5ded-45aa-b41c-89d065194d6bdaniel downeyPlease wait while connections to configured servers are tested. This could take several minutes.. then it sits there for hours.. Nothing happens. We can access the Exchange services, SQL database, Lotus Notes, Active Directory using the account credentials.https://www.quest.com/community/notes-to-exchange-migration/f/forum/30621/probleme-beim-ubertragen-von-daten-von-nsf-in-das-pst-format/80579Thu, 25 Jul 2024 07:14:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:2fb8a526-962c-4400-979d-dfb7b1924883piravi7751Wenn Sie Probleme beim Übertragen von Daten vom NSF- ins PST-Format haben, können Sie dieses Problem mithilfe des TrustVare NSF-zu-PST-Konvertierungstool lösen, das eine schnelle Methode zur Konvertierung von NSF in PST darstellt. Dieses Tool erleichtert die Konvertierung einzelner und großer Lotus Notes-Dateien in das PST-Dateiformat, ohne dass Microsoft Outlook installiert werden muss. E-Mails, Kalender, Kontakte, Ereignisse, Notizlisten, Journale und andere Elemente aus IBM-Dateien werden in das Outlook-PST-Dateiformat konvertiert. Es ist benutzerfreundlich und sicher für alle Benutzer. Diese Anwendung ist mit allen Versionen des Windows-Betriebssystems, MS Outlook und Lotus Notes kompatibel.https://www.quest.com/community/notes-to-exchange-migration/f/forum/34030/problems-after-migrating-a-resource-from-notes-to-m365-when-rescheduling-an-appointmentWed, 08 Nov 2023 13:54:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:5608ca0b-08f6-4c7d-9f54-a44296490bdaandre gramsWe have a room in HCL Notes that contains both appointments via HCL Notes and M365 via coexistence After we migrated the room to M365 we have problems moving appointments. The appointments can be moved without an error message, but in the room calendar they are duplicated (at the old and the new time) Is there a solution to solve this problem?Coexistence Manager for NotesMigration Manager for Notes to Exchangehttps://www.quest.com/community/notes-to-exchange-migration/f/forum/33875/ssdm-errror-migrating-pab-address-bookTue, 26 Sep 2023 15:50:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:f5588313-e18b-48fa-a1d6-0ef30d5f256djulianfernandez externoHello everyone, when I try to migrate a personal address book (names.nsf) to a 365 account using SSDM Tool I get the following error in log: You did not choose to migrate your mail file. Migrated 0 of 70 object(s) with 2 error(s) and 0 warning(s) from your address book. Address Books for Migration: Reg. nombres de CSIF [namescsif.nsf] You did not choose to migrate an archive. I took an outlook in SSDM log 17:38:58 Creating the Outlook Services client for migrating to Exchange using the MNE MAPI/HTTP library. 17:43:02 DEBUG: DtMigSrc::CallCallback: Exit(1,2618 ms.) 17:43:03 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:03 DEBUG: DtMigSrc::CallCallback: Exit(1,2185 ms.) 17:43:03 DEBUG: InitializeMapiHttp - Connecting to the target mailbox. 17:43:03 DEBUG: The MAPI/HTTP connection request failed with the following error [Error en el servidor remoto: (403) Prohibido.]. Retrying after 30 seconds. 17:43:04 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:04 DEBUG: DtMigSrc::CallCallback: Exit(4,6268 ms.) 17:43:05 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:05 DEBUG: DtMigSrc::CallCallback: Exit(0,8727 ms.) 17:43:06 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:06 DEBUG: DtMigSrc::CallCallback: Exit(1,0852 ms.) 17:43:07 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:07 DEBUG: DtMigSrc::CallCallback: Exit(1,2747 ms.) 17:43:08 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:08 DEBUG: DtMigSrc::CallCallback: Exit(1,188 ms.) 17:43:09 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:09 DEBUG: DtMigSrc::CallCallback: Exit(1,175 ms.) 17:43:10 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:10 DEBUG: DtMigSrc::CallCallback: Exit(2,9613 ms.) 17:43:11 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:11 DEBUG: DtMigSrc::CallCallback: Exit(1,8688 ms.) 17:43:12 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:12 DEBUG: DtMigSrc::CallCallback: Exit(0,9322 ms.) 17:43:13 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:13 DEBUG: DtMigSrc::CallCallback: Exit(1,4688 ms.) 17:43:14 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:14 DEBUG: DtMigSrc::CallCallback: Exit(2,8751 ms.) 17:43:15 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:15 DEBUG: DtMigSrc::CallCallback: Exit(2,6481 ms.) 17:43:16 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:16 DEBUG: DtMigSrc::CallCallback: Exit(1,4811 ms.) 17:43:17 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:17 DEBUG: DtMigSrc::CallCallback: Exit(1,2146 ms.) 17:43:18 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:18 DEBUG: DtMigSrc::CallCallback: Exit(1,5112 ms.) 17:43:19 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:19 DEBUG: DtMigSrc::CallCallback: Exit(2,1761 ms.) 17:43:20 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:20 DEBUG: DtMigSrc::CallCallback: Exit(1,6005 ms.) 17:43:21 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:21 DEBUG: DtMigSrc::CallCallback: Exit(1,4774 ms.) 17:43:22 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:22 DEBUG: DtMigSrc::CallCallback: Exit(0,8958 ms.) 17:43:23 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:23 DEBUG: DtMigSrc::CallCallback: Exit(1,2848 ms.) 17:43:24 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:24 DEBUG: DtMigSrc::CallCallback: Exit(1,5132 ms.) 17:43:25 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:25 DEBUG: DtMigSrc::CallCallback: Exit(1,7706 ms.) 17:43:26 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:26 DEBUG: DtMigSrc::CallCallback: Exit(1,1695 ms.) 17:43:27 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:27 DEBUG: DtMigSrc::CallCallback: Exit(2,4375 ms.) 17:43:29 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:29 DEBUG: DtMigSrc::CallCallback: Exit(1,5363 ms.) 17:43:30 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:30 DEBUG: DtMigSrc::CallCallback: Exit(1,1755 ms.) 17:43:31 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:31 DEBUG: DtMigSrc::CallCallback: Exit(1,9611 ms.) 17:43:32 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:32 DEBUG: DtMigSrc::CallCallback: Exit(2,9191 ms.) 17:43:33 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:33 DEBUG: DtMigSrc::CallCallback: Exit(2,5484 ms.) 17:43:34 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:34 DEBUG: DtMigSrc::CallCallback: Exit(1,4513 ms.) 17:43:34 DEBUG: InitializeMapiHttp - Connecting to the target mailbox. 17:43:34 DEBUG: The MAPI/HTTP connection request failed with the following error [Error en el servidor remoto: (403) Prohibido.]. Retrying after 30 seconds. 17:43:35 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:35 DEBUG: DtMigSrc::CallCallback: Exit(2,7943 ms.) 17:43:36 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:36 DEBUG: DtMigSrc::CallCallback: Exit(2,5082 ms.) 17:43:37 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:37 DEBUG: DtMigSrc::CallCallback: Exit(1,5815 ms.) 17:43:38 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:38 DEBUG: DtMigSrc::CallCallback: Exit(1,7066 ms.) 17:43:39 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:39 DEBUG: DtMigSrc::CallCallback: Exit(2,1987 ms.) 17:43:40 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:40 DEBUG: DtMigSrc::CallCallback: Exit(1,3133 ms.) 17:43:41 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:41 DEBUG: DtMigSrc::CallCallback: Exit(2,0976 ms.) 17:43:42 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:42 DEBUG: DtMigSrc::CallCallback: Exit(3,1431 ms.) 17:43:43 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:43 DEBUG: DtMigSrc::CallCallback: Exit(2,019 ms.) 17:43:44 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:44 DEBUG: DtMigSrc::CallCallback: Exit(1,2434 ms.) 17:43:45 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:45 DEBUG: DtMigSrc::CallCallback: Exit(2,2884 ms.) 17:43:46 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:46 DEBUG: DtMigSrc::CallCallback: Exit(1,2649 ms.) 17:43:47 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:47 DEBUG: DtMigSrc::CallCallback: Exit(1,0503 ms.) 17:43:48 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:48 DEBUG: DtMigSrc::CallCallback: Exit(1,2548 ms.) 17:43:49 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:49 DEBUG: DtMigSrc::CallCallback: Exit(1,5357 ms.) 17:43:50 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:50 DEBUG: DtMigSrc::CallCallback: Exit(2,928 ms.) 17:43:51 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:51 DEBUG: DtMigSrc::CallCallback: Exit(2,1282 ms.) 17:43:52 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:52 DEBUG: DtMigSrc::CallCallback: Exit(1,7076 ms.) 17:43:53 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:53 DEBUG: DtMigSrc::CallCallback: Exit(2,2534 ms.) 17:43:54 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:54 DEBUG: DtMigSrc::CallCallback: Exit(2,0703 ms.) 17:43:55 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:55 DEBUG: DtMigSrc::CallCallback: Exit(2,4409 ms.) 17:43:56 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:56 DEBUG: DtMigSrc::CallCallback: Exit(2,6994 ms.) 17:43:57 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:57 DEBUG: DtMigSrc::CallCallback: Exit(3,0458 ms.) 17:43:58 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:58 DEBUG: DtMigSrc::CallCallback: Exit(1,5022 ms.) 17:43:59 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:43:59 DEBUG: DtMigSrc::CallCallback: Exit(0,6756 ms.) 17:44:00 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:44:00 DEBUG: DtMigSrc::CallCallback: Exit(2,178 ms.) 17:44:01 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:44:01 DEBUG: DtMigSrc::CallCallback: Exit(1,2037 ms.) 17:44:02 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:44:02 DEBUG: DtMigSrc::CallCallback: Exit(1,4534 ms.) 17:44:03 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:44:03 DEBUG: DtMigSrc::CallCallback: Exit(1,9924 ms.) 17:44:04 DEBUG: (376) DtMigSrc::CallCallback: Enter 17:44:04 DEBUG: DtMigSrc::CallCallback: Exit(2,2502 ms.) 17:44:04 DEBUG: InitializeMapiHttp - Connecting to the target mailbox. 17:44:04 ERROR: [0-239-10-80131509] System.Net.WebException: Error en el servidor remoto: (403) Prohibido. 17:44:04 ERROR: [4072-25-4-00000000]Unable to open target mail store 'xxxx@xxxx.xx'. 17:44:05 Acquired lock 'NOTESLOCK', continuing with operation. Does anybody has an Idea about this ? I am using version Migrator for Notes to Exchange 4.16.3.52 Thanks in advancehttps://www.quest.com/community/notes-to-exchange-migration/f/forum/33534/add-additional-username-to-person-document-using-cmn-dirsyncTue, 20 Jun 2023 09:47:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:652bd355-b840-42db-8ea3-1decd2ff2a4bmarvin dickhaus_41622Hey there, I know that it is possible for MNE to add the routing mail to the username field during migration. (Trevor answered this here ) However our use case is a bit different. We are still in the migration process, but new users are already only created in AD / Exchange Online. This requires CMN DirSync to write the contacts back into the Domino directory. How do I add the routing address as an additional usernames within the DirSync process to the respective user?https://www.quest.com/community/notes-to-exchange-migration/f/forum/32967/unable-to-retrieve-o365-domains/78429Wed, 07 Jun 2023 18:28:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:60784036-a924-4882-add7-7a10bcc9f367marvin dickhaus_41622Hey everyone, we experienced the same issue today. After the hint from Trevor and re-enabling RPS , we also needed to create an exclusion rule in our Conditional Access Policies to allow the Quest service account to use Basic Authentication. After two more minutes and also validating sign-on in the regular Exchange Online PowerShell (version 2.0.5) we were able to retrieve the domain list.https://www.quest.com/community/notes-to-exchange-migration/f/forum/32967/unable-to-retrieve-o365-domains/78372Thu, 25 May 2023 00:14:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:f05eccca-d91c-46f6-9a1b-aee79e4293bbmarc_93946I am dealing with the exact same thing at the moment. My logs are identical to the above. Been stuck on this for way too long. Our tenant was created long ago but I found that RPC was disabled. Ether way, enabling it again did not make a difference. Any other ideas?https://www.quest.com/community/notes-to-exchange-migration/f/forum/32967/unable-to-retrieve-o365-domains/78349Tue, 16 May 2023 17:45:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:9a35be77-0700-4444-bf91-78f90a6ea58fTrevor TaegderHello maxim souffriau , Thanks for posting in the Migrator for Notes to Exchange (MNE) forum. Any idea when this target Microsoft 365 tenant was created? Microsoft is disabling Remote PowerShell in new tenants. Here is a Microsoft article that discusses this situation and explains how to enable Remote PowerShell. This would only be a possible cause of the issue you are experiencing if the target M365 tenant was created after April 1st, 2023. Regards, Trevor Taegder Senior Technical Support Engineer Quest | Supporthttps://www.quest.com/community/notes-to-exchange-migration/f/forum/32967/unable-to-retrieve-o365-domainsTue, 16 May 2023 06:52:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:e30a25de-7e18-4b3f-8a5f-1bfe6ee9a1fcmaxim souffriauI am unable to retrieve Office 365 domains. All Prereqs are installed, no network connectivity issues found. Exchange online management 2.0.5 & Graph API on prerequisites have been installed. TLS 1.2 is enabled. getting following log. 17:04:14.758(1044:0594) DEBUG: Initializing powershell with domain controller: , global catalog: , server: , user: beheerderinetum@ecowerf.be, auth type: ModernAuthentication, proxy access type: None (empty), proxy auth type: Negotiate (empty), proxy user: 17:04:14.758(1044:0594) DEBUG: Creating PowerShell connection by account: beheerderinetum@ecowerf.be 17:04:14.758(1044:0594) DEBUG: [0-0-0-00000000] 17:04:14 Waiting for available connection. 17:04:14.758(1044:0594) DEBUG: [0-0-0-00000000] 17:04:14 Acquired available connection. 17:04:51.279(1044:0594) DEBUG: [0-0-0-00000000] Attempt 1 failed. Reason: Connecting to remote server outlook.office365.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic. 17:05:31.295(1044:0594) DEBUG: [0-0-0-00000000] 17:05:31 Waiting for available connection. 17:05:31.295(1044:0594) DEBUG: [0-0-0-00000000] 17:05:31 Acquired available connection. 17:06:03.256(1044:0594) DEBUG: [0-0-0-00000000] Attempt 2 failed. Reason: Connecting to remote server outlook.office365.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic. 17:06:43.271(1044:0594) DEBUG: [0-0-0-00000000] 17:06:43 Waiting for available connection. 17:06:43.271(1044:0594) DEBUG: [0-0-0-00000000] 17:06:43 Acquired available connection. 17:07:19.247(1044:0594) DEBUG: [0-0-0-00000000] Attempt 3 failed. Reason: Connecting to remote server outlook.office365.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic. 17:07:59.269(1044:0594) DEBUG: [0-0-0-00000000] 17:07:59 Waiting for available connection. 17:07:59.269(1044:0594) DEBUG: [0-0-0-00000000] 17:07:59 Acquired available connection. 17:08:31.251(1044:0594) DEBUG: [0-0-0-00000000] Attempt 4 failed. Reason: Connecting to remote server outlook.office365.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic.. Exception rethrow. 17:08:31.251(1044:0594) ERROR: Fail to Init PowerShell session due to : Connecting to remote server outlook.office365.com failed with the following error message : For more information, see the about_Remote_Troubleshooting Help topic. 17:08:31.251(1044:0594) DEBUG: PSBase::Init: Exit(256495 ms.) 17:08:31.251(1044:0594) ERROR: [619-256-1-00000000]Unable to get hosted domains. Please check the administrator user name and password. 17:08:31.251(1044:0594)https://www.quest.com/community/notes-to-exchange-migration/f/forum/32690/nme-service-account-from-o365-must-be-a-global-admin-or-may-have-other-permission/78027Thu, 01 Dec 2022 14:46:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:671a1d29-a43f-4912-b4f6-390ca4fc88eaJeff ShahanFor full functionality a GA is required, there are a lot of administrative tasks the tool needs to/can perform . If the customer is willing to except doing some task manually/scripted and presenting mailbox enabled users with the service account having full control/receive as permissions, the GA is not required.https://www.quest.com/community/notes-to-exchange-migration/f/forum/32690/nme-service-account-from-o365-must-be-a-global-admin-or-may-have-other-permissionThu, 01 Dec 2022 14:02:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d3a2f44c-f03e-42a8-9ef9-b5b12234936brenato cardiaHi, I am coonfiguring NME and my customer is not allowing to have a Global Admin in O365. To get around, what permissions this account needs to have? Thank youNME