Closed jspern closed 1 year ago
Are you running this from a standard powershell and not an exchange management shell.
Can you send me a full log?
============================== Timothy J. McMichael Senior Support Escalation Engineer @.**@.> (980)-776-7465
Hours: Sunday - Wednesday 08:00 - 16:00 eastern time zone.
Manager: Tom Roughley @.**@.>)
Premier Support - (800)-936-3100 Broad Commercial Support - (800)-936-4900
==============================
From: jspern @.> Sent: Monday, February 13, 2023 12:19 PM To: timmcmic/DLConversionV2 @.> Cc: Subscribed @.***> Subject: [timmcmic/DLConversionV2] The term 'get-o365Recipient' is not recognized (Issue #120)
When running a basic migration, it errors out due to the renamed cmdlets not being found.
Get-O365DLConfiguration : The term 'get-o365Recipient' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At C:\Program Files\WindowsPowerShell\Modules\DLConversionV2\2.9.6.4\DLConversionV2.psm1:1430 char:39
... nfiguration=Get-O365DLConfiguration -groupSMTPAddress $groupSMTPAddre ...
+ CategoryInfo : ObjectNotFound: (get-o365Recipient:String) [Get-o365DLConfiguration], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,Get-o365DLConfiguration
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftimmcmic%2FDLConversionV2%2Fissues%2F120&data=05%7C01%7Ctimmcmic%40microsoft.com%7C7977b9725d7a46e9944308db0de66cbf%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638119055538368566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Xrm9ze5jjKLUsEhcBY8hLrfTiv4%2FXrYBjO7mZrgjjQM%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKGTN6JVCYG3W42E4H5F3ATWXJUI7ANCNFSM6AAAAAAU2REBZU&data=05%7C01%7Ctimmcmic%40microsoft.com%7C7977b9725d7a46e9944308db0de66cbf%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638119055538368566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MdIAeyfPkZNAe8ef3PKJxZDxXJ8mki2MyL%2FGVGCvZgo%3D&reserved=0. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>
I was able to narrow it down to .NET 4.8 not being installed on the machine I was running the migration from. All is good now, thank you.
I'd still like to see the log - you should have been failing before this I would have thought.
============================== Timothy J. McMichael Senior Support Escalation Engineer @.**@.> (980)-776-7465
Hours: Sunday - Wednesday 08:00 - 16:00 eastern time zone.
Manager: Tom Roughley @.**@.>)
Premier Support - (800)-936-3100 Broad Commercial Support - (800)-936-4900
==============================
From: jspern @.> Sent: Monday, February 13, 2023 1:13 PM To: timmcmic/DLConversionV2 @.> Cc: Tim McMichael @.>; Comment @.> Subject: Re: [timmcmic/DLConversionV2] The term 'get-o365Recipient' is not recognized (Issue #120)
- Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftimmcmic%2FDLConversionV2%2Fissues%2F120%23event-8507472100&data=05%7C01%7Ctimmcmic%40microsoft.com%7Cbb197bcd085d4fe23a7c08db0dedf442%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638119087888377613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NbsGYKhl8KvjF9w6OrWDvbooLZ9B%2BU7KRaYo0IxG7go%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKGTN6NU3VOO2DFO3WLZIRLWXJ2TDANCNFSM6AAAAAAU2REBZU&data=05%7C01%7Ctimmcmic%40microsoft.com%7Cbb197bcd085d4fe23a7c08db0dedf442%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638119087888377613%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Lshh86By%2Bdd5HJ3jcz1WD3YINbunSYYGMX8t6HDDw4M%3D&reserved=0. You are receiving this because you commented.Message ID: @.**@.>>
I can't share the full logs as they contain sensitive information that I'm not authorized to share; I would have to sanitize the log first. The other thing I did change to get it working was to specify the -exchangeOnlineCredential
parameter, which I was not doing previously because the documentation said that it was an optional parameter. I was able to successfully migrate one DL, but now on another I am getting an "OFFICE_365_DEPENDENCY_NOT_FOUND_EXCEPTION" for one particular member of the DL.
In newer builds the credential is optional because it should be prompting you if not specified. This was to support interactive authentication in single DL migrations.
Tim
============================== Timothy J. McMichael Senior Support Escalation Engineer @.**@.> (980)-776-7465
Hours: Sunday - Wednesday 08:00 - 16:00 eastern time zone.
Manager: Tom Roughley @.**@.>)
Premier Support - (800)-936-3100 Broad Commercial Support - (800)-936-4900
==============================
From: jspern @.> Sent: Monday, February 13, 2023 1:35 PM To: timmcmic/DLConversionV2 @.> Cc: Tim McMichael @.>; Comment @.> Subject: Re: [timmcmic/DLConversionV2] The term 'get-o365Recipient' is not recognized (Issue #120)
I can't share the full logs as they contain sensitive information that I'm not authorized to share; I would have to sanitize the log first. The other thing I did change to get it working was to specify the -exchangeOnlineCredential parameter, which I was not doing previously because the documentation said that it was an optional parameter. I was able to successfully migrate one DL, but now on another I am getting an "OFFICE_365_DEPENDENCY_NOT_FOUND_EXCEPTION" for one particular member of the DL.
- Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftimmcmic%2FDLConversionV2%2Fissues%2F120%23issuecomment-1428457914&data=05%7C01%7Ctimmcmic%40microsoft.com%7C97b4b50813f5416d277708db0df0fd7c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638119100913916049%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pvYGsByTDT2ZTAHkukgukxic0tQUFD3oUc8NMaFSnnc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKGTN6MMPNGZQ3LL3Q65ZVDWXJ5ETANCNFSM6AAAAAAU2REBZU&data=05%7C01%7Ctimmcmic%40microsoft.com%7C97b4b50813f5416d277708db0df0fd7c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638119100913916049%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JWsNGaI%2BXQ66fZfJdAX1d931Aceq4uLQGnwSV90%2Fk78%3D&reserved=0. You are receiving this because you commented.Message ID: @.**@.>>
When running a basic migration, it errors out due to the renamed cmdlets not being found.