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!!!!

Advertisements

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

OS X – Lion from Apple…releasing on July 2011!!!

In continuation of my previous blog about Mac OS X Lion developer preview 3, Apple announced its release on July 2001 to Mac App Stores for just $29.99. This software works hand in hand with apple hardware for a better operating system.

  • Built on a rock-solid UNIX foundation
  • OS X is engineered to take full advantage of the technologies in every new Mac
  • Deliver the most intuitive and integrated computer experience possible.

Enjoy!!!

June 14, 2011 Posted by | Active Sync, Apple, EWS, Exchange server 2010, Lion OS, Mac Mini, Outlook, Safari | , , , | 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

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 | , , , , , , , , | 10 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 – SAN certificate creation for autodiscover,EWS and OWA etc…!

Good News for installations guys out there, Exchange server 2010 SAN certificate creation very easy…click here to read my blog
ENJOY!!!!!!!!!!!!!!!!!!!!

June 20, 2010 Posted by | Active Sync, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange server 2010, Forefront, IMAP, Internet Information Services (IIS), Microsoft, OAB, Office 2010, Outlook Webapps, OWA, SAN Certificate, Software, Threat Management Gateway, Transport architecture | , , | 1 Comment

Exchange server 2007 to 2010 Live migration!!!! Live blog!!! Live Platform…real time scenario!!!

Please find on my blog, one page dedicated to this task…you can see it on my blog top page… or click here

             TO                                          

 MIGRATION…Started on June 8, 2010 ….Today 20th of June..all the objects has been replicated to Exchange 2010..Now the decommissioning starts..Finish too

June 10, 2010 Posted by | Active Sync, Calendar, DAG, DELL, ECP, Edge Server, EWS, Exchange Management Console, Exchange Management Shell, Exchange Pre-Deployment Analyzer, Exchange Server 2007, Exchange server 2010, Exchange Server Profile Analyzer, Facebook, Firewall, Forefront, HTTP, HTTPS, IMAP, Internet Information Services (IIS), iOS4, IP, IP Block List, iPhone, iSCSI, Linkedin, Log Parser, Mailbox Server Requirements Calculator, MailTips, Microsoft, OAB, Office, Office 2010, Office 2011, Office for Mac, Outlook, Outlook Webapps, OWA, Phone, POP3, Protocols, Public Folder, Remote Connectivity Analyzer, SAN, SAN Certificate, Sender Policy Framework, Social Connectors, Software, Threat Management Gateway, Transport architecture, Twitter, Windows 7 phone, Windows Server 2008 R2 | , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | Leave a comment

   

%d bloggers like this: