 | jmmelkon on Robocopy ERROR 5 (0x00000005)… |
 | Jake on AGDLP (Accounts, Global groups… |
 | ShineOn on Robocopy ERROR 5 (0x00000005)… |
 | Lauren on Creating a Reverse Lookup Zone… |
 | thejas on Robocopy ERROR 5 (0x00000005)… |
Ignited RSS
The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.
Here’s an excerpt:
The concert hall at the Syndey Opera House holds 2,700 people. This blog was viewed about 10,000 times in 2011. If it were a concert at Sydney Opera House, it would take about 4 sold-out performances for that many people to see it.
Exchange Server 2003 comes with a set of four Internet protocol services. These let you extend the reach of Exchange users beyond Microsoft’s very good, but proprietary, electronic messaging protocol MAPI. The four services are Hypertext Transmission Protocol (HTTP), which supports Outlook Web Access (OWA); Post Office Protocol (POP3); Internet Message Access Protocol (IMAP4); and Network News Transfer Protocol (NNTP):
HTTP: HTTP is the core protocol that supports web access. OWA uses the HTTP protocol to give users access to everything in their Exchange mailboxes, as well as items in public folders, using a web browser such as Microsoft Internet Explorer. On the server side, OWA is supported by Windows Server 2003s Internet Information Server.
POP3 Server: Exchange Servers POP3 server gives users with standard POP3 e−mail clients, such as Eudora or Outlook Express, limited access to their Exchange mailboxes. Users can download mail from their Exchange Inboxes, but that’s all. Users have no direct access to other personal or public information stores or to their schedules. This is due to limitations in the POP3 protocol itself, not in Microsoft’s implementation of the protocol.
IMAP4 Server: The Exchange IMAP4 server goes one better than POP3, adding access to folders in addition to the Exchange Inbox. With IMAP4, folders and their contents can remain on the Exchange server, be downloaded to the computer running your IMAP4 client, or both. You can keep Exchange Server based folders and their contents in sync with the folders on an IMAP4 client.
NNTP Server: The NNTP server lets you bring all those exciting Usenet newsgroups into your Exchange servers public folders, where your users can read and respond to them with the same e− mail clients that they use to read other public folders.
EF stands for “Education First”. Founded in 1965 by entrepreneur Bertil Hult, EF is a privately-held company with 16 divisions that offer a range of educational programs from language training, educational travel, and academic degrees to cultural exchanges. With a mission to break down barriers in language, culture and geography, EF has helped people of all ages and nationalities become citizens of the world.
From Berlin to Beijing, Moscow to Mexico City, Dubai to Denver, EF operates 400 schools and offices in over 50 countries. EF’s global network includes 9,000 staff and 25,000 teachers and guides. To date, EF has helped over 15 million people to learn a new language, discover the world, or earn an academic degree.
“Education First” is more than our company name. It is our corporate passion.
EF’s mission is to break down the barriers of language, culture and geography that divide us.
About EF Bangalore
It all started with the idea that rather than outsourcing our systems development and maintenance, we could do it smarter and better ourselves – with our own people!
Just over a year and a half ago, a team of people therefore came to Bangalore, the Santa Barbara of India, interviewing hundreds and hundreds of people to find the most remarkable talent the market could offer. We started small, hiring only the best of the best, and began the journey from a very tiny temporary office.
As the number of highly skilled people grew, we also initiated the hunt for a bigger and more suitable workplace. After months of negotiations with landlords and architects, innumerous approval stamps, vanished construction workers and delayed furniture, we finally got everything in place and moved in to our new EF office on Cambridge Road on February 1st.
The office was built on the notion that you should feel at home, even when you are in the office; it should be a place where creativity and ideas spire, where you can feel the energy and power to achieve the impossible, and where your friends and colleagues inspire you to walk the extra mile.
We in Bangalore are very proud of our new office and would love for you to come and visit, maybe have a chai in our coffee lounge or enjoy the views from our roof terrace. And, we would of course take the opportunity to show you what we can and will achieve with technology!
Get IT right! Own IT!
Outlook Anywhere uses the HTTP protocol to encapsulate RPC information for sending
between the Outlook client (version 2003 and 2007) and the Exchange Server 2010 server. For
this service to run properly the RPC over HTTP Proxy service has to be installed on the Client
Access Server. This can be achieved either by adding this as a feature via the Server Manager,
or by entering the following command on a PowerShell Command Prompt:
ServerManagerCmd.exe -i RPC-over-HTTP-proxy
When the RPC over HTTP Proxy is installed use the following steps
to configure Outlook Anywhere:
1. Open the Exchange Management Console;
2. In the navigation pane, expand “Microsoft Exchange On-Premises”;
3. In the navigation pane, expand “Server Configuration”;
4. Click on “Client Access” and select your Client Access Server;
5. In the Actions pane, click on “Enable Outlook Anywhere”.
6. On the Enable Outlook Anywhere page enter the External host name. Make sure that
this name is also available in the certificate you created on the previous Paragraph. Select
the authentication methods used by clients, i.e. Basic Authentication or NTLM authentication.
For now leave these settings on default and click Enable to continue;
7. This will activate the Outlook Anywhere service on this service, and it may take up to 15
minutes before the service is actually useable on the Client Access Server. Click Finish to
close the wizard
Exchange Server 2010 cannot send out SMTP messages to the Internet by default. To achieve
this you’ll need to create an SMTP connector, which is a connector between one or more
Hub Transport Server and the Internet. Since this information is stored in Active Directory,
all Hub Transport Servers in the organization know of its existence and know how to route
messages via the SMTP connector to the Internet.
To create an SMTP connector to the Internet, follow these steps:
1. Logon to the Exchange Server 2010 server using a domain administrator account, and
open the Exchange Management Console;
2. Expand “Microsoft Exchange On-Premises” and then expand the Organization
Configuration.
3. Click on the Hub Transport, and then click on the “Send Connectors” tab in the middle
pane;
4. In the Actions Pane click on “New Send Connector”;
5. On the Introduction page enter a friendly name, “Internet Connector” for example,
and in the “Select the intended use for this Send connector” drop-down box select the
Internet option. Click Next to continue;
6. On the Address Space page, click on the Add button to add an address space for the
Internet Connector. In the address field enter an asterisk *, leave the cost on default and
click OK. Click Next to continue;
7. On the Network settings page you can select if the Send Connector will use its own
network DNS settings to route E-mail to other organizations, or to use a smart host.
Change this according to your own environment and click Next to continue;
8. On the source server page you can choose multiple source servers for the Send
Connector. You can compare this to Bridgehead Servers in Exchange Server 2003. When
you enter multiple Hub Transport Servers, the Exchange organization will automatically
load balance the SMTP traffic between the Hub Transport Servers. Since we have only
one Hub Transport Server installed we can leave this as default. Click Next to continue;
9. Check the Configuration Summary, and if everything is ok click on New to create the
Send Connector;
10. On the Completion page click Finish.
You have now created a Send Connector that routes messages from the internal Exchange
Server 2010 organization to the Internet.
Exchange recipients clearly need an email address for receiving email. For receiving email
from the Internet, recipients need an email address that corresponds to an accepted domain.
Recipients are either assigned an email address using an Email Address Policy, or it is also
possible to manually assign e-mail addresses to recipients.
To configure Email Address Policies follow these steps:
1. Logon to an Exchange Server 2010 server with domain administrator credentials and
open the Exchange Management Console;
2. Expand the “Microsoft Exchange On-Premises”;
3. Expand the Organization Configuration;
4. Click on Hub Transport in the left pane;
5. In the middle pane there are eight tabs, click on the on labelled E-Mail Address Policies;
6. There will be one default policy that will be applied to all recipients in your organization.
For now the default policy will be changed so that recipients will have the E-mail address
corresponding to your Accepted Domain. Click on New E-mail Address policy to create a
new policy;
7. On the Introduction page enter a new Friendly Name. Click the Browse button to select
a container or Organizational Unit in Active Directory where you want to apply the
filter. Select the Users container. Click Next to continue;
8. On the Conditions page you can select conditions on how the recipients in the container
will be queried, for example on State, Province, Department, Company etc. Do not select
anything for this demonstration, and click Next to continue;
9. On the E-mail Addresses tab click the Add button, the SMTP E-mail Address pop-up
will be shown. Leave the local part default (Use Alias) and select the “Select the accepted
domain for the e-mail address” option and click Browse;
10. Select the Accepted Domain you entered earlier , click OK twice and
click Next to continue;
11. On the Schedule page you have the option to apply the policy immediately or schedule
a deploy during, for example, non-office hours. This is useful when you have to change
thousands of recipients. For now leave it on Immediately and click Next to continue;
12. Review the settings, and if everything is ok then click New to create the policy and apply
it immediately;
13. When finished successfully click the Finish button.
You can check the E-mail address on a recipient through the EMC to confirm your policy
has been correctly applied. Expand the Recipient Configuration in the left pane of the
Exchange Management Console and click on ‘Mailbox’. In the middle pane a list of recipients
should show up, although right after installation only an administrator mailbox should be
visible. Double click on the mailbox and select the E-mail Addresses tab. The Administrator@
yourdomain.com should be the primary SMTP address.
The first thing for Exchange Server 2010 to configure is the accepted domains. In order to
receive SMTP messages from the Internet, an Exchange server has to know what domains
it will be receiving email for, as well as which domains it is responsible for. These are called
‘accepted domains’, and there are three types:
• Authoritative Domain – For this type of domain, the Exchange organization is fully
responsible and there will be no other messaging environment responsible. This
Exchange organization will also generate NDR (Non Delivery Report) messages when
mailboxes are not available.
• Internal Relay Domain – The Exchange organization will receive mail for this type of
domain, but it will relay all messages to an Exchange organization within the company.
• External Relay Domain – And for this type of domain, the Exchange organization will
receive mail, but it will relay all messages to a messaging platform outside the company.
For all three scenarios the MX records for the domain will be pointing to your Exchange
organization, and mail will be initially delivered to your Exchange servers.
Accepted domains are configured on the organization level and, as such, are known by all
Hub Transport Servers. If you are using an Edge Transport Server as well, the accepted
domain information will also be synchronized to the Edge Transport Servers.
To configure accepted domains follow these steps:
1. Logon to an Exchange Server 2010 server with domain administrator credentials and
open the Exchange Management Console;
2. Expand the “Microsoft Exchange On-Premises”;
3. Expand the Organization Configuration;
4. Click on Hub Transport in the left pane;
5. In the middle pane there are eight tabs, click on the Accepted Domains one;
6. One entry will appear, and the name will be the local domain (FQDN) that’s used when
installing the Active Directory. In the Actions pane click on New Accepted Domain;
7. In the New Accepted Domain Wizard enter a (friendly) name and the Accepted Domain
itself, for example yourdomain.com. When entered, select the type of Accepted Domain
in your Exchange Organization. In this example select the “Authoritative Domain”. Click
New to continue;
8. The Accepted Domain will now be created, and you can now click Finish on the Completion
window.
You have just created an accepted domain in your Exchange organization; the Exchange
server will accept messages for this domain, and if no recipients are found a NDR (Non
Delivery Report) will be generated.
When the installations of both the internal Exchange organization and the Edge Transport
Server are finished, the “post setup” configuration can be started. As in Exchange Server 2007,
there are a couple of additions and changes in the configuration that have to be made to the
Exchange Server 2010 instance before mail can be sent or received from the Internet.
• Enter an Exchange Server 2010 license key.
• Enter accepted domains and setup email address policies.
• Configure a Send Connector to send e-mail to the Internet.
• Configure the Hub Transport Server to accept anonymous SMTP if an Edge Transport
Server is not used.
• Add a Certificate to the Client Access Server role.
• Configure the Client Access Server role.
The Exchange Server 2010 Edge Transport Server is not part of the internal
Active Directory and Exchange organization, and is typically installed in the network’s
DMZ. A mechanism obviously needs to be in place for keeping the server up to date with
information.
For example, for the recipient filtering in the Edge Transport Server to take place, the server
needs to know which recipients exist in the internal Exchange environment. The Edge
Transport Server also needs to have knowledge about the existing Hub Transport Server in
the internal Exchange organization, where the Edge Transport Server has to deliver its SMTP
messages to.
This information is pushed from an internal Hub Transport Server to the Edge Transport
Server by a process called “Edgesync”. Please note that for a successful synchronization from
the Hub Transport Server to the Edge Transport Server, you have to open port 50636 on the
internal firewall. This port has to be opened from the internal network to the DMZ and not
vice versa.
To setup an Edge Synchronization, a special XML file has to be created on the Edge Transport
Server. This XML fi le has to be imported to a Hub Transport Server on the internal network
creating a relationship between the Edge Transport Server and the respective Hub Transport
Server. Once that relationship is created, the Edgesync service can be started. To setup the
Edgesync service, please follow these steps:
1. Logon to the Edge Transport Server using an administrator account and open an
Exchange Management Shell;
2. Enter the following command:
New-EdgeSubscription –Filename <<filename.xml>>
Copy the <<filename.xml>> to a directory on the Hub Transport Server.
3. Logon to the Hub Transport Server using an administrator account and open an
Exchange Management Shell command prompt.
4. Enter the following command:
New-EdgeSubscription –Filename <<filename.xml>> -CreateInternetSe
ndConnector:$TRUE –Site “Default-First-Site-Name”
When successfully finished on the Exchange Management Shell command prompt, enter the
following command:
Start-EdgeSynchronization
The Edge Synchronization process should now successfully start.
5. On the Edge Transport Server, open the Exchange Management Shell and check if the
settings are identical to the settings on the Hub Transport Server.
When making changes to the internal Exchange organization, these changes will
automatically replicate to the Edge Transport Server in the DMZ.
When all the prerequisite software for the Exchange Server 2010 Edge Transport Server role is
installed, you can move on to the Exchange server itself
1. Logon to the server with local administrator credentials, go to the installation media and
start the setup.exe installation program
2. Once all prerequisite software is installed correctly, the first two options are grayed out
and you can directly select “Install Exchange Server 2010”
3. On the Introduction Page click Next
4. Accept the License Agreement and click Next
5. Select whether or not you want to participate in the Error Reporting Feature and click
Next
6. On the Installation Type page select “Custom Installation” and click Next. If needed you
can select another directory where the Exchange software is installed
7. On the Server Role Selection page select the Edge Transport Server role. Notice that
when you select this role the other roles (Mailbox, Client Access & others) are grayed out
immediately. Click Next to continue.
8. The setup program will now perform a readiness to check to see if your server is capable
of running the Edge Transport Server role. When successfully completed click Install to
continue.
9. The Exchange binaries will now be copied to the local disk, the Management Tools will
be installed and the Edge Transport Server will be installed. This can take quite some
time to finish.
10. When finished you can continue configuring the Edge Transport Server using the
Exchange Management Console.
The Edge Transport Server is now installed, but not yet configured. It is possible to configure
everything, like the Accepted Domains, Send Connectors etc., manually using the Exchange
Management Console. An easier way is to use a synchronization process which synchronizes
information from the Hub Transport Server within the company’s Active Directory and
Exchange organization to the Edge Transport Server in the DMZ. This process is called the
Edge Transport Synchronization, or Edge sync.
Ravindra Kulkarni
IgNiTeD SoUL 