Exchange 2013 Edge Transport Replacement

Hi all,
I have a quick question regarding a new 2013 Edge Transport that I need to move to a physical machine.
It currently resides on a VM and I would like to decommission this machine, remove the edge subscription and redeploy the same configuration on a physical box.
Do you see any issues using the same name and IP with the new box? I know it says it is not supported to rename the edge, but If I remove it completely and redeploy?

Hi Scott4768,
Based on my experience, you should uninstall the EDGE server which on a VM and then re-install it on a physical box, and you could use the same IP and name.
In simple terms, the steps are following:
1. Remove-EdgeSubscription
2. uninstall EDGE server
3. re-install EDGE server on a physical box
4. Create New-EdgeSubscription
Best regards,
Eric

Similar Messages

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

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 2013 Edge Transport install fails

I'm trying to install the Edge Transport for Exchange 2013 but it gets to step 7 of 9:
then give's 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.".
Then in event viewer I have the following two events.
Watson report about to be sent for process id: 260, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, ExSetupUI, M.E.Data.Directory, M.E.D.D.ADObjectId.GetChildId, System.ArgumentNullException, 2ac6, 15.00.0847.031.
ErrorReportingEnabled: True
and
Exchange Server component Edge Transport Role failed.
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.".
I've rebuilt the server but since it has something to do with the GUID I assumed it wouldn't work but I was grasping at straws and it didn't fix the issue.
I can run the setup again and it does finish but it doesn't show up in the list of servers in the ecp management. I've yet to find a solution on this issue if anyone has a suggestion or two it would be greatly appreciated.

Thanks for response.
when I run Get-ExchangeServer I get the following
Name Site ServerRole Edition AdminDisplayVersion
Exchange03 Edge Standard... Version
15.0 (Bu...
and the errors that are in the log
[02/17/2015 20:06:33.0084] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: ADAM is installed on this machine; only the Microsoft Exchange Edge Transport server role may be installed. See the Exchange setup log
for more information on this error.
[02/17/2015 20:07:50.0288] [1] The following 1 error(s) occurred during task execution:
[02/17/2015 20:07:50.0288] [1] 0. ErrorRecord: Service SMTPSVC was not found on computer '.'.
[02/17/2015 20:07:50.0288] [1] The previous errors were generated by a non-critical task and will be ignored.
then I have a load of error that failed to load dependency below is a small sample
[02/17/2015 20:07:57.0648] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V15\bin\edgetransport.exe
Failed to load dependency Microsoft.Management.OData of assembly Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
from HRESULT: 0x80070002)
Failed to load dependency Microsoft.Ceres.InteractionEngine.Processing.BuiltIn of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified.
(Exception from HRESULT: 0x80070002)
Failed to load dependency Microsoft.Ceres.NlpBase.RichTypes of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
from HRESULT: 0x80070002)
Failed to load dependency System.IdentityModel.Tokens.Jwt of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from
HRESULT: 0x80070002)
Failed to load dependency Microsoft.Passport.RPS of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from HRESULT:
0x80070002)
Thanks

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 2013 edge

Hi!
Today we have a site with Exchange 2013 multi-role servers. On our DMZ we have 2 exchange 2010 edge servers. We are planning to install 2 new Exchange 2013 edge servers that will replace the once currently installed. When the new servers are installed and
we have created the edge subscription, will all edge servers (2010 and 2013) be used until we remove the old ones?
Regards,
UC

yes.

Exchange 2013 Edge on Web server

I just purchased 2 new servers. Both will be running Windows Standard 2012 R2. One will be used to run Exchange 2013 HUB/CAS (LAN) and the other will be a Web server (DMZ) hosting various internal websites (IIS/PHP). Instead of having a 3rd older server
run Exchange 2013 Edge, I was thinking on installing it on the new Web server. Any disadvantages or no-nos?
Thanks

Hi,
In theory, there is no conflictions. But the performance of the server is hard to know.
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 Server 2013 Edge Transport Role

Dear,
I have a question regarding Exchange Server 2013 SP1 that, I have installed Edge Transport Server Role on separate box without Domain Joined. Obviously I installed Exchange CAS and Mailbox on Same box with
Domain Joined in Corporate LAN.. But my edge is placed on DMZ and it is ready with all configuration, Mailbox Server Synchronization is also installed with Edge. Means all required configuration are properly configured and it is verified. But I want clients
to OWA Access from Edge only. Because I want to restrict my internal network from the internet. So kindly provide me any possible ways to access OWA from Edge only ??. I have see some another methods like "Web Application Proxy instead of TMG because
TMG is expired"..
Kindly provide me possible ways or URL so I will configure it..
Thanks.
Fuzail (FM)

Hi,
Is there any further question on this thread?
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 2013 Edge subscription

I have Exchange 2013 installed using a second site for resilience.
I am configuring Exch 2013 Edge servers at both locations.
Lets say Edge01 and Edge02 are in Santa Fe along with CAS and Mailbox servers,
Edge03 and Edge04 are in Minneapolis along with associated CAS and MB servers.
Santa Fe and Minneapolis are in different AD Sites.
For each edge server, I will need to create a subscription for each location, right?
Edge01 will require a subscription for Santa Fe and a separate subscription for Minneapolis.
And the same would go for each edge server.
Am I correct?
Tom

Hi,
Here you go...
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.
http://technet.microsoft.com/en-us/library/aa997438(v=exchg.150).aspx
Kottees :My Blog Please mark it as an answer if it really helps you.

Error During Exchange 2013 Mailbox Transport Role Install On Server 2012

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.".
The only option on the screen was exit, so I did. I checked the start menu, and there were two new Exchange icons, but I did not click them. I ran the installer again, and it detected an incomplete install, the only option was to click next to
finish the install, so I clicked next. This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service." I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013
came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh. Any suggestions?

I've tried three times since my last post, following
http://msexchange2010.info/archives/2330 as closely as possible the most recent time. I am consistently getting the same error that appears to imply I don't have write access to the domain. I don't understand this, because I am using the
same domain admin account I have been using all along. Nonetheless, here is the powershell output starting with the first Exchange setup.exe step (all other steps were already performed, all available updates were installed, and the server was rebooted
prior to this):
Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.
PS (domain admin home)> D:
PS D:\> .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema COMPLETED
The Exchange Server setup operation completed successfully.
PS D:\> .\Setup.exe /PrepareAD /OrganizationName:PRD-INC /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis COMPLETED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx
Configuring Microsoft Exchange Server
Organization Preparation COMPLETED
The Exchange Server setup operation completed successfully.
PS D:\> .\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t E:\Exchange /IAcceptExchangeServe
rLicenseTerms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Languages
Management tools
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Client Access role: Front End Transport service
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup COMPLETED
Stopping Services COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Exchange Management Tools COMPLETED
Mailbox role: Transport service COMPLETED
Mailbox role: Client Access service COMPLETED
Mailbox role: Unified Messaging service COMPLETED
Mailbox role: Mailbox service FAILED
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox.".
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS D:\>
I am cleaning out in ADSI and rebuilding the server for now, because the server is behaving oddly (not as oddly as it was with 6GiB, but oddly, nonetheless). I probably won't try to install Exchange again before tomorrow. What should I do to prevent
encountering the above again and/or if I encounter it again?

How to add exceptions for Sender Filtering in Exchange 2013 Edge

hi everyone.
got a bit of a problem.
I've installed 2 exchange 2013 servers. one for Mailbox-CAS (Hub) & one as Edge Server.
I've configured Blocked domains for blocking my users from sending emails to public mail servers such as Hotmail,google & yahoo and I've set up some users as exceptions (such as CEO & managers).
I wanna configure my Edge server to block inbound email from such servers as well & have to set some exclusions.
as I searched online, the command would be "set-senderfilterconfig -blockeddomainsandsubdomains"
but I can't use -Bypassed switch as I do in Content Filtering.
now my question is am I using the right method (commands & stuff) to reach my goal?
also how I set some users as exceptions?
thanks in advance
this post is provided as is, with no warranties/guarantees

Hi,
I find this article for your reference:
Understanding Anti-Spam and Antivirus Mail Flow
http://technet.microsoft.com/en-us/library/aa997242.aspx#Content
If you want to block inbound email, please try to configure IP Block list, IP Block List providers, blocked domain or blocked sender.
If you want to block outbound email, please try to configure Recipient Filtering, like Recipient Block list.
More details to check the article above.
Thanks
Mavis Huang
TechNet Community Support

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.

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]

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

Is it possible to remove 2010 Hub Transport entirely in an Exchange 2013 environment?

I'm using Exchange 2010 Edge Transport in our organization that I've recently upgraded to Exchange 2013. I like Edge Transport - along with our spam filter it is an effective and simple way to send and receive external e-mail - and I don't want
to get rid of it. But it seems like it needs a 2010 Hub Transport server to interact with.
Right now the only other Exchange 2010 Server I have left running in the organization is the one Hub Transport server that interacts with the Edge Server. Is there a way to undeploy this server too and connect the Edge Server directly to one of the
2013 Mailbox Servers? Or will this need to stay as part of the organization as a pair with Edge Transport?
I noticed mail flow was running just fine while the Hub Transport server was turned off. So it seems like it's possible. But I want to be able to undeploy it safely without hurting mail flow. Are there any links or white papers that show
how best do do this?
----------- Ron E Biggs Chief Tech Officer Entertainment Studios

Before you remove your HUB servers, make sure you re-subscribe the Edge server using the below steps:
On Edge Server:
New-EdgeSubscription -FileName "C:\EdgeSubscription.xml"
copy the file to one of the mailbox servers, and run:
New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeSubscription.xml " -Encoding Byte -ReadCount 0)) -Site
"ADSITENAME"
once completed, most of the tasks to manage/test your Edge sync will be via PowerShell, please see the below link for more details:
http://technet.microsoft.com/en-us/library/aa996865(v=exchg.150).aspx
Mohammad Saeed | MCSE 2003 | MCTS: Lync, OCS, Exchange This posting is provided "AS IS" with no warranties, and confers no rights

Exchange 2013 Edge Transport Replacement

Similar Messages

Maybe you are looking for