https://docs.microsoft.com/archive/blogs/karthikm/feed.xml #Microsoft Tue, 08 Nov 2016 14:55:09 GMT en-US hourly 1 https://docs.microsoft.com/archive/blogs/karthikm/mailbox-restore-fails-failurecode-2147024809-operation-idestinationfolder-setrules Tue, 08 Nov 2016 04:02:19 GMT https://blogs.technet.microsoft.com/karthikm/?p=276 https://docs.microsoft.com/archive/blogs/karthikm/exchange-2010-sp3-ru15-fails Tue, 08 Nov 2016 01:52:19 GMT https://blogs.technet.microsoft.com/karthikm/?p=225

Edit the PowerShell activation configuration file located in this path: "<C:\Program Files (x86)\Common Files\NetApp \powershell.exe.activation_config>".

Change the configuration as below ==== <configuration> <startup  useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v2.0.50727"/> <supportedRuntime version="v4.0.30319"/> <supportedRuntime version="v1.1.4322"/> <supportedRuntime version="v1.0.3705"/> </startup> </configuration>

Rerun the setup

]]> https://docs.microsoft.com/archive/blogs/karthikm/replies-to-meeting-request-are-showing-as-tentative-when-they-have-been-address-rewritten Wed, 12 Oct 2016 04:48:36 GMT https://blogs.technet.microsoft.com/karthikm/?p=215 Symptom =========== When sending replies to meeting request these are showing as Tentative when they have been address rewritten. In these instances for example we go from x_y@contoso.com  and get rewritten to x.y@contoso.com  by a third party, when the response is received it’s Tentative, even if it was Accepted   Cause =========== We have seen this issue before in a very small amount of cases, pipeline tracing has shown that this is because Exchange uses a mixture of P1 and P2 headers along with the ICS information in the mail in base64 encoding to match up the recipients, doing address rewrite breaks this. As mentioned the testing and the research has shown that the mismatch of SMTP headers and ICS body is causing this.   Resolution ============ The attendee is showing as Tentative because the P1 and P2 SMTP header information does not match with the contents of the ICS Calendar information in the body of the message, Exchange uses these to correlate recipients and attendees to meetings etc. By performing address rewrite when the message has left Exchange we are breaking this link.   Additional Information ==================  Accepted Meeting Invite shows up as 'Tentative'   Currently you have a domain rewrite to rewrite your domain from internal addresses to an external addresses. However, under certain scenarios when sending Meeting Requests or Accepting Requests the email domain is not rewritten causing incorrect  display of the response. This behavior is by design and it is actually a  limitation of the application rewriting the domain. SMTP MIME messages have 2 sets of properties, commonly refer to P1 and P2. The P1 properties are transport level properties that are passed from the sending server to the receiving sender via the SMTP Protocol. The P2 properties are message level properties which are passed as part of the message. Both of these property sets contain recipient and sender information, including email addresses. In your scenario the rewriting application is able to change these properties correctly to ensure that the internal domain is rewritten to the external domain.   In addition to the P1 and P2, the message may also have different body parts that contain additional information. When sending Meeting Requests, Exchange uses an iCal body part (<https://www.ietf.org/rfc/rfc2445.txt>) to describe the detail of the message and it is included in the message body. This is a widely used method for transmitting Scheduling events. This attachment contains all the information regarding the meeting request. The problem is that the rewrite tool only looks at the P1 and P2 headers and not at the body of the message. The receiving client will then use the iCal body part to gather all the information for Meeting Request, which contains the original internal domain.   During my testing I was able to decode the base64 encoded iCal information and make the domain changes to the iCal properties and the P2 headers. I encoded the iCal to base64 again and put the data back into the message. After doing this in both directions (incoming and outgoing) I did not see any of the issue with Tentative or incorrect addresses. It may or may not be difficult to have your Domain rewrite application do this, but that is where the problem is happening.   Using Rich Text Format for these messages is another workaround for this problem. When Exchange uses Rich Text Format to send a Meeting Request, it encapsulates the message using TNEF. During the encapsulation of a Meeting request, the Organizer and Attendee are actually mapped and stored in the From: and To: field respectively in the P2 header. When the message is sent the Rewrite tool is able to change the P2 header. The receiving server then rebuilds the message back and uses the P2 sender and recipient information to recreate the meeting request in addition to the information in the TNEF message body.   Please note that TNEF will only work between Exchange servers, since it is a proprietary format used by Exchange and other Microsoft Products. Non-Outlook clients will see the TNEF format as a winmail.dat attachment and the may cause other issues.    ]]> https://docs.microsoft.com/archive/blogs/karthikm/emails-with-irm-are-getting-stuck-in-poison-queue-on-hub-server Fri, 30 Sep 2016 21:41:53 GMT https://blogs.technet.microsoft.com/karthikm/?p=185 Transport service crashing on the transport servers causing delayed emails or mails are stuck in queue Emails with IRM are getting stuck in Poison queue on Hub Server  Log Name:      Application Source:        MSExchange Common Date:          9/29/2016 11:54:20 AM Event ID:      4999 Task Category: General Level:         Error Keywords:      Classic User:          N/A Computer:      xyx.contoso.com Description: Watson report about to be sent for process id: 14256, with parameters: E12, c-RTL-AMD64, 14.03.0235.001, edgetransport, M.E.Data.Storage, M.E.D.S.R.RmsoProxyUtil.CheckRedirectUrl, System.ArgumentException, a11a, 14.03.0235.001. ErrorReportingEnabled: False Cause: IRM Protected message enters Poison queue and Crashes Transport Service Resolution:

• Set the Default registry key set it to value not set
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\IRM\CertificationServerRedirection
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\IRM\LicenseServerRedirection

]]> https://docs.microsoft.com/archive/blogs/karthikm/opening-destination-mailbox-failed-to-open-mailbox-with-error-the-operation-failed-error-code-1056749262 Wed, 28 Sep 2016 09:13:28 GMT https://blogs.technet.microsoft.com/karthikm/?p=155

Paste the Mailbox GUID  into Notepad. For example,f911a4c2-42de-42c1-8d97-abef7766063c. Note The GUID contains five sections that are separated by hyphens.

On a blank line in Notepad, type the characters from the first section of the GUID (for example,f911a4c2), in two-character portions separated by backslash character, in reversed order. For example: \c2\a4\11\f9. Note You must include the initial backslash character.

Type the characters from the second section of the GUID (for example, 42de) in two-character portions separated by backslash characters, in reverse order. For example: \de\42.

Type the characters from the third section of the GUID (for example, 42c1) in two-character portions separated by backslash characters, in reverse order. For example: \c1\42.

Type the characters from the fourth section of the GUID (for example, 8d97) in two-character portions separated by backslash characters. For example: \8d\97. Note For this section of the GUID, you do not reverse the order of the two-character sections.

Type the characters from the fifth section of the GUID (for example, abef7766063c) in two-character portions separated by backslash characters. For example: \ab\ef\77\66\06\3c. Note For this section of the GUID, you do not reverse the order of the two-character sections.

Add each of the re-typed GUID sections together to form the msExchMailbox value. For example:

\c2\a4\11\f9\de\42\c1\42\8d\97\ab\ef\77\66\06\3c

On a new line in Notepad, use this new msExchMailbox value to create a msExchMailboxGUID entry similar to the following:

(msExchMailboxGUID=\c2\a4\11\f9\de\42\c1\42\8d\97\ab\ef\77\66\06\3c)

Note Include the parentheses in the preceding command.

]]> https://docs.microsoft.com/archive/blogs/karthikm/unable-to-upgrade-cu-the-installation-source-for-this-product-is-not-available-verify-that-the-source-exists-and-that-you-can-access-it-error-code-is-1612 Wed, 28 Sep 2016 06:00:12 GMT https://blogs.technet.microsoft.com/karthikm/?p=145

checked and find if the Exchange services were disabled

Re Run the setup

Monitor exchange services from services.msc and check when the services get disabled

run Get-Service | where{$_.Name –Like ‘MSExchange*’} | set-Service –StartupType ‘automatic’

]]> https://docs.microsoft.com/archive/blogs/karthikm/the-store-driver-couldnt-deliver-the-public-folder-replication-message-folder-content-backfill-response-pf-1contoso-com-because-the-following-error-occurred-the-message-content-has-become-co Wed, 28 Sep 2016 05:50:18 GMT https://blogs.technet.microsoft.com/karthikm/?p=126 Issue : Issues Replicating Public Folder Data from Exchange 2007 to Exchange 2010   Setup Information: Exchange Environment : Exchange 2007 Exchange Environment: Exchange 2010   Increased the diagnostics logging on Public folder to expert level on below parameters

• Replication Backfill
• Replication Conflicts
• Replication Erros
• Replication General
• Replication Incoming Messages
• Replication NDRS
• Replication Outgoing Messages Messages
• Transport General
• Transport Sending
• Transport Delivering
• Storage Limits Source:        MSExchange Store DriverEvent ID:      1020Level:         ErrorUser:          N/ADescription:Log Name:      ApplicationDate:          6/2/2016 10:12:01 AMTask Category: Replication ErrorsKeywords:      ClassicComputer:      XYZ_2010.contoso.comError -1605 occurred while processing an incoming replication message.Folder: (156-11D20F16EC5) IPM_SUBTREE\PF1\PF2\PF3Recommendation:
• Cause: Due to corrupted message exchange is preventing the replication of the public folder and dropping the message
• Description:
• User:          N/A
• Level:         Warning
• Event ID:      3091
• Source:        MSExchangeIS Public Store
• The store driver couldn't deliver the public folder replication message "Folder Content Backfill Response (PF-1@contoso.com)" because the following error occurred: The message content has become corrupted
• Computer:      xyz.contoso.com
• Keywords:      Classic
• Task Category: MSExchangeStoreDriver
• Date:          6/2/2016 1:22:23 PM
• Log Name:      Application
• Below events were noticed during Public folder replication
• Take public folder database offline Run isinteg to fix the corruption
• Change the replication limit of the public folder to 1KB and that could help us determine the corrupted message from the event and delete the corrupted message.
• Run the report to identify the public replication status and identify the public which hasn’t replicated 100 %. Export the public folder from exchange 2007 and import them on exchange 2010
• Check if the rename of the public folder triggers replication
• Create the copy of all failed public folder to trigger the replication and delete the original public folder after the copy has been replicated successfully.

]]> https://docs.microsoft.com/archive/blogs/karthikm/deploying-cache-mode-pros-and-cons Wed, 28 Sep 2016 05:24:01 GMT https://blogs.technet.microsoft.com/karthikm/?p=115

Microsoft recommends Cached mode for shared mailboxes

 

• It insulates users from network latency and connectivity issues while they are using Outlook. local cached information is always faster and Outlook prefers to get data from the OST whenever possible

 

2. Why do we recommend cached mode

 

• Outlook 2013 changes its cached model to allow users to selectively keep a certain amount of data cached in the local OST while the remainder is held in the online mailbox. The theory here is that as we deal with larger and larger mailboxes, it does not make much sense to keep everything cached because users really only need access to their most recent data.
• Most users find that Cached Exchange Mode performs faster than online mode. However, several factors can influence a user's perception of Cached Exchange Mode performance, like hard disk size and speed, CPU speed, .ost file size, and the expected level of performance.
• By default, when Cached Exchange Mode is enabled in Outlook 2013 and Outlook 2010, shared mail and non-mail folders that users access in other mailboxes, are downloaded and cached in the user's local .ost file. Cached folders enable offline access and can provide a much more reliable experience on slow or unreliable networks. But be aware that cached folders do take a little more time to populate at first

 

3. What are pros and cons

 

• By default, when Cached Exchange Mode is enabled in Outlook 2013 and Outlook 2010, shared mail and non-mail folders that users access in other mailboxes, are downloaded and cached in the user's local .ost file
• For example, if a coworker 1 shares a calendar with coworker 2 and coworker 2 opens it, Outlook 2013 starts caching the folder locally so that coworker 2 has offline access to the folder and is insulated from potential network issues. Similarly, if a manager delegates access to his or her Inbox to a team member, when the team member accesses the folder, Outlook 2013 also starts caching the Inbox folder locally.

 

• Cached folders enable offline access and can provide a much more reliable experience on slow or unreliable networks

 

• Portable computer users who frequently move in and out of connectivity.

 

• Users who frequently work offline or without connectivity.

 

• By default, when you install Outlook 2013 and enable Cached Exchange Mode, a new compressed version of the Outlook data file (.ost) is created. This new compressed version of the .ost is up to 40% smaller than the size of the .ost files that were created in earlier versions of Outlook.
• In addition, be aware that caching for shared folders works differently from other caching for Cached Exchange Mode. For shared folders, replication to the local .ost file starts only when the user chooses the shared folder. After a user starts caching for the folder by choosing (clicking) it, Outlook updates the folder exactly like other Outlook folders that are synchronized in Cached Exchange Mode. However, if the user does not go to the folder at least one time every 45 days (the default value), the locally cached data for the folder is removed from the .ost file and will not be downloaded until the user chooses on the folder again.

 

4. How to prevent the cons

• If you are moving from using Online Mode to Cached Exchange Mode as part of the deployment of Outlook 2013, be aware that users' local .ost files can increase 50 percent to 80 percent over the size of the mailbox that is reported in Exchange Server. The format that Outlook uses to store data locally for Cached Exchange Mode is less space-efficient than the server data file format. This means that more disk space is used when mailboxes are downloaded to provide a local copy for Cached Exchange Mode.

 

• Large mailboxes on computers that don’t have sufficient hard disk space for a local copy of the mailbox.

 

• Large mailboxes (greater than 25 GB). For large mailboxes, performance can become an issue in Cached Exchange Mode. Choose the slider outlook to reduce the size of OST

 

• If you plan to upgrade a large group of users from an Online Mode deployment of Outlook to Outlook 2013 with Cached Exchange Mode enabled, stage the rollout over a period of time. A staged rollout helps your organization's Exchange Server computers manage the requirements of creating or updating users' .ost files. If most user accounts are updated to use Cached Exchange Mode at the same time and then start Outlook at the same time (for example, on a Monday morning after a weekend upgrade), the Exchange Server computers may have significant performance issues—so a staged approach is preferable.

 

• If you have a large .pst or .ost file, you may experience application pauses while you perform typical operations in Outlook. These typical operations include reading email messages, moving email messages, and deleting email messages. Up to 5 GB: This file size should provide a good user experience on most hardware.
• The following list summarizes expected behavior based on the size of your Outlook data file.

Between 5 and 10 GB: This file size is typically hardware dependent. Therefore, if you have a fast hard disk and lots of RAM, your experience will be better. However, slower hard disk drives, such as drives that are typically found on portable computers or early-generation solid-state drives (SSDs), experience some application pauses when the drives respond. More than 10 GB: When the .ost file reaches this size, short pauses begin to occur on most hardware. very large (25 GB or larger): An .ost file of this size increases the frequency of short pauses, especially while you are downloading new email messages. However, you can use Send/Receive groups to manually sync your mail. Choose the  Mails to keep offline slider in outlook to reduce the size of OST and maintain the value that works optimum in the environment]]> https://docs.microsoft.com/archive/blogs/karthikm/change-the-file-share-witness-on-exchange-server Wed, 28 Sep 2016 05:16:25 GMT https://blogs.technet.microsoft.com/karthikm/?p=76

• The witness server can't be a member of the DAG.

 

• The witness server must be in the same Active Directory forest as the DAG.

 

• The witness server must be running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, or Windows Server 2003.

 

• A single server can serve as a witness for multiple DAGs; however, each DAG requires its own witness directory.

   

• We recommend that you use an Exchange 2013 Client Access server in the Active Directory site containing the DAG. This allows the witness server and directory to remain under the control of an Exchange administrator. Regardless of what server is used as the witness server, if the Windows Firewall is enabled on the intended witness server, you must enable the Windows Firewall exception for File and Printer Sharing.

 

• If the witness server you specify isn't an Exchange 2013 server, you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the witness server prior to creating the DAG. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed.

  Command to change FSW   Set-DatabaseAvailabilitygroup -Identity <DAGNAME> -WitnessDirectory <C:\FSW_DIR_DAG1> -WitnessServer <Server FQDN>     You can use the below method to verify the status of File share witness on windows server 2008 R2   Method 1.

• Using Failover Cluster Manager connect to the cluster service.  You can connect to either a node or specify the DAG name as the connection point.
• Click on the cluster name in the upper left hand corner of the utility.
• In the center window information is displayed regarding the cluster configuration.
• One piece of information is the “Quorum Configuration”.  This will list the type of quorum in use and if a file share witness is configured the server and share name utilized as the witness.

    Method 2:  

• open cmd prompt and run cluster dag.contoso.com res

    https://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx  ]]> https://docs.microsoft.com/archive/blogs/karthikm/error-problem-4003-insuff_access_rights Wed, 28 Sep 2016 05:06:03 GMT https://blogs.technet.microsoft.com/karthikm/?p=65

Open Active Directory Users and Computers.

Click View, and then click Advanced Features.

Right-click the OU that contains the user and then click Properties.

In the Security tab, click Advanced.

In the Permissions tab, click Add.

In the Enter object name to select box, type Exchange trusted subsystem, and then click OK.

In the Object tab, select This object and all descendant’s objects in the Apply onto list, locate Modify Permissions in the Permissions list, and then set it to Allow.

Click OK

Make sure above option is checked on all OU’S listed in the object path of the user object

 ]]>