I have been trying to export a few mailboxes for the past 2 days with only 1 sucessful export.
I'm currently trying to export an archive of a user but it stays "queued" even tho there are no other export requests:
[PS] C:\Windows\system32>Get-MailboxExportRequestStatistics -Identity Cam.Ansell\mailboxexport1
Name Status SourceAlias PercentComplete
---- ------ ----------- ---------------
MailboxExport1 Queued cansell 0
any ideas how to force it to start it?
Try restarting the MS Exchange Mailbox Replication service on the CAS server.
Related
I am new to Microsoft Windows clustering, and we have an environment in which it is required that we bring 'clustered roles' down and up on schedule. Currently, I have been manually processing this, but would like to automate it using Powershell.
I have read through the Cmdlets here , but can't seem to find one that references roles specifically. I was looking at the commands to stop the entire cluster, but that looks like it will take down resources that are not covered by the two roles that I am specifically required to take down.
Example of role I would like to bring down:
Stop-ClusterResource is your friend. This cmdlet takes one selected part of cluster (one resource) offline. Then you can Start-ClusterResource at the desired time.
Stop/Start/Query Microsoft Windows Cluster Roles with Powershell [Tested in Windows Server 2012-R2]
C:\>powershell Stop-ClusterGroup "ARCSDE52"
Name OwnerNode State
---- --------- -----
ARCSDE52 PRODNODE_AC Offline
C:\>powershell Get-ClusterGroup "ARCSDE52"
Name OwnerNode State
---- --------- -----
ARCSDE52 PRODNODE_AC Offline
C:\>powershell Start-ClusterGroup "ARCSDE52" -Wait 0
Name OwnerNode State
---- --------- -----
ARCSDE52 PRODNODE_AC Pending
C:\>powershell Get-ClusterGroup "ARCSDE52"
Name OwnerNode State
---- --------- -----
ARCSDE52 PRODNODE_AC Online
A week back I upgraded my Exchange environment from E2K10 SP1 to E2K10 SP3.
Since then, I am unable to export mailboxes with New->MailboxExportRequest powershell script. Even though, I'm having right permission to export the mailboxes.
The cmdlet which I'm making use of is this:
New-MailboxExportRequest-Mailbox user-FilePath \\MailServer\PST\user.pst
The above cmdlet is identified and it is has been queued permanently.
Can anyone tell me why this has happened?
Did you have a DAG?
Have you tried to restart the Exchange Mailbox Replication service on all CAS servers to verify the result?
I suggest you to check the status of this mailbox database if it is mounted. You can use the following command to check this.
Get-MailboxDatabaseCopyStatus -Identity "mailbox database name"
Alongside, please make use of the Get-MoveRequestStatistics cmdlet to view full information about move requests.
We had an issue with our Exchange 2010 outlook or server and for some reasons we had all our user receiving internally and externally duplicated mails with the same message ID.
I know there are third party software we can buy and we are not allowed to do so.
Is there any code we can run on PowerShell to delete all the duplicated mails on the all mailboxes on the server?
thanks
Mes
There is this script (https://gallery.technet.microsoft.com/office/Removing-Duplicate-Items-f706e1cc) which suggested by Microsoft, but you must specify the user mailbox.
Put this script to that destination
C:\Program Files\Microsoft\Exchange\Web Services\1.2
After that use this command:
.\Remove-DuplicateItems.ps1
-Mailbox "user#domain.com"
-Type All
-Impersonation
-DeleteMode HardDelete
-Mode Full
-Verbose
You can change the delete mode to 'SoftDelete' or 'MoveToDeletedItems' etc.
I'm trying to use impersonation in my application to connect to user mailboxes and add/remove appointments.
I created an account called "EWSAdmin" and ran the following EMS commands on them:
New-ManagementScope -Name:"MyEWSImpersonation" -RecipientRestrictionFilter
{memberofgroup -eq "cn=My User Container,DC=MyDomain,DC=local"}
New-ManagementRoleAssignment -Name:"MyEWSImpersonation" -Role:ApplicationImpersonation
-User:"EWSAdmin#MyDomain.local" -CustomRecipientWriteScope:"MyEWSImpersonation"
Just to confuse the issue, I called my scope EWSImpersonation, too.
When I try to connect to the user's mailbox to view an appointment (Using a third party DLL), I get the following error:
Throwing GeneralException e=The account does not have permission to
impersonate the requested user.
If anybody could help me diagnose this, I'd appreciate it.
Thanks
Nick
We ran into this issue with a different cause, I want to share it here because when searching for the error message this post and a post on TechNet come up, but not the KB Articles that eventually helped us solve the issue.
It turns out that there is a limit to the amount of requests any windows server can do to Active Directory, at some point the NetLogon service just runs out of Threads and all kinds of things start to happen. The process is explained in this blog post and this KB article and this KB article, the fix is pretty simple, increase the number of threads available through a simple change to a Registry key on every CAS server in the Exchange cluster.
The process is simple:
Start Registry Editor.
Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
Create the following registry entry:
Name: MaxConcurrentApi
Type: REG_DWORD
Value: Set the value to the larger number, which you tested (any number greater than the default value).
At a command prompt, run net stop netlogon, and then run net start netlogon.
Notes
The maximum value that can be configured depends on the operating system version and whether a hotfix is available.
The maximum configurable setting in Windows Server 2003 is 10.
The maximum configurable setting in Windows Server 2008 (without the hotfix in this article) is 10. With the hotfix, the maximum is 150.
The maximum configurable setting in Windows Server 2008 R2 (without the hotfix in this article) is 10. With the hotfix, the maximum is 150.
If you decide to increase the MaxConcurrentApivalue to greater than 10, the load and the performance of the desired setting should be tested in a nonproduction environment before you implement in production. This is recommended to make sure that increasing this value does not cause other resource bottlenecks.
I know almost nothing about "admin" side of setting up impersonation for EWS but maybe you can take a look at this article and compare your actions with what this guy did to make it work
http://www.thesoftwaregorilla.com/2010/06/exchange-web-services-example-part-3-exchange-impersonation/
in my company admin setup impersonation according to msdn and it works for me so I presume it can't be so hard and probably you missed some steps or maybe that 3rd party dll needs some additional magic.
link to msdn article in case you didn't know it: http://msdn.microsoft.com/en-us/library/bb204095.aspx
It would be nice to have an example for E2010 as it is not as easy as 2007.
Here is an example to creating EWS impersonation for a group. Any member of the group would be impersonated by the service account. Just add additional members to the group as requirements demand. Two steps...create the New Management scope and then the Role assignment.
New-ManagementScope “Scope Name” -RecipientRestrictionFilter {(MemberOfGroup -eq 'CN=group name,CN=Users,DC=Contoso,DC=com')}
New-ManagementRoleAssignment -Name “EWS ROLE NAME” -Role applicationimpersonation -User Domain\Service Account -CustomRecipientWriteScope “Scope Name”
Where “Scope Name” is the management scope created in step one.
We have an Exchange Server running, we're trying to connect with it from an application in another server. Thing is, we have to set some permissions for it to work (we want to access any mailbox with an Administrator mailbox, but we have to set it Full Mailbox Access first). We somehow need to set this for every new user at the moment it's created. Could you tell us how do we do that?
Thanks in advance.
Here is one way to do it.
http://support.microsoft.com/kb/821897
Another way to do this is , type following command in the Exchange Management Shell
Add-MailboxPermission -Identity "" -User "" -AccessRights FullAccess -InheritanceType All
Using Exchange Management Shell commands, you can do many useful things easily.