SME 7.1 not working with Exchange 2013 SP1 CU6

Hello, i tried upgrading to SME 7.1 on our Exchange 2013 SP1 CU6, but when trying to configure the Exchange Server in the SME management console using the configuration wizard, it gave an error before the LUN mapping page, saying "Failed to get Exchange information for server" and "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.". I upgraded Snapdrive to 7.1, verfied all credentials according to the manuals, re-installed and rebooted multiple times (registry and filesystem cleaned, even tried to rename the existing SnapInfo directory, ...), stopped all other services on the server but without any change... Every time when trying to run the configuration wizard, the debug log shows no errors, lists all Exchange information and ends with the following lines:[11/18 12:51:58 155] Exit CSmeCDOExm::GetExchangeStructureInternal 0x0
[11/18 12:51:58 155] Exit CNtapSnapMgr::GetExchangeStructure: 0x0
[11/18 12:51:58 233] Enter CSmeServerBase::~CSmeServerBase ...
[11/18 12:51:58 248] m_ptrSnapShot released
[11/18 12:51:58 248] m_pISnapShot4 released
[11/18 12:51:58 248] m_pISnapShot5 released
[11/18 12:51:58 248] m_pISnapShot6 released
[11/18 12:51:58 248] m_pISnapShot7 released
[11/18 12:51:58 248] m_pISnapShot8 released
[11/18 12:51:58 248] m_pISnapShot9 released I ended up uninstalling SME 7.1 and re-installed SME 7.0 which is working. Exchange Server: ESXi 5.5 VM, Windows Server 2012 R2 (with current patches), Exchange 2013 SP1 CU6 - no DAG, single server installation (in co-existence with Exchange 2010), 4 iSCSI LUNs created with Snapdrive (1x Log, 3x Store), System drive and Exchange installation drive on vmdk Disks (via ESXi -> NFS store on the same NetApp)NetApp: FAS 2240-2 with Data ONTAP 8.1.4P1 7-mode (with complete license bundle) Anyone else got this problem or even better - a solution?

We could not reproduce the error with the upgrade workflow.Looking at the error and the relevant function, we could force the problem in following conditions: -SME is configured or ran at the DAG level-one of the following services is stopped or not responding on one nodes of the DAG Snapdrive Service, Snapmanager Service, Snapdrive Storage Management Service,Snapdrive Management Service. Would be good if we could get the output of following powershell cmdlet before and after the upgrade: Get-Service –ComputerName Node1, Node2, Node3 –name Snap*, SDMGMT*, SWSvc Best regards,Dan

Similar Messages

Lync integration not working after Exchange 2013 SP1 is installed...

Hi,
I have two Exchange 2013 servers running and everything is fine, almost.
The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
Have any of you Guys seen or experienced any thing like this?
Thanks in advance.
Regards
Kenneth

Hi,
I recommend that you refer to the following article to troubleshoot the issue:
Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
In addition, here is a similar thread for your reference:
Lync 2013 with Exchange 2013 SP1 OWA integration failed
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Cannot write email body in OWA with Exchange 2013 SP1 CU6

Hi,
I have a problem with Exchange 2013 SP1 with CU6.
All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
Have you an idea ?
Thanks in advance!
Sebastien

Hi,
After contacting Microsoft support, we have found the solution.
The problem appear after we have recently install the patch described in this KB 2997209:
https://support.microsoft.com/kb/2997209?wa=wsignin1.0
But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
No need to reboot, or restart IIS, it's working after that!
@+
Sébastien

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

SCDPM 2012 R2 Backup with Exchange 2013 SP1 CU6 DAG

Hi,
Correct me if I'm wrong.
DAG setup as follow,
1. Server1\MBX01 (Active)
2. Server2\MBX01 (Passive)
DPM
1. Select Full for Active
2. Select Copy for Passive
We always select active copy so that logs can be purge. On the other hand, if we select backup passive copy and purge logs. My guess is logs will be replicated from Active copy.
How about when active copy change passive copy? Do I need to change the backup option?
Please advice. Thanks.
Kelvin Teang

Hi,
It sounds like an exchange problem - this was the application event log entry on the passive node after taking an incremental backup from DPM. After the below event was posted, I checked both active and passive node and the logs were successfully truncated.
It took a few minutes before the logs were deleted.
Log Name:      Application
Source:        MSExchangeRepl
Date:          12/9/2014 3:40:46 PM
Event ID:      2046
Task Category: Exchange VSS Writer
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      MJLC-E14-2.mjacquet.com
Description:
The Microsoft Exchange Replication service VSS Writer instance 5cc17efd-1acc-41c3-b68a-f667027032b6 has successfully completed the backup of database 'N1-MB2'.
Database log truncation has been requested for this database. Log truncation will occur on the active copy after the next log generation is created. Log truncation will occur automatically on the passive copies after that log file is copied.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="16388">2046</EventID>
    <Level>4</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-09T23:40:46.000Z" />
    <EventRecordID>399855</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MJLC-E14-2.mjacquet.com</Computer>
    <Security />
</System>
<EventData>
    <Data>5cc17efd-1acc-41c3-b68a-f667027032b6</Data>
    <Data>N1-MB2</Data>
</EventData>
</Event>
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Crystal report 8.5 export to csv and rtf format not working with office 2013

Hi Experts,
Crystal report version 8.5 hangs and eventually crash when i export my report to csv or rtf format on windows 7 with office 2013 installed, code is written in VB 6 although the same scenario is working with office 2010 installed.
i debugged the code and found the application hangs at function Report.Export(False).
below is the code snippet
       .PDFExportAllPages = True 'ePDFExportAllPages
       .PDFFirstPageNumber = ePDFFirstPageNumber
       .PDFLastPageNumber = ePDFLastPageNumber
       .RTFExportAllPages = True 'eRTFExportAllPages
       .RTFFirstPageNumber = eRTFFirstPageNumber
       .RTFLastPageNumber = eRTFLastPageNumber
       .UseReportDateFormat = eUseReportDateFormat
       .UseReportNumberFormat = eUseReportNumberFormat
       .UseReportNumberFormat = eUseReportNumberFormat
       .XMLAllowMultipleFiles = eXMLAllowMultipleFiles
       .XMLFileName = eXMLFileName
     Report.Export (False) ----Application hangs here and eventually crash
Looking forward for your help, as it is very urgent
Regards
Mohit

Hi Mohit
CR 8.5, being about 15 years old, does not support Windows 7. I am surprised this works for you with MS Office 2010 and to be honest, I'd consider my self lucky there. The fact that is does not work with office 2013... well, like I said, lucky with Office 2010 and your luck ran out with Office 2013.
Your option; rewrite the app in VS 2010 / 2012 / 2013 and use the CR Assemblies for VS .NET from SAP Crystal Reports, Developer Version for Visual Studio .NET. The CR Java SDK would be another option.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2013 SP1 CU6 / WinSer 12R2 - Recreate Daily Performance Logs

Hi there,
I disabled the jobs in Task Sheduler to get rid of the logfiles. Now I wanted to reactivate the jobs but they are missing and I don´t know how to "install" them again.
Some said after rebooting the server, the jobs are automatically recreated, but that´s not the case on my server. Additionally I get Performance Counter errors, don´t know if these have anything to do with that.
It´s a test environment with an Exchange 2007 SP3 and Exchange 2013 SP1 CU6 (+ ActiveSync hotfix).
Has anybody an idea how to get the sheduled tasks available/working again?

Hi,
Do you mean:
Task ConvertLogEntries missing from C:\Windows\System32\Tasks\Microsoft\Windows\PLA\System
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PLA\System\ConvertLogEntries]
"Id"="{76663950-2087-40B2-A63E-9A940F2C5508}"
"Index"=dword:00000000
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Throttling policy not working on Exchange 2013 CU6

Hi,
We have a test throttling policy to restrict a mailbox to send at most 2 messages
per minute in our live Exchange 2013 CU6 enviroment. It was associated to a test mailbox. We have separated installed 2 mailboxe and 2 cas server roles in our enviroment. I have checked latest CU-s (7 & 8) but these are
not fixing any related bugs.
We tried lots of workaround (see below list) and solutions to fix this but it is still not working with outlook MAPI and OWA client.
Throttling policy not working
smtp service restart
RPC Client Acces service restart
The policy details:
Get-ThrottlingPolicy low_rate_limit |fl *limit*
MessageRateLimit : 2
RecipientRateLimit : 1000
Get-mailbox [email protected] | fl ThrottlingPolicy
ThrottlingPolicy : low_rate_limit
Do you have any idea what is the problem?
Thank you in advance.
br,
Zoltan

Hi Zoltan,
Base on my research, you need to configure the MessageRateLimit parameter on receive connector also.
The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute. The default value for a Receive connector configured in the Transport service on a Mailbox server is
unlimited. The default value for a Receive connector configured on an Edge server is 600 messages per minute. The valid input range for this parameter is 1 to 2147483647. To remove the message rate limit on a Receive connector, enter a value of
unlimited.
https://technet.microsoft.com/en-us/library/bb125140(v=exchg.150).aspx
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Microsof VX 3000 or 6000 Webcam does not work with Lync 2013 under Windows 8.1

Hi,
The problem is that i cannot use the Microsoft VX-3000 or VX-6000 with Lync 2013 under Windows 8.1.
If i go in settings under Video i can see the preview from the webcam just fine, so it works there no problem.
Wenn i try to enable my camera in a conference it does not work, i get an error: Your video cannot be started.
Now, there are no Windows 8.1 drivers for the Webcam so i installed the latest Windows 7 drivers. Because of that this webcam does not work with apps, that is fine i understand the driver problem and the way the new apps work.
But this Webcam works with skype under Windows 8.1 and it works with Lync 2010 client.
The same Webcam works just fine with Lync 2013 under Windows 7.
Is there anything i could do so that i get this Webcam to work with Lync 2013 desktop client under Windows 8.1?
Thanks

Hi,
According to your description, it may be caused by driver.
You can try to install the latest version of Display Driver to fix the display issue.
Since there is no driver for Windows 8.1, I suggest you wait for updating.
You can also post a case on Windows 8 forum, thank you for your understanding:
http://social.technet.microsoft.com/Forums/en-US/home?forum=W8ITProPreRel%2Cw81previtpro&filter=alltypes&sort=lastpostdesc
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Acrobat XI combine to PDF feature is not working with Office 2013 is there a compatibility issue?

Tested with Office 2010 and it works fine
Seems to only be the combine to PDF feature that doesn't work, done updates, tried combining a variety of documents still no joy

There isn't any compatibility issue with Office 2013 and Combine should work with office 2013 same as it with 2010.
Can you please tell us some more details so that we can investigate the problem which you are facing:
1) Please update the exact Acrobat version you are using. This you can find out via "Help -> About Adobe Acrobat XI Pro.." Version should be something like 11.0.x. If it is not 11.0.7, then please update it to 11.0.7 and try again.
2) Is this problem you faced recently (after some update - Acrobat or OS update) or it never used to work earlier for you?
3) You mentioned that when combining, it convert first document only. Can you please let us know how many documents you are combining and what are those formats?
4) Also please update about you environment as well. Is you Operating System and MS Office 32bit or 64bit?
Thanks,
Vishal

RBL not working on Exchange 2013 Edge Transport

Single multi-role server with a couple of mailboxes, recently added an Edge Transport server. After configuring the Edge Subscribtion I added sen.spamhaus.org as a RBL Provider:
Add-IPBlockListProvider -Name Spamhaus -LookupDomain zen.spamhaus.org
This is not working. A lot of spam is still entering Exchange and the http://www.crynwr.com/spam/ test failed.
Both servers run Exchange 2013 CU5.
Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

Hi,
Yes, the command is specific for provider SpamHaus.
http://tweaks.com/windows/40003/cut-down-on-spam-with-ip-block-list-providers-rbl/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Have you added the additional parameters in the command and did it work?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

POP3 is not working in Exchange 2013

Hi,
Facing Wiered issue in Exchange 2013, POP3 is not working ... When configuring POP3 in outlook it failed to authenticate.
unknown user name or bad password. [Error=ProxyNotAuthenticated Proxy=ZAJNBEXC03.cws.sasol.com:1995:SSL]"
Amit

Credentials are correct
Here is the output ..... pls. let me know if this is correct
[PS] C:\Windows\system32>Get-PopSettings |fl
RunspaceId                        : ecc593c8-067e-4d9d-aca1-c121295b8499
Name                              : 1
ProtocolName                      : POP3
MaxCommandSize                    : 512
MessageRetrievalSortOrder         : Ascending
UnencryptedOrTLSBindings          : {[::]:110, 0.0.0.0:110}
SSLBindings                       : {[::]:995, 0.0.0.0:995}
InternalConnectionSettings        : {ZAJNBEXC02.cws.sasol.com:995:SSL, ZAJNBEXC02.cws.sasol.com:110:TLS}
ExternalConnectionSettings        : {ZAJNBEXC02.cws.sasol.com:995:SSL}
X509CertificateName               : mail.sasol.com
Banner                            : The Microsoft Exchange POP3 service is ready on ZAJNBEXC02.
LoginType                         : PlainTextLogin
AuthenticatedConnectionTimeout    : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections                    : 2147483647
MaxConnectionFromSingleIP         : 2147483647
MaxConnectionsPerUser             : 16
MessageRetrievalMimeFormat        : BestBodyFormat
ProxyTargetPort                   : 1995
CalendarItemRetrievalOption       : iCalendar
OwaServerUrl                      :
EnableExactRFC822Size             : False
LiveIdBasicAuthReplacement        : False
SuppressReadReceipt               : False
ProtocolLogEnabled                : True
EnforceCertificateErrors          : False
LogFileLocation                   : D:\Program Files\Microsoft\Exchange Server\V15\Logging\Pop3
LogFileRollOverSettings           : Daily
LogPerFileSizeQuota               : 0 B (0 bytes)
ExtendedProtectionPolicy          : None
EnableGSSAPIAndNTLMAuth           : True
Server                            : ZAJNBEXC02
AdminDisplayName                  :
ExchangeVersion                   : 0.10 (14.0.100.0)
DistinguishedName                 : CN=1,CN=POP3,CN=Protocols,CN=ZAJNBEXC02,CN=Servers,CN=Exchange Administrative
                                    Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Sasol,CN=Microsoft
                                    Exchange,CN=Services,CN=Configuration,DC=cws,DC=sasol,DC=com
Identity                          : ZAJNBEXC02\1
Guid                              : 4c5d5409-1b4a-4127-a4cd-11b064156322
ObjectCategory                    : cws.sasol.com/Configuration/Schema/ms-Exch-Protocol-Cfg-POP-Server
ObjectClass                       : {top, protocolCfg, protocolCfgPOP, protocolCfgPOPServer}
WhenChanged                       : 2015-02-24 08:57:41 AM
WhenCreated                       : 2014-12-08 11:25:29 AM
WhenChangedUTC                    : 2015-02-24 06:57:41 AM
WhenCreatedUTC                    : 2014-12-08 09:25:29 AM
OrganizationId                    :
OriginatingServer                 : ZAJNBWCWSFGC001.cws.sasol.com
IsValid                           : True
ObjectState                       : Unchanged
==================================================================
In my case I have 4 DAG and each having 3 server. .. I am POP test and it is failing with below error
RunspaceId                  : 75d8800c-3f32-4750-8fe1-940133eaf6e8
LocalSite                   : AFR-BYN
SecureAccess                : True
VirtualDirectoryName        :
Url                         :
UrlType                     : Unknown
Port                        : 0
ConnectionType              : Plaintext
ClientAccessServerShortName : ZAJNBEXC01
LocalSiteShortName          : AFR-BYN
ClientAccessServer          : ZAJNBEXC01.cws.sasol.com
Scenario                    : Create a MailboxSession object.
ScenarioDescription         : Creating MailboxSession object to access the mailbox [[email protected]].
PerformanceCounterName      :
Result                      : Failure
Error                       : Unable to create MailboxSession object to access the mailbox [[email protected]].
                              Detailed error information:
                              [Microsoft.Exchange.Data.Storage.WrongServerException]: The user and the mailbox are
in different Active Directory sites. Inner error [Microsoft.Mapi.Ma
UserName                    : migrationtest3
StartTime                   : 2015-02-24 10:58:51 AM
Latency                     : -00:00:00.0010000
EventType                   : Error
LatencyInMillisecondsString :
Identity                    :
IsValid                     : True
ObjectState                 : New
Amit

Redirect emails in OWA and Outlook 2010 not working in Exchange 2013

I have an new install of Exchange 2013 with all updates.
When I setup an inbox rule to redirect messages to another contact it is not working.
When I used Outlook 2010 and ran the rule manually I received this error:
"the redirect action is not currently supported with run rules now"
It seems that I didn't setup up something correctly in Exchange 2013 or a feature is not turned on. Please assist.
In the EM console when I setup forwarding that is working. Its the inbox rule redirect not working.

Hi,
From your description, I recommend you use the following cmdlet to ensure that the DeliverToMailboxAndForward parameter is set to $True.
Get-Mailbox <identity> | fl DeliverToMailboxandForward
If this parameter is false, you can use the Set-Mailbox cmdlet to set it and check the result.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

AutoReplyState is Enabled. But still OOF is not working on exchange 2013

Hi All,
We have exchange 2013 installed. How can I make our OOF (Out of Office) reply works?
Thanks in advance.
Jake

Hi Sneff,
Sorry, but I can't find anything on my event viewer that is "MSExchangeMailboxAssistants". Do i need to start the "Microsoft Account Sign-in Assistant" in services?
Checking oof with
https://testconnectivity.microsoft.com/. I got lots of "x". Please give some advice :
Exchange Web Services synchronization, notification, availability, and Automatic Replies.
Not all tests of Exchange Web Services tasks completed.
Additional Details
Elapsed Time: 42852 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for blank.com.ph.
Testing Autodiscover failed.
Additional Details
Elapsed Time: 42852 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 42852 ms.
Test Steps
Attempting to test potential Autodiscover URL https://blank.com.ph:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Test Steps
Attempting to test potential Autodiscover URL https://autodiscover.blank.com.ph:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 21299 ms.
Test Steps
Attempting to resolve the host name autodiscover.blank.com.ph in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host autodiscover.blank.com.ph to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_ctl01_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Test Steps
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Test Steps
Checking if there is an autodiscover CNAME record in DNS for your domain 'blank.com.ph' for Office 365.
Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl04_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
There is no Autodiscover CNAME record for your domain 'blank.com.ph'.
Elapsed Time: 24 ms.
Thanks
Jake

SME 7.1 not working with Exchange 2013 SP1 CU6

Similar Messages

Maybe you are looking for