Dear All
i have implement new exchange server 2013 installed on virtual Machine with windows server 2012 R2 but we face a problem all the emails sent isdelayed until to send from exchange up 20 minutes.
Dear All
i have implement new exchange server 2013 installed on virtual Machine with windows server 2012 R2 but we face a problem all the emails sent isdelayed until to send from exchange up 20 minutes.
Proper permission play an important role in Exchange administration. One of my customers came across an issue on permission. He would like to know the minimal permission when connecting to a mailbox.
1. If you just want administrators to connect mailbox through PowerShell, follow the steps below.
a. Create new management role.
New-ManagementRole -Name “connect-mailbox test1” -Parent “Mail Recipients”
From the picture below, we can see, there are too many role entries about this management role.
b. Use the following cmdlet to remove other role entries except the connect-mailbox role entry.
Get-ManagementRoleEntry "connect-mailbox test1\*" | Where {$_.name -ne "Connect-Mailbox"} | Remove-ManagementRoleEntry
c. Then you can use the following cmdlet to check the result.
d. New role group
e. Add the user you want to grant this connect-mailbox permission to this role group through EAC.
f. Here is result when I logon to connect the mailbox.
Note: Using the above permission, you only can connect mailbox using PowerShell.
2. If you want to connect mailbox via EAC, you need more permissions:
Get-user, Get-recipient, Get-mailbox and Get-MailboxStatistics role entries in the View-Only Recipients role; Get-MailboxServer role entry in the View-only Configuration role; Connect-Mailbox role entry in the
Mail recipients role. Here are the detailed steps to assign it.
a. Create New Management Role named View-Only Recipients test.
New-ManagementRole -Name “View-Only Recipients test” -Parent “View-Only Recipients”
b. Also, there are too many role entries of the View-Only Recipients role. Here are some of these role entries.
c. Remove other entries except the Get-Mailbox role entry.
Get-ManagementRoleEntry "View-Only Recipients test\*" | Where {$_.name -ne "Get-Mailbox"} | Remove-ManagementRoleEntry
d. Add Get-User, Get-recipient, Get-Mailboxstatistics role entries to this role.
Add-ManagementRoleEntry "View-Only Recipients test\Get-User"
Add-ManagementRoleEntry "View-Only Recipients test\Get-recipient"
Add-ManagementRoleEntry "View-Only Recipients test\Get-Mailboxstatistics"
e. All the role entries of View-Only Recipients test role are listed here.
f. Create a new management role named View-Only Configuration test.
New-ManagementRole -Name “View-Only Configuration test” -Parent “View-Only Configuration”
g. Remove all but one Get-MailboxServer role entry from the role.
Get-ManagementRoleEntry "View-Only Configuration test\*" | Where {$_.name -ne "Get-MailboxServer"} | Remove-ManagementRoleEntry
h. New Role Group named connect mailbox via EAC.
New-RoleGroup -Name “connect mailbox via EAC”
i. Add the above three custom role to this role group, and then add amy01 as the member of the connect mailbox via EAC role group.
j. Logon to EAC to connect mailbox.
References:
http://blogs.technet.com/b/agobbi/archive/2009/12/11/understanding-and-implementing-rbac.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.
Hi!
We updated our Exchange 2010 to SP3 and then install update roll up 7 but Exchange is still showing Version 14.3 (Build 123.4).
Any Suggestions?
Thanks.
Hello,
I'm in the process of migrating mailboxes from Exchange 2010 SP3 servers to new Exchange 2013 SP1 CU6 servers.
I'm seeing issues post migration with around 50% of users, being prompted for credentials when opening Outlook. All users use Out look in cached mode.
The connection that is prompting is that for the OAB download. Once the creds are entered the connection is established and the OAB can be downloaded.
The users that are being prompted for credentials are downloading the OAB associated with the new Exchange 2013 database to which they have been migrated.
The users who are not being prompted for credentials are downloading the old 2010 OAB, even though their mailbox resides on a new Exchange 2013 database with a new 2013 OAB associated.
It's worth mentioning that public folder distribution is enabled for the 2010 OAB, as well as web distribution.
Public folder distribution is not enabled for the 2013 OAB, as I understand it cannot be enabled (and errors when I attempt to enable).
The public folder hierarchy has yet to be migrated from 2010.
Can anyone explain why I'm seeing this issue, and how to overcome it?
Thanks
Matt
I cannot disable a mailbox in Exchange 2013 CU6. I get the following error:
Anyone seen this error? As you know, I just want to remove the Exchange attributes from the user object in Active Directory. Of course, deleting the user object works just fine but don't want to go that route.
Hello
Does anybody know how to interrogate the Exchange server in order to obtain the following information:
The total amount of messages received by a specific connector (send or receive) within the last 24hours for a specific smtp domain name (eg yourname.com)
I'm currently hunting around in the message tracking logs area...Am I barking up the wrong tree?
Im actually looking for the powershell command that could obtain the required information?
Any help would be greatfully appreciated
Thanks in advance
Does anyone know if i export an mailbox to PST if the mailbox is still available to the user? also does the export "move" the emails to PST or does it "copy"?
We are looking at a migration project and workaround solution might be to export to PST, fly to the datacentre and import :)
Hi All,
I seem to have now gotten stuck with failed content index on all my databases. I have tried every known remedy (creating contentsubmitters group, removing references to it, etc) but still my content indexes remain in a failed state. The warning message I keep getting is the common MSExchangeFastSearch Event source with EventID 1009:
The indexing of mailbox database XXXX encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Fast.FastConnectionException:
Connection to the Content Submission Service has failed. ---> Microsoft.Ceres.External.ContentApi.ConnectionException: Given CSS specification failed:
Could not connect to CSS node at net.tcp://localhost:3828/ContentSubmissionServices/content with flow: Microsoft.Exchange.Search.Writer.36. Error: This request operation sent to net.tcp://localhost:3828/ContentSubmissionServices/content did not receive a reply
within the configured timeout (00:10:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message.
Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. Inner exception:---
at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder.SetCssNodes(IEnumerable`1 newCssNodes)
at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder..ctor(DocumentFeederOptions options)
at Microsoft.Exchange.Search.Fast.FastFeeder.Initialize()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Search.Fast.FastFeeder.Initialize()
at Microsoft.Exchange.Search.Fast.Factory.InternalCreateFastFeeder(ISearchServiceConfig config, String indexSystemFlow, String indexSystemName, String instanceName, Int32 numberOfSessions)
at Microsoft.Exchange.Search.Engine.SearchFeedingController.InitializeFastFeederAndWatermarkStorage()
at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()
at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)
PLEASE HELP!!!!!!!!!
Having nothing but problems with this Exchange 2013 deployment, and its the simplest way to deploy Exchange. Single server, single domain controller, on the same box.
A few weeks ago, out of nowhere a server that was running fine, started reporting ASP errors and no access to the ECP or OWA would function. Rebooting didn't help. Restarting IIS didn't help. Only Exchange and ADDS run on this server.
Was recommended through an Exchange 2013 forum to install SP1 to fix this issue. That was a nightmare in itself, 18 steps, 50% of which failed one by one and had to work through those issues. Once it completed, OWA and ECP worked again, but only for 24 hours or probably less if I was up all day. Now OWA works if I typehttps://ffws01/owa and login, but if I try https://ffws01/ecp I get a login prompt, then when logging in it goes 500 Internal Error.
PowerShell command Get-MailboxDatabaseCopyStatus shows ContentIndexStatus as "Failed and..."
There are three mailbox databases, the default randomly generated one, then MBX1 and MBX2.
I am at a loss right now, and have no idea what to do with this box. Users are able to access their mailboxes though from Outlook 2010 and Outlook 2013. Just have no way of managing this server anymore.
I've seen that you can set an Organization-wide scope for a ThrottlingPolicy in Exchange 2013 (for a RecipientRateLimit) but I cannot find a way to do that in Exchange 2010. Will the following command work in 2010, or is there a comparable command/method for 2010? I need this to be set for all existing users, on all servers/databases, and for all future users as well.
New-ThrottlingPolicy -Name RecipientsLimit -RecipientRateLimit 500 -ThrottlingPolicyScope Organization
Thank you.
Über Random
Hello all. Love how there isn't a category on the forums for Exchange 2010.. Anyhow, I am trying to add a single e-mail address to safe senders for all mailboxes. I found the following commands work for adding an address to a single mailbox. How would the syntax need to change to preserve everyone's unique settings and add just one address?
$Address = Get-MailboxJunkEmailConfiguration "username"
$Address.newentry += "test@domain.org"
$Address.TrustedSendersAndDomains += "test@domain.org"
Set-MailboxJunkEmailConfiguration "username" -TrustedSendersAndDomains $Address.TrustedSendersAndDomains
After Upgrading my Exchange 2013 to CU1, I no longer can add the reset password functionality in ECP's Organization Management. The administrator account is part of that group but when i try adding the reset password role to it i get:
| ||
|
Hi,
We've just increased the message size limit using the EAC (Mailbox Features-->Message Size Restrictions) of a particular user to 15000 kb.
Now when I test from the external an email of 13mb, I got a bounce saying
The error that the other server returned was: 552 5.3.4 Message size exceeds fixed limit
Is there anywhere else I should check for increasing message size limits? Or is it just taking some times? Or maybe a service I should restart?
(Forgot to mention, we are using Exhange 2013 Server.)
Thanks to all
Martin
Randomly on my exchange server (Exchange 2007 SP3 with Rollup 14 on Server 2008 R2, fully patched), the validports registry value data revert from the data I entered to the "default" data. The "default" values I'm describing are machinename:ports and fqdn:ports. I modify the data to include the external fqdn:ports. I'm not sure what's causing this, this has been happening for a while, though; i.e., since outlook anywhere was initially set up.
Moderator note: I couldn't put this topic into a non-exchange 2013 forum, as I was only presented with 2013 choices in the forum chooser. Please move this topic to the appropriate forum.
EDIT: I can't find any Tasks or items in RSOP that point to this issue. Also, I though this behavior was only present when I rebooted the system, but I just had the data revert after an hour of the system just sitting there.
EDIT: Outlook Anywhere was initially configured using the Exchange Management Console. In the console, if I go to server configuration -> Client Access, go to the server properties -> Outlook Anywhere tab, the External host name field is populated correctly.
EDIT: Found the answer at http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspxHello everyone,
Babu
Hi, we have an Exchange 2013 environment for hosting purposes.
One client uses two seperate company names (and domain names). These companies are seperated in Exchange and use seperate address lists. This client uses mail between the two domains.
Let's say the domains are yin.com and yang.com. The users use Outlook Webmail and the Mac OSX builtin mailclient
The problem is that when kevin@yin.com sends email to bob@yang.com, Bob is able to receieve the mail, but the email-address from Kevin is not included in the mail. It is just listed as Kevin, without any property.
When Bob replies to the message from the OSX Mail client, it apparently tries to make up an address and generates something to the effect of this:
Kevin </o=Hosting Company/ou=Exchange Administrative Group /cn=Recipients/cn=*longnumber*>
This address is not correct and when sent, the email is bounced back with a NDR-report.
When Bob replies to the message from OWA, the address is simply the name with no email-address. This also results in an NDR report.
What can we do to make OWA or Mac mail keep the correct emailaddresses?
Hi Friends
I need your help for getting information on exchange mailbox user who had sent or received mails along with attachment file name for entire day.
Basically I get the information of entire mails which had received or sent in all days but I am unable to get the information about attachment file name.
Please do the needful.
Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
Hi,
there is a way to export PF structure and contents to a .PST file instead to use MS Outlook for that
tks,
Renato P
I am running Exchange 2013 on Server 2012 Datacenter (VM). Windows 7 clients with Outlook 2010 work fine. Windows XP clients with Outlook 2010 prompt for credentials (user name and password) each time Outlook is started, and checking the "Remember my password" box does not prevent this from happening the next time. The "Always prompt for logon credentials" checkbox on the "Security" tab of the "More Settings" section of the Exchange account is not checked. I have found a myriad of posts with similar issues, but they all seem to have to do with SBS/Exchange 2007, and I haven't come across something that works as a solution for me. One suggested certificate issues, and I was having certificate security warnings, but I got that resolved. I am hopefuly that the fact that this only happens on Windows XP will be telling.