Enable-RemoteMailbox "Kim Akers" -RemoteRoutingAddress "[email protected]" -Archive
This example does the following:
<<-- Mail-enables an existing on-premises user. -->> This needs to be removed.
<<-- Creates the associated mailbox in the service. -->> This needs to be removed.
Creates an archive mailbox in the service for the mailbox.
To mail-enable an on-premises user, create the associated mailbox in the service, enable the archive mailbox in the service and include the Archive switch with the Enable-RemoteMailbox cmdlet.
In order to configure archive mailbox in service primary mailbox should be either provisioned in On-Prem or On Cloud.
The cmdlet will in the example two will error out:
Parameter set cannot be resolved using the specified named parameters.
If you remove the remoteroutingaddress paramter you will see the following exception which would validate that the recipient type isn't supported for this task unless primary mailbox is not provisioned.
This task does not support recipients of this type. The specified recipient domain.com/OU/User is of type User. Please make sure that this recipient matches the required recipient type for this task.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@officedocsbot assign @yogkumgit
Hello @sujithnair79 thanks for your feedback.
I am proposing thru a pull request, to change the example number 2 to a working example.
Hopefully, if the article author approves it, it will go live.
Thank you
@chrisda Please merge the PR #3815
Hello @sujithnair79 thanks for your feedback.
I am proposing thru a pull request, to change the example number 2 to a working example.
Hopefully, if the article author approves it, it will go live.
Thank you
Thanks Andres.
@get-itips Thank you very much for the contribution and updating the documentation with PR. @sujithnair79 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.
@officedocsbot close
I could not understand if this change is approved and if in deed we have the change effective. I do not see any update in the doc yet.
Hello @sujithnair79 the PR was merged and it will take a while to be reflected live. Please check back in a few days.
This change is still not updated. The example description is still incorrect.
Hello @sujithnair79 Can you please be more descriptive about why you see that the description is still incorrect? Thank you, I appreciate.
[Image]
Please refer to my previous comment in the below link and currently what is displayed in article.
https://github.com/MicrosoftDocs/office-docs-powershell/issues/3792
Thanks,
Sujith Nair
Get Outlook for Androidhttps://aka.ms/ghei36
From: Andres Mariano Gorzelany notifications@github.com
Sent: Monday, September 16, 2019 7:44:47 PM
To: MicrosoftDocs/office-docs-powershell office-docs-powershell@noreply.github.com
Cc: sujithnair79 sujithnair79@msn.com; Mention mention@noreply.github.com
Subject: Re: [MicrosoftDocs/office-docs-powershell] Example 2 statement update request. (#3792)
Hello @sujithnair79https://github.com/sujithnair79 Can you please be more descriptive about why you see that the description is still incorrect? Thank you, I appreciate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/3792?email_source=notifications&email_token=AM2G6LWHA23BI3J6S2M3E6TQJ6IFPA5CNFSM4IJKWGMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6ZJEYQ#issuecomment-531796578, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM2G6LWHG3TRK7DF2PFON7LQJ6IFPANCNFSM4IJKWGMA.
@sujithnair79 already see your previous comment but I think it needs more descriptive explanation by you, what are you trying to achieve, did you try the correct example, etc.
thanks
@sujithnair79 Please reply
@get-itips Thank you very much for the contribution and digging deep into it. @sujithnair79 We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.