John Yassa's Blog

Home » 2014 » February

Monthly Archives: February 2014

Exchange Server 2013 Service Pack 1 is released

Exchange Server 2013 Service Pack 1 (SP1) is now available for download! Please make sure to read the release notesbefore installing SP1. The final build number for Exchange Server 2013 SP1 is 15.00.0847.032.

Upgrading to SP1/Deploying SP1

As with all cumulative updates (CUs), SP1 is a full build of Exchange, and the deployment of SP1 is just like the deployment of a cumulative update.

Active Directory Preparation

Prior to or concurrent with upgrading or deploying SP1 onto a server, you must update Active Directory. These are the required actions to perform prior to installing SP1 on a server.

1. Exchange 2013 SP1 includes schema changes. Therefore, you will need to execute the following command to apply the schema changes.

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

2. Exchange 2013 SP1 includes enterprise Active Directory changes (e.g., RBAC roles have been updated to support new cmdlets and/or properties). Therefore, you will need to execute the following command.

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Server Deployment

Once the above preparatory steps are completed, you can install SP1 on your servers. Of course, as always, if you don’t separately perform the above steps, they will be performed by Setup when you install your first Exchange 2013 SP1 server. If this is your first Exchange 2013 server deployment, you will need to deploy both Client Access Server and Mailbox Server roles in your organization.

If you already deployed Exchange 2013 RTM code and want to upgrade to SP1, you will run the following command from a command line.

setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms

Alternatively you can start the installation through the GUI installer.

For More Info : http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx

Change the UPN Suffix (User Principle Name) for Users in domain contorller

Below is a PS1 script to modify the UPN Suffix for Users inside OU

#Replace with the old suffix

$oldSuffix = ‘Existing UPN Domain name’

#Replace with the new suffix
$newSuffix = ‘New UPN Domain name

#Replace with the OU you want to change suffixes for
$ou = “LDAP Path of the OU that contain the users”

#Replace with the name of your AD server
$server = “Domain Controller name”

Get-ADUser -SearchBase $ou -filter * | ForEach-Object {
$newUpn = $_.UserPrincipalName.Replace($oldSuffix,$newSuffix)
$_ | Set-ADUser -server $server -UserPrincipalName $newUpn }

How to Install Updates on Exchange Server 2010 CAS Arrays

In our case we will assume that we are using Windows load balance and not H/W load balance

Preparing the NLB Cluster for Updates:

The first thing is to remove this server from load balance and make sure there is no active session on that server
1- Issue a Drainstop command to the server (By this you are stop accepting any new session on that server)

nlbdrainstop01

 

When the server has no more active connections it will be in a stopped state

nlbdrainstop02

 

2- Set the default state of the server to Stopped.  This will prevent it from automatically starting and accepting client connections after any reboots that the updates require, to allow you time to verify the updates were successful first before rejoining the NLB cluster.

nlbdrainstop03

 

Stop Conflicting Services:

Stop any service that affect and contact Exchange like (forefront – Antivirus – Anti spam – Backup Solution)

Updating the Server:

Run the setup.exe file and wait till completes
Restart the server

Verifying the Update:

1- Run the command Get-ExchangeServer to get the version of the Exchange server ( Version 14.3 refer to Exchange 2010 SP3)

Confirm

 

2- Run the command get-service *exchange*

getservice


Returning the Server to Production:

1- Return all the third party services that communicate with Exchange to its normal status (Anti spam – Antivirus – Backup – …….)

2- Start the NLB

nlbstart01

 

Set the default status of the NLB to be started

nlbstart02


%d bloggers like this: