Exchange 2013 Static Ports

I've seen many articles about setting static ports in Exchange 2010, but nothing about 2013. Can it still be done the same way in 2013? My concern isn't blocking ports/firewalls/etc, but between our sites we have WAN accelerators which have limits
by connection. The connection count by the device seems a bit "sticky" where an Outlook client at one site accessing a shared mailbox on the other site can end up counting as almost 100 connections because of the dynamic RPC ports used for
different connections. Thus setting static ports would greatly reduce the connection count on the device. Is that still possible?

Hello,
Here you can find port references for all Exchange server versions (except 2013):
http://blogs.technet.com/b/exchange/archive/2013/02/18/exchange-firewalls-and-support-oh-my.aspx - the Exchange Network Port References section.
The list for Exchange 2010 and 2013 is similar but 2013 version uses Outlook Anywhere (port 443) instead of RPC for client connections. So you do not need to configure static RPC
ports for Exchange 2013.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Similar Messages

Exchange 2013 - OutlookAnywhere port usage

Exchange 2013 Enterprise
- two CAS
- six MB
HLB
Outlook 2010 / 2013
- Outlook Anywhere
I am seeing that my Outlook clients are maintaining persistent connections to my HLB device at between 2 - 6 connections per client. I have not opened up my full migration from Exch 2007 to Exch 2013 yet, and I am already seeing in excess of 4,000 conntecions
to my HLB.
Is there a way to minimize the connections used by Outlook?
Tom

Hi,
Agree with the above suggestions, every Outlook client may have more than one connection and we can confirm it by the tool “connection status”. And it’s not necessary to minimize the connections.
However, I’d like to confirm whether you come across some issues like slow connections, not responding and so on.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Error 550 5.7.1 unable to relay with SMTP PORT 25 Exchange 2013

Hi All,
I know this issue has been posted for a while, but still can't resolved issue. We've new Exchange 2013 SP1 (CU4) installation, everything is working properly, the OWA, Exchange Client Connection, SMTP/POP with SSL, except with SMTP Using Port 25 Non-Encrypted
Connection.
If I'm using the SMTP Port 25 without TICK "My Outgoing Server (SMTP) Requires authentication", I've got the error: "550 5.7.1 Unable to relay", but if I TICK the option above, my message will be deliver without any error, how do i get
rid this problem, I need to UN-TICK the option above for the time being, since we've hundreds email account, I want to avoid to educate and tell the user and even remote their PC, just to configure this issue, it will drive me crazy, we're going to use the
Exchange Client Connection in the future, If everything is smooth and ok.
I research this problem on the Internet and of course with TECHNET, but still can't, anyone can help me on this?
fyi, I tried so many things, delete the default the Default Front End Transport for Port 25, it also not fix my issue.
Thx
Irwan

Hi
You can paste the output of below result
Get-receiveconnector | fl name,bindings,PermissionGroups
I think your default receive connector should be missing out some permissions.
Also try to see if you get any message on protocol logs and paste them too
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2013 Frontend Receive Connector - cannot telnet port 25

Hello There,
I’m going to proceed with migration form exchange 2007 to 2013 but just encounter problem.
I can telnet port 25 form new Exchange 2013 server but cannot telnet it form any other computer within LAN.
We have notice it when I was changing SMTP banner to match RevDNS. If I change Receive Connector to role Hub Transport it is responding on telnet 25 from other servers.
But correct is to set it up as Frontend Transport.
There is no AV and Friewall is disable. I can telnet prots form hubtransport role receive connectors.
Fresh installation and server is fully updated. Please help.
Maciej

multi-role CAS + MBX
on ESXi 5.1
I found some topics that this could be related to problem with Network card E1000E and Exchange 2013
I did experience vmware host crash during EX2013 installation. But after restart Installation took off when its left and as far as i could tell everything else is working fine.
I also used wiershark to check negotiation and it looks like 25 is listening and even establishing conneciton but no baner and disconneciting couple of secconds after it is established.
It is 4AM so I hope Im writing it clear :)
Thanks

Staging the NLB cluster Static port change of Exchange 2010 CAS or do it all in one day ?

Folks,
Here is the server deployment in my AD domain:
Email flow and Outlook client connection go through the NLB cluster VIP email.domain.com.au which is served by the following server:
PRODHT-CAS01 (HT-CAS Server Windows NLB node 1)
PRODHT-CAS02 (HT-CAS Server Windows NLB node 2)
Public Folder access through Outlook client goes through the following servers:
PRODMBX01 (Stand-alone Mailbox Server 1) no DAG
PRODMBX02 (Stand-alone Mailbox Server 2) no DAG
Can I make the changes first on the first stack of Exchange Server set as below first:
PRODHT-CAS01 (HT-CAS Server NLB node 1)
PRODMBX01 (Stand-alone Mailbox Server 1) no DAG
in order to test the Outlook email & Public Folder connectivity in the first week and then followed by the rest of the server set:
PRODHT-CAS02 (HT-CAS Server NLB node 2)
PRODMBX02 (Stand-alone Mailbox Server 2) no DAG
would that cause the NLB or user email access problem?
Do I have to make the changes all in one day for those four servers followed by the reboot?
Reason of changing: The hardware load balancer (Riverbed) requires to have static RPC port to work properly.
This is the article to change the Static port in my NLB cluster Exchange HT-CAS server role on Exchange Server 2010 SP2: http://social.technet.microsoft.com/wiki/contents/articles/864.configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx
Thanks in advance.
/* Server Support Specialist */

All the servers behind the load balancer must be the same.
You can change the stand alone MBX server's RCA port as that traffic is not load balanced.
Changing Exchange is straight forward, just be careful to enter the registry keys correctly and then check AB and RCA is listening on the new static ports after you restart the services.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Rhoderick,
Many thanks for the suggestion. My goal here is to minimize any impact / email service downtime to the user while configuring the static ports.
1. Do I have to dissolve the Windows NLB cluster after the static port configuration on both HT-CAS servers or can I still keep the NLB cluster?
2. "All the servers behind the load balancer must be the same." Do you mean do I have to do the static RPC port the same day for all server set ?
/* Server Support Specialist */

Exchange 2013 CAS servers cannot accept connections on Exchange ports

Exchange 2013 Enterprise SP1 / Windows Server 2008 R2 SP1
I have configured site resilience setup with the following at two sites:
- two CAS servers
- six MB servers
Traffic to the CAS servers pass through HLB.
I just discovered that the "01" CAS server at each site is not accepting Exchange traffic.
If I telnet to one of the Exchange ports, it looks like there is a connection, however the moment any character is entered, the connection dies.
For example
- telnet Site01CAS01 25
- ( screen goes blank and DOES NOT display the expected "220 servername Microsoft ESMTP ...." message )
- when I attempt to enter "ehlo" the moment I enter "e" the session is disconnected.
I can successfully perform a telnet connection to the CAS02 server and run through the complete send a test message through telnet process. The session disconnect occurs on the CAS01 server at each site for ANY port controlled by Exchange: 25, 143, 587,
717, 993
I can successfully telnet to ports NOT controlled by Exchange: 80, 81, 8080, 443
There appears to be nothing essentially wrong with IIS
The firewall is DISABLED.
I discovered this issue yesterday.
I upgraded to Excahgne 2013 SP1 10 days ago.
I cannot say for sure if this condition existed before the SP! upgrade. I upgraded from CU1 to SP1
Any thoughts?
Thanks! Tom

Well, port 25 doesnt have anything to do with IIS regardless.
Since this is the CAS, port 25 is handled by the Microsoft Exchange Frontend Transport service .
A couple of things I would check.
Check the server component state. Get-ServerComponentState -Identity <server> to ensure everything is "active".
I assume all the services are running and you have rebooted the server to ensure things start up clean.
Also ensure the NIC on this server is set to register itself in DNS.
Finally, If you have disabled the firewall service on the server, its not supported. You should enable the firewall service and then disable it logically netsh advfirewall set Allprofiles state off
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

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

Exchange 2013 port reference

I don't see any port reference in TechNet for Exchange 2013. I am having exchange servers in two sites (production and DR)looking for the list of ports required for site to site link.

Starting with Exchange Server 2007 and current as of Exchange Server 2013, having network devices blocking ports/protocols between Exchange servers within a single organization or between Exchange servers and domain controllers in an organization is not
supported. A network device may sit in the communication path between the servers, but a rule allowing “ANY/ANY” port and protocol communication must be in place allowing free communication between Exchange servers as well as between Exchange servers and domain
controllers. - http://blogs.technet.com/b/exchange/archive/2013/02/18/exchange-firewalls-and-support-oh-my.aspx
Amit Tank | Exchange - MVP | Blog:
exchangeshare.wordpress.com

FIXED - Exchange 2013 - Can I Recreate Default Frontend Receive Connector SAFELY?

Hi
I'm need of some urgent assistance please.
I had a fully functional Exchange 2013 server and decided to create a receive connector for a photocopier/scanner to included its static IP  port number 25.
I accidentally chose Hub Transport role and not FrontEndTransport role which appears to have messed up port 25 connectivity on mail coming in from the internet. When I stopped and restarted the Transport Service within services.msc I then got this error.
Source: MSExchangeTransport
Event ID: 1036
Task Category: SmtpReceive
Level: Error
Description: Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running
properly.
I proceeded to delete the offending Receive connector for the scanner/photocopier and restart the server, the transport service started ok this time but still I cant receive mail from the outside world.
My question: Can I delete the automatically created default Frontend "servername" connector which contains the proper settings then recreate it again with the same settings and NOT harm/delete all the users emails or the mailstore
or anything bad for that matter?
I have the details on how to create the connector but just wanted to check that's its ok to remove it and re-add it again now that everything was setup and running fine. I'm hoping the recreated Connector will fix what I broke.
Appears what I have done has broken my connectivity to telnet to port 25 to the exchange server from the outside world although oddly I can telnet to the server from a command prompt on the exchange server (telnet "servername" 25) and
getpresented with the exchange server responding. The tickbox for anonymous is ticked already. Port 25 already is forwarded from the firewall to the exchange server and was working fine till I made the error.
Any help is greatly appreciated. Thankyou.

OK so I found some more details online and decided to take the plunge (after a backup was taken) and my problem is now fixed. Although thank you to the 40 people that atleast looked at my query.
This worked for me, please read, backup and decide yourself if you wish to follow my steps.
1. I Read this to understand more on how I broke it in the first place  :
First section of this......
https://exchangemaster.wordpress.com/tag/smtp/
then
http://support.microsoft.com/kb/2958036
2. Deleted the Default Frontend "servername" Receive connector
3. Recreated it using these guidelines below. (I included them all for your ref). Source https://social.technet.microsoft.com/Forums/exchange/en-US/32e13998-a84e-4f10-8557-3f7ce6fdb824/2013-default-receive-connectors:
[PS] C:\>Get-ReceiveConnector | fl Name,AuthMechanism,RemoteIPRanges,TransportRole,permissiongroups,MaxMessageSize
Name             : Default EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Name             : Client Proxy EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Name             : Default Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Name             : Outbound Proxy Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Name             : Client Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : ExchangeUsers
MaxMessageSize   : 35 MB (36,700,160 bytes)
4. Recreated the Receive connector for my photocopier/scanner but this time choose Frontend Transport role and Not the default Hubtransport. Restarted the server, crossed my fingers and everything worked!! (Apparently restarting both transport services
is sufficient, but hey I just want to be sure it works from reboot in future.
Exchange SP1 will break any custom receive connectors that you have made prior to installing the update (nor even warn you that you're about to create an addition hub transport connector on port 25 after the SP1 update, there should
be only one hubtransport on port 25 as I understand it, its ok for Frontend transport) . The transport service will not start, so to save you the hassle of deleting your custom connector just run this command from an elevated exchange powershell command to
change the custom connector from hubtransport to Frontend Transport then start the transport service. ( you may have to kill the Transport service .exe process in task manager, then start the transport services after this amendment from the services.msc panel)
Set-ReceiveConnector –Identity "Your Receive connector name" –TransportRole FrontendTransport
Alternatively, delete and re-create the receive connector and set its role to
FrontendTransport and NOT HUBTRANSPORT !!!!!!!!!!!
This issue occurs if there is a receive connector of Transport type
HubTransport that has the binding set to port 25 on the affected Exchange 2013 server. On an Exchange 2013 server that has both back-end and front-end roles, only the
FrontendTransport server-type receive connector should have the binding set to port 25.
To fix this issue, run the following cmdlet to change the connector type from
HubTransport to FrontendTransport:
Source: http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-server-2013-sp1-transport-service-stops-and-does-not-restart.html

Static ports

i have an Oracle7 server running, the listner is on the standard port (1521 i believe) but wher it responds to clients, it keeps using different port numbers and this is making it difficult to impossible to cross my firewall.
the v-one vpn i have has an oracle proxy, it doesnt work...
can i do a registry mod or something, so oracle always replies on the same port(s)?
thanks,
null

Hello,
Here you can find port references for all Exchange server versions (except 2013):
http://blogs.technet.com/b/exchange/archive/2013/02/18/exchange-firewalls-and-support-oh-my.aspx - the Exchange Network Port References section.
The list for Exchange 2010 and 2013 is similar but 2013 version uses Outlook Anywhere (port 443) instead of RPC for client connections. So you do not need to configure static RPC
ports for Exchange 2013.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Exchange 2013 cant send or receive email

new server with clean install
static IP
firewall is configured for smtp on port 25
single exchange 2013 server
checked DNS settings in servers tab
checked mail connectors per MS KB's
deleted all connectors and rebuilt only 1 send and 1 receive connector
still not sending or receiving email they stay stuck in drafts and email never gets delivered coming in
David Sheetz MCP

Can users send email to each other, in house? Is the Exchange Server part of a domain, if so, what OS is the Domain Controller? Check list to run through:
1. Port 25 is forwarded to Exchange Server IP address
2. Send Connector is using MX Records and using * for the domains
3. Receive Connector has the appropriate domain listed for the Accepted Domains, ie. Contoso.com not just .local
4. mailbox username convention has been specified and you clicked the "Apply" link to the right after creating the mailbox username policy
5. After the above, go into Services and restart the Exchange Mailbox Store

Cannot send email from Exchange 2007 to Exchange 2013 - Coexistence

Existing Exchange 2007 SP3 1 MBX, 2 CAS/HT, 2 ET servers.
I have added an Exchange 2013 server with MBX/CAS role.
Email will flow from Ex2013 server no problem. Mail from Ex2007 systems cannot deliver to Ex2013 boxes, it dies in queue with a 4.4.7 expired message after issuing a delay message.
I can telnet to ports 25, 587,717,465,475, and 2525 from Ex2007 HT role to new Exchange 2013 server. I can send email from Ex2007 HT role server to new Exchange 2013 server using telnet to port 25.
A ‘get-mailbox’ from the Ex2007 HT role server returns the server and database properly on the test users on Exchange 2013 server.
The only strange thing I am seeing is from the Ex2007 systems, a ‘get-exchange server’ command shows the new Ex2013 server as role ‘16439’ which looks to perhaps be normal.
Why is email not flowing to the new users on Exchange 2013?

You should have exchange server authentication ticked in Default Receive connector in Exchange2007.
Exchange 2007 and Exchange 2013 in the same subnet/network. if not please check any spam agent running between the networks. Are you running antispam on Exchange2013 ?
MAS

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Exchange 2013 External Relay gives me a headache... Anonymous relay fail to external address

I tried to set up external relay on my Exchange 2013 but was not able to do it. I don't know what else to do. I tried these:
http://technet.microsoft.com/en-us/library/bb232021.aspx
and these (which is pretty much same thing)
http://www.shudnow.net/2013/06/04/how-anonymous-relay-works-in-exchange-2013/
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
But still no luck. Here is somewhat detailed description what I tried do accomplice.
Server which need to send mail reports is sending these from web server on another location connected with site-to-site VPN to location server resides like on picture. I am able to send relay to all of
addreses of local domain but when I tried to send mails to my clients to external e mail addresses exchange return me message unable to relay.
Here is log from unsuccessfully operation
Connecting to [smtp.mydomain.com] port [25]...
220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 17:19:45 +0100
>HELO webserver
250 smtp.mydomain.com Hello [89.x.x.x]
>MAIL FROM: <[email protected]>
250 2.1.0 Sender OK
>RCPT TO: <[email protected]>
ERR: Received the following unexpected repsonse:
550 5.7.1 Unable to relay
>QUIT
221 2.0.0 Service closing transmission channel
Here is log from successfully operation:
Connecting to [89.x.x.x] port [25]...
220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 18:04:52 +0100
>HELO webserver
250 smtp.mydomain.com Hello [89.x.x.x]
>MAIL FROM: <[email protected]>
250 2.1.0 Sender OK
>RCPT TO: <[email protected]>
250 2.1.5 Recipient OK
>RCPT TO: <[email protected]>
250 2.1.5 Recipient OK
>DATA
354 Start mail input; end with <CRLF>.<CRLF>
>From: Dane <[email protected]>
>To: [email protected]
>Subject: asd
>Date: Fri, 24 Jan 2014 18:03:08 +0100
>X-Mailer: Qm Version 2.1
>MIME-Version: 1.0
Content-type: text/plain
>
>test>
250 2.6.0 <3ffb1fd6-e5e0-4232-9a6e-cac7b59db9df@exchange.mylocaldomain.local> [InternalId=6240587481093] Queued mail for delivery
>QUIT
221 2.0.0 Service closing transmission channel
And here is picture:

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Regards,
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

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.

Exchange 2013 Static Ports

Similar Messages

Maybe you are looking for