Category Archives: Microsoft

Microsoft

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.

Exchange 2010 not receiving external mail | Step by step

One quite common problem that administrators might encounter is this:

Scenario: Exchange 2010 environment. The external mails are not being received, and if someone from the organization sends an e-mail to an external receipt it works with no problems.

Cause: Forced reboot / Power down

1. The first step that probably all administrators will do is to check what is happening to those e-mails that are received. Send a test mail from an external e-mail address ( like gmail / yahoo ) to your internal e-mail address, and then go to EMC ( Exchange Management Console ), then click on Toolbox in the right menu, and after that double-click on Message Tracking. A new ie window will appear, and you will be prompted for login. After that go to: search for messages i’ve received from select user / and enter the address from were you made the test. Then click OK.

The search results will appear, and then double click on the test message for details. If the delivery report looks like this, go to step 2:

Delivery Report for Aurel Proorocu

Failed
6/27/2011 10:03
The message couldn’t be delivered.

2. Go to Start services.msc / press enter:

3. After the Services window appears, search for Microsoft Exchange Transport, then right-click on it and select restart.

4. Then after the service is restarted repeat the external mail test and it should be ok.

ENJOY.

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

How to Install Exchange 2010 in Virtual Environment | Step By Step Tutorial

Since the trend is to move more and more from the classical on-premises system to a VM environment, I am going to present today a step-by-step tutorial about how to install Exchange 2010 on a VMWARE Virtual machine ( you can also use this tutorial if you have a Hyper-V Environment ).
The tutorial goes from creating the virtual machine, to installing windows 2008, creating a domain and installing exchange 2010 + post-install setup / updates and test using an windows 7 with Outlook 2010 VM.

This tutorial will show you how to do:
A. Create a virtual machine using VMWARE ( Step 1 )
B. Install Windows Server 2008R2 Enterprise X64 / install WinRar  ( Steps 2-6 )
C. Creating a new domain  ( Steps 7-17 )
D. Installing Exchange 2010 (pre-install / install / post-install )  ( Steps 18-39 )
E. Create a new domain account + an e-mail address for it  ( Steps 40-50 )
F. Install a Windows7 Virtual Machine  ( Step 51 )
G. Join the new machine into the domain  ( Steps 51-53 )
H. Install Office 2010 on it  ( Steps 54-56 )
I. Log with the new user / Install and configure a new Exchange account in Outlook 2010  ( Steps 57-67 )
J. Send a Test e-mail  ( Step 68 )
K. Test the webmail ( OWA 2010 )  ( Step 69 )
*You can use this tutorial for any steps, ex. if you have to join a machine to a domain read the 40-50 Steps

STEPS:

1. Make a new virtual machine, in our example i am going to use 1 processor / 4Gb ram and 100GB HDD space:

2. The operating system i am going to use is Windows Server 2008R2 Enterprise x64. So I start the install:

3.After the install had finished log on:

4. We are going to use a NAT connection for this example, but if you use a Bridged Network Adapter you should configure the IPs ( or skip step if you have DHCP ):

5. Install WinRar, or any other archive software/image player to open the exchange .iso file with. Or skip this step if you have the DVD.

6. Now copy the Exchange 2010 ISO file on desktop, and then right click and extract here:

7. Then go to Server Manager ( Start / Administrative Tools / Server Manager ), and go to Roles, click on Add roles, and select: Active Directory Domain Services, and then NEXT:

8. Then click INSTALL:

9. The ADDS Wizard will start, after that click NEXT:

10. At the next step we will select: Create a new domain in a new forest, because we are installing a standalone server in a new domain. If you already have a domain or a forest select the option that fits you, then click NEXT:

11. Now we have to insert the FQDN, in our case aurelp.com, then we click NEXT:

12. At this step we set the FFL ( Forest Functional Level ), which in our case will be Windows Server 2008R2. But you have to know that the Forest Function Level must be at least “Windows Server 2003″ for Exchange 2010 to work, so if it`s not you have to raise it.

13. At this next step we configure the DC Options, we will select the DNS Server because we have only one server. Depending of your case, you select it or not, and then click NEXT:

14. Here you can configure the Location for the Database / Log / SYSVOL. We will keep the default values, then click NEXT:

15. At this step you configure the AD Services Restore Mode Administrator Password. Insert it, and then click NEXT:

16. We are at the final step of the ADDS Wizard, where we review the selections. Review it and then click NEXT:

17. Now the wizard is going to configure ADDS, select Reboot on completion and go drink a coffee ( in our case it will take 10-12min but in some existing scenarios it might take 1-2hours ).

18. After you rebooted go back to Server Manager ( Start / Administrative Tools / Server Manager ), and go to Roles, click on Add roles, and select: Web Server (IIS) and click NEXT:
*You can select this Role at step 7, i put them separately so we can see the steps.

19. For the IIS Role, select the Services:
– IIS 6 Management Compatibility, and all the services that are under it, then click Install:

20. After the roles are installed reboot the Server. Then go to:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20109
And download 2007 Office System Converter: Microsoft Filter Pack:

21. After the FilterPack64.exe is downloaded, run it. And the install wizard will appear, and we click NEXT:

22. We accept the terms, and click NEXT:

23. After the install we click Ok:

24. The next step is to open the Windows PowerShell ( Start / Administrative Tools / Windows PowerShell Modules ). After it loads we enter the following command:

Set-Service NetTcpPortSharing -StartupType Automatic

*This will change startup mode of “Net.Tcp Port Sharing Service” from Manual to Auto for Client Access Server installation

25. After that, we open the folder that contains the Exchange 2010 installation files, and we click onSetup.exe. After the installer starts, we click on Step3: Choose Exchange language options and then on Install only languages from the DVD.
*We select “Install only languages from the DVD” because we want English, if you want other language chose the other option: “Install all languages from the language bundle” 

26. Then we click on “Step 4: Install Microsoft Exchange” and start the installation:

27. This is the first step of the wizard, we read the introduction and then click NEXT:

28. Now we read & accept the terms and click NEXT:

29. Now we can choose either if we want, or not to send error reporting. I recommend to select Yesbecause this helps Microsoft find bugs and improve the product, and then click NEXT:

30. Here we choose the Installation Type. We will go for a Custom install. Click on it, and then NEXT:

31. Now we select the server roles. In our case we will go for the mailbox role / client access and Hub Transport. But this may vary from case to case. After this chose the folder in which Exchange 2010 will install ( we will keep the default location ). Then click NEXT:

32. At this step we specify the name for the Organization. In our case we put AurelP, and then click NEXT:

33. At this step you should be very careful. If you still have Outlook 2003 or Entourage in your organization select YES. In our case we will use Outlook 2010 so we select No, and then click NEXT:

34. Now we configure the Client Access Server external Domain. This will configure Internal URL and External URL for services of Client Access. In our case it will be: webmail.aurelp.com, and we hit NEXT:

35. Now you can select if you want to join the Customer Experience Improvement Program. We will select “I don`t wish to join the program at this time” and click NEXT:

36. The next step is Readiness Checks, where the installer will check if Exchange is ready to be installed. If you followed the tutorial so far it should like in the next image. However if error occur, they will have instructions of how to fix it. If everything is Ok, click INSTALL:

37. And the last step of the installation is Completion. Here you can see what was successfully installed. When they are all Completed, select Finalize this installation using the Exchange Management Console and click FINISH:

38.Now you will go back to the initial installer screen. Here you should select Step5: Get critical updates for Microsoft Exchange and then follow the update procedure.

39. After that the EMC ( Exachange Management Console ) will start and you will be prompted to license your software.

40. The next thing we are going to do in this tutorial is to create a new user and create an e-mail address for him. For that we go Start and type: dsa.msc and then press Enter. ( or go to Start / Administrative Tools / Active Directory Users and Computers )

41. Here we expand the domain ( in our case aurelp.com ) and then go to the Users OU. ( this may vary from case to case if you already have an AD structure ). Then we right click somewhere in the right side and select New / User.

42. And the User Wizard will start. Complete all the fields with the information of the new user, then click NEXT:

43. At the next step we set the password. Insert it and then select the password options, then click Next:

44. Now the user was created, and we click FINISH:

45. After that, we double click on the newly created user, and the proprieties window will appear. Here we go to Member Of Click on ADD / Type domain in the “Enter the Object names to select” and then clickOK, and in the new list that appears double click on Domain Admins, and after that OK and OK.
*This will make the new user account an domain admin**. If you don`t want to do this skip this step. If you don`t know what a domain admin is:
**Domain Admins – a global group whose members are authorized to administer the domain. By default, the Domain Admins group is a member of the Administrators group on all computers that have joined a domain, including the domain controllers. Domain Admins is the default owner of any object that is created by any member of the group.

46. Now go back to EMC ( Exchange Management Console ), expand Microsoft Exchange ON-Premises, and then under Server Configuration click on Mailbox. Now in the right side menu click on New Mailbox. After that the wizard will appear, select User Mailbox and click NEXT:

47. At the next step select Existing users / ADD, and then search for the user you just created, select it and then press OK and NEXT:

48. At the next step you must select the Alias, that is usually the same as the username. Then you select the mailbox you want to put the new e-mail account in ( if you don`t select, it will auto set thedefault one ).
The next options are for Managed folder mailbox policy ( if you have more then one ), and the Active Sync mailbox policy ( if you also have more then one ).
Select the options that fits you best, then click NEXT:

49. Now the Configuration Summary will be displayed. Review it and click NEW:

50. The last step is the Completion. After you see the Completed status click FINISH:

51. For the next step of the Tutorial we will need a Windows 7 virtual machine that is connected in the same network with the Exchange Server Virtual Machine. We created this using VMWARE and a kit of Windows 7 x64. After the install is ready, log on to the machine and go to Start / right click on MY COMPUTER and select PROPERTIES:

52. Now the System window will appear. Here go to Computer name,domain, and workgroup settings and click on Change Settings. After the System properties appears, click on Change ( on the computer name tab ). Now select domain, and insert the name of your domain ( in our case aurelp.com ) and change the computer name ( if you want ), after that click OK. You will be prompted for credentials. Here insert user: Administrator, and the password you set at the domain wizard ( in our case we could use the aurel.proorocu account because it`s a domain admin, and if you already have a domain use an Domain admin account ).

53. After it completes the following window will pop-up. Click OK:

54. For the next step we will need an Office KIT ( we will use Office 2010 Plus x64 ). Double click on thesetup and the wizard will appear. Enter the Product Key, and click CONTINUE:

55. At the next Step we select what to install. We will go for the typical and click Install now. If you want to customize it click on Customize:

56. After the setup had finished click CLOSE:

57. Now go to START / click on the button next to Shut down and select LOG OFF:

58. Now click on SWITCH USER:
59. Click on Other USER:

60. And insert the credentials of the user you created, then press ENTER:

61. After the windows user loads, go to Start / All Programs / Office / Outlook 2010 :

62. Then the Outlook wizard will appear. Click NEXT:

63. Select YES, and then click NEXT:

64. The Exchange Account should be auto completed, then click NEXT:

65. At the last step click FINISH:

66. Now Outlook will begin to load and will prompt for full name and initials. Insert them and click OK:

67. Select the Use Recommended Settings, and press OK. And you are now Connected to Microsoft Exchange ( right-down ).

68. You can make an e-mail test, and enjoy your new Exchange 2010 Server.

69. You can also check the OWA, using this link: https://nameofserver/owa , where name of server is the computer name of the Exchange 2010 Server ( in our case WIN-9a156e4dejn ).
You will also get an Certificate ErrorI will later explain the Certificates and make an tutorial.

ENJOY.

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

How to add a mail server to whitelist, on exchange 2010 ? Step-By-Step

This is a very common problem…
The client cannot send e-mails to someone in your organization because his e-mail server is on a blacklist, and the mail gets blocked and he receives this message:

host mail.aurelp.com [90.150.150.90] said: 550 5.7.1 :127.0.0.3:Client host 90.180.140.10 blocked using 88.blocklist.zap; Mail from IP banned. To request removal from this list please forward this message to delist.forefront@messaging.microsoft.com (in reply to RCPT TO command)

* Where mail.aurelp.com is your mail server, 90.150.150.90 is your mail server ip address, and 90.180.140.10 is his mail server ip address

Solution:

1. You need to find all the IP Addresses of the mail servers of the user that has the problem. This step is recommended even if he gives you the ip you should enter on the whitelist, because they may havemultiple mail servers.
To check the domain for mail servers, go to www.mxtoolbox.com and enter the domain ( for example: aurelp.com ) in the MX Lookup, then click on the button:

2. Now open the Exchange server and go to the EMC ( Exchange Management Console ). Here expand the Server Configuration menu ( in the left ), and click on Hub Transport. Now click on Anti-Spam tab ( center-middle ), and then double click on IP ALLOW LIST.


3. A new window will appear. Here click on the Allowed Addresses tab, and then click ADD.


4. Here you enter the IP ADDRESS of the mail server that is blacklisted. If they have multiple servers, repeat step 3 and for all of them. After that they should be able to send mails to users in your organization.

upload6

ENJOY.

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

HowTo set mailtips in Exchange 2010 ? Step-by-Step & Advanced

Exchange 2010 brings a new feature that displays an info message when the user wants to send an e-mail. This is very useful for restricted e-mail addresses / unmonitored mailboxes slow-response users or to alert the user that the message size exceeds senders send list / when sending e-mail to  large number of recipients sending e-mails to invalid domains / and more.

upload4

You can set mailtip for:
– mailbox
– distribution group
– dynamic distribution group
 mail contact
– mail enabled folder

In our first example I am going to show you how to set an mailtip for a single mailbox:

1. First Way:
Open Exchange Management Shell and run this command:
Set-Mailbox -identity “aurel.proorocu” -MailTip “Specialist IT”
*Here you replace aurel.proorocu with the alias you want to set the mailtip to, and you replace the Specialist IT with your message.

Second Way:

a. Open and login into ECP ( Exchange Control Panel ) with an account with admin rights, then select“My organization” and after that select Users & Groups from the right menu. Then go on the Mailboxesand search for the account you want to set the mailtip to. After you find it double click on it and move to the next step.

b. In the new window that will appear, click on the Mailtip, and on the box that enlarges enter the mailtipfor that account. After you finish click SAVE:

2. After you had set the mailtip the message will appear in OWA or Outlook, like this:

OWA:

Outlook:
upload5

3. Enjoy your new Mailtip, and read the advanced examples:

ADVANCED EXAMPLES:

1.The command to see the current mailtip configuration on your server:
Get-OrganizationConfig | fl *mailtips*

2. If you want to enable / disable mailtips you can use this command:
ENABLE: Set-OrganizationConfig -MailTipsAllTipsEnabled $true
DISABLE: Set-OrganizationConfig -MailTipsAllTipsEnabled $false 

( *Mailtips are by default enabled )

3. If you want to set the mailtip for large audience ( it would display to the sender if he added more then X recipients in the TO box ), you have to use the following command:
Set-OrganizationConfig -MailTipsLargeAudienceThreshold 10 
( *By default it is 25, you can check your own server using the cmdlet from point 1 )


4.
 You can alert the user that an address is an external one using mailtips. The command is:
ENABLE: Set-OrganizationConfig –MailTipsExternalRecipientsTipsEnabled $True

DISABLE: Set-OrganizationConfig –MailTipsExternalRecipientsTipsEnabled $False

5. You can enable the Mailtips for mailbox data ( Out Of Office and Mailbox FULL Alert ) with the following command:
ENABLE: Set-OrganizationConfig -MailTipsMailboxSourcedTipsEnabled $true
DISABLE: Set-OrganizationConfig -MailTipsMailboxSourcedTipsEnabled $false



6. 
You can configure the Group Metrics ( Group metrics data provides information on the size of distribution groups and dynamic distribution groups. The exchange query many LDAP requests to ActiveDirectory to get group membership information.This could affect the the performance, and ti eliminate this issue Exchange 2010 uses the Group Metric Data which can be set to run during low-activity hours. ).
ENABLE: Set-MailboxServer AURELSERVER -GroupMetricsGenerationEnabled $true
DISABLE: Set-MailboxServer YOURSERVER -GroupMetricsGenerationEnabled $false

ENJOY.

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

Exchange 2010 Network Ports | Complete list

This is very useful to any Administrator, so here it is:

( The credits for the great picture goes to EighTwOne.com )

And the complete PORT LIST:

Transport Servers 
Hub Transport server to Hub Transport server: 25/TCP (SMTP)
Hub Transport server to Edge Transport server: 25/TCP (SMTP)
Edge Transport server to Hub Transport server: 25/TCP (SMTP)
Edge Transport server to Edge Transport server: 25/TCP SMTP
Mailbox server to Hub Transport server via the Microsoft Exchange Mail Submission Service:135/TCP (RPC)
Hub Transport to Mailbox server via MAPI: 135/TCP (RPC)
Unified Messaging server to Hub Transport server: 25/TCP (SMTP)
Microsoft Exchange EdgeSync service from Hub Transport server to Edge Transport server:50636/TCP (SSL)
Active Directory access from Hub Transport server: 389/TCP/UDP (LDAP), 3268/TCP (LDAP GC), 88/TCP/UDP (Kerberos), 53/TCP/UDP (DNS), 135/TCP (RPC netlogon)
Active Directory Rights Management Services (AD RMS) access from Hub Transport server:443/TCP (HTTPS)
SMTP clients to Hub Transport server: 587 (SMTP) / 25/TCP (SMTP)

Mailbox Servers

Active Directory access: 389/TCP/UDP (LDAP), 3268/TCP (LDAP GC), 88/TCP/UDP (Kerberos), 53/TCP/UDP (DNS), 135/TCP (RPC netlogon)
Admin remote access (Remote Registry): 135/TCP (RPC)
Admin remote access (SMB/File): 445/TCP (SMB)
Availability Web service (Client Access to Mailbox): 135/TCP (RPC)
Clustering: 135/TCP (RPC)
Content indexing: 135/TCP (RPC)
Log shipping: 64327 (customizable)
Seeding: 64327 (customizable)
Volume shadow copy service (VSS) backup: Local Message Block (SMB)
Mailbox Assistants: 135/TCP (RPC)
MAPI access: 135/TCP (RPC)
Microsoft Exchange Active Directory Topology service access: 135/TCP (RPC)
Microsoft Exchange System Attendant service legacy access (Listen to requests): 135/TCP (RPC)
Microsoft Exchange System Attendant service legacy access to Active Directory: 389/TCP/UDP (LDAP), 3268/TCP (LDAP GC), 88/TCP/UDP (Kerberos), 53/TCP/UDP (DNS), 135/TCP (RPC netlogon)
Microsoft Exchange System Attendant service legacy access (As MAPI client) 135/TCP (RPC)
Offline address book (OAB) accessing Active Directory: 135/TCP (RPC)
Recipient update to Active Directory: 389/TCP/UDP (LDAP), 3268/TCP (LDAP GC), 88/TCP/UDP (Kerberos), 53/TCP/UDP (DNS), 135/TCP (RPC netlogon)

Client Access Servers

Active Directory access: 389/TCP/UDP (LDAP), 3268/TCP (LDAP GC), 88/TCP/UDP (Kerberos), 53/TCP/UDP (DNS), 135/TCP (RPC netlogon)
Autodiscover service: 80/TCP, 443/TCP (SSL)
Availability service: 80/TCP, 443/TCP (SSL)
Outlook accessing OAB: 80/TCP, 443/TCP (SSL)
Outlook Web App: 80/TCP, 443/TCP (SSL)
POP3: 110/TCP (TLS), 995/TCP (SSL)
IMAP4: 143/TCP (TLS), 993/TCP (SSL)
Outlook Anywhere (formerly known as RPC over HTTP ): 80/TCP, 443/TCP (SSL)
Exchange ActiveSync application: 80/TCP, 443/TCP (SSL)
Client Access server to Unified Messaging server: 5060/TCP, 5061/TCP, 5062/TCP, a dynamic port
Client Access server to a Mailbox server that is running an earlier version of Exchange Server:80/TCP, 443/TCP (SSL)
Client Access server to Exchange 2010 Mailbox server: RPC
Client Access server to Client Access server (Exchange ActiveSync): 80/TCP, 443/TCP (SSL)
Client Access server to Client Access server (Outlook Web Access): 80/TCP, 443/TCP (HTTPS)
Client Access server to Client Access server (Exchange Web Services): 443/TCP (HTTPS)
Client Access server to Client Access server (POP3): 995 (SSL)
Client Access server to Client Access server (IMAP4): 993 (SSL)
Office Communications Server access to Client Access server: 5075-5077/TCP

Unified Messaging server data paths

Active Directory access: 389/TCP/UDP (LDAP), 3268/TCP (LDAP GC), 88/TCP/UDP (Kerberos), 53/TCP/UDP (DNS), 135/TCP (RPC netlogon)
Unified Messaging Phone interaction (IP PBX/VoIP Gateway): 5060/TCP , 5065/TCP, 5067/TCP (unsecured), 5061/TCP, 5066/TCP, 5068/TCP (secured), a dynamic port from the range 16000-17000/TCP (control), dynamic UDP ports from the range 1024-65535/UDP (RTP)
Unified Messaging Web Service: 80/TCP, 443/TCP (SSL)
Unified Messaging server to Client Access server: 5075, 5076, 5077 (TCP)
Unified Messaging server to Client Access server (Play on Phone): Dynamic RPC
Unified Messaging server to Hub Transport server: 25/TCP (TLS)
Unified Messaging server to Mailbox server: 135/TCP (RPC)

If you encounter any problems feel free to comment contact me

How to automatically add e-mail signature ? Exchange 2010 Step-by-Step

Exchange 2010 offers the option to set an automatic e-mail signature to all users, customized with theinformation from Active Directory.

This is very useful in large environments such as enterprises because:
1. The users doesn`t have to set his own signature, so everybody has the same unique brand signature. And they cannot modify it.
2. If you are using an image in the signature that has 5-20KB it will generate a lot of volume ( for 100.000 mails each day it generates an extra space of approx. 2000MB / day ).
3. You have the centralized control of the signatures, so you can easily modify the template and/or content.

So here is the Step-by-Step tutorial to do that:

1. Go to the Exchange Server, and open the Exchange Management Console.
Then go to Organization Configuration, then on the Hub Transport, and then to the Transport Rules Tab:

upload3

2. Then click on the New Transport Rule, in the Actions Menu right ):

3. Then the New Transport Rule Window will appear. Here you set a name for the new Rule, and a comment for later identification, then click NEXT:

4. Select the Conditions for the rule ( by default i will check those ):
From users that are inside or outside the organization
Sent to users that are inside or outside the organization, or partners
If you need to check any other conditions, check the ones that apply to your case, then click NEXT:

5. In the next window we select the actions.
By default i will check: Append disclaimer text and fallback to action if unable to apply.
Then click on the Disclaimer Text to set the Signature code.

6. In the little window that appears you must enter the code for the signature.

Here are a two templates:
Template 1
%%Firstname%% %%Lastname%%<br>
%%Title%%<br>
%%Company%%<br>
Phone: %%Phonenumber%%<br>
Mobile: %%Mobilenumber%%<br>
Faxnumber: %%Faxnumber%%<br>

Template 2
Regards,<br>
%%displayName%%<br>
%%Title%% | %%Department%%
Phone: %%Phone%%

But you can compose your own using HTML, and the commands to import data from ActiveDirectory:
Department -> %%Department%%
Display Name -> %%displayName%%
First Name -> %%FirstName%%
Last Name -> %%LastName%%
Business Phone -> %%Phone%%
Title -> %%Title%%
Fax -> %%Fax%%
Manager -> %%Manager%%

To import an image you can use the HTML code:
<img src=”http://domain.com/image_test.jpg”>

After you are finished click OK, then NEXT:

7. Here you can add some exceptions if you want, if not click NEXT:

8. And now the final Step were you can review your Summary, and click NEW:

9. After the NEW Transport Rule is made you can test your new Enterprise Signature:

10. Don`t forget to do an GPO to disable the Outlook Signatures, or to instruct the users to not use the Signatures to avoid double ones   .

ENJOY.

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

How to configure a shared mailbox in Exchange 2010 ? Step-by-Step

This is probably one of the most-wanted tutorial for junior administrators of Exchange 2010 all-around the world… So here it is: How to configure a shared mailbox in Exchange 2010 the Step-by-step version:

1. Open the Exchange Server Management Console, then go to Recipient Configuration, and click beneath that on the Mailbox Section, after the section loads, click on New Mailbox ( from the right side panel ).

2. At this step you select the type of mailbox you want to create. Usually it is User Mailbox, so this is the option that we will use in this tutorial, then click Next.

If you are new to this, here is a little wiki about what each option is used for:
User mailbox: This is a traditional mailbox.

Room mailbox: This is a mailbox specifically assigned to Meeting Rooms. Its associated user account will be disabled in Active Directory.

Equipment mailbox: This is a mailbox specific to resources, (i.e. TV, Projector and so on). As with a Resource mailbox, this kind of mailbox will disable a user in Active Directory.

Linked Mailbox: This kind of mailbox will be used in environments with multiple forests.

3. Here you can select a New User mailbox, or if the user is already created select Existing users, then click next:

4. If the user is new, you will be prompted to complete the user-details, insert them and then click next:

5. At the next step you must select the Alias, that is usually the same as the username. Then you select the mailbox you want to put the new e-mail account in ( if you don`t select, it will auto set the default one ).
The next options are for Managed folder mailbox policy ( if you have more then one ), and the Active Sync mailbox policy ( if you also have more then one ).
Select the options that fits you best, then click next:


6. This is the final step of creating a new mailbox. After you see the Completed status you can clickFinish.


7. After you created the mailbox, go back to Recipient Configuration / Mailbox and find the newly created one and right click on it, and select the Manage Full Access Permission option.

8. new window will appear, and here you add the users that you grant permissions to this newmailbox. You can add users and/or groups.  When you finished setting the permissions, clickManage.

upload
9. After this, you can close the Exchange Server and go to the users that will use the shared mailbox. Here you open Outlook ( our tutorial will be based on Outlook 2010 ), go to File tab / Info / Account Settings, and click on the Account Settings Section.

10. Here go to the E-mail tab, select the Exchange account, and then click on the Change button:

11. A new window will appear, and here click on More Settings:

12. In the new window that appears, select the Advanced Tab, then click Add, and insert theSharedMailbox Alias, then click Ok :

13. After that, click Ok again:

14. And now you can view the newly configured SharedMailbox in Outlook:

upload2

Enjoy your new SharedMailbox.

If you encounter any problems feel free to comment contact me