PREMNAIR'S Blog

"..Unnatural work produces too much stress.."

Exchange server 2010 SP1 – Step by Step installlation on the production server – Live

Earlier i’ve done the Exchange server migration – 2007 to 2010 – Live cast, Its been 10 months since Exchange team release the SP1 for Microsoft Exchange server 2010….today i’m doing Microsoft Exchange server 2010 SP1 upgradation…Live page is opened.

Click here to view this live page

Enjoy!!!!

June 24, 2011 Posted by | Active Sync, DAG, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange Pre-Deployment Analyzer, Exchange server 2010, Exchange Server Profile Analyzer, Forefront, Forefront Endpoint protection 2010, Hyper-V, IP Block List, Log Parser, Mailbox Server Requirements Calculator, Microsoft, New Service Pack, Office 2010, Office for Mac, Power Shell, Software, Transport architecture, Windows Server 2008 R2 | , , , , , , , , , , , , , , | Leave a comment

Exchange 2010 – Attachment size – Global setting (for Send & Receive)

Attachment size setting inside Exchange server 2010 for global user settings.

  • Go to your mailbox server
  • open EMC
  • goto Organization configuration
  • goto Hub Transport
  • select global setting tab

Edit the Transport settings and change the parameters as below.

Once you done it, click Apply and ok

Remember one thing, the more you increase the size of the attachment, the load on the CAS & Edge server increase…plus the Virus scanning engine too.

Thats all folks!!!

March 28, 2011 Posted by | Computer TIPS, Edge Server, Exchange Management Console, Exchange server 2010, Forefront, Mailbox Server Requirements Calculator, Mails, Microsoft, Software, Transport architecture | , , | Leave a comment

Exchange server 2010 CAS array to MAPI load balance – Detailed

Most of you guys must have experience the scenario when “Outlook connection lost….” even if you have Exchange server 2010 (with Edge, 2 clustered H&C and 2 DAG configured MB) and Outlook 2010 in place. The reason is that, when you are doing a maintenance on one of the H&C, and if the client is connected to that H&C, communication to the MB is lost. The reason for this is that the cluster load balancing on the H&C cluster handler is not in place, even if the cluster name is published in the DNS server.

In Exchange 2007, 5 server roles that performed distinct functions within the Exchange organization. One role in particular – the Client Access server role – introduced a variety of new Web services, including the Availability service, the Auto discover service and Calendar Concierge services.

In Exchange 2010, same 5 server roles exists. However, there are some significant architectural changes and some shift in responsibilities. The most significant change in Exchange 2010, two new services on CAS called the RPC Client Access and Address Book services establish the RPC (Repote Procedure Call) endpoint for MAPI(Messaging Application Programming Interface), NSPI(Name Service Provider Interface) and RFR (Request for Response) client access. This new functionality replaces the RPC endpoints in the Information Store. The RPC endpoint in the Information Store has not been removed in Exchange 2010, but it has been modified to only accept requests from CAS servers. The RPC endpoint for public folder database access remains on the Mailbox server, however, Outlook clients now communicate directly with the RPC Client Access service on the Mailbox Server for public folder database access, and not with the Information Store.

When CAS starts communicating with the Mailbox server, it makes sense to view it as the Client Access server communicating with the Mailbox database via the Mailbox server that hosts the database. This is especially evident in a load-balanced array of Client Access servers and/or where your environment is configured to use Database Availability Groups that are associated with a Client Access server or Client Access server array.

  • In a non-load balanced environment, the mailbox database is associated with only a single Client Access server.
  • In a load-balanced environment, the Mailbox database is associated with the load balanced array of multiple Client Access servers.

By default, before a Client Access array is configured,

  • all databases are associated with a Client Access server in the environment
  • the Outlook clients communicate directly with the Client Access server until the association with the database is updated to be the Client Access array.

In order for the clients to utilize a CAS array

  1. Create a Client Access array with an FQDN (Fully Qualified Domain Name).
  2. Load balance your CAS servers in a CAS array by whatever method you choose – Both Hardware LB or Windows Network LB are supported load balancers
  3. Add the Client Access servers within the AD site to a load balanced array and in DNS associate the unique FQDN to the Virtual IP of the load-balanced array.
  4. Configure your load balancing array to load balance the MAPI RPC ports – TCP 135, UDP/TCP 6005-65535; or set static ports
  5. Configure the databases to utilize the CAS array… Use the new-clientaccessarray cmdlet to create the CAS array object. Eg: New-ClientAccessArray –Name “Tromso CAS Array” –Fqdn tromso.site.com” –Site “SITEA”

How to Setup!!!..

Goto one of the CAS server where the NLB is ( to read more about New-ClientAccessArray cmdlet, click here )

[1] Check is there are any pre-created CAS Arrays. PS Command : Get-ClientAccessArray

[2] Create new Client Access Array. Run the Cmdlet in EMS New-ClientAccessArray -Fqdn server.contoso.com -Site “Redmond” -Name “server.contoso.com”

[3] Associate databases with this CAS Array -

Use this CMDLet to add mailbox database to CAS array. Add all mailbox databases at once – Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “CASNLB.contoso.com”

Now the best part -

Configuring Outlook 2010 using Auto Discover

If you already configured Outlook client, Close the outlook, then goto Control Panel->Mail and change the Server name to the new CAS NLB name

If you are going to use a new outlook configuration, Auto discover will return the new CAS NLB name.

Thats all folks!!! Enjoy!!!

March 28, 2011 Posted by | Active Sync, DAG, ECP, Entourage, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, HTTPS, Hyper-V, IMAP, IP, Mailbox Server Requirements Calculator, Mails, Microsoft, OAB, Office, Office 2010, Office 2011, Office for Mac, Office Professional Plus, Outlook, Outlook Webapps, OWA, POP3, Protocols, Public Folder, Software, TCP, Transport architecture | , , , , , , , , , , , , , , | Leave a comment

Restricting email to the Internet on a per user AND per domain basis

This blog post is meant to show how easy it now is to accomplish this oft heard request in Exchange 2010. Transport rules, introduced with Exchange 2007, provided a lot of new options for administration of mail resulting in even more requests for additional functionality. The rules now have new predicates and actions extending the possibilities of what can be done. For our example, the rule will restrictActive Directory Mail enabled users” who have their ‘Department‘ defined as ‘Temp Employees‘ from sending mail to the internet, except they must be allowed to send to 2 external domains called: ‘partnerdomain.com‘ and ‘fourthcoffee.com‘. Additionally, to reduce Helpdesk calls, you want to send an NDR when they violate the rule. For demonstration purposes I will use 2 Conditions, one Action and one Exception.

Microsoft Exchange Team Blog will explain you how to do it in Exchange 2010…beautiful blog post..click here

March 15, 2011 Posted by | Exchange Online, Exchange Server 2007, Exchange server 2010, Mails, MailTips, Microsoft, Office, Office 2010, Office 2011, Outlook, Outlook Webapps, Software, Transport architecture | , , | Leave a comment

Un-installing/De-commissioning Exchange server 2007 Mailbox from Passive cluster node for Exchange 2010

  1. Open the command prompt of the Passive mailbox server..make sure you logged in as domain administrator.
  2. Go to C:\Program Files\Microsoft\Exchange SErver\Bin
  3. Type the command setup /mode:uninstall

Now you have successfully uninstall the Exchange server mailbox role from the passive node, but the cluster environment server information still exists, and we need to remove that as well.

To do that we need to…

  • Open the Cluster Management Tool
  • Expand the cluster resource name
  • Expand the Nodes
  • Right click the passive node server
  • Click on More actions -> click on “Stop cluster service”

 

 Once you “Stop Cluster Service”, then click on More actions again and click Evict and click the Evict Node….

Once you done this, restart the server.

Once the server is up…do the following too

  1. Open the Server manager console
  2. Click on Features and then click on Remove Features
  3. Uncheck Failover Clustering
  4. Click on Yes to reconfirm and click on NEXT
  5. Click on Remove.
  6. After the Server is restarted
  7. Remove any remaining files and folders from the Exchange Server program files folder and subfolders.

Thats the end of Exchange Server 2007 Mailbox de-commissioning on a Passive node….Now go to the Active mailbox server of Exchange server 2007

This process is not as same like passive node. Here we can’t go with uninstall command only, because this server holds the culstered mailbox server information and it is online. In order to remove this,

Go to the command prompt..change the directory to C:\Program files\Microsoft\Exchange Server\Bin

Type command setup.com /removeCMS /CMSName:<Clustername>

This will take the mailbox now offline from the cluster…

Now type setup /mode:uninstall

Once you finish this uninstallation, Exchange server 2007 last mail box has been remove from your domain..now do the evict

Goto command prompt (If the command prompt is open, close it and open it and then type

Cluster <mailbox cluster name> node <nodename> /force

That’s the end of the “EXCHANGE SERVER 2007 DE-COMMISSIONING PROCESS”

Now you are completely depended on Exchange server 2010.

March 15, 2011 Posted by | Edge Server, Exchange Management Console, Exchange Management Shell, Exchange Server 2007, Exchange server 2010, Mailbox Server Requirements Calculator, Microsoft, Remote Connectivity Analyzer, Software, Transport architecture | , , | Leave a comment

Exchange 2010 Architecture Poster

To download the Exchange 2010 Architecture Poster, click here  Image size  in 36″ x 24″

To download the Exchange Server 2010 Architecture Poster (PDF).

For Transport architecture diagrams, see Exchange 2010 Transport Architecture Diagrams Available for Download.

Thanks to Microsoft Exchange Team for this

December 14, 2010 Posted by | Exchange server 2010, Microsoft, Software, Transport architecture | , | Leave a comment

Exchange Server 2010 Service Pack 1 Beta released

In my last post Exchange Server 2010 Service Pack 1 – Sneak-peak and Microsoft Exchange Team Blog Yes Virginia, there is an Exchange Server 2010 SP1, the team shared information on some of the features  and  expected fixes  that are coming with the SP1 update. Microsoft committed to providing the final version of Exchange Server 2010 SP1 before the end of 2010, and now they have release the Beta of Exchange Server 2010 SP1. Video Preview from MSEXCHANGE Team ..You can download the Microsoft Exchange Server 2010 SP1 Beta from here…This pre-release software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use the software. There is no product support for this trial software.

Is The New Exchange 2010 Service Pack Enough to Stop the Migration to Google Apps?..Click here to read

July 13, 2010 Posted by | Exchange Management Console, Exchange Management Shell, Exchange server 2010, Microsoft, New Service Pack, Office, Office 2010, Office 365, Software, Transport architecture | , , | 1 Comment

Configure EWS, Autodiscover, OWA, OAB, ECP on Exchange Server 2010

As you all know that the service connectivity for a mail server is the  main concern to all of us. In Exchange server 2010, the connectivity is as same as Exchange server 2007. Once you migrate or install the new version, this should be tested with the proper credentials and certificate..or else, you will end up with your mail server IP going to the blacklist, because of the wrong pointers and configurations. First of all, do the internal test. Go to your computer start bar, right side where Date and time is showing, you will find the Outlook icon, hold Ctrl + right click on the outlook icon and click “Test Email Auto Configuration…”

Select the “Use AutoDiscover” and click Test..

Above one is a success one..If failed, do the below. The Exchange Web Service (EWS) is the web service that allows access to the Out of Office service. If either the internal or external URL for the EWS is missing or incorrect, OOF will fail and other services may not work as expected. Using Exchange Management Shell, check the URLs assigned to the web service virtual directory using the Get-WebServicesVirtualDirectory command

First goto CAS server

Type the following Power Shell command for EWS (Exchange Web Service)

Copy code Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

You will get the result like below

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl : https://mailv.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mailv.domain.com/ews/exchange.asmx

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl : https://mailv.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mailv.domain.com/ews/exchange.asmx

If this is not correct, you need to fix it.. This has to be done on Powershell command on the CAS server.

To do that…Copy code

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS1\EWS (Default Web Site)” -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$true

[PS]C:\Windows\system32>Set-WebServicesVirtualDirectory -Identity “ECAS2\EWS (Default Web Site)” -InternalUrl https://mail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$true

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Identity    : ECAS1\EWS (Default Web Site)
InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.domain.com/ews/exchange.asmx

Identity    : ECAS2\EWS (Default Web Site)
InternalUrl : https://mail.domain.com/EWS/Exchange.asmx
ExternalUrl : https://mail.domain.com/ews/exchange.asmx

Now you can see that the URL has been fixed. This is for Web Services.

Now for Autodiscovery….

[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory

To see the settings

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri

RESULT

[PS] C:\Windows\system32>Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri
Identity                       : ECAS1
AutoDiscoverServiceInternalUri : https://mailv.domain.com/Autodiscover/Autodiscover.xml

Identity                       : ECAS2
AutoDiscoverServiceInternalUri : https://mailv.domain.com/Autodiscover/Autodiscover.xml

To FIX it..

[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS1 -AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml
[PS] C:\Windows\system32>Set-ClientAccessServer -Identity ECAS2 -AutoDiscoverServiceInternalUri https://mail.domain.com/Autodiscover/Autodiscover.xml 

 Now for the Outlook Web Apps, Exchange Control Panel, Exchange ActiveSync, Offline Address book…you have to go to Exchange Management Console (EMC)

  1. Goto one of the CAS server
  2. Open EMC
  3. Goto Server Configuration
  4. Select Client Access
  5. On the Middle top pannel, you can see the CAS server listed.
  6. Select one, on the bottom pannel, you will see like below.

Select each tab and then right click on the object and change the path as required. Once you done with the first CAS servr, do the same for the second as well.

Thats it…you are good to go for production.

July 3, 2010 Posted by | Active Directory, Active Sync, ECP, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Internet Information Services (IIS), Microsoft, OAB, Office, Office 2010, Office 2011, Outlook, Outlook Webapps, OWA, Public Folder, Software, Transport architecture, Windows Server 2008 R2 | , , , , , , , , | 9 Comments

Exchange Server 2010 Service Pack 1 – Sneak-peak

Exchange Team Blog that provides the first public details about Exchange Server 2010 Service Pack 1 (SP1).  SP1 will of course include fixes and enhancements in the areas customers have helped us identify (including code from all of the Exchange 2010 post RTM update rollups we’ve released to date).  But SP1 will also include some new features and functionality changes, as well….cool

  • A new search preview helps with early case assessment by providing you an estimate on the number of items in the result set-with keyword statistics-before e-mail located in the search are copied to the designated discovery mailbox.
  • And, a new search result de-duplication option, when checked, only copies one instance of a message to the discovery mailbox.

Look at the below  menu for the DAG…what a cool feature it will be

With the release of Exchange Server 2010 last November, Microsoft introduced integrated archiving capabilities aimed at helping you preserve and discover e-mail data. In SP1, this has enhanced its archiving functionality based on the great feedback you’they got since the launch. This includes adding the flexibility to provision a user’s Personal Archive to a different mailbox database from their primary mailbox. This means your organization can now more easily implement separate storage strategies (or tiered storage) for less frequently accessed e-mail. And, we didn’t just stop there! We’ve also added new server side capabilities so you can import historical e-mail data from .PST files, directly into Exchange, as well as IT pro controls to enable delegate access to a user’s Personal Archive.

To help streamline the implementation of retention policies, SP1 updates the Exchange Management Console with new tools to create Retention Policy Tags, so you can automate the deletion and archiving of e-mail and other Exchange items. New optional Retention Policy Tags give you even more flexibility in defining your organizations retention management strategy….coooool

Can’t wait to get hold of this…Announcement blog from Microsoft Exhange Team …click here Yes Virginia, there is an Exchange Server 2010 SP1

Learn more about our approach to archiving by reading the Archiving with Exchange 2010 whitepaper.

Scott Schnoll’s weblog…click here

June 27, 2010 Posted by | Active Sync, Calendar, DAG, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange Online, Exchange server 2010, Internet Information Services (IIS), IP Block List, Lync Online, Microsoft, New Service Pack, OAB, Office, Office 2010, Office 2011, Office 365, Office Professional Plus, Outlook, Outlook Webapps, OWA, Public Folder, Social Connectors, Software, Transport architecture | , , , , | 2 Comments

Exchange Server 2010 Migration – Useful tools

Exchange Pre-Deployment Analyzer..Click here

The ExPDA tool performs a scan of your existing Exchange and Active Directory environments and produces a report that lists all items that require attention prior to deployment.

Exchange Server Profile Analyzer..Click here

The EPA tool performs a scan of either a single database or the entire organization to create an aggregated report of mailbox statistical information.

Log Parser…Click here

Log Parser, a powerful tool for querying text-based log files such as those that are generated by IIS and Message Tracking on Exchange servers

Exchange Server Remote Connectivity Analyzer..Click here

This tool will help you analyze whether the configuration has been done properly.

Performance Monitor..Click here or click here

The built-in Performance Monitor tool for Windows lets you collect performance data for every element of the Exchange servers and use it for capacity planning of the new Exchange 2010 servers.

Mailbox Server Requirements Calculator…Click here

The most complicated server role in an Exchange Server 2010 environment to calculate the sizing for is the Mailbox Server role, particularly when it comes to storage.

June 26, 2010 Posted by | Exchange Management Console, Exchange Management Shell, Exchange Pre-Deployment Analyzer, Exchange server 2010, Exchange Server Profile Analyzer, Internet Information Services (IIS), Log Parser, Mailbox Server Requirements Calculator, Microsoft, Office, Remote Connectivity Analyzer, Software, Transport architecture | , , , , , , , | Leave a comment

Follow

Get every new post delivered to your Inbox.

Join 420 other followers

%d bloggers like this: