Ladder Up With Me Five Steps Towards Cloud Microsoft Office 365 – Exchange Wave 15

Let me will walk you through five simple steps towards Cloud Microsoft O365 via this article and you will be able to experience the whole New Exchange wave 15 with minimal expense in my case approx.  102 – Rs. Only

  1. Register your Company DNS Domain – e.g.  In my case I have registered a domain called msexchangeasia.com at godaddy.com which is cheap and I got for approx. 102 Rs.
  2. Subscribe for a free trial – Subscribing for a trial account will give you chance to experience the all New Exchange and take advantages of its features.
  3. Configure your Domain – Once you got the trial account add and verify your company domain to the Office 365 portal.
  4. DNS Record Update – Using automatic DNS records created by O365 portal just update at the pubic DNS registration for MX/CNAME/TXT/SRV.
  5. Create Mailbox à Send / Receive Emails – Once you are done with the above four steps all you need to do is collaborating with colleagues and friends and enjoy the free subscription for a month.

Let us know understand each towards Cloud – Microsoft Office 365 as below mentioned.

  1. Register your Company DNS Domain – e.g.  In my case I have registered a domain called msexchangeasia.com at godaddy.com which is cheap and I got for approx. 102 Rs.

1

Go the DNS domain registration website, enter the desired domain and search for availability – there are many DNS domain registration website but I preferred to go with godaddy.com

2. Subscribe for a free trial – Subscribing for a trial account will give you chance to experience the all New Exchange and take advantages of its features.

2

Go to URL – http://office.microsoft.com/en-001/business/compare-office-365-for-business-plans-FX102918419.aspx and select a free trial plan

3

Signup, once done filling your details and select create my account and login on to below portal

4

5

Once logged in explore the management options.

3. Configure your Domain – Once you got the trial account add and verify your company domain to the Office 365 portal.

6

Using Domain section – add your company domain which you just registered at godaddy.com in my case msexchangeasia.com

7

Specify the DNS hosting provider detail, by default are the available  hosting listed in the portal so that O365 portal can directly query or you can simply default options and click done verify now.

8

Once you select I selected godaddy as hosting provider – it will instruct further to create TXT record so that MS can query to verify as below mentioned in the godaddy DNS registration zone portal.

9

10

Upon successful creation of TXT record it will verify and add the domain

11

Now the domain status will be seen as verified and click on manage DNS

4. DNS Record Update – Using automatic DNS records created by O365 portal just update at the pubic DNS registration for MX/CNAME/TXT/SRV.

12

The Office 365 portal will populate with the records needs to be created and update at godaddy.com DNS zone file and will look as below mentioned.

13

5. Create Mailbox à Send / Receive Emails – Once you are done with the above four steps all you need to do is collaborating with colleagues and friends and enjoy the free subscription for a month.

15

Go to User management and create mailboxes – with the trial account subscription you can have up to 10 mailbox license with Lync enabled.

Test mail flow – in my case am sending test email from Hotmail to O365 mailbox and replied received.

16

Enjoy 🙂

Advertisements
Posted in Exchange Servers | 1 Comment

Understanding Information Technology Infrastructure Library v3 Foundation – Part 2

Hope you enjoyed going through the first part of this series and let me continue with the next & final part of this series.

3. Service Transition:

The objective is to ensure that new, modified or services which are retired meet the expectations of the business as document in the service strategy and service design stages of the life cycle. In this stage the planning and managing services are efficiently and effectively taken care including the risk. It sets right expectation on the performance and the use of new or changed services. It practices release of planning, building, testing, evaluating and deploying new or changed services. With the introduction of new services it also takes care of the existing services minimizing the unintended consequences of change.

Let us now know in phrase about the important topics which are involved in Service Transition

Configuration Item – It is a service asset that needs to be managed in order to deliver IT services.

Configuration Management System – To manage large and complex IT services & infrastructure, service assets and configuration management requires the use of a supporting system known as the configuration management system. It holds all the information about configuration item within the designated scope. It maintains the relationship between all the service components and may also include records for related incidents, problem, known errors, changes and releases.

Service Knowledge Management System – It is the set of tools and databases that are used to manage knowledge, information and data. Many configuration items are available in the form of knowledge or information and these are typically stored in the SKMS – for example, a service level agreement, a report template or a definitive media library (I will explain you soon below).

Definitive Media Library – It is the secure library in which the definitive authorized versions of all media (Hardware) configuration items are stored and protected. It contains all master copies of controlled documentation, definitive copies of purchased software with licensed document or information.

Change Management Process – It can be anything which is in addition, modification or removal that could have an effect on IT services. It includes changes to all architectures, processes, tools, metrics and documentation as well as changes to IT services and other configuration items. It has three different type of service change.

Standard Change – A pre-authorized change that is low risk, relatively common and follows a procedure or work instruction.

Emergency Change – A change that must be implemented as soon as possible for example to resolve a major incident.

Normal Change – Any service change that is not a standard change or an emergency change.

Change Model – It is also called as Change Template predefining the steps that should be taken to handle a particular type of change in an agreed way.

Remediation Planning – Actions which are taken to recover after a failed change or release. That is the reason test plans are done to validate successful change or release.

Change Advisory Board – It is a body that exist to support the authorization of changes and to assist change management in the assessment, prioritization and scheduling of changes. It also involvement of different stake holders depending on the changes being considered.

Emergency CAB – When there is requirement of change need to be done in the services which may be delayed due to the process involved in CAB, that change could be done as quickly as possible with the help of ECAB and later the rest of the process needs to be taken care.

Release and Deploy Management – It is to plan, schedule and control the build, test and deployment of releases, and to deliver new functionality required by the business while protecting the integrity of existing services. There are four phases to release and deployment as mentioned below.

R & D Planning – This phase starts with change management authorization to plan a release and ends with change management authorization to create the release.

Release build & Test – This phase starts with change management authorization to build the release and ends with change management authorization for the baseline released package to be checked in definitive media library.

Deployment – This phase starts with change management authorization to deploy the release package to one or more target environments and ends with handover to the service operation functions.

Review and Close – Experiences and feedbacks are captured, performance targets and achievements are reviewed and lessons are learned.

Knowledge Management – It is to ensure that reliable and secure knowledge, information and data is available throughout the service lifecycle.

DIKW – For now it is just essential to know how it moves forward Data à Information à Knowledge à Wisdom.

4. Service Operation:

The purpose is to coordinate and carry out the activities and processes required to deliver and manage services at agreed level to business users and customers. It is also responsible for the ongoing management of the technology that is used to deliver and support services. The value is realized by operating the services effectively and efficiently. Also strategic objectives are ultimately realized through service operation hence making it a critical capability. The objective is to maintain business satisfaction and confidence in IT through effective and efficient delivery and support of agreed IT services. It minimized the impact of service outages on day-to-day business activities.

Let us now know in phrase about the important topics which are involved in Service Operation

Workaround – A temporary way of overcoming the difficulties in the services.

Known Error & KEDB – As soon as any diagnose is complete and particularly where a workaround has been found (even though it may not be a permanent solution), a known error record must be raised and placed in the Known Error Database so that if further incident or problem arise they can be identified and the services are restored more quickly.

Role of communications – An important principle is that all communication must have an intended purpose or a resultant action.

Incident Management – The purpose of incident management is to restore normal service as quickly as possible and minimize the adverse impact on business operations. It can be reported by anyone.

Problem Management – It is the process responsible for managing the life cycle of all problems and ITIL defines a problem as the underlying cause of one or more incidents. Problem management seeks to get the root cause of incidents, document and communicate known errors and initiate actions to improve or correct the situation. The objective is to prevent problems and resulting incidents from happening, eliminate recurring incidents and minimize the impact of incidents that cannot be prevented.

There is a good Incident & Problem Management process chart available you can refer to.

Event Management – It is the basis for operational monitoring and control. If events are programmed to communicate operational information as well as warning and exceptions, they can also be used as a basis for automating many routine operation management activities.

Request Fulfillment – It provides a channel for uses to request and receive standard services for which a predefined authorization and qualification process exists. It also provides information to users and customers about the availability of services and the procedure for obtaining them.

Access Management – It is to provide the rights for users to be able to use a service or group of services. It is therefore the execution of policies and action defined in the information security management.

5. Continual Service Improvement

It is the last but not the least and important volume, it is not actually a separate but evolves with the other above mentioned services.  The purpose is to align IT services with changing business needs by identifying and implementing improvements to IT services that support business processes. It reviews, analyzes and make recommendations on improvement opportunities in each lifecycle phase. It improves IT service quality and the efficiency, cost effectiveness of delivering IT services with affecting customer satisfaction adversely, it ensures applicable quality management methods that are used to support continual service improvement, it also ensures that processes have clearly defined objectives and measurement that lead to actionable improvements.

W. Edwards Deming is best known for his management philosophy leading to higher quality, increased productivity and a more competitive position. He formulated 14 points of attentions for managers.

The PDCA (Plan, Do, Check and Act) cycle is critical at two points in CSI: Implementation of CSI and for the application of CSI to services and service management processes.

Seven Step Improvement Process – The purpose is to define and manage the steps needed to identify, define, gather, process, analyze, present and implement. It also includes the analysis of the performance and capabilities of services, processes throughout the lifecycle, partners and technology.

CSI Approach – It can be summarized as mentioned below.

  • What is the vision? – Business vision, mission, goals and objectives?
  • Where are we now? – Baseline assessment. (Assessment of the current situation)
  • Where do we want to be? – Measurable targets,
  • How do we get there? – detail the CSI plan to achieve higher quality service
  • Did we get there? – verify the measurement and metrics are in place to ensure that milestones were achieved.
  • How do we keep the momentum going? – The process should ensure that the momentum for quality improvement is maintained by assuring that changes become embedded in the organization.

Hope this was informative.

Posted in Documents | Leave a comment

Understanding Information Technology Infrastructure Library v3 Foundation – Part 1

This is what I Say: – “ITIL is the one of the methodology in delivering IT Service Mgmt. for Service Providers to give value meeting the Customer’s Expectation in agreed SLA.”

I wish I could jot down what I meant in above statement, this blog page wouldn’t be enough for it.

Some time back I had this opportunity to go through this training called ITIL Foundation v3, had known its worth and why it is important to apply in our professional activities as well as our personal life too. I should thank IBM for this opportunity and availed the benefits out from it. I would like to especially thank the Trainer from whom I got this knowledge – Ganesh Shrishrimal, holds an ITIL Expert Certification with good Industry experiences.

Moreover the concepts were cleared and I realized it is very much essentials for the IT people to know this methodology and apply it to our day to day activities.

I would like to share what I have learned and hope it will be informative to you. I will not take you through the whole syllabus but to the important topics which is essential to know.

To start with let us know what ITIL is and why we need to practice this in an organization and where it came from…?

The UK government’s Central Computer and Telecommunications Agency in 1980 developed a set of recommendations, standards, and framework for an organization to improve its IT Service Management independently. ITIL stands for Information Technology Infrastructure Library, it is a collection of books that covers specific best practices with IT Service Management. ITIL has been updated with its versions from time to time as required and currently V3 is the latest.

ITIL has five major volumes as below mentioned and I will take you through the overview what I know and actually like about it.

  1. Service Strategy
  2. Service Design
  3. Service Transition
  4. Service Operation
  5. Continual Service Improvement

Let’s understand one by one a bit in details – Read from the Service Provider perspective.

1. Service Strategy:

It is known as conceptualization of value creation, as said this was the important point what I understood and it means a lot. It talks about the ability to create value which is created and delivered. A clear identification of the services to the customer who use them. It precisely clarifies how services will be delivered and funded to whom it will be delivered and for what purpose. It helps in forecasting the means to understand the organization capabilities to deliver the service. It helps to know which services will achieve the strategy, what level of investment will be required, at what level of demand and the means to ensure a working relationship exists between the customer and service provider. There are different type of customers and its businesses but here the strategic part would be for service provider deliver services meeting customer business outcomes.

Let us now know in phrase about the important topics which are involved in Service Strategy.

There are two important aspects which needs to be considered for the value creation that is combination of utility (fit for purpose) and Warranty (Secure)

Service Catalog – Offerings made known towards the customer

Service Portfolio – A set of services that is managed by a Service Provider

IT Governance – It is to ensure there is fairness, control, transparency and accountability of the services provided to the customer

Business Case – It also called business justification which supports and help in planning tool that projects the likely consequence of business action.

Risk Management – Uncertainty of outcome whether a positive opportunity or negative threat. It is also something the term called “that might happen”.

Service Provider Type – There are 3 types of service providers called Internal, Shared & External

Patterns of Business Activity – It influences customer behavior by differential charging, penalty, reward and timeouts.

Financial Management – It provides budgeting, accounting and charging requirement.

Business Relationship Management – It establishes and maintain a business relationship between the service provider and the customer based on the understanding and its business needs.

There is so much to talk about on above topics of which I do not want go in depth here but would move on to the next phase i.e. Service Design

2. Service Design

The purpose is to design IT services, together with the governing IT practices, process and policies to realize the service provider’s strategy and to facilitate the customer’s delivery and satisfaction. The main objective here is to reduce the Total Cost of Ownership, improve quality of services, easier implementation of new or changed services. It looks at identifying, defining and aligning the IT solution with the business requirement.

Service design is not something which is planned in isolation/individual element rather it considers overall service like the management information tools, the architects, the technology, the service management process and the necessary measurements and metrics to ensure not only the functional elements are addressed by design but also that all of the management and operational requirement are addressed as fundamental part of the design and are not added as an afterthought.

Let us know in phrase about the important topics involved in Service Strategy.

4 P’s – You must have already heard about the 3 P’s but here comes the all 4 P’s which talks about People, Process, Products(Technology) & Partners(Suppliers).  It is very much self-explanatory, implementing ITIL is all about preparing, planning the effective and efficient use of the 4 P’s.

Service Design Package – It is the document defining all aspect of an IT service and requirement through each stage of its life cycle. It is an output of a service design one or more combined phase which goes as an input to Service Transition.

Service Level Management – The purpose is to ensure that all current and planned IT services are delivered to agreed achievable targets. It ensures that IT and customers have a clear and unambiguous expectation of the level of service to be delivered. It includes three types of agreements as mentioned below.

  • SLA – Service Level Agreement (between SP & Customer)
  • OLA – Operational Level Agreement (between Internal Team of SP with different customers)
  • Contracts – Underpinning (between SP & Supplier)

Service Level Agreement Monitoring – It charts the details performance against the SLA targeted together with details of any trend or specific actions being undertaken to improve service quality. The SLAM reporting mechanisms, intervals and reports formats must be defined and agreed with the customers.

Service Catalog Management – It maintains a single source of consistent information on all services currently being offered to customer. The objective is to reflect the current details, status, interfaces and dependencies of all services that are being run or being prepared to run, in the live environment according to the defined policies.

Availability Management – It ensures the level of availability delivered in all IT services meets the agreed availabilities needs or service level targets in a cost-effective and timely manner. It includes two types of activities called Reactive (Monitoring/Measuring/Analyzing) & Proactive (planning/designing).

FARMS – You better know the full form for this as Fault tolerance, Availability, Reliability, Maintainability and Serviceability.

Information Security Management – This is to align security with business security and ensure that confidentiality, integrity and availability of the organization assets, information, data & IT services always meets the agreed needs of the business

Supplier Management – It is to obtain value for money from suppliers and to provide seamless quality of IT service to business by ensuring that all contracts and agreements with the suppliers support the needs of the business and that all suppliers meet their contractual commitments.

Capacity Management – It is to ensure the capacity of IT service and the IT infrastructure meets the agreed capacity and performance related requirement in a cost effective and timely manner. It is concerned with meeting both the current and future capacity and performance needs of the business.

IT Continuity Management – It is to support the overall business continuity management process by ensuring that by managing the risks that could easily affect IT services, the IT service provider can always provide minimum agreed business continuity related service level.

Business Impact Analysis – The purpose is to quantify the impact to the business that loss of service would have. This could be hard (financial loss) or soft impact (public relation). The BIA will identify the most important services to the organization and will therefore be a key input to the strategy, it is also called as business justification.

Design Coordination – It coordinates all design activities across projects, changes, suppliers and support teams and manages schedules, resources and conflicts where required.

See you soon in the next and final part of this series…stay tuned!

Posted in Documents | 1 Comment

Understanding Exchange 2013 Mail Flow – ExchangeMs.In

With Exchange 2013 now there is no HUB Transport Role in other words it is divided and merged between Client Access & Mailbox Server Role. There are very good reasons and benefits too behind the architectural changes but at the same time Exchange Admins has to update its knowledge with this new mail flow concept.

While going through the TechNet documentation I found it to be interesting and enjoyed going through each topics on mail flow, thought of sharing the knowledge of basic mail flow how it works in an Exchange 2013 via this article.

There are three main services with regards to mail flow in Exchange 2013 as mentioned below:

  • Front End Transport Service – This is runs on CAS Servers and acts as a stateless proxy server. It takes care of all the inbound and outbound external SMTP traffic for Exchange 2013 Organizaiton
  • Transport Service – This service runs on Mailbox Servers and is virtually identical to the HUB Transport role in previous version. This service handles all the mail flow for the organization
  • Mailbox Transport Service – This service runs on Mailbox Server and consist of two separate types: the Mailbox Transport Submission & Mailbox Delivery Transport Service. Since Transport service never communicate directly with mailbox database, the task is now handled by the Mailbox Transport Service.

Below is the mail flow topology diagram of Exchange 2013 Organization @High Level

Mail Flow

 

 

Scenario A – User@externaldomain.com sends email to UserA@exchangems.in

  1. Externaldomain.com SMTP Server queries internet domain exchangems.in for MX record and it sees pointed to the firewall listening on port 25
  2. Since we have Smart Host setup in the DMZ network – the email is forwarded to the CAS server behind the DMZ network on port 25
  3. Exchange 2013 CAS accepts the email using receive connector (by default it has anonymous option checked unlike its previous version Exchange 2007/10).
  4. Exchange 2013 being stateless doesn’t hold the email which then proxies the SMTP request using Front End Transport Service to Transport service (Equivalent to MS Transport Service in legacy version – 2007/10) on the Mailbox Server role.
  5. The Transport service on Mailbox Server then categorizes the email, performs message content inspection, etc. Since it doesn’t connects directly to Mailbox database it sends email to the Mailbox Transport Service over port 25
  6. The Mailbox Transport Service is again divided into two service out of which Mailbox Transport Delivery service receives SMTP message from Transport service
  7. The Mailbox Transport Delivery Service using Store Driver would connect to the mailbox database via RPC and deliver the e-mail to the mailbox database

Note: If the mailbox is in different mailbox server DB – The message received at Transport service would route the email to Transport Service on the destination Mailbox Server via SMTP on port 25 and the process continues from Transport service to Mailbox Transport Delivery service as mentioned above.

Scenario B – UserB@exchangems.in sends email to User@externaldomain.com

  1. The Mailbox Transport Submission service using Store Driver would connect to the mailbox database via RPC and pull the e-mail
  2. The Mailbox Transport submission would try to resolve the recipient to its mailbox database and look up for the delivery group
  3. The Transport service on the mailbox server will receive the e-mail sent over SMTP from the Mailbox Transport Submission service using its default receive connector (on port 25)
  4. The categorizer then picks up message from submission queue and since it is external domain (outbound to internet) the message is routed to the Front End transport service on CAS server using the send connector
  5. Since we have configured the Smart Host on the Send Connector, the CAS Server Front End Service would route the email to Smart Host on port 25
  6. Smart Host would then query on the internet for the MX record of externaldomain.com for message delivery

Note: If the recipient was of the same organization(UserA@exchangems.in) but on the other mailbox server database, the transport service instead of forwarding message to CAS server frond end service it would directly connect to other mailbox server transport service on port 25 and the process continues as above mentioned in scenario A delivering message to database.

 

For the in-depth process and its working please refer TechNet Documentation.

Posted in Exchange Servers | 29 Comments

Setting Up Microsoft Exchange 2013 with Windows Server 2012 for ExchangeMs.In Domain

This articles explains about an IT Organization (ExchangeMS.In) who wants to deploy Exchange 2013 Server on premises as their email solution and I have tried to document step by step with the minimal setup required including security as a solution/guidance.

Currently as there is no service pack 3 available for Exchange 201o and RollUp for Exchange 2007 SP3 there is no official documentation on migration and coexistence scenarios however the companies who wants to go for Exchange 2013 have to setup in an AD where no legacy Exchange versions are installed.

The documents would seem to be more of understanding installation, configuration & implementation of Exchange 2013 setup rather than actual end to end solution to meet the company’s requirement.

If time permits me to extends this articles series further the company might grow rapidly to have setup High Availability & Site Resilience solutions.

For this lab I have used three virtual machines of good configuration on Dell 15 R Laptop (8 Core I7 CPU / 1TB / 16GB RAM) and it seems to be running smoothly having left resources for my other Exchange 2010 Labs. (1 core / 50 GB HDD / 3GB RAM for each VM)

Below is the high level diagram of the current setup:

Image

1. Installing & Configuring OS Windows Server 2012 Datacenter for DC_1

  • This document will help in installing Windows Server 2012 OS for Domain Controller

2. Installing & Configuring DNS for Domain ExchangeMs_2

  • Installing DNS server role on Standalone server
  • Creating and configuring Forward & Reverse lookup zone for DNS ExchangeMS.in

3. Configuring OS Pre-Requisite to Promote as Domain Controller_3

  • Setting up pre-requisites before installing AD DS role

4. Installing & Configuring Active Directory Domain Services_4

  • Installing Active Directory Domain Services Roles
  • Promoting standalone server as Domain Controller
  • Configuring DNS Domain ExchangeMS.in to be Active Directory Integrated

5. Installing & Configuring Active Directory Certificate Services_5

  • Installing Active Directory Certificate role and its services
  • Configuring Active Directory Certificate services. (CA / CA Web Enrollment / Web Service)

6. Installing & Configuring Windows Server 2012 OS for Exchange 2013 Mailbox Server_6

  • This document will help in installing Windows Server 2012 OS for Exchange 2013 MBX server

7. Installing Pre-requisite for Exchange 2013 Mailbox Server Role_7

  • Installing required windows features
  • Installing UcmaRuntime setup API 4.0
  • Installing Microsoft Filter Pack 2.0 / SP1

8. Installing & Configuring Windows Server 2012 OS for Exchange 2013 CAS server_8

  • This document will help in installing Windows Server 2012 OS for Exchange 2013 CAS server

9. Configuring Pre-requisite for Installing Exchange 2013 CAS Server Role_9

  • Installing required windows features
  • Installing UcmaRuntime setup API 4.0

10. Pre-requisites & Preparing Active Directory forest and domain for Exchange 2013 installation_10

  • Installing RSAT tool on EXMB01 (Since the server doesn’t have this tool installed)
  • Configuring AD user member of Domain/Schema/Enterprise Groups
  • Preparing Schema for Exchange 2013 installation
  • Preparing Active Directory for Exchange 2013 Installation
  • Verifying successful Schema & AD Preparation

11. Installing Exchange 2013 Mailbox Server Role_11

  • Using media installing Exchange 2013 Mailbox Server Role step by step via GUI

12. Installing Exchange 2013 CAS Server Role_12

  • Using media installing Exchange 2013 CAS Server Role step by step via GUI

13. Creating & Configuring Certificates for Exchange 2013 CAS Servers using Internal Root Certifcate Authority_13

  • Creating Exchange Certificate request using Exchange Admin Center
  • Submitting CSR to internal Certificate authority server
  • Completing the pending request on CAS server
  • Assigning Exchange Certificate to web services (IIS)
  • Exporting Exchange Certificate to install on Mailbox Server
  • Importing Exchange Certificate on Mailbox Server role

14. Creating Exchange 2013 Recipients_14

  • Creating Mailbox
  • Creating Mail Contact
  • Creating Exchange Distribution Group
  • Creating Public Folder Mailbox (Master Hierarchy)
  • Creating Public Folder
  • Creating Mailbox Database
  • Verifying all the creations using Exchange Admin Center

15. Exchange 2013 Post Installation Configuration_15

  • Creating and Configuring Send connectors for External Mail Flow
  • Verifying default / adding additional accepted domain
  • Verifying default / adding additional email address policies
  • Creating C Name record / PTR for accessing Exchange Services (EWS/OWA/ECP/EAS/PowerShell)
  • Configuring Exchange External Virtual Directories (EWS/OWA/ECP/EAS/PowerShell)
Posted in Exchange Servers | 8 Comments

Discontinued Features in Exchange 2013 from Exchange 2010

Exchange Roles

  • HUB Transport Role :The HUB Transport role is longer in Exchange 2013 and is replaced with the Transport Service on Mailbox Server and the Front End Transport Service on CAS server.
  • Unified Messaging Role :The Unified Messaging is longer in Exchange 2013 and is replaced with the Microsoft Exchange Unified Service on both Mailbox and the CAS server.

Management Features

Exchange Management Console and Control Panel is now replaced with Exchange Administrative Console in Exchange 2013.

Email Clients

  • Outlook 2003 – In Exchange 2013 the use of autodiscover is required and since Outlook 2003 doesn’t use Autodiscover hence it is not supported.
  • RPC/TCP – It is now replaced with RPC/Http

Transport

  • Linked Connectors – In Exchange 2010 we used these connectors to link send connector to receive connector which is no longer available in Exchange 2013.
  • Anti-spam Agent – In Exchange 2010 you could manage Anti-spam agent when enabled via both Exchange Management Console as well as Exchange Management Shell however in Exchange 2013 when you enable you can only manage via Exchange Management Shell. (You cannot manage using EAC)
  • Connection Filtering – In Exchange 2010 when you enable Anti-spam agent it was the only attachment filtering agent that wasn’t available but in Exchange 2013 when you enable Anti-spam agent both the attachment filtering agent as well as connection filtering agent is not available.

Exchange Retired Tools

  • Exchange Best Practice Analyzer – used to analyze whether the configuration was in line with MS best practices
  • Mail Flow Troubleshooter – used to troubleshoot common mail flow problems
  • Performance Tool – used to collection performance report for the Exchange Server
  • Performance Troubleshooter – used to locate and identify performance related issues that could impact Exchange Servers
  • Routing Log Viewer – used to help viewing routing topology from a routing log file

Messaging and Compliance

  • Managed Folders – In Exchange 2010 we used Managed folders for Messaging Retention Management which is now longer supported instead we have to use retention policies.
  • Port Managed Folder Wizard – Since there is no support for Managed folders to create retention tags we now have to use New-RetentionPolicyTag using Exchange Management Shell.

 Outlook Web App features that Isn’t Supported in Exchange 2013

  • Shared Email Folders – Using this feature we could access other mailbox shared folders
  • Distribution List Moderation – Used to approve/reject email sent to a specific DL group
  • Spell Check – OWA now relies on the web browser spell check services
  • Reading Pane @bottom of the Page – There is no display of reading pane at bottom of the page using OWA
  • Reply to Embedded Emails – Users won’t be able to reply emails that are sent as attachments.
Posted in Exchange Servers | Leave a comment

Codenamed Windows Server 8 – AD Domain Services

Windows Server 2012 is already out and below are some of the topics you want to have real quick look and learn(if you aren’t aware).

Code

There is lot of changes in this versions but the fundamentals are same as usual from the very beginning since Windows 2000. Over a decade lot of new features have been added and great improvements for its scalability and security.

Below are few document prepared on Active Directory Domain Services – hope you all will enjoy 🙂

Preparing Forest & Domain on 2008 R2 AD to support Server 2012 Active Directory Domain Services

Promoting Windows Server 2012 as Additional Domain Controller for existing Windows 2008 R2 DC

Transferring Operation Masters (also called Flexible Single Master Operations) from Windows 2008 R2 DC to Server 2012 ADC

Demoting Windows 2008 R2 domain controller from the domain contoso.com having Server 2012 as ADC

Adding replica of Server 2012 DC using Install From Media Option

Installing and configuring Windows Server 2012 Active Directory Certificate Services (Certification Authority Only)

Demoting Windows Server 2012 Active Directory Domain Services

Posted in Active Directory | Leave a comment