Solutions (36)
Enterprise Vault, one of the widely used/accepted solution for Email and File Archiving. The solution has improved drastically in version 11. However, it lack control in many area such as monitoring, partition size monitoring etc. This script will help you to extract the existing size of all open partitions across all Enterprise Vault Servers. The script is tested on Enterprise Vault Ver 11.0. Download the complete script do few modification to work with your infra. Note - The Enterprise Vault scripts will only run on x86 powershell version. This limitation is because the commands from EV are not designed to work in 64 bit version of powershell. Ensure you run the script in x86 powershell. Download the Script Here The Full Script: Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.AdminAPI.dll" Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.Core.dll" Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.IMAP.dll" Import-Module "C:\Program Files (x86)\Enterprise Vault\Symantec.EnterpriseVault.PowerShell.Monitoring.dll" $PartitionSize = "C:\Scripts\HTML\Partition_Size.htm" #Update the path you wish…
Published in
Solutions
Event ID 15021, HTTPEvent Error An error occurred while using SSL configuration for endpoint 0.0.0.0:444 – Exchange Server 2013 Error Decription: An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data. You will find the multiple events are thrown every minute with similar description. This is a common error I observed in Exchange Server 2013. You will observe the all or few of the following, 1. Exchange Administration Center (EAC) returns blank page 2. The OWA allows login, but returns blank similar to EAC result 3. Outlook or any other Exchange Clients will fail to connect. 4. Exchange Management Shell Fails to connect. This happens, I suppose, due to the usage of non-existed certificate. I have verified the ID of the certificate in question with the available certificate in my SSL store, however I did not find the one which…
Published in
Solutions
The previously reported issue with Cumulative Update 6 (CU6) for Microsoft Exchange Server 2013, that you cannot manage Exchange Online mailboxes by using Exchange Admin Center (EAC) from an on-premises server. This issue has been addressed by Microsoft in lightning response, the following script will help you to fix this issue. Download: Exchange Online mailboxes cannot be managed in Exchange Server 2013 CU6 To know more about the issue, please see Exchange Online mailboxes cannot be managed by using EAC after you deploy Exchange Server 2013 CU6 -Praveen
Published in
Solutions
As active sync, one of the common technologies used for mobility of email, is used very widely now a days. So it is very important to know the volume of Exchange 2003 Active Sync (EAS) usage. EAS logs a lot of data in IIS about what’s going on, but parsing out this will be a huge headache. To analyze the data we can use the Log Parser tool from Microsoft.Download Log Parser tool from below link: http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=enWe can use SQL scripts to work with the Log parser tool to generate the hit ratio of EAS usage.Note – We should enable the IIS W3C Extended Log File Format. The output will also give you the details of user alias name of the users who are currently using the Exchange Active Sync feature. This way the EAS usage report can be generated.
Published in
Solutions
Hope you all would have planned to upgrade your Exchange 2007 to Exchange 2007 SP3. In this post I would like to inform you one of the issues reported. In Exchange 2007 SP3, there is a mismatch between OWA (Outlook Web Access) S/MIME control. An active X component provides the S/MIME support in OWA. So, after you upgrade the exchange 2007 with SP3, the user will be prompted to install the upgraded version of the control into their client computers. The mechanism works in this way, the code checks the ‘Version’ of the client S/MIME control (MIMECTL.DLL) in end user’s computer with the ProductVersion of MSI file (OWASMIME.MSI) on the CAS server. During the SP3 release, the version of the MSI has incremented to 8.3.83.2. However, the DLL in MSI retained to the old one (8.3.83.0). So even though the client has updated the S/MIME version it will still prompt them…
Published in
Solutions
Start-DatabaseAvailabilitygroup is one of the cmdlets used when we do a datacenter switchover of Exchange DAG, especially during a disaster recovery situation. We might end up unsuccessful in executing the Start-DatabaseAvailabilitygroup and will fail with below error. WARNING: Server 'EX2010-DR' failed to be started as a member of databaseavailability group 'DAG-01'. Error: A server-side database availability groupadministrative operation failed. Error: The operation failed. CreateClustererrors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Node ex2010-dr isalready joined to a cluster. [Server: EX2010-02.fabrikam.com]WARNING: The operation wasn't successful because an error was encountered. Youmay find more details in log file"C:\ExchangeSetupLogs\DagTasks\dagtask_2013-11-26_06-39-40.462_start-databaseavailabilitygroup.log".Start-DatabaseAvailabilityGroup failed to start server(s) 'EX2010-DR' in database availability group 'DAG-01'. + CategoryInfo : InvalidArgument: (:) [Start-DatabaseAvailability Group], FailedToStartNodeException + FullyQualifiedErrorId : 8D6C2942,Microsoft.Exchange.Management.SystemCon figurationTasks.StartDatabaseAvailabilityGroup One of the reasons why this error is generated could be because of the previous un-successful execution of the command. During the previous attempt…
Published in
Solutions
As you aware, the receive connectors are created on server identity, and we might end up in creating similar receive connector in multiple servers for redundancy/disaster recovery purposes. You can easily export and import the RemoteIPRages from one connector to other by just following the following simple steps, First of all, create the receive connector on the server where you want to import the RemoteIPRanges (relay IPs). Ensure you do the necessary settings for the receive connector properties, as we only import the remoteIPRanges not all configurations’. new-ReceiveConnector -Name 'connector_name' -Usage 'Custom' -Bindings '0.0.0.0:25' -RemoteIPRanges 'x.x.x.x' -Server 'new_server_name' Now, we have to export the RemoteIPRanges values from the other server that we need to import to this newly created receive connector. Get-ReceiveConnector "EXH2\ connector_name" | fl remote* If the result is truncated as seen in the above figure, you can set the value $FormatEnumerationLimit to display the complete list. The…
Published in
Solutions
Many of us have started upgrading the work station to Windows 8, and the Exchange 2010 Management Tools installation prior to Exchange Server 2010 SP3 cannot be installed on a Windows 8 64 bit machine. Here I have shared the work around for installing the Exchange 2010 SP2 Management tool on a Windows 8 64 bit machine (I used Windows 8 pro). Step1: Ensure that you have installed all the pre-requisites for management tools, Install the .NET Framework 3.5 Windows Feature Install the IIS 6 Management Console Feature Install the IIS Metabase and IIS 6 Configuration Compatibility Feature Install RSAT (Remote Server Administration Tools for Windows 8) Link - http://www.microsoft.com/en-us/download/details.aspx?id=28972 Step 2: Modify the value of registry key CurrentVersion from 6.2 to 6.1. Location of the Key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion Step3: Prepare for the Exchange 2010 Server Management Tool Installation (readiness will show you green signal) Step 4: Click on Installation and…
Published in
Solutions
Recently I was testing the Datacenter failover of Database Availability Group (DR), and observed few things/errors when adding back the DAG members after the successful failover. During the failback, I could add one of the 2 servers in primary datacenter but failed to add another server. The Start-Databaseavailabilitygroup failed to complete with error as pasted below, WARNING: Server 'EX-01' failed to be started as a member of database availability group 'DAG-01'. Error: A server-side database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Node ex2010-01 is already joined to a cluster. [Server: Ex-DR.fabrikam.com] WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2013-07-30_06-10-35.992_start-databaseavailabilitygroup.log". Start-DatabaseAvailabilityGroup failed to start server(s) 'EX-01' in database availability group 'DAG-01'. + CategoryInfo : InvalidArgument: (:) [Start-DatabaseAvailabilityGroup],…
Published in
Solutions
As per the updates from various sources, the iOS 6.1 version creates issues with Exchange Server, as it overloads the Exchange Server 2010. According to the latest updates, apple and Microsoft are currently working towards an update to workaround this issue. This issue looks to have some relation with earlier reported meeting hijacking, as it has turned out to be happening when Apple users process their calendar updates using their iPAD or iPhone. Need to know more, read the following blogs, Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1-based device Apple iOS 6.1 upgrades result in excessive transaction log growth Request the users not to update the new version until Apple and MS are coming up with a fix. Update: (14- Feb-2013) Apple has acknowledge the bug, iOS 6.1: Excess Exchange activity after…
Published in
Solutions
More...
You may have observed an unexpected growth in the database size and transaction log after a cross forest migration. It happened to me when I was doing a cross forest migration project from Exchange 2007 Server to Exchange 2010 server, so I thought of sharing it so that it may help you to plan the migration in a better manner. The database size and transaction logs growth was unacceptably high due to few users’ outlook client. I observed ~30GB logs generated because of 2 users, and the database is also grown about 25 GB in a time span of 8 hours without any reason. Cause: When I identified the users and clients (used Exchange User Monitor), it is observed that all the client versions are outlook 2010 original version (without any service pack), have mentioned it below. Microsoft Outlook 2010 OUTLOOK.exe 14.0.4760.1000; I also observed that most of them were…
Published in
Solutions
We have discussed about a bug in Apple iOS 6 with the Exchange Active Sync(EAS) in one of the previous posts, you may read it here Good news is that, Apple has come up with a software upadate that addresses the issue with EAS along with other few fixes, please find the details about new apple iOS software update below, Fixes a bug that prevents iPhone 5 from installing software updates wirelessly over the air Fixes a bug where horizontal lines may be displayed across the keyboard Fixes an issue that could cause camera flash to not go off Improves reliability of iPhone 5 and iPod touch (5th generation) when connected to encrypted WPA2 Wi-Fi networks Resolves an issue that prevents iPhone from using the cellular network in some instances Consolidated the Use Cellular Data switch for iTunes Match Fixes a Passcode Lock bug which sometimes allowed access to Passbook…
Published in
Solutions
We have been hearing (at least for last couple of weeks) that the Apple IOS 6 which is released along with Apple iPhone 5 is creating some issues with Microsoft Exchange Server when using Active Sync feature. The actual issue is “the meeting request’s owner is changed (or meeting hijacked)", and according to MS almost every call raised on this issue was some or the other way related when the meeting request is acted on IOS 6 devices. MS has already contacted Apple and has officially written on their Exchange Blog. As you know, the IOS 6 is now available to update of other compatible Apple devices, so it is recommended not to update the new version (if you are an Active Sync user) until Apple announces the fix. Few ways to work around (precautions / mitigations) the situation as mentioned in the Exchange Team Blog are, Tell users not…
Published in
Solutions
You may see the databases dismounted after you restarted the member server of a DAG (mostly when you only have 2 copies of databases). And if you try to mount the database, it will through the below error. -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Failed to mount database 'Mailbox Database 0834974974'. Mailbox Database 0834974974 Failed Error: Database 'Mailbox Database 0834974974' can't be mounted on server 'EXH1.exchangedictionary.local' due to a previous error: Failed to determine the mount status of the active database copy. Verify that the underlying cause of the error has been corrected before attempting to mount the database. The error can be ignored and the mount allowed if Mount-Database is reissued with the -Force switch. Resolution: As mentioned in the error, it is better try to fix the underlying cause, before you forcefully mount the database. Ensure that the cluster service is up and running Ensure that the DAG members…
Published in
Solutions
