User Profile
Iriy777
Brass Contributor
Joined Feb 15, 2023
User Widgets
Recent Discussions
Re: New-MigrationBatch strange behavior of parameters
[PS] C:\Temp>Get-ManagementRoleAssignment -Role 'Migration' | ft Role, RoleAssigneeName Role RoleAssigneeName ---- ---------------- Migration Organization Management Migration Recipient Management Migration Organization Management Migration Account Management Migration Admin-Test Second command shows that I am the member of Organization Management I am running it directly from Exchange server, though I tried a few times from my laptop through pssession to different servers962Views0likes1CommentRe: New-MigrationBatch strange behavior of parameters
[PS] C:\Temp>Get-ManagementRoleEntry -Identity '*\*' -Parameters StartAfter | ft Name, Role Name Role ---- ---- New-MailboxRelocationRequest Move Mailboxes Set-MoveRequest Move Mailboxes New-MoveRequest Move Mailboxes New-MigrationBatch Migration Set-MigrationBatch Migration Both users has roles Migration and Move Mailboxes. New user I tried too. I also tried to take my user out of the group, wait a few hours and add back - same result1KViews0likes3CommentsNew-MigrationBatch strange behavior of parameters
I encounter a strange issue when trying to use New-MigrationBatch command with -StartAfter parameter. It does not auto fill it when typing 'st' + TAB and gives "Parameter cannot be found" if I write it explicitly. I am a member of Organization Management group. However, helpdesk technician can use this parameter!!! Tried connecting to the same or different Exchange server with RDP + EMS or through pssession - for him it works, for me - it doesn't. I tried to create a new admin role, assign it all roles there are and assigning it to the new user - same result as me. When me and the other tech run (Get-Command New-MigrationBatch).Definition - I don't get the -StartAfter parameter, but he does! Everything else works fine, from what I tried. The New-MigrationBatch is also working for me without -StartAfter parameter, but I need it for script. Couldn't find anything useful on the Internet, any ideas? Running Exchange 2016 CU23Solved1.2KViews0likes5CommentsForwarding issue when sending to DL
Hi, I have a following scenario: In the domain A and Domain B. There is a userDomainA. He sends email to userDomainB that has forwarding configured on his mailbox to forward all with keeping copy to contactA with address userDomainA. Everything works fine. Now userDomainA sends email to groupDomainBmailto:email address removed for privacy reasons, where userDomainB is a member and getting Delivery Failed message. There is a mail relay that allows only internal Exchange servers to send from DomainA. When sending directly to userDomainBmailto:email address removed for privacy reasons, the email that was forwarded is received with envelope sender of userDomainBmailto:email address removed for privacy reasons, as it should be. However, when the message is sent to DL - envelope sender is listed as userDmainA and thus being blocked by relay. I have access to both Exchanges. Issue is reproducible with new users and groups. Any idea how I can solve it? I have a few users that has mailboxes in both domains and want the same setup681Views0likes1Comment
Recent Blog Articles
No content to show