Get-queue command in exchange 2013

I want to know what is the new velocity option means when we type get-queue command in exchange 2013.
1dentity
DeliveryType Status MessageCount Velocity RiskLevel OutboundIPPool
XMAIL02\74177
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75312
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75378
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75404
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75429
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75443
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75446
SmtpDeliv... Ready 5            0        Normal    0
XMAIL02\75473
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75486
SmartHost... Ready 0            0        Normal    0
XMAIL02\75494
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75495
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75496
SmtpDeliv... Ready 0            0        Normal    0
XMAIL02\75524
SmartHost... Ready 0            0        Normal    0
XMAIL02\75810
SmtpDeliv... Ready 0            0        Normal    0

Hello,
Please see below:
http://technet.microsoft.com/en-us/library/bb125022(v=exchg.150).aspx#RatesAndVelocity
Exchange 2013 measures the rate of messages entering and leaving a queue and stores these values in queue properties. You can use these rates as an indicator of queue and transport server health. The properties are:
IncomingRate   This property is the rate that messages are entering the queue.
This value is calculated from the number of messages entering the queue every 5 seconds averaged over the last 60 seconds. The formula can be expressed as (i1+i2+i3+i4+i5+i6)/6,
where in = the number of incoming messages in 5 seconds.
OutgoingRate   This property is the rate that messages are leaving the queue.
This value is calculated from the number of messages leaving the queue every 5 seconds averaged over the last 60 seconds. The formula can be expressed as (o1+o2+o3+o4+o5+o6)/6,
where on = the number of outgoing messages in 5 seconds.
Velocity   This property is the drain rate of the queue, and is calculated by subtracting the value of IncomingRate from the value
ofOutgoingRate.
If the value of Velocity is greater than 0, messages are leaving the queue faster than they are entering the queue.
If the value of Velocity is equals 0, messages are leaving the queue as fast as they are entering the queue. This is also the value you'll see when the queue is inactive.
If the value of Velocity is less than 0, messages are entering the queue faster than they are leaving the queue.
At a basic level, a positive value of Velocity indicates a healthy queue that's efficiently draining, and a negative value of Velocity indicates a queue that isn't efficiently draining. However, you also
need to consider the values of the IncomingRate, OutgoingRate, and MessageCount properties, as well as the magnitude of the Velocity value for the queue. For
example, a queue that has a large negative value of Velocity, a largeMessageCount value, a small OutgoingRate value, and a large IncominRate value are accurate
indicators that the queue isn't draining properly. However, a queue with a negative Velocity value that's very close to zero that also has very small values for IncomingRate, OutgoingRate,
andMessageCount doesn't indicate a problem with the queue.

Similar Messages

Getting Error while installing Exchange 2013 on server 2012

Error During Exchange 2013 Mailbox Transport
Role Install On Server 2012
Exchange
Server forums
>
Exchange
Server 2013 - Setup, Deployment, Updates, and Migration
Question
1
Sign
in to vote
I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past
the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this:
Step 8 of 15: Mailbox role: Transport service
Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;
          while($currTime -le $timeout)
            $setSharedCDCErrors = @();
            try
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
              if($successfullySetConfigDC)
                break;
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            catch
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          if( -not $successfullySetConfigDC)
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "Unable to set shared config DC.".

Hi Deepak,
From the error description, I would like to clarify the following things:
1. Please ensure that IPv6 on the network adaptor is turned on.
2. Please check if the account that you used to install Exchange has necessary permissions to perform the installation.
3. Make sure that DNS is configured correctly.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Outlook 2011 for Mac users must click send/receive to get new mail from exchange 2013 server

I recently switched our primary CAS servers over from a single exchange 2010 cas/mailbox/hub server to a couple new exchange 2013 CAS/Mailbox servers. Exchange 2013 has cu3, and is hosted on windows server 2012. Anyone who has their mailbox hosted
on one of these exchange 2013 servers has an issue where they must click the send/receive button to get new messages downloaded to their client. This is only the case for outlook 2011 for mac client. Activesync clients, mac mail, OWA, and Outlook 2010/13
all behave normally.
Where can I look or what can I check to troubleshoot this issue?

Hi,
Any good news from the Mac Forum?
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

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

Exchange 2013 - The connection to Microsoft Exchange is unavailable

Hi there,
i have some problems on my new Exchange 2013 Server: Here is the topology:
1 serveur 2012 in workgroup with the Hyper-V role
2 VM: DC2012 is the DC of the domain: intra.mydomain.com, Windows 2012
The other VM is member of the domaine, Windows 2012, Exchange 2013 SP 1 installed.
So, i have dc2012.intra.mydomain.com and mail1.intra.mydomain.com (another DC: DC2008, name: dc2008.intra.mydomain.com)
I have some troubles with the SSL and the connexion of Outlook outside the LAN.
In the LAN on a client, i launch Outlook 2010 and the autodiscver make the rest. The connexion is ok.
But i have a client not in the LAN, so i configured a SSL. I made a request. First Question:
In the ECP, Server, Certificate, i have 3 times "Microsoft Exchange Server Auth Certificate" and 3 times "Microsoft Exchange" with differents dates. Why?
I installed my PKI on the DC2012, and paste the request and download the certificate. I retuned on the exchange server in ECP, Server, Certificate and treat the pending request. In Services i checked IMAP, POP, IIS, SMTP.
Then, in Server, Server, Mail1, OutlookAnywhere, in url extternal: mail.mydomain.com and Authentification: NTLM.
In ECP, Servers, Virtual Directories i wrote the same url external and internal: mail.mydomain.com for ECP, OWA, ActiveSync, OAB.
In my DNS on the DC, i created a CNAME record for mydomain.com et i created a A record for mail. on a client if i make nslookup then mail.mydomain.com the IP is the LAN IP of my exchange server.
I modified the MX record of my public domain: mail.mydomain.com to point on my Public IP. That works.
On the client outside of the LAN, i installed the root certificate and the exchange certificate.
second question:
Why my client outside of the LAN can't connext with outlook.
Thanks a lot for your answers and sorry for the long post.
Alex

I resolved my problem!
here is the solution that solved it:
actually, i tried to connect Outlook 2010 ti Exchange 2013. I knew that Exchange now connect Outllok via rpc over http(s), BUT, the Autodiscover (in LAN) transform the field server to something like that:
[email protected] , the xxx correspond to the GUID of the mailbox. So, for my remote user, i launch this command on Exchange 2013:
Get-Mailbox test | fl name, exchangeguid , it give to me the GUID, then in te field "Server" i fill ([email protected]): [email protected]
And in advanced parameters, same things i mentioned in previous post. And it works!!!!!
Thanks to me.

Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

In the midst of Exchange 2013/2007 coexistence configuration.
Currently:
Exchange 2007:
2 CAS\HUB
1 Mailbox server
Exchange 2013 (2 sites):
LA:
1 CAS
2 MBX servers
MKE:
1 CAS
2 MBX servers.
We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com".
Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
"The name of the security certificate is invalid or does not match the name of the site" for
"LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

Hi,
Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
Get-ExchangeCertificate | FL
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 installation Problem on Hyper-V

Hello,
I have a very interesting problem Exchange 2013 installation step on Hyper-V.
I have 2 server. I installed on server Server 2012 R2 Standart. And then installed hyper-v role for both server.
I created virtual machine for first server and this virtual machine domain controller.
And then I created virtual machine for second server and this virtual machine Exchange 2013.
I installed all prequisites and exchange 2013 finished successfuly. When I opened https://server/ecp it give me http 500 internal error. I checked almost all forums but any recommendation didn't solve my problem.
And then I removed hyper-v role and installed vmware v11. and installed same applications like above.
Very interesting finished installation and opened ecp console. eveythink seen to good.!
Actualy I find problem.
There is exchange feature installation command on microsoft exchange prequisite. When ruunning this command installing two program on program and feature name is "c++ redistrubutable x64 and x32"
I must uninstall this programs before install unified communication api 4.0.
I cannot see on hyper-v when running this feature.
But I can see on vmware this features on programs and feature.
This is very absurt.
Anybody have an idea for this
Thank you for your clarify.

Hi,
Thanks for your reply.
I run this command before Exchange 2013 installation:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering,
RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell,
Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth,
Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging,
Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,
Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
later run this code on vmware platform , installing 2 program in programs and feature. name is Visual
C++ Redistributable package x64 and x86. I know Unified Communications Managed API 4.0
install same program too. But I must unintall Visual C++ Redistributable package before
install Unified Communications Managed API 4.0. But My problem I cannot see this two program
in programs and feature on hyper-v platform.
I tried it many times.

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013 Reports

Hello All,
I recently installed SCOM 2012 R2 and have installed the Exchange 2013 management packs however there does not seem to be any good reports that are included with this management pack. I was wondering if anybody has an tutorials on creating a exchange
specific report. The basic criteria would be cpu usage, memory usage, hard drive space, up time, and any relevant exchange metrics.

Hi,
There are no performance counters collected by this Management Pack: the monitoring does cover any performance issue that might arise, leveraging Exchange Managed Availability.
However, all Exchange PerfMon counters are still available. It should be simple to create your own performance collection rules, if you do require them.
There are no reports in this Management Pack: you can still use some of the built-in Operations Manager reports (such as the Health and Availability reports) to track organization availability, or define SLAs against the Organization.
In addition, I would like to suggest you go through the link below to get more details about Exchange 2013 MP, we should be able to see CPU and Memory performance from the MP:
SCOM Management Pack for Exchange 2013 – Top 6 Things I Like
http://ok-sandbox.com/2014/11/scom-management-pack-for-exchange-2013-top-6-things-i-like/
Regards,
Yan Li
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]

Exchange 2013 Site Resilience - Basic questions for setup in two seperate AD Sites, same domain

I am just getting ramped up with Exchange 2013 and have a friend that I am assisting with planning an exchange 2013 deployment for. I am not asking for step by step directions for setup, just asking for a basic overview so I can dig in to this and
assist.
Goal is to have an exchange server, one in NC and one in Switzerland in an active/passive mode for site resilience. Both servers will be multi role servers.
This is a small organization, less than 50 users and on a budget for equipment. HQ is in NC and the server will have all roles installed on a single server. Switzerland will have only one Exchange server for fail over. There is only
one domain total with two AD Sites.
My questions for clarity -
1. Can I create a Site resilient deployment with two Exchange Multi Role servers in these locations?
2. Currently, the organization does not have a Load Balancer. Will this be required?
3. They do not have a third location for a Witness Server, what issues could potentially happen if the witness sits in one of the two sites?
4. Any other basics for this design are much appreciated. I am reading a lot, however a little confused as I read through the requirements.
Thanks for your input and direction!
Wall

Hi
Please find below answers to your questions.
1. Can I create a Site resilient deployment with two Exchange Multi Role servers in these locations?
Yes
2. Currently, the organization does not have a Load Balancer. Will this be required?
No you don't need to have a load balancer. As you are setting up the infrastructure in Active / Passive mode you don't need a dedicated LB for this.
3. They do not have a third location for a Witness Server, what issues could potentially happen if the witness sits in one of the two sites?
The issue with the witness server in primary or DR site is if your witness server is not responding your DAG won't work properly (failover). If you don't have a 3rd site then you can setup a witness server in your primary site and Alternate witness server
to your DR site.
4. Any other basics for this design are much appreciated. I am reading a lot, however a little confused as I read through the requirements.
I would recommend to use Exchange sizing calculator and technet is the best resource for you :)
Kindly mark this as answer if it fulfill your requirements. :)
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Outlook 2013 connection status 'Exchange Directory' disconnected randomly for random users (Exchange 2013)

We have been encountering an issue where upon random Outlook 2013 users are unable to open the address book, or add a room to a meeting (using 'Add Rooms...' button), and an error message is displayed that the server is unavailable. Mail flow and
everything else functions normally.
If I look at the Outlook connection status of an affected user, I will see that all connections are established except for the 'Exchange Directory' connections which show disconnected. If I click the 'Reconnect' button the Exchange Directory connections
are re-established, and the user can now access the address book/meeting rooms as normal.
Are there any ideas what I would check, logs I could look at, events or anything I can check on the server side that might lead me to an answer what could cause this?

Outlook 2013 gets that data from Exchange 2013 by connecting to Exchange Web Services. That's where you should look.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Revocation checked failed status in Certificate on Exchange 2013

Hi,
Got error in certificate that we have get from Godaddy for exchange 2013 which was earlier working fine, but now getting error on status that Revocation checked failed and because of that in outlook user getting certificate error.
please suggest to fix this issue.

We've had this error before, and it was solved by configuring the proxy settings.
> via netsh winhttp set proxy
> set-exchangeserver InternetWebProxy setting (don't know if still
applicable in Exchange2013)
> iexplorer proxy settings
ps : You can also
check the crl location, when you take a look into the properties of the certificate. (crl distribution points)

Should we migrate to Exchange 2013?

Exchange 2010 SP3, two hubs, two mbs
i'm trying to decide if we should migrate to 2013 Exchange. so far, what I see are mostly cosmetics gains like in OWA, EAC, but it does talk about "site mailboxes". will "site mailboxes" benefit us if we're not using sharepoint?

I wouldn't compare the end-user cosmetic changes but rather focus on service availability that end users are getting... Exchange 2013 has changed drastically with New
managed store process means entirely rewritten information store process in C# with
granular management of resource consumptions, Managed Availability that helps to do internal monitoring to prevent failure and self-healing with various service restoration, Automatic reseed
helps to quickly restore the DB redundancy after disk failure and counting...
Check details here :
What's New in Exchange 2013
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1
site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)
Problem
EMS on CU5 return very slow result.
EMS on SP1 still ok.
Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
reply from Social.technet

Hi,
Have you used the above cmdlets to check your Exchange server health?
"all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

Hi Everybody,
For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
So i did the traditional cmdlet
Get-SendConnector
Set-SendConnector -Indentity "connector name" -Port 551
Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
When i type Get-ExCommand
Any reference to SendConnector and ReceiveConnector are not on the list.
Am I missing somethings? This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials. However, i very much doubt the on-premise installation add-on to SBS would cause any issues
to missing cmdlets.
I searched all over the internet and found nothing.
Now my biggest fear is to re-install Exchange and import the mailboxes manually.
Any help is greatly appreciated.
MattLok

Hello
check role asigment for your user:
Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
sorry my english

Get-queue command in exchange 2013

Similar Messages

Maybe you are looking for