Skip Ribbon Commands
Skip to main content

IT Blog

:

Quick Launch

IT Support to Go > IT Blog
February 29
Exchange 2010 Edge Transport Server: Configuring EdgeSync

 

Firewall Ports for Exchange Server 2010 Edge Transport Servers

For EdgeSync and mail flow to work there are a few network ports that need to be open on the firewall between the Internet, the Edge Transport server, and the internal Hub Transport server.

Edge Transport Server Network Ports for EdgeSync

  • Secure LDAP (TCP 50636) from the Hub Transport server to the Edge Transport server

Edge Transport Server Network Ports for Mail Flow

  • SMTP (TCP 25) from the Internet to the Edge Transport server
  • SMTP (TCP 25) from the Edge Transport server to the Hub Transport server
  • SMTP (TCP 25) from the Hub Transport server to the Edge Transport server
  • DNS (UDP 53) from the Edge Transport server to a DNS server capable of public DNS lookups (ie to look up MX records)

 

Creating the Edge Subscription for Exchange Server 2010 Edge Transport Servers 

With the firewall access all configured correctly the next step is to configure the Edge Subscription itself.
On the Edge Transport server open the Exchange Management Shell and run the following command using the New-EdgeSubscription cmdlet.
[PS] C:\>New-EdgeSubscription -FileName C:\edgesubscription.xml

Confirm
If you create an Edge Subscription, this Edge Transport server will be managed via EdgeSync replication. As a result,
any of the following objects that were created manually will be deleted: accepted domains, message classifications,
remote domains, and Send connectors. After creating the Edge Subscription, you must manage these objects from inside
the organization and allow EdgeSync to update the Edge Transport server. Also, the InternalSMTPServers list of the
TransportConfig object will be overwritten during the synchronization process.
 EdgeSync requires that this Edge Transport server is able to resolve the FQDN of the Hub Transport servers in the
Active Directory site to which the Edge Transport server is being subscribed, and those Hub Transport servers be able
to resolve the FQDN of this Edge Transport server. You should complete the Edge Subscription inside the organization in
 the next "1440" minutes before the bootstrap account expires.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): y
There are two important things to be aware of here:
  • You must complete the next step of the Edge Subscription process within 1440 minutes (24 hours), otherwise you’ll need to generate a new Edge Subscription again
  • The Hub Transport servers in the Active Directory site that will be subscribed must be able to resolve the FQDN of the Edge Transport server. You can either add DNS records manually or use a HOSTS file entry.
Copy the “edgesubscription.xml” file to the Hub Transport server. Launch the Exchange Management Console and navigate to Organization Management/Hub Transport.
In the Actions pane click on New Edge Subscription.
 
 
Browse and select the Active Directory site to be subscribed, as well as the XML file that you copied from the Edge Transport server.
 
 
Click the New button to complete the wizard.
After the Edge Subscription has been created you will see two Send Connectors configured for your organization.
 
 
It can take up to an hour before the first Edge synchronization process runs, but you can run it manually if you need to. On the Hub Transport server launch the Exchange Management Shell and run the following command using the Start-EdgeSynchronization cmdlet.
[PS] C:\>Start-EdgeSynchronization -Server esp-ho-ex2010a

RunspaceId     : b7415ae2-f763-449e-bb36-20a6a18759cd
Result         : Success
Type           : Configuration
Name           : esp-ho-ex2010e
FailureDetails :
StartUTC       : 5/7/2011 1:27:39 PM
EndUTC         : 5/7/2011 1:28:07 PM
Added          : 290
Deleted        : 0
Updated        : 0
Scanned        : 295
TargetScanned  : 0

RunspaceId     : b7415ae2-f763-449e-bb36-20a6a18759cd
Result         : Success
Type           : Recipients
Name           : esp-ho-ex2010e
FailureDetails :
StartUTC       : 5/7/2011 1:27:39 PM
EndUTC         : 5/7/2011 1:28:08 PM
Added          : 401
Deleted        : 0
Updated        : 0
Scanned        : 401
TargetScanned  : 0
After the initial Edge synchronization has occurred you will be able to see the Send Connectors and Accepted Domains configured on the Edge Transport server.
 

Testing Mail Flow

After the Edge Subscription is in place and you’ve synchronized at least once you can send email between your Exchange organization and an external mailbox, and then inspect the email message headers to verify that the messages are traversing your Edge Transport server.
Received: from esp-ho-ex2010e.exchangeserverpro.net (10.0.3.2) by
 esp-ho-ex2010a.exchangeserverpro.net (10.0.1.4) with Microsoft SMTP Server
 (TLS) id 14.1.289.1; Sat, 7 May 2011 23:50:10 +1000
Received: from (192.168.0.45) by esp-ho-ex2010e.exchangeserverpro.net
 (10.0.3.2) with Microsoft SMTP Server id 14.1.218.12; Sat, 7 May 2011
 23:50:07 +1000
MIME-Version: 1.0
Content-Type: text/plain

 

Published by About Paul Cunningham

Paul is a Microsoft Exchange Server specialist for one of Australia's largest companies, and is the Publisher of ExchangeServerPro.com. He is also an MCP, MCSA, MCSE, MCTS, and an MCITP for Exchange Server 2007/2010. Connect with

February 20
How to Change Site Icon

​To change site icon.

 

  1. Start up SharePoint Designer 2010
  2. Open your site
  3. Navitate to the Master Pages library
  4. Click on the the Master Page that your site uses (this is v4.master for a default team site)
  5. Click on the Edit file link under Customization
  6. Locate the tag "<SharePoint:SPShortcutIcon " in the code
  7. Replace the url to favicon.ico with your own ico file.

 

February 14
How To Install An SSL Certificate in Microsoft Exchange 2010

1.   From the Start menu, click Run..
2.   Type mmc, and then click OK. The Microsoft Management Console (Console) window opens.
3.   In the Console window, click the File menu and select Add/Remove Snap-in. The Add or Remove Snap-ins window displays.
 
4.   Select Certificates, and then click Add.
5.   Select Computer Account, and then click Next.
6.   Select Local Computer, and then click Finish.
7.   Click OK.
8.   In the Console window, expand the Certificates folder on the left.
9.   Right-click Intermediate Certification Authorities, mouse-over All Tasks, then click Import.
10.   In the Certificate Import Wizard, click Next.
11.   Click Browse to find the intermediate certificate file.

 

12.   Change the file extension filter to PKCS #7 Certificates (*.spc;*.p7b), select the *_iis_intermediates.p7b file, and then click Open.

 

13.   Click Next.
14.   Select Place all certificates in the following store.
15.   Click Browse, select Intermediate Certification Authorities, and then click Next.
16.   Click Finish.
17.   Close the Console window.
18.   From the Start menu, go to Programs, Microsoft Exchange 2010, and click Exchange Management Console.
 
19.   Click Manage Databases.
20.   Click Server Configuration.
21.   In Exchange Certificates, select your certificate.
22.   From the Actions panel on the right, click Complete Pending Request.
23.   Click Browse to locate the certificate file. The file extension might be .txt or .crt instead of .cer (search for all files).
 
24.   Click Open.
25.   Click Complete.
 
If you receive the error, "The source data is corrupted or not properly Base64 encoded," check the Self Signed field. If it is True, refresh console by pressing F5 on your keyboard. If it still displays True, create a new CSR and then re-key your certificate.
 
26.   Click Finish.
27.   From the Actions menu, click Assign Services to Certificate.
28.   Select servers, then click Next.
29.   Select services you want to assign to the certificate, then click Next.
30.   Click Assign.
31.   Click Finish.

 

February 14
How to Deploy a WSP

1: Download and extract the web part to a folder on the server.

 

 

2: Launch the sharepoint 2010 Management Shell with administrator priveleges (important!) (start > all programs > Microsoft SharePoint 2010 Products > Sharepoint 2010 Management Shell)
 
3: Run this command line to add the solution to the solution store in Sharepoint: Add-SPSolution <Path to itacschangepassword.WSP file in resources folder of download>
 
4: Run this command line to deploy the solution to the actual web application: Install-SPSolution -Identity "Web Part Name" -WebApplication http://<path to your web application> -GACDeployment
 
5: Open the sharepoint site and go to "Site Actions > Site Settings > Site Collection Features" page
 
6: Click "Activate" for the web part you installed.
You should now see the web part available to you in the web part gallery ("Site Actions > Site Settings > Galleries > Web parts).

 

February 13
How to Seize FSMO Roles

Roles and Locations
 
The five FSMO roles are:

 

  1. Schema Master
  2. Domain Naming Master
  3. Infrastructure Master
  4. Relative ID (RID) Master
  5. PDC Emulator

 

Seize FSMO roles
 
To seize the FSMO roles by using the Ntdsutil utility, follow these steps:
  1. Log on to a Windows 2008 Server-based or Windows Server 2008-based member computer or domain controller that is located in the forest where FSMO roles are being seized. We recommend that you log on to the domain controller that you are assigning FSMO roles to. The logged-on user should be a member of the Enterprise Administrators group to transfer schema or domain naming master roles, or a member of the Domain Administrators group of the domain where the PDC emulator, RID master and the Infrastructure master roles are being transferred.
  2. Click Start, click Run, type ntdsutil in the Open box, and then click OK.
  3. Type roles, and then press ENTER.
  4. Type connections, and then press ENTER.
  5. Type connect to server servername, and then press ENTER, where servername is the name of the domain controller that you want to assign the FSMO role to.
  6. At the server connections prompt, type q, and then press ENTER.
  7. Type seize role, where role is the role that you want to seize. For a list of roles that you can seize, type ? at the fsmo maintenance prompt, and then press ENTER, or see the list of roles at the start of this article. For example, to seize the RID master role, type seize rid master. The one exception is for the PDC emulator role, whose syntax is seize pdc, not seize pdc emulator.
  8. At the fsmo maintenance prompt, type q, and then press ENTER to gain access to the ntdsutil prompt. Type q, and then press ENTER to quit the Ntdsutil utility.

 

January 19
Welcome to your Blog!

To begin using your site, click Create a Post under Blog Tools.

What is a Blog?

A Blog is a Web site designed to help you share information related to a particular subject area in the form of text, images, links, and other media such as video. Blogs can be used as team sites, news sites, journals, diaries, and more.

Blog posts usually consist of frequent short postings and are typically displayed in reverse chronological order (newest entries first). Blogs encourage site visitors to interact with one another by leaving comments on posts.

Blogs can be also be used as a team communication tool. Keep team members informed by providing a central place for links and relevant news.

 

 About this blog

 
About this blog

This blog is a collection of articles found on the internet during verious installations and deployment.  

We spent time looking for answers, and wanted to save you time in your How To needs.