Monthly Archives: January 2013

How to Configure Storage Quotas in Exchange 2010 ?

In exchange 2010 the quotas can be either set for the entire ExchangeDB, or per mailbox.
Atention ! If you set a quota on the DB, and then you set a quota on the mailbox, the mailbox setting will override the DB setting.

A. How to set a storage QUOTE for a Exchange Database, using EMC ( Exchange Management Console ):

1. Open the EMC, then expand the Organization Configuration / Mailbox, then go to Database Management tab. After that, right click on the database you want to change the quote to, and selectProperties.

2. In the properties window, go to Limits Tab, and change the Issue warning / Prohibit send / Prohibit send and receive according to your needs. Then click OK, and you`re done.

B. How to set a storage QUOTE for a specific user, using EMC (Exchange Management Console):

1. Open the EMC, then expand the Recipient Configuration / Mailbox, and then click on the desired mailbox you want to change the quote to, and then either right click / Properties or click on propertiesfrom the right menu.

2. In the Properties window go to Mailbox Settings tab, click on Storage Quotas and thenProperties:

3. In the storage quotas window deselect the Use mailbox database defaults, and then set your desired values for Issue Warning / Prohibit send at / Prohibit send and receive at. Then click OK / OK. And you`re all set up.

ENJOY.

And if you encounter any problems feel free to comment / contact me.

Solved | An error caused a change in the current set of domain controllers – Exchange 2010

One of our administrators was facing some weird errors in the EMC and came to me for support. He showed me the errors bellow, and i knew them because this is quite common in Exchange 2010.
In our case this issue was caused by a recent demotion of a Domain Controller, and however the configuration of Exchange 2010 was updated the errors occurred.

Errors:

An error caused a change in the current set of domain controllers. It was running the command ‘Get-Mailbox – Identity ” -ReadFromDomainController’.
An error caused a change in the current set of domain controllers. It was running the command ‘Get-Recipient -PropertySet ConsoleLargeSet -ResultSize ’1000′ -SortBy DisplayName -RecipientType ‘DynamicDistributionGroup’,’UserMailbox’,’MailContact’,’MailUser’,’MailUniversalDistributionGroup’,’
MailUniversalSecurityGroup’,’MailNonUniversalGroup”.


Solution:

1. Close the EMC
2. Go to c:\users\<the user with problem>\appdata\roaming\microsoft\mmc\ and delete or rename the file Exchange Management Console.
3. After this restart the EMC ( no reboot of the server is necessary ).



ENJOY.

And if you encounter any problems feel free to comment / contact me.

 

Export-Mailbox and Import-Mailbox commands not recognized | Powershell | Exchange 2010

This is one topic that i faced when Exchange 2010 was released…

So for the Export-Mailbox and Import-Mailbox commands to work, you have to enable them:

1. Open EMS ( Exchange Management Shell ), and check if you have the Exchange Server Admin Tasks installed by running this command:

Get-PSSnapin

2. In most of the cases you will not find it in the list so you have to run the next command:

Get-PSSnapin -registered

3. Now you have to install Admin Tasks for the Exchange Server, by running the command:

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010

4. After you ran those commands, you can enjoy the Export-Mailbox / Import-Mailbox:

ENJOY.

And if you encounter any problems feel free to comment / contact me.

How to add a Second Domain with E-mail Address Policy on Exchange 2010

One of the administrators came with an request from one of the managers… to add a new domain on the exchange server so he can have configured on his outlook the account: manager@newdomain.com.

Ok, so now we have to do this scenario:
New domain: aurelpro.com
We need to make the address: manager@aurelpro.com

1. Buy the new domain name. In our example we will use the 1and1 website to buy www.aurelpro.com

2. After the domain is active, we have to set the MX Records ( In our case the 1and1 admin panel ):

3. Then open Exchange 2010 Management Console, and go to Organization Configuration / Hub Transport and then to the Accepted Domains tab and right click on the white section and select New Accepted Domain:

4. The New Accepted Domain Wizard will appear. Here we set the:
Name ( to help you identify the domain in the list )
Accepted domain ( The domain name, in our case: aurelpro.com )
Authoritative Domain ( if you want to deliver the e-mails to this domain, used in our example )
When ready press NEW:

5. In the next screen review the changes and press FINISH:

6. The next step is to create an e-mail address policy, so that every user from the IT Department ( in our case scenario ) will have an @aurelpro.com e-mail address.
*If you want to manually add a new e-mail address go directly to STEP 13 !

So we go to the EMC ( Exchange Management Console ) / Organization Configuration / Hub transport/ E-mail Address Policies Tab / right click on the white zone and select New E-mail Address Policy:

7. The wizard will appear, and here we select:
Name ( the name of the new policy, so we can identify it in the list )
Recipient Container ( the OU that will use the policy, in our case: the whole aurelp.com domain )
All recipient types ( you can select specific users type, depending of you scenario )
After completing click NEXT:

8. On the next step we select the conditions for our policy. In our case it will be for the Recipients in a Department ( IT ). Select the conditions that fits your case and click NEXT:
*The department has to be filled for the users AD objects for the condition to work !


9. In the next step we have to enter the e-mail addresses. Click on the ADD button and then select thetype you want ( in our case First name.last name -> aurel.proorocu@aurelpro.com ), and specify theFQDN for the e-mail address ( in our case: aurelpro.com ). Then click OK and NEXT:

10. Now we have to set the Schedule. We will run this policy Immediately, but you can custom it to fit your scenario. Then click NEXT:

11. In the final step we review the configuration. Review it and click NEW:

12. After the Completed status appear we can click FINISH, and enjoy your new policy for the new domain:

13. Skip this step and 14 if you made the policy ! If you want to manually create a new SMTP address,open EMC ( Exchange Management Console ) and go to Recipient Configuration / Mailbox / Right clickon the user you want to add the new address to / select Proprieties:

14. Then go to the E-mail Addresses tab and click on ADD. Now insert the new alias for the user ( in our case aurel.proorocu@aurepro.com ). Then click OK / OK:

15. The final step is to test that the new domain e-mail server works. Go to www.mxtoolbox.com / MX lookup and enter the command: “mx:aurelpro.com” ( *replace aurelpro.com with your domain ) and click on Lookup.
If the e-mail servers appear then the MX records work and you can proceed in sending one incoming and one outgoing e-mail from the new domain addresses. If that also succeds then you can enjoy your new domain e-mail addresses !



ENJOY.

And if you encounter any problems feel free to comment / contact me.

How to Send As and Send on Behalf Of in OWA 2010

If you need to configure Send As or Send on Behalf in Exchange 2010 read this post:https://www.aurelp.com/?p=369

 

If you already have the permissions follow this tutorial to make the configuration in OWA 2010:

1. In the first step we will enable the BCC and From fields, that are by default hidden in Owa 2010.
Open OWA 2010 in your browser, log in, and after that go to Options / Settings / Mail, and scroll down to Message Format and select: Always show BCC and Always show From:

2. Make a new e-mail, and if you can see From field ( if not repeat step 1 ) click on it and select
“Other e-mail address…” and select the account you have the Send-As or Send on Behalf of permission:

3. Send the e-mail. If it succeeds then your mail would look like this ( in the Sent items folder ):
( In our scenario Test send a mail on behalf of Aurel Proorocu )

4. If you get the error: ‘You don`t have the permissions required to send messages from this mailbox’ , you should check if you selected the account you have rights, and if it`s ok you should see if you really have permissions over that mailbox ( check this post regarding Exchange 2010 howto: https://www.aurelp.com/?p=369 )


ENJOY.

And if you encounter any problems feel free to comment / contact me.

 

Delegate user access to mailbox with Add-ADPermission | Using Exchange Shell

The first step is to check the actual permissions of the user.

1. Open EMS ( Exchange Management Shell ) and insert the command:
Get-Mailboxdatabase | get-ADPermission -User aurel.proorocu
*Replace aurel.proorocu with the user you want to check

This will show if the user doesn’t have rights:

This will show if the user have rights:

2. Run one of the following cmdlets:

Get-Mailboxdatabase | Add-ADPermission -User aurel.proorocu -AccessRights ExtendedRight -ExtendedRights receive-as, send-as
*Replace aurel.proorocu with the user you want to grant access to

Get-Mailboxdatabase | Add-ADPermission -User aurel.proorocu -AccessRights ExtendedRight -ExtendedRights ms-exch-store-admin, receive-as, send-as
*Replace aurel.proorocu with the user you want to grant access to


ENJOY.

And if you encounter any problems feel free to comment / contact me.

How to Send on behalf / Send as in Exchange 2010

Send on behalf and Send as are quite similar.

Send on behalf will permit a user to send e-mails as another user, but it will show that it was send by administrator@aurelp.com on behalf of aurel.proorocu@aurelp.com ( the case in this example ).

Send as will give a user ( administrator@aurelp.com ) the permission to send mail as another user ( aurel.proorocu@aurelp.com ). In this case the recipient will see only aurel@aurelp.com in the from field. He will never know that X send that e-mail

A. Send on Behalf
There are 3 ways to accomplish this ( using Outlook Delegates / using Exchange Management Shell / using Exchange Management Console )

a. Using Outlook Delegates

1. Open Outlook 2010, go to File Tab / Info / click on Account Settings / select Delegate Access from the drop down menu:

2. On the delegates window, click ADD :

3. Select the user you want to delegate access to, and click OK:

4. At the next step you delegate the permissions to the user. To give the user Send on behalf rights, you ahve to select Editor or Author in the Tasks section.
If you need to give other special rights select them, and then click OK:
upload18

5. At the final step select if you want to receive a copy of meeting requests and responses. Then click OK:

b. Using Exchange Management Console

1. Open EMC ( Exchange Management Console ), then expand Microsoft Exchange / Recipient Configuration / Mailbox. Then right click on the user that you want to grand access to and selectProprieties:


2. Then go to Mail Flow Settings tab / Click on Delivery Options / And in the Delivery Options window click on ADD and select the user you want to give rights to send on behalf. Then click OK / OK :

c. Using Exchange Management Shell

1. Open EMS ( Exchange Management Shell ) and insert the following command:

Set-Mailbox aurel.proorocu -GrantSendOnBehalfTo Administrator

*replace aurel.proorocu with the user that will share his mailbox
**replace administrator with the user that will send on behalf

B. Send As
As we know from Exchange 2007 there are 2 ways to accomplish this ( using Exchange Management Shell / using Exchange Management Console ):

a. Using Exchange Management Console

1. Open EMC ( Exchange Management Console ), then expand Microsoft Exchange / Recipient Configuration / Mailbox. Then right click on the user that you want to grand access to, and click Manage Send As Permission:

2. Click ADD and select the user you want to grant Send As Permission, then click Manage:

b. Using Exchange Management Shell

1. Open EMS ( Exchange Management Shell ) and insert the following command:

Add-ADPermission -Identity “Administrator” -User aurel.proorocu -AccessRights ExtendedRight -ExtendedRights “send as”

*replace administrator with the identity of the user that will share his mailbox
**replace aurel.proorocu with the user that will send AS

ENJOY.

And if you encounter any problems feel free to comment / contact me.

Exchange 2010 Windows Services Explained

Microsoft Exchange Active Directory Topology – Provides Active Directory topology information to Exchange services. If this service is stopped, most Exchange services are unable to start. This service has no dependencies. ( Default startup type: Automatic )

Microsoft Exchange ADAM – Stores configuration data and recipient data on the Edge Transport server. This service represents the named instance of Active Directory Lightweight Directory Service (AD LDS) that’s automatically created by Setup during Edge Transport server installation. This service is dependent upon the COM+ Event System service. ( Default startup type: Automatic )

Microsoft Exchange Address Book – Manages client address book connections. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Automatic)

Microsoft Exchange Anti-spam Update – Provides the Microsoft Forefront Protection 2010 for Exchange Server anti-spam update service. On Hub Transport servers, this service is dependent upon the Microsoft Exchange Active Directory Topology service. On Edge Transport servers, this service is dependent upon the Microsoft Exchange ADAM service. ( Default startup type: Automatic )

Microsoft Exchange Credential Service – Monitors credential changes in AD LDS and installs the changes on the Edge Transport server. This service is dependent upon the Microsoft Exchange ADAM service. ( Default startup type: Automatic )

Microsoft Exchange EdgeSync – Connects to an AD LDS instance on subscribed Edge Transport servers over a secure LDAP channel to synchronize data between a Hub Transport server and an Edge Transport server. This service is dependent upon the Microsoft Exchange Active Directory Topology service. If Edge Subscription isn’t configured, this service can be disabled. ( Default startup type: Automatic )

Microsoft Exchange File Distribution – Distributes offline address book (OAB) and custom Unified Messaging prompts. This service is dependent upon the Microsoft Exchange Active Directory Topology and Workstation services. ( Default startup type: Automatic )

Microsoft Exchange Forms-Based Authentication – Provides forms-based authentication to Microsoft Office Outlook Web App and the Exchange Control Panel. If this service is stopped, Outlook Web App and the Exchange Control Panel won’t authenticate users. This service has no dependencies. ( Default startup type: Automatic )

Microsoft Exchange IMAP4 – Provides IMAP4 service to clients. If this service is stopped, clients won’t be able to connect to this computer using the IMAP4 protocol. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Manual )

Microsoft Exchange Information Store – Manages the Exchange Information Store. This includes mailbox databases and public folder databases. If this service is stopped, mailbox databases and public folder databases on this computer are unavailable. If this service is disabled, any services that explicitly depend on it will fail to start. This service is dependent on the RPC, Server, Windows Event Log, and Workstation services. ( Default startup type: Automatic )

Microsoft Exchange Mail Submission Service – Submits messages from the Mailbox server to Exchange 2010 Hub Transport servers. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Automatic )

Microsoft Exchange Mailbox Assistants – Performs background processing of mailboxes in the Exchange store. This service is dependent upon the Microsoft Exchange Active Directory Topology service.
Microsoft Exchange Mailbox Replication Service – Processes mailbox moves and move requests. This service is dependent upon the Microsoft Exchange Active Directory Topology and Net.Tcp Port Sharing service.
Microsoft Exchange Monitoring – Allows applications to call the Exchange diagnostic cmdlets. This service has no dependencies. ( Default startup type: Automatic )

Microsoft Exchange Monitoring – Allows applications to call the Exchange diagnostic cmdlets. This service has no dependencies. ( Default startup type: Manual )

Microsoft Exchange POP3 – Provides POP3 service to clients. If this service is stopped, clients can’t connect to this computer using the POP3 protocol. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Manual )

Microsoft Exchange Protected Service Host – Provides a host for several Exchange services that must be protected from other services. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Automatic )

Microsoft Exchange Replication Service – Provides replication functionality for mailbox databases on Mailbox servers in a database availability group (DAG). This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Automatic )

Microsoft Exchange RPC Client Access – Manages client RPC connections for Exchange. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Automatic)

Microsoft Exchange Search Indexer – Drives indexing of mailbox content, which improves the performance of content search. This service is dependent upon the Microsoft Exchange Active Directory Topology and Microsoft Search (Exchange Server) services. ( Default startup type: Automatic )

Microsoft Exchange Server Extension for Windows Server Backup – Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange. This service has no dependencies. ( Default startup type: Manual )

Microsoft Exchange Service Host – Provides a host for several Exchange services. On internal server roles, this service is dependent upon the Microsoft Exchange Active Directory Topology service. On Edge Transport servers, this service is dependent upon the Microsoft Exchange ADAM service. ( Default startup type: Automatic )

Microsoft Exchange Speech Engine – Provides speech processing services for Unified Messaging. This service is dependent upon the Windows Management Instrumentation (WMI) service. ( Default startup type:Automatic )

Microsoft Exchange System Attendant – Forwards directory lookups to a global catalog server for legacy Outlook clients, generates e-mail addresses and OABs, updates free/busy information for legacy clients, and maintains permissions and group memberships for the server. If this service is disabled, any services that explicitly depend on it will fail to start. This service is dependent on the RPC, Server, Windows Event Log, and Workstation services. ( Default startup type: Automatic )

Microsoft Exchange Throttling – Limits the rate of user operations. This service is dependent upon the Microsoft Exchange Active Directory Topology service. ( Default startup type: Automatic )

Microsoft Exchange Transport – Provides SMTP server and transport stack. On Hub Transport servers, this service is dependent upon the Microsoft Exchange Active Directory Topology service. On Edge Transport servers, this service is dependent upon the Microsoft Exchange ADAM service. ( Default startup type:Automatic )

Microsoft Exchange Transport Log Search – Provides remote search capability for Microsoft Exchange Transport log files. On Hub Transport servers, this service is dependent upon the Microsoft Exchange Active Directory Topology service. On Edge Transport servers, this service is dependent upon the Microsoft Exchange ADAM service. ( Default startup type: Automatic )

Microsoft Exchange Unified Messaging – Enables Microsoft Exchange Unified Messaging features. This allows voice and fax messages to be stored in Exchange and gives users telephone access to e-mail, voice mail, calendar, contacts, or an auto attendant. If this service is stopped, Unified Messaging isn’t available. This service is dependent upon the Microsoft Exchange Active Directory Topology and the Microsoft Exchange Speech Engine service. ( Default startup type: Automatic )

Microsoft Search (Exchange Server) – This is a Microsoft Exchange-customized version of Microsoft Search. This service is dependent on the RPC service. ( Default startup type: Manual )

ENJOY.

And if you encounter any problems feel free to comment / contact me.

How To Configure Receive Connectors in Exchange 2010 | Step By Step

This tutorial is useful for the post-install setup of Exchange 2010.

After you set the Send Connectors and publish the MX records in DNS ( so that other email systems can find the server ) you have to configure the Exchange Server to receive e-mails.
The Hub Transport Server in Exchange is configured by default to not allow other systems to send emails to it. This default configuration is made to encourage the Edge Transport Servers to be set up for receiving mail, because it has a lot of security features that should be used in all organizations.

But, if you have an fresh install, and plan to use an Exchange Server without an Edge Transport you have to change the permissions on the receive connector for the Hub transport servers, using the tutorial bellow:

A. Configure Receive Connector Permissions Using the EMC ( Exchange Management Console )

1. Open EMC ( Start / All Programs / Microsoft Exchange Server 2010 / Exchange Management Console ):

2. Expand Server Configuration ( from the left menu ), and click on Hub Transport. Then right click on the Default Receive Connector, and select Proprieties:

3. After the Proprieties box appears go to Permission Groups Tab, and select Anonymous users, then click OK:

And now the Receive connector is ready to receive e-mails from other Mail Systems.


B. Configure Receive Connector Permissions Using Exchange Management Shell


1. Open Exchange Management Shell ( Start / All Programs / Microsoft Exchange Server 2010 / Exchange Management Shell )

2. Run the following command:

Get-ReceiveConnector “Default WIN-9A156E4DEJN” | Set-ReceiveConnector -PermissionGroups AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers

*Replace
WIN-9A156E4DEJN -> with the name of you server

ENJOY.

And if you encounter any problems feel free to comment / contact me.

How to create a send connector in Exchange 2010 ? Step by Step

At least one send connector must be set up, to ensure that the Exchange 2010 Server knows how to route the outgoing mail requests.
In this example we will create one send connector for the Hub Transport server that will route ALL the outgoing messages. The Hub Transport server will use DNS along with public MX records that were published by other mail servers.

A. Create a Send Connector using the EMC ( Exchange Management Console )

1. Open EMC ( Start / All Programs / Microsoft Exchange Server 2010 / Exchange Management Console ):
upload7

2. Click on Organization Configuration to expand, then click on Hub Transport. Now go to Send Connectors tab, and the right click on the white space and select New Send Connector ( like in the screenshot below ) or click on New Send Connector in the right pane.

3. The wizard launches, and at the first step we must select the Name and the intended use for the Send Connector ( chose the one that fits you best ):
upload8

*More info about intended use for the Send Connector options: 
Custom Select this option to create a customized connector to connect with systems that aren’t servers running Exchange 2010.
Internal Internal Send connectors send e-mail to servers in your Exchange organization. This connector is configured to route e-mail to your internal Exchange servers as smart hosts.
Internet Internet Send connectors send e-mail to the Internet. This connector is configured to use Domain Name System (DNS) MX records to route e-mail.
Partner Partner Send connectors send e-mail to partner domains. This connector is configured to only allow connections to servers that authenticate with Transport Layer Security (TLS) certificates for SMTP domains included in the list of domain-secured domains. You can add domains to this list by using theTLSSendDomainSecureList parameter in the Set-TransportConfig command.
4. At the next step we specify the address space(s) on which the connector will route mail. Click on ADD, and then select the Address. In our case we will use * and we check the include all subdomains.

*More info about this step: 
a. A “*” in the Address indicates that this connector will route all domains that do not match the internal organization’s list of accepted domains.
“Domain.com” in the address indicates that this connector is dedicated to sending email to domain.com addresses.
b. “*.aurelp.com” in the address space indicates that this connector is used for sending email to recipients in aurelp.com and any sub-domains.
c. Cost is used to set the priority of this connector, used when two or more connectors are configured for the same address space. The lower the cost higher the priority.
d. A Scoped Send connector identifies which Hub Transport servers can use this connector. Send connectors are objects stored in Active Directory and, as they are also an organization configuration object, can normally be used by any Hub Transport servers in the organization. If you want to restrict the scope of the Send connector, so as to limit its use to just within the AD site of the Hub server it was created on, then this option needs to be checked.

5. After you configure the Address space, click NEXT:
upload9
6. At the Network Settings step we will chose the first option then click NEXT.
upload10

*More info about this step:

Route mails though to one or more smart hosts:
The option to use Domain Name System MX records to route email automatically should be taken when you want your Send connector to talk directly with the destination SMTP server’s gateway and deliver the emails to that destination gateway itself. You need to make sure that DNS is properly configured for the server to resolve the Destination MX Records.
Alternatively, if you select the route mail through the following smart hosts option, you will need to supply one or more IP addresses or the FQDN of the smart host which is going to accept the email from this connector. Obviously, you need to make sure that the smart host is capable of delivering emails to the destination SMTP server.

The options available for control authentication with the smart host servers are:
None: The smart host does not require any authentication, and it accepts anonymous connections.
Basic Authentication: You will need to provide the smart host with an appropriate username and password to authenticate the connection. If you have multiple smart hosts, then you will need to make sure that they all allow access to the same username and password. Basic Authentication sends the credentials as plain text, and checking Basic authentication Over TLS will enable encryption on the communication.
Exchange Server Authentication: This option authenticates the connection to a smart host using an Exchange authentication mechanism, such as TLS direct trust or TLS\Kerberos.
Externally Secured: Select this option if the connection to the smart host is secured by external means, such as being physically secured over a private network or secured using Internet Protocol security (IPsec).

7. At the next step we set the source server. Ensure that the correct one is selected ( Adding only required servers helps to ensure that only specific servers are able to participate in email delivery to the Internet or other partner networks. ), then click NEXT:

upload11

8. At the final step we review the summary. When ready click NEW:
upload12

9. After the Completed status appears, you can click Finish:
upload13

10. And now the new Connector will be ENABLED in the Send Connectors Tab:
upload14

B. Create a Send Connector using the Exchange Management Shell

Info: We will create a Send Connector who will route mail through the smart hosts ( 192.168.0.2 and 192.168.0.3 ) with the Authentication: None.

1. Open Exchange Management Shell ( Start / All Programs / Microsoft Exchange Server 2010 / Exchange Management Shell )
upload15

2. Run the following command:

New-SendConnector -Name `AurelP.com’ -Usage `Custom’ -AddressSpaces `SMTP:*;1′ -IsScopedConnect or $false -DNSRoutingEnabled $false -SmartHosts `[192.168.0.2]`,’[192.168.0.3]` -SmartHostAuthMechanism `None’ -UseExternalDNSServersEnabled $false -SourceTransportServers `WIN-9A156E4DEJN’

*replace 
AurelP.com with the name you want to set for your new connector.
192.168.0.2 and 192.168.0.3 with the smart host servers you want to use
WIN-9A156E4DEJN with the name of the Source Transport Server

*SmartHostAuthMechanism `None’ -> None is the authentication for the smart host.

upload16

3. After the shell command had been run, the new connector will also appear in the Send Connectors Tab in the EMC.

upload17
4. If you want to check the setup of one connector, you can use the Sendconnector cmdlet:

Get-sendconnector “Aurelp.com”

*replace 
AurelP.com with the name of the connector you want to check.

ENJOY.

And if you encounter any problems feel free to comment / contact me.