Hi, 

Don't know if this is the right place to ask, but i have setup Exchange Server 2013 and bought an SSL Wildcard Certificate from Comodo.. Problem is when i try to add the Imap it says; 

warning 

This certificate with thumbprint 0B60BE0164E8DB7B7A9D190DF98F56ABFE60F4BC and subject '*.domain.org' cannot used for IMAP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-IMAPSettings to set X509CertificateName to the FQDN of the service. 

I have done "Set-ImapSettings -X509CertificateName mail.domain.org" and the same for PopSettings, still no luck.. Any idea as to what can 'cause this problem? Shouldn't Exchange support wildcard SSL?

Thanks in advance.

i have given the service desk "recipient management" rbac permissions. however when they add mailbox permissions, they are adding ti the GUI way, and are leaving Automapp on. Which we do not want. I want them to use the script i have created that they can run from any powershell, or they can us the EMS (exchange management shell) , and run the ps command.

anyways, is there a way of blocking access to the EMC, and just giving them access to the EMS??

cheers y'all

Hi All,

When I try to add an app ( like linkedin ) in the ecp "Exchange admin Center" I got the below errors. The thing is that I want to roll out apps for my users in a central way. 

I hope someone can help me with this one.

XML CODE :

Log Name:      Application

Source:        MSExchangeApplicationLogic

Date:          24-10-2013 10:29:21

Event ID:      3054

Task Category: Extension

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      NLVRY5803AP8905.domain.local

Description:

Scenario: ProcessOrgExtensions. The organization mailbox for cpmail.nl could not be retrieved.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchangeApplicationLogic" />

    <EventID Qualifiers="49156">3054</EventID>

    <Level>2</Level>

    <Task>3</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-10-24T08:29:21.000000000Z" />

    <EventRecordID>40096</EventRecordID>

    <Channel>Application</Channel>

    <Computer>NLVRY5803AP8905.domain.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>ProcessOrgExtensions</Data>

    <Data>cpmail.nl</Data>

  </EventData>

</Event>

Hello.

I wonder what should happen with database after migration user to cloud. If user account is about 10gb should database be smaller after migrating this user?

I got hybrid configuration with exch2013. I moved  couple of user but database on premise is still the same size.

Good Morning,

Thank you for your time and any feedback you can provide.

--Scott

Hi,

 I have been asked to add a new Exchange server to a Domain, uninstall old Exchange servers (two) and stop using DAG.

 This is te status now:

 I have 3 Exchange servers in a DAG running fine, the servers have all the roles except edge.

 I am wondering what is the best way to do this. Will I get a problem if I uninstall the old Exchange server i.e. regarding Active directory? UM is also configured an used, is there something there I should be aware of?

My Next plan is to remove the old servers from HW LB an make database active on the new Exchange server, then all users should connect to the new server. Remove the old server from the DAG and delete the DB copy. Delete DAG.

Is this a correct and safe way to do this?

It is not my decision to not to use DAG, but I do what I am told :)

thanks.

Erró

We have Exchange 2010 SP3 on premises. We want to deploy online archiving. Actually we have EOP but we add users to it manually.

I Known we need a Hybrid Deployment. Also, I found this on TechNet "Active Directory synchronization between the on-premises and the Office 365 organizations is a requirement for configuring a hybrid deployment"....

Then...is it necessary deploy a Synchronization server for Exchange Online Archiving ??

hello,

i have enabled mailbox auditing for one user, how can i disable the audit for that user.

Regards,

Good Evening,

I have a couple of users who are saying that they are missing Tasks and Older non-recurring appointments in Outlook.

We are in the process of migrating our storage from NetApp to Hitachi.  In doing this, we built two new exchange servers and created database copies on them.  Last night we activated one of the replicas to be the primary database.  This morning we started getting calls the users with mailboxes on these database had missing items.  It could just be coincidence.  One lady reported that older items from Jan and Feb that are not recurring meetings were gone (although I think we have a policy in place to remove older Calendar items).  Another gentleman called to say that he was missing his Tasks, he had 61 in his folder, but said that was only a portion of them. We do not have retention policy set on the Task folder.

Has anyone seen or heard of this??? I am trying to avoid having people blame this on the fact that a database copy was activated.  I believe retention is set per mailbox, not database or server.

OS: Windows 2012R2
Exchange 2013 CU6

10 Mailbox server (5 active/5 passive)

Each server has 6 databases on them (3 Primary/ 3 Archive)

Any feedback would be appreciated and if did not accurately explain the problem, I can try and elaborate further if need be.

Thanks

Brian Dougherty

Hi.

Although ive found many answers on here, ive never asked or contributed to the forum, so thank you for asking and answering everything i have already had to find! :)

This time however, i cant find any answers... I am running a new-mailboxexportrequest on a series of mailboxes in an exchange 2013 dag environment and they are failing, each at a different point in 'size' and there is no correlation to when, or why the mailboxexportrequests fail. However, if i move individual mailboxes to a different mailstore on the same server, i can instantly export the items within the criteria i need to. I have repaired both the mailbox and the database before i have resorted to moving and both repair jobs finish successfully.

Any ideas welcome, i have tried everything i can find on the internet already, but the exportrequests will not move past a certain point in time before i move the mailbox to another store first

Cheers all! :)

we have two exchange 2013 servers setup in DAG group with witness server.

just today I noticed that in the queue viewer I was seeing a nexthopdomain that is my secondary exchange server, type shadow redundancy.  never seen that before that I can recall, and now it has 10-20 message count.

open up the queue and the from address is healthmailboxdd something something at my domain.com

I have seen couple of messages in event log stating the periodic heartbeat between the two exchange servers failed, and "the ehlo properties for client proxy target (second exchange server) did not match while setting up proxy for user healthmailbox@mydomain. The mismatched settings might cause some messages to get rejected. Continue with proxying even though there is a mismatch. The critical non-matching options were maxSize. The non-criticalnon-matching options were"

ran constant ping between the two servers for over two hours.  no drops, min=0ms, maximum = 2ms, average =oms.

I mean, there does not APPPEAR to be a network issue between the two systesms, they are on the same subnet, heck maybe 1 switch apart.

mailbox database copy status is healthy all around.

what would cause these errors?

People,

I wonder what could be the caveats or things to consider before migrating my on-premiseExchange Server 2010 SP3 mailboxes into Office 365 at the end of this year the total Exchange Mailbox count is 2890 and total Mailbox database size is 8.5 TB.

My clients are using Outlook 2010 & 2013 (multiple Active Sync devices) spread across multiple geographical region site offices (Europe and Asia Pacific).

Note:

         I also have emails older than 1 year archived by Symantec Enterprise Vault 10 with approximate size is 7 TB
         Single AD domain forest.


My goal after migrating to Office 365 is to achieve the following:

1. No need to worry about Microsoft Exchange Updates, Hotfixes, updates and bugs with Active Sync devices (Delegate calendar nightmare).
2. Release the disk space used by the email infrastructure back to the existing Storage Array for another VM to use.
3. No need to worry about any outage or reliability issue at all.

Any thoughts and comments would be greatly appreciated.

Thanks in advance.

/* Server Support Specialist */

Hi, hoping I get a bit of help on this one.. 

We are running exchange 2013 sp1 in a two node DAG.  I was applying CU8 onto the second node of the DAG last night and got a warning: 'setup can't detect a send connector with an address space of '*'.  Mail flow to the internet may not work properly' Running get-sendconnetor returns:

Internet                                {SMTP:*;1}                              True

Delivery is by MX using the DNS settings on transport server and both nodes are listed in the connector scoping as source servers.

With the databases all located on the second node I stopped the transport service on the first node and mail was stuck in the outbox until this service was restarted again then mail was delivered as normal.  On checking the header of a mail sent with telnet from the second node it shows the mail being sent from node 2 onto 1 to be delivered.  I need to take down node 1 to apply the CU but this will mean downtime.  How can I stop the mail being sent via node 1?

does exchange 2013 have the pre-canned scripts (ps1).

I have a client site running Exchange 2013 on Server 2012 with most PCs using Office 2010 with a few using Office 2013.

One customer last week said he was getting a popup in Outlook at least once a day stating "The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook." No one has been making changes to Exchange so there must be some glitch in the system that is now causing the popup to appear.

His only recourse then was to follow the message and restart Outlook. He said he was the only one in the office (about 12) who was getting it.

I checked out Exchange and I found that it was at CU3 level. I installed CU9 and now he said that he only gets the popup when he opens Outlook but he can click through it and doesn't have to restart it. He also said that now some others are saying they are getting that popup when opening Outlook also.

I was certain this was an Exchange issue at first and I'm still certain of that. However I can't find any concise help. I've found several suggestion as to what to do and I don't want to chasing around after suggestions hoping one of them will work. Does anyone have any clear idea of what would cause this and how to fix it?

Jonathan

Hi there,

Is the following possible?

We have a distribution list (say call DL1) containing all users in our organisation (about 1000 mailboxes)

And we have a distribution list (say call DL2) containing all users in one particular office (about 400)

I've sent an email to DL2 already.

Now I want to send an email to DL1, but excluding the people in DL2 as they already have the email and I don't want to confuse them.

These are Exchange lists, not Outlook ones.

Thanks

Hi,

Can one delete the built-in default cert of servername from an Exchange 2013 CAS frontend server?  I have 2 front-end CAS servers and 2 backend mailbox servers.

Thank you,

Kurt

Hi Everyone

Yesterday evenything was working fine, and then this morning, I`m unable to establish a connection with the Exchange shell. I receive the following errors. Any help is appreciated.

         Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Tip of the day #55:

Want to view the mounted status of all mailbox databases? Type:

 Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted

VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
VERBOSE: Connecting to .
New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value
"http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer="
to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
At line:1 char:30
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+                              ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-PSSession], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand

[PS] C:\Windows\system32>

Ernie Prescott

Updated information.

I can succussfully connect to the exchange powershell from a remote computer, using this method.

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://<FQDN of Exchange 2013 Client Access server>/PowerShell/ -Authentication Kerberos

Import-PSSession $Session

So the problem is localised on the server.

Regards