Exchange 2010 edge transport server, degraded desktop / remote desktop

I have a 2010 edge transport server loaded on windows server 2008 R2 that after about 3 days will no longer allow RDP connections or desktop logons due to a serious performance lag / time out. A reboot clears the performance issue for about another 3 days.
I allowed an RDP connection to stay open for the 3 days and it continues to work however actions like trying to load the task manager, start button, computer or any windows not currently open takes an extremely long time. Task manager and perf mon show very
little processor and memory usage.
Tried the following to resolve:
Replaced hard drives (raid 1)
Replaced server (moved drives from one server to another chassis)
Monitoring iops, memory usage and proc transactions. Nothing shows any unusually high usage.
I tried disabled AV services, log monitoring and backup services both while the issue was happening and as preventative measure before the issue arose.

hi cna you check if by any chance you have bandwidth limitations configured. either on router or on tour switch. i had this kind of issue and it ended with bandwidth issue which was configured wrongly. you said this is happening with RDP. hows the performance
when accesing locally
did you check performance counters and event viewer.. anything there
Mark as useful or answered if my replies helped you solving your query.
Thanks, Happiness Always
Jatin
Skype: jatider2jatin, Email: [email protected]

Similar Messages

Exchange 2010 Edge Transport - Not being detected by SCOM agent?

All,
I recently installed the SCOM 2007 R2 agent onto our Edge Transport server for Exchange 2010. Our architecture is pretty simple. We have a DMZ network where I have a SCOM 2007 R2 Gateway server and our Edge Transport server.
Essentially it goes like this:
Edge Transport Server Agent <-> Gateway Server <-> SCOM RMS server
I have the Exchange 2010 and the FOPE for Exchange 2010 MP's loaded on our RMS server. When I loaded the SCOM 2007 R2 agent onto our Edge server, the agent discovered it had FOPE and does reflect as such on the RMS server, but it did not seem to pick
up that it was also the Exchange Edge Transport role.
I looked on the RMS server in the Authoring -> Object Discoveries and the Edge transport is set to discover, so I am a little stumped as to why the agent didn't discover the role.
Any suggestions where to look next?

Just a little more detail on this. I've been working on this exact issue for probably 3 weeks with an engineer.
This issue is actually a bug in the Exchange 2010 MP.
How is it a bug exactly? Well, the MP is looking for the Active Directory site that the Edge Server is a member of... let's think about this, the Edge server is NOT domain joined, and as such, shouldn't have an active directory site.
Additionally, the regkey path referenced above is incorrect, though it seems that numerous others have figured that out on their own as well. The correct regkey path should be:
hklm>system>currentcontrolset >services>netlogon>parameters
So sure, this "fixes" the issue - but the real issue is that the MP is looking for an Active Directory site, on servers that aren't a member of an active directory site. Kind of a BIG oversight by the MP authors in my opinion.
I'm sure there are plenty of orgs relying on SCOM to monitor their Exchange 2010 implementations that don't even realize that their Edge servers aren't being monitored for the Exchange roles.

Deploy Exchange 2013 Edge Transport Server for multi-site environment

Hi,
I have a multi-site Exchange 2013 environment. The configurations are as below.
Active Directory Sites and Exchange Servers.
SiteA - EXMB1 & EXCAS1
SiteB - EXMB2 & EXCAS2
SiteC - EXMB3 & EXCAS3
All sites are connected via VPN. (Good speed. No latency issues)
All the three Mailbox Servers are in DAG. Only one mailbox database. All servers running Exchange 2013.
I am planning to deploy Edge Servers in the infrastructure (I am doing it for the first time). Normally, it will be in DMZ.
Now, I can deploy 2 Edge Servers for reliability.
Question.
1. Can I deploy 2 Edge Servers and create subscription to all the mailbox server in 3 different site? Or, is it like one edge server can make subscription to only mailbox servers in one Active Directory Site? I am not sure about this and could not find much
information from TechNet.
One Edge Server can make subscription to all 3 mailbox server in 3 sites. Similarly, I can make the subscriptions in the second edge server as well. Configure 2 external MX records with the same priority so that there will be some load balancing.
Also, in such a case if the mailbox database become active from a different site, I need not make any new changes to the Edge Servers right?
2. If the first way is not correct, I will have to deploy 1 Edge Server each for each of the Active Directory Site. (In DMZ only, not in domain)
Make Edge Subscription to the mailbox server in corresponding site.
Make 1 MX record and point it to the Edge Server which is subscribed to the Mailbox Server from which the Database is Active. The problem is, every time will have to change the DNS record when ever the database copy is activated from a different mailbox
server. And the issues with propagation.. delay..
I am not sure which of the above 2 ways will work. Appreciate suggestions from anyone who have previous experience with similar infrastructure.
Thanks in advance. :)

Hi
One or more Edge Transport servers can be subscribed to a single Active Directory site. However, an Edge Transport server can't be subscribed to more than one Active Directory site. If you have more than one Edge Transport server deployed, each server can be
subscribed to a different Active Directory site. Each Edge Transport server requires an individual Edge Subscription.
A subscribed Edge Transport server is associated with a particular Active Directory site. If more than one Mailbox server exists in the site, any of them can replicate data to the subscribed Edge Transport servers.
I don't think there is a solution to subscribe edge servers for more than 1 site. Edge Servers can be scoped only to one site.
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 2010 hub-transport server

i have 2 exchange 2010 hubtransport servers.
ideally when i send email my email should be load-balanced but emails send using hubcas1 goes fine and hubcas2 kepts in queues
suppose if i send at a time 5 mail
3 emails go through hubcas1
2 emails stucks in queue in hubcas2

Hi,
As you said you have added both the hub transport servers in the source server option of the send connector.Same time you have mentioned you don't have the smart host to deliver the emails to the internet and also the server hubcas2 can able to resolve the
external domain namespaces .Then do the following .
step 1 :Then please enable the protocol logging on the send connector to see the why the connections from the server hubcas2 is rejected to send emails to internet.
Step 2: Then do the outbound email test from EXRCA tool by using the ip address or name which is mapped on the MX record which belongs to the server hubcas2.
Please feel free to reply me if you have any queries .
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Does Edge transport server for Exchange 2013 work with Exchange 2010?

Hello everyone,
I want to install Edge transport server for my Exchange servers,
Could you tell me if Edge transport server 2013 works with Exchange 2010?
Thank you in advance

Hello
tip:
https://technet.microsoft.com/en-us/library/jj898583%28v=exchg.150%29.aspx
2 If you want to create an EdgeSync
Subscription between an Exchange 2010 Hub Transport server and an
Exchange 2013 SP1 Edge Transport server, you need to install Exchange
2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport
server.
sorry my english

Exchange SP1 Edge Transport Install Error

Hi everyone,
I've successfully installed multiple Mailbox and CAS 2013 SP1 servers into an existing Exchange 2010 environment.
However, when I get to the Edge Transport role on a separate server, at step 7 of 9, it throws the following error:
Error:
The following error was generated when "$error.Clear();
new-ExchangeServer
" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
Any ideas what could be causing this? I haven't been able to find anything of significance while searching around...
Thanks!

Hi,
Make sure prerequisites for Exchange 2013 Edge Transport server role are met. For more details about this, you can refer to the following article.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354%28v=exchg.150%29.aspx#WS2012Edge
If you have checked above, and this issue persists, please check the set up log to see if there is related error message to narrow down the issue.
Besides, here is an article about Edge Server installation for your reference.
Install the Exchange 2013 Edge Transport role using the Setup Wizard
http://technet.microsoft.com/en-gb/library/dn635117(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 Edge server shows previous version

I have an Exchange 2010 environment with the Edge role installed on TMG and its working fine. All servers have had SP3 installed and rebooted.
I am trying to introduce my first Exchange 2013 server into the environment but the readiness check tells me not all the servers have SP3. On the Edge server it shows SP3 is installed but from all other Exchange servers it shows SP2.
Any ideas?
Thanks

For anyone else wondering. I've done this in my lab, and I didn't have to remove the old subscription, just export the file from your edge server, copy it to any server running emc internally and import it, then force a sync and the version should
update.
On edge server open exchange
     powershell and run New-EdgeSubscription -FileName
     "C:\EdgeSubscriptionInfo.xml"
Import edge file
     into new server
You
need to be assigned permissions before you can perform this procedure. To see
what permissions you need, see the "EdgeSync" entry in the
Transport
Permissions topic.
In the console tree, navigate
     to Organization Configuration >
Hub Transport.
In the result pane, click the
     Edge
     Subscriptions
     tab.
In the action pane, click
New Edge
     Subscription. On
     the New Edge Subscription page, complete the following fields:
Active
      Directory site   Click
      Browse, and then select an Active
      Directory site in the drop-down list. This field identifies the Active
      Directory site where the Hub Transport server is connecting to the Edge
      Transport server for which the Edge Subscription exists.
Subscription
      file   Click
      Browse, and then select an Edge
      Subscription file.
Automatically
      create a Send connector for this Edge Subscription   Select
      this check box to automatically create a Send connector that routes
      messages from the Exchange organization to the Internet. The Edge
      Subscription is configured as the source server for the Send connector.
      The Send connector is configured to route messages to all domains by
      using Domain Name System (DNS) MX resource records.
Click
New to create the new Edge
     Subscription.
On the
Completion page, review the following,
     and then click Finish to close the wizard:
A status of
Completed indicates that the wizard
      completed the task successfully.
A status of
Failed indicates that the task
      wasn't completed. If the task fails, review the summary for an
      explanation, and then click Back to make any configuration changes.
Start-EdgeSynchronization
     -Server Hub01 -TargetServer Edge03 -ForceFullSync

Edge Transport Server - Exchange 2013 coexistence Exchange 2007

Hi Exchange-Gurus,
We have one Exchange Org.
sub AD Domain1: A.domain.com (with Exchange 2007 SP3 R10)
sub AD Domain2: B.domain.com (with Exchange 2013 CU6); DMZ contains Exchange Transport Server - Exchange 2013
Is it possible to install within the DMZ of AD Domain1 a Edge Transport Server - Exchange 2013?
Thanks.
Guitarman

Hi Guitar,
Thank you for your question.
Is it possible to install within the DMZ of AD Domain1
an Edge Transport Server - Exchange 2013?
A: Yes, we could create an Exchange 2013 Edge server on the DMZ of AD domain1.
Notice: Before we create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, we need to install Exchange 2007 SP3
Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Using Exchange 2010 Edge server as an SMTP gateway without other roles

I am looking to implement a simple SMTP gateway solution for a few applications to relay emails and hence am not looking at a full fledged Exchange deployment. As SMTP component is no longer available in Windows Server 2012, I would like to know if the Exchange
2010 Edge role can function as a simple SMTP gateway solution without having the other roles of Exchange 2010 deployed like the CAS, Hub and Mailbox ?
My requirements from this SMTP gateway solution would be the ability to append disclaimers, relay restrictions based on IP addresses and sender email addresses, and provide both authenticated and unauthenticated relay access.
Any inputs would be highly appreciated. Thanks in advance.

Hi again
I decided to test the scenario - just for fun, and it seems to work. A strange setup :-)
So you will have to prepare your schema and AD - and create an Exchange organisation.
Then you will have to assign the receive connector(s) AD permission to relay outside the organisation - by default it can only relay internal, but since your mailsystem is "outside" seen from Exchange - you'll need to do that.
Is your AD domain the same as your SMTP namespace? Because then you have to make it external relay after you have removed it from the e-mail address policy :-)
BR
Steen

EXCHANGE 2010 - Edge server with forefront FULL OF SPAM

Hi there.
We have recieved on Exchange 2010 EDGE server a lot of spam 200k messages in queue.
We have stoped inboud SMTP traffic on firewall to stop the attack.
Any suggestion how to empty the queue? I've heard there is a way to rename the "Exchange queue folder" but forget the procedure.
How to stop the attacker?
bostjanc

Hi There,
Use the KB below to find the Queue DB, then stop the service listed In the KB, rename the old DB and create a new one with the same name, than start the Service.
http://www.ntweekly.com/?p=653
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

EdgeSync service cannot connect to this subscription because of error "No EdgeSync credentials were found for Edge transport server

When checking Edge Synchronization on our Exchange 2010 HUB server (Test-EdgeSynchronization) I get SyncStatus "Failed". I suspect this failed after we had moved all of our Exchange 2010 servers (Except the Edge server which not member
of any domain or site) to a new site.     In hopes to resolve this, I did the following:
Removed the Edge Subscription from our HUB server using the EMC.
Deleted the cert used by ADAM on our Exchange 2010 Edge server (using the Certificates MMC).
On the Exchange 2010 Edge server created a new Edge subscription file using: “New-EdgeSubscription –FileName "C:\EdgeSubscription20150424.XML"
Restarted the "Microsoft Exchange ADAM" service on our Edge server.
Copied the "EdgeSubscription20150424.XML" to our HUB server. Then completed the New Edge subscription import on our HUB server using the MMC (specifying the AD site and location/name of the XML).
After this, I still get syncstatus failed on our HUB.   Thought to check the certificate using "Get-ExchangeCertificate | FL" but that results in: "Get-ExchangeCertificate : The Exchange Certificate operation has failed
with an exception. The error message is: Access is denied".   I tried to create a new certificate on our HUB serve using "New-ExchangeCertificate", but get the exact same "Access is denied" error message
again.
I believe we never noticed that the Edge sync wasn't working because we only use our Edge server when our hardware email filter fails (Symantec Message Gateway). Our Edge server has a lower priority in our MX record and lower priority in our send connectors
on our HUB servers. The Edge server though does receive email from internal email relay from some servers for notifications. These do get delivered unless the user mailbox is new (suspect ADAM isn't updating - that's why I started looking into
this).
This should be simple!   What am I missing???   Thanks in advance for any feedback.
PS - this is my first posting here.... I apologize if I posted this in the wrong forum or category. :)

Hi PongoDog,
Thank you for your question.
By your description, we could refer to the following steps to check if issue persist:
Remove all hub servers certificate
Create a new hub server certificate with command "New-ExchangeCertificate"
Remove the edge subscription on hub & edge server
Recreate sync subscription and import it on hub server.
If the issue persist, we could Check network connectivity between the Hub Transport server and Active Directory. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. then
run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange Server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. Finally Rreview the Application log for MSExchangeADAccess and MSExchange
Topology events that could provide more information about the root cause of this event and post Event ID to
[email protected] for our troubleshooting.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Positioning and role of Edge Transport Server

Good afternoon, all!
I'm working on a new Exchange design and implementation project. I had some research that seemed to indicate that I could have my Edge Transport server in the DMZ to receive Internet mail and to act as a web proxy for the Client Access server residing
in the internal network. However, in my testing I haven't found where that is possible.
Will the Edge Transport server provide that capability or will I need to open a path to the Client Access/Mailbox server? Is there a tradeoff in separating the Client Access server into a separate machine in the DMZ for remote access, that is, if the
Edge Transport server won't supply web proxy services, will I need to make a separate machine for Client Access?
Thanks!
Gregg

Hi Gregg,
Based on my knowledge, Edge Server role handles Internet-facing mail flow and act as an SMTP relay and smart host for Exchange servers in your internal network. We can use Edge server if don't want to expose internal CAS and MBX. We can also
configure Anti-Spam on Edge server to block specific emails.
Unlike other Exchange server roles, the Edge server doesn’t need to be a member of an AD domain, so locating it within a DMZ does not create any difficult firewall configurations.
Confirm that any firewall between your Exchange servers and Edge servers allow port 53 for DNS resolution and port 25 for SMTP traffic.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Edge Transport Server Limitations - messages delivered per day?

I'm currently on the hunt for some kind of baseline / benchmark that will indicate how many messages per day (or per second) an Edge Transport server is capable of handling. I feel like this should be in some whitepaper somewhere for when Edge Transport
is designed, so you know how many to deploy, but I can't find it.
I know system specs will be a factor. We have the current hardware in our box:
2 processors (2.67 GHz)
16 GB RAM
64-bit OS (Windows Server 2008 R2 Enterprise)
If anyone has come across any kind of guideline for email delivery limitations of ET, I'd appreciate being pointed to them.
Thanks

The current Exchange servers are much faster and beefier than they were when I worked with Exchange 4 Beta 2 with a customer many years ago. They tried to swamp their Exchange server (dual 90 MHz Pentium server with 128 MB RAM) using six Unix workstations
running Mailstorm against it. They had to stop when their primary Unix systems handling inbound email were overloaded due to how they set up their test. And the Exchange server never skipped a beat.
Another customer situation that may help is that I have seen 10,000 messages in an Exchange 2010 queue (due the smart host they were using for external delivery was offline for maintenance) drop to zero within 15 minutes. I'd suggest that you run some
sort of test of your own to determine how many messages your edge is capable of delivering, but these may give you an indication of the expected capabilities.

Risk of not having an Edge Transport server

What is the risk of not using an Edge Transport server? Is it worth the extra cost? Environment is Exchange 2010 and ForeFront TMG 2010.

Hi,
if the internal server can handle the load I don't see any problem.
Regarding the CAS server is facing the Internet you should have a firewall in front of it that stopps most of the attacks.
Greetings
Christian
Christian Groebner MVP Forefront

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

Exchange 2010 edge transport server, degraded desktop / remote desktop

Similar Messages

Maybe you are looking for