Service Pack

All posts tagged Service Pack

Exchange 2010 SP3 available soon

It looks like we can expect Exchange 2010 SP3 very soon. There are a lot of rumors on going on Twitter and Facebook the Microsoft Downloads already contains the Exchange 2010 SP3 UM Language Pack.

A question by Exchange fan Hakim Taoussi that it has been announced but not available:

 

Hakim_Taoussi

 

Was answered by Bharat Suneja from the MsExchange team with the following tweet:

 

Bharat_Suneja

So for those who have been waiting till they can migrate to Exchange 2013 from Exchange 2010 you should be able soon. If it is wise to do it, well read the several blog posts from Exchange guys and then rethink your decission again.

In Exchange 2010 SP1 beta you will find a lot of changes. In this tutorial I will have a closer look at the Unified Messaging Role from Exchange 2010 SP1. 

Before starting the installation of the UM role you will need to ensure that you have installed the two prerequisits mentioned below: 

This is one of the new things in Service Pack 1, in the RTM version this was not necessary. In RTM you only needed to install the prerequisits using the Excahnge-UM.xml file. The files mentioned above are additional to this. Please pay attention when installing the Unified Communications Managed API 2.0 it might look the installation is done very quickly. But what is only done during the installation is extracting the files to C:\Microsoft UCMA 2.0 RuntimeInstaller Package\amd64 here you can find the file  SetupUcmaRuntime which does perform the installation of UCMA 2.0. 

 

After the files have been installed you can start the installation of Exchange and select the Unified Messaging Role. Besides selecting the Unified Messaging Role don’t forget to place a checkmark before automatically install Windows Server Roles and Features required for Exchange Server. This new option will install all Windows Server Roles and Features necessary for the installed Exchange role. 

Once installed it’s time to start the Exchange Management Console and selecting the UM Server which can be found under the organizational configuration tree. On the organizational configuration level you can configure the following things: 

  • dial-plan
  • gateway
  • hunt group
  • auto attendant
  • UM policy

Let’s begin with creating the dial-plan. First we need to specify the name, the length of the extensions, URI type, VOIP Security and Country/Region code. Depending on what kind of implementation you are performing you might chose other options for the URI type and VOIP security. In this case the dial-plan will be used to attach the Exchange UM server to an OCS 2007 R2 environment. 

 

In the next step we will need to add the servers attached to the dial-plan. In this case it’s only one server but in an environment where you’ve got multiple UM servers you can easily add them all here. 

Before the dial-plan is created you will get an overview of the settings which will be used. When pushing the New button the dial-plan will be created. 

When the dial-plan is created you will see a warning. This warning is the result of the default configuration of the UM server. The UM Server is default configured to accept traffic using TCP. Since we configured the dial-plan to accept only traffic which is secured we will need to modify this option on server configuration level so that the server will accept TLS traffic. 

 

After the wizard has been closed you will need to get the properties of the dial-plan to configure the subscriber-access. This feature can be used by users to call their mailbox to, for example, check if new mails have arrived. Once you get the properties of the UM server select the subscriber access tab and add the extension which you would like to use fot this functionality. 

 

Next step in the process is to add the gateway to which the Exchange UM server will need to send it’s traffic to. 

We will only need to specify a name, IP-address of FQDN of the gateway and the dial-plan which may use this gateway. 

 

During the creation of the gateway a hunt group will be automatically created. In some cases it may be necessary to remove the hunt group and create a new one.  This because the pilot identifier will not be configured by default. If want to skip the creation of the hunt group don’t select a dial-plan and attach the gateway manually to the dial-plan. 

Default a UM Mailbox policy will be created during the creation of the dial-plan. With this policy you may not have to change things as the settings are OK for your organization. But if you like to make changes to the text of the message which is send to the users when they are UM enabled then modify the policy. 

Beside the text there are a lot of other settings which are defined by this policy. For example the pin policies which you would like to apply to users: complexity, minimum pin length and wrong pin attempts. 

Optional it’s possible to configure an auto attendant. This is an electronic operator which can transfer calls and play a menu to the caller with options which will transfer him/her to the correct department. 

 

The configuration at organizational configuration level is finished and so it’s to configure some things on server configuration level. Get the properties of the UM server and select the UM Settings tab. Change the value of the startup mode to TLS or Dual and press OK. 

A warning will be displayed that the Exchange UM service will need to be restarted and that you will need to verify that a valid certificate is assigned to the service. The certificate is important because we selected secure at the dial-plan. This will ensure that all traffic is secured using certificates for authentication. If an invalid certificate is used by one of the parties the communication will fail. 

 

If you decide to install the certificate later then you may have some issues with restarting the Exchange UM service. This because the self-signed certificate is not assigned to the Exchange UM service. 

Configuring UM can be dan a lot easier when using Powershell. Below you will find an overview of commands which you can use to create the configuration exactly as done via the GUI: 

New-UMDialplan -Name Utrecht -UriType SipName -NumberOfDigitsInExtension 3 -VoIPSecurity Secured -AccessTelephoneNumbers “110” -CountryorRegion 030 

New-UMIPGateway -Name “Utrecht VOIP Gateway”  -Address 192.168.1.250 -UMDialplan “Utrecht”   

New-UMAutoAttendant -Name Utrecht_AA -UMDialPlan Utrecht -PilotIdentifierList “+313012345100″ -SpeechEnabled $true 

Set-UMserver -identity “ex” -DialPlans “Utrecht” -UMStartupMode “TLS” 

If you like Powershell then I recommend to use it because configuring UM goes a lot faster.

New in SP1 are two additional expensions for the UM role, these can be found under tools in the Exchange Management Console:

  • Call Statistics
  • User Call logs

First the call statistics, this report utility can be used to generate overviews of calls which are processed by your Exchange UM server. This may be very usefull when you would like to get an overview of how much users will use the UM functionality of Exchange.

Besides to the overall overview you can generate reports per user using the user call log. In this overview you can for example see how much calls a user receives and which quality the call was. This may be very usefull when troubeshooting the quality of calls

But what are the other changes in SP1 when looking at UM:

  • you can assign a second dial plan to a user. In some scenario’s ut may be usefull to assign a second extenstions to a user.
  • cross-forest migration of UM-mailboxes is possible
  • UM Settings can be managed using the Exchange Control Panel
  • no support for Exchange 2010 SP1 in combination with Office Communication Server 2007

Remark: all features and screenshots mentioned in this article are based on the beta of SP1 and may change in the final release.

One of the new features in Exchange 2007 Service Pack 3 is the ability for users to change their password before logging in. Before service pack 3 a user who’s password had expired needed to call the helpdesk to reset their password or use another solution. With this new feature a user will be redirected to another page where he/she can change the password.

But how does this work? In the OWA directory, which you can find here: Exchange\ClientAccess\OWA, you will find a directory called auth. This directory contains several files which are used for login and logout. But besides these files there are two new files expiredpassword.aspx and exppw.dll.

Before you can use the new functionality you will need to make an adjustment in the registry of the CAS server. Go to the following location in the registry:

HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA

Create a new DWORD called ChangeExpiredPasswordEnabled and change the value of the key to 1. This should look the same like below:

During the logon (logon.aspx) a check is done if the password is expired and if this is the case the user will be redirected to expiredpassword.aspx.

Before the user can change his/her password he will first needs to specify the old password. Once the password has change the user will be redirected to his/her mailbox.

Exchange 2007 SP2

If everything goes OK Exchange 2007 Service Pack 2 will be released tonight and else tomorrow. That’s what a post from Paul Rowden (Release Manager Exchange Development) will tell you. Paul posted the text below:

Additionally, Exchange 2007 SP2, which releases tomorrow will also contain the same AD schema extensions as Exchange 2010.

So now it’s just waiting for the links to be available but it won’t take long I think. Now SP2 will be released it’s officially supported to have Exchange 2010 RC can run in the same organization as Exchange 2007. One of the pre-requisits is that you need Exchange 2007 SP2. The SP will contain new schema extensions which are also used with Exchange 2010 RC.

Slipstreaming, it’s a known term that is known by pretty much people. With Windows OS client and server software and Office products it is a known proces. Why shouldn’t you integrate a service pack with the original installer, it will save you a lot of time.

With Exchange 2007 this is not possible anymore, you may think this is strange, this was my first reaction also. Then I searched further and discovered that slipstreaming is not necessary anymore. You just download the latest trail version from the Microsoft website and install it. When finished you will fill in the key and you are ready.

open

XP Sp3 available at the end of April

Windows XP cd

According to a lote of rumor sites SP3 vor Vista will be available at the end of April. Microsoft has not confirmed this but tells that they are trying to get it ready before in the first half of 2008. On the internet you can download many beta’s but Microsoft does not recommend to install them. The funniest is that you can read the release notes for SP3 since the begin of this month and RC2 can be downloaded from the Microsoft site. When you are looking further in the release notes they appear to be for RC2 and not for the official release so the title of the download is not really clear. RC2 contains a few new features: Network Access Protection, Black hole router detection, Enhanced security for Administrator and Service policy entries and Windows Product Activation. This last feature is also available in products such as Vista, Windows 2008 and Office 2007. You can install the product without a key and then use it for a short period just like a trial.

Vista SP1 available

Windows Vista SP1 

Last night SP1 for Vista is release for all users. The servicepack is not available for all languages only: Engels, Frans, Spaans, Duits en Japans (Wave 0) are included. Microsoft has announced that some users can’t install the servicepack if they have specific drivers installed. There are some issues with drivers from Realtek, Intel, Conexant and a few other vendors. When the dutch version will be available is not announced.

download

SP1 blocks securitysoftware

Bitdefender

Microsoft has release a list with programs that may not work or lose functionality after installing SP1. Microsoft recommands to have a look at this list before installing SP1. Software such as BitDefender and Zone Alarm Security Suite may not work anymore after the installation of SP1. Microsoft tells on their site that if you have this issues you need to contaact the vendor of the software. Most vendors who are listed have brought out a patch for their software to get it working again.

Vista SP1 keeps rebooting

Vista SP1

Microsoft has found a problem which be the result of installing Vista SP1. It looks like the issue only happens with Vista pc’s who don’t have some patches installed. Last week Microsoft has released this patches last week. According to Microsoft the problem is that some systems “think” their is an update downloaded which is not there yet. Microsoft advises to wait with installing SP1 when you don’t have installed all patches.

Vista SP1 ready at 4 February ??

Vista SP1

According to some sites on the internet SP1 for Vista should reach the RTM status on 1 February. Microsoft denies the rumor. The servicepack will be relaased in 2 phases: Phase 1: contains English, French, Spanish, German and Japanese. Phase 2 will be brought out 2 weeks later and will contain all the languages.