Exchange Administration Center ( EAC )

EAC is web-based management console in Exchange 2013 which is replaced EMC in Exchange 2010.  The MMC base console used to be slow when it loads and new business logic in Exchange 2013 forced to have new EAC in my opinion. Most of us,  most often appreciate new futures and try to adapt them as quick as possible. When certain things are done in certain way over years and people get used to it, it could be bit disappointment to some of you out there to see brad new management interface.

So my recommendation is, forget about GUI if you are going to stay in Exchange Server business (-: , learn and use PowerShell and who knows next version we might not even get EAC (-: , pure PS to manage next generation of Exchange Server.

To get to EAC this is what you have to insert into your browser ( from your CAS Server or replace the local host with CAS Server FQDN or IP Address)

https://localhost/ecp

Now this will give you EAC

If you are in Co-existence with Exchange 2010 , same URL wont work for you , so need to use this one

ECP= Exchange 2013

https://localhost/ecp/?ExchClientVer=15

ECP= Exchange 2010

https://localhost/ecp/?ExchClientVer=14

Now if you miss old console and keep cursing things as you get used to EMC here is a nice trick might be able to lessen your pain (-: , yehh I hear you….

Create custom MMC , see the video , I have also added ADUC and ADSIEDIT into my console. I wish at the least MMC console was bit more flexible to do more with it.

http://technet.microsoft.com/en-us/library/jj150562.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 2013 Surviving Server Roles and Business Logic

In exchange 2010 we do have 5 Server roles and the business logic build in middle tier, which means MAPI request goes to HLB ( if exists ), from there is goes to CAS Servers in Exchange 2010 Architecture, then the Exchange 2010 CAS start talking to Exchange 2010 MBX Server. The process in Exchange 2013 has changed, the business logic got moved into MBX Server role, while Exchange 2013 supports RPC/HTTP only dropping support for RPC/TCP. This means MAPI client will use RPC packets wrapped inside the HTTP to talk to their respected MBX Server.

Some of the compelling futures build into Exchange 2013……

• Exchange 2013 is much simpler to deploy , less servers roles, simple name space and better site resilience support.
• Exchange 2013 introduces huge cost saving by offering faster, and smarter messaging application.
• Exchange 2013 does have built in "application awareness" , new Exchange 2013 Application can detect and fix most of the problems automatically while the service continuity is not interrupted, ( much better seamless end user experience)

 

IOPS Reduction !!!!

This translate better performance obviously and cost saving, Faster the application is, better disk utilization and usage will be, allowing low end disk to be used and utilized by Exchange 2013.

Comparing exchange 2013 IOPS with some of the previous versions of Exchange Server

Exchange 2003---------------------------->95.5% IOPS reduction ( compare to Exchange 2013 )

Exchange 2010----------------------------->50-70% reduction in IOPS ( compare to Exchange 2013 )

 

CAS	Client Access  ( Available Role in Exchange 2013 )
HTS	Hub Transport ( Combined into CAS Role )
MBX	Mailbox    ( Available Role in Exchange 2013 )
UM	Unified messaging ( Combined into CAS & MBX Roles)
EDGE	Edge Transport Server ( depreciated !!!! )

 

In Exchange 2013 the Server Roles do have major reduction

CAS	Client Access Server  Role
MBX	Mailbox Server Role

 

CAS Server Role

Domain joined Server ( not placed in DMZ ) existed within the ADDS name space. Provides Layer4  (transport) Load balancing

• Session affinity functionality got moved into CAS Server role.
• CAS Server Light weight protocol proxy Server
• Exchange Aware proxy Server, supports proxy and redirection

 

 

Here where you can find more information in regards to exchange 2013…

http://technet.microsoft.com/en-us/exchange/fp179701.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 2013 and Server Roles

One of the biggest surprise in Exchange 2013 is the reduction on the server roles. I remember days when Exchange server had to do all in once ( Exchange 5.5) later version of Exchange Servers 2007 and 2010 had server roles separations , the major roles ( HTS, CAS and MBX) Hub transport, Client Access, and Mailbox , also ( UM and EDGE) Unified messaging and Edge Server roles and when the most latest and greatest version Exchange is almost on the way ( it is listed in MSDN for download today) out Exchange 2013 let's take a look at the server roles…

• CAS ROLE ( Client Access Server)
• MBX ROLE ( Mailbox Server )

That is it, there will be no more roles, much simpler and efficient in a way and the future best practices as far as deploying roles may change , and all in one deployments might be recommended officially ( we will see (-: how that goes )

What happen to HTS , UM and EDGE roles ? The HTS ( Hub transport role) has been distributed in between CAS Server and MBX Server roles see below

UM role story is the same, so does EDGE, UM and EDGE roles are not there anymore (-:

I will get into more details in remains these two roles and their functions…..

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)

Iphone iOS6 , Exchange 2010 Calendar Issues ………..

If you have recently upgraded iOS6 and your IPhone devices are having issues have  a look, the issue mentioned in KB2768774 and remedy  is to “wait” (-: yes you have heard correctly , there has not been any fix for the issues described in the KB.

iOS6 devices erroneously take ownership of meetings

I will update the post as the workaround is available.

best

ocd

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)

CAS Array HLB or NLB

If you are planning or implementing  CAS Array and wondering what are the options for load balance your CAS servers here is quick reference to remember.

Options

• HLB ( hardware load balance ) solution, This is what is being recommended.
• SLB ( Software load balance) solution, This is also recommended.
• Windows NLB ( network load balancing) This is no longer recommended

If you have not see Rose Smith video presentation do not miss it , How Outlook connects to Exchange 2010 Client Access Server

The main reason why HLB & SLB  are recommended , these solutions provides “ Application awareness” and also managing CAS servers behind these type of deployment is very easy and efficient.

MAPI Request comes to HLB , HLB has CAS servers published within , Administrator easily can stop MAPI request going specific CAS server etc. These deployments are also far more stable and easy to configure IMO. I think we will see more official statement soon and expecting to see ending support recommendations to HLB with CAS in the near future.

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)

Server CORE Install GUI

Part#2 Changing Server Environment Switching to GUI and uninstalling it. This example we have installed initially Server 2012 Core, we will install GUI on top of Core 2012. One we have complete the task we will go back and un-install GUI. The new futures of Windows 2012 is incredible PowerShell is fun and easy to use. I really love to see “simplicity” backed up with PS power behind Server 2012.

From CMD.exe Type “start PowerShell”

Start PowerShell

From PS

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart

After reboot you will get GUI and its futures.

Now we will uninstall GUI

 

Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -Restart

 

Resource

http://technet.microsoft.com/en-us/library/hh831809.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)

Server 12 Core Configuration, Part 1 Configuring Basic

PART 1 Preparing Server 2012 CORE for Active directory installation…

After installing S2012 Core when you change your password, first thing you will see is CMD.EXE

Now we would like to jump into PowerShell and start configuring the S2012 Core to be additional domain controller into existing Active Directory Forest/Domain ( mix AD 2008R2 & AD 2012 )

In CMD window type "start Power Shell" and hit enter

Start Power Shell

Now we have PS window open if you like to open another PS window simply type same command

Sometimes it is hand to have two separate windows.

Start PowerShell

Now tape host name to see the current computer generic name , Now let’s start renaming our Server in my case I choose the name as "S2012Core"

Rename-Computer -NewName “S2012CORE” -Restart

*Tips, in PS, a lot of typing is involved, use the tab completion feature saves “tons” of time and makes command line “fun” to learn.

After reboot log back in and type host name

Now it is time to look at the NIC Card and configure it

Get-NetAdapter

 

 

Get-NetAdapter –InterfaceIndex 12 | rename-NetAdapter –NewName “Production”

See the new name

 

New-NetIPAddress –IPAddess 10.10.10.31 –DefaultGateway 10.10.10.1 –PrefixLength 24 –InterFaceIndex 12

*** Change the IP address to fit to your needs

Set-DNSClientServerAddress –interfaceIndex 12 –ServerAddress 10.10.10.30

Lets add  the server into Domain

Add-Computer –DomainName  r1.internal

***r1.internal is the Domain name I have, in the LAB , replace this to fit into your environment

Reboot the Server

ShutDown –r –t 5

Resources

• Manage a Server Core Server
• http://technet.microsoft.com/en-us/library/jj574205.aspx
• Windows PowerShell Support for Windows Server 2012
• http://technet.microsoft.com/en-us/library/hh801904.aspx
• Install or Uninstall Roles, Role Services, or Features
• http://technet.microsoft.com/en-us/library/hh831809.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)

Windows 2012 Server First look, good by DCPromo

Installing Server 2012 is pretty fast and easy, what may people will be finding pretty impressive the new Metro interface.

Metro-styled Control Panel is the new era for windows, and it may strike you as it does not look like any other versions of windows you may have known.

Now here are few recommendations to get you going, get familiar with managing Windows from command line

PS is your friend , to be honest if you have not skill in command line and you are in this line of work you better get the basic down. Upcoming versions of windows and applications such as Exchange is more command line less GUI integrated.

I will show you some of the simple , basic stuff you can use to get started,

Open PS,,,,,,,,,,

 

You can open most of the GUI you used to have from PS

Go to Control panel type control hit enter

Devmgmt.msc

From PS type Start PowerShell to invoke another window ( very handy)

Start PowerShell

start http://blogs.technet.com/b/exchange/

Use server manager to Add remove roles to your server,

DCPromo wont work from command line )-:

 

As you can quickly realize basic is still there , if you have promoted server to be domain controller in the past you should not have any hard time to hang up on new interface and to be honest , it looks pretty neat and useful competed to previous versions GUI presentation.

• What is new in Server 2012
• Install and Deploy Windows Server 2012
• Migrate Roles and Features to Windows Server 2012
• Secure Windows Server 2012
• Server Roles and Technologies in Windows Server 2012
• Management and Tools for Windows Server 2012
• Command-Line Reference for Windows Server 2012
• Windows PowerShell Support for Windows Server 2012

 

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 Clearing out all mail in the mail queues

 

Scenario:

Al of a sudden you have figured out there are thousands of messages are queued up on your Edge server and you have identified all these messages are spam etc.

End goal:

you need to delete all mails within the queue folder as quick as possible

On the Edge Server  Stop Transport Service

Get-Service MsExc*

Get-Service MsExc* |FL

Get-Service MsexchangeTransport

Stop-Service MsExchangeTransport

Start-Service MsExchangeTransport

once this is done drill down to this directory

Select everything and delete them

Once you re-start the transport service , the required files will be put in there and all queues will be cleared out

This is quick and dirty way of dealing with un-wanted mails if there are mails in the queues which you have business purpose you can be more sophisticated with this PS command

Remove Messages from Queues

http://technet.microsoft.com/en-us/library/bb123535.aspx

http://blogs.technet.com/b/exchange/archive/2010/10/27/removing-specific-messages-from-your-exchange-server.aspx

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)