Allowing application servers to relay off Exchange Server 2010

Scenario: You have application server which needs to relay off your internal Exchange 2010 server ( printer, application etc.)

Platform:

Exchange 2010 HUB server	10.10.10.31
Application Relay Server	10.10.10.162

Task: Allow Application relay server relay off Exchange 2010 HTS server.

Log onto Exchange 2010 HTS Server open EMC under server configuration create new connector for application relay ( fallow the video)

• New Receive connector, give it a name
• Specify the FQDN for this connector , next
• Modify who can relay off this connector , next, finish , Set Authentication and permissions group.

 

 

We have do the fist part now we will test the application relay, so log on to application server, and open command line, we will telnet on port 25 from application server to the HUB server and sent mail from command line if mail is received your application will work. Before we get going make sure port 25 from application server to HTS server is NOT BLOCKED , common issues antivirus software blockage, or firewall etc..

 

Respectfully,
Oz Casey, Dedeal ( MVP north America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)

TMG 121 The semaphore timeout period has expired.

 

Error Code: 500 Internal Server Error. The semaphore timeout period has expired. (121)

If you are working on TMG server and Exchange 2010 scenario and receiving above errors , verifying couple things may save the day.

Check your static route table and make sure there is no loop causing this issue. Delete all your static route and add them one by one and make sure Static route is persistent and TMG internal NIC properties has these networks

Windows 2008 use Netsh ( route add , windows 2008 may not honor the static route, even the route may seem to be there from GUI)

NetSH Interface ip show route

Lets assume we have two interface

The interface inside =  talk to Active Directory , This interface does not have DGW ( Default Gateway) , hence we need static route to tell the TMG how to reach back to this network.

Outside interface = Talk to Outside  ) This interface has  DGW ( Default Gateway) , okay if the internal DGW is 10.80.3.1 and we are trying to reach out to 10.80.3.102, then the NetSH command would be as fallows….. ( Replace the IP addresses suits to your own environment)

netsh Interface ipv4 add route 10.80.3.102/32 "inside" 10.80.3.1 store=persistent

*The netsh command automatically assumes – unless otherwise specified in the command – that the route added is persistent. We added the persistent statement anyways (-:

To delete any static route

netsh interface ipv4 delete route 10.0.0.0/8 "Internal" 10.0.0.5

See the Static route

netsh interface ip show route

Reset the Interface ( very powerful)

netsh interface tcp reset

Respectfully,
Oz Casey, Dedeal ( MVP north America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)

How to Customize Outlook for Company Users, adding different attributes.

 

If your company has requirement adding different attributes on user at  GAL, such as employee number, IPhone or blackberry filed into user properties in GAL, here is supper easy and safe way to get the work done.

In this scenario the management is looking to see additional field for all users within the GAL

• Emp. number
• IPhone
• Black Berry

As you can see we do not have any of these files in out the box configuration on GAL

Open MMC from Exchange server ( you need correct permissions to achieve the desired goal) see the link for permissions if you are interested in granular permissions.

http://technet.microsoft.com/en-us/library/aa996881(v=exchg.80).aspx

Log into your Exchange Server

Click Start , in the search type “MMC”

hit enter

Click on “Details Templates Editor”

Here is full Video

Now you will see these filed within the outlook

 

To delete what you have done is pretty simple open MMC Console and click on “restore”

 

How to Customize the Details Template

http://technet.microsoft.com/en-us/library/bb124494(v=exchg.80).aspx

Respectfully,
Oz Casey, Dedeal ( MVP north America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)

Exchange 2010 Performance Counters

When you have performance related issues and concerns that are the basic things to look for in exchange 2010?

Possible causes of poor performance ,

Performance issues may raise when mail server is sized wrong and unable to satisfy the current load, the basic counters, Memory, CPU, Disk averaged read write. The typical indication of poor performance , outlook popup indicates retrieval data from problem.ExcahngeServer.local etc..

What to look for?

Isolate if the issues is specific to one client or effecting more then one user.

Understand and investigate your CAS Servers , “CAS ARRAY”, remember when MAPI ( Outlook) client opens up MAPI request to connect to it’s own mailbox the, MAPI request will not directly go to Mail Box servers, it will go to your CAS server and CAS will talk to MBX server ( MAPI) behalf of requester.

Use your tool box and set of tools in there in E210. the most common one is Performance Troubleshooter.

I want to talk about MSExchangeIS\RPC Averaged Latency and the changes in the counter recommended thresholds.

in Exchange 2003 and 2007

MSExchangeIS\RPC Averaged Latency < 10ms

The value has changed as the business logic

MSExchangeIS\RPC Averaged Latency < 250ms

The new model in E210 Client MAPI request shown as below. The MAPI client ( Outlook) who want to connect to it’s mailbox database has to fallow below logic.

Outlook Client ( MAPI Users)---------(MAPI)------------> CAS ----------(MAPI)-----------MBX Server

MBX--------------(MAPI)------------->CAS----------(MAPI)---------->Outlook Client ( MAPI Users)

• Averaged Latency should be less than 250ms at all times……
• The generally-accepted warning threshold for MSExchangeIS\RPC Requests is less than 70 at all times…..

What would be considered as bottleneck ?

• Although store.exe has 500 threads in Exchange Server 2007 / 2010, consuming more than 70 at one time is evidence of a bottleneck.

 

Performance Monitoring Getting Started Guide

Respectfully,
Oz Casey, Dedeal ( MVP north America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)