Archive for November, 2009

Cannot create SQL database during SCCM 2007 SP1 installation

Today I’ve installed a new System Center Configuration Manager 2007 environment. During the installation, I get the following error “The site server computer’s machine account does not have Administrator’s previleges on the SQL Server selected for site database installation. To install a Configuration Manager site, all servers must be in an Active Directory domain and the site server’s machine account must have Administrator’s privileges on the SQL Server”.

To fix this problem, you’ll need to do the following steps:

1.) On the SQL Server, right-click My Computer and select Manage to open the Computer Management console
2.) Expand the Local Users and Groups node and select Groups
3.) Double-click Administrators in the right-hand pane of the Computer Management console
4.) Click the Add… button to open the Select Users, Computers and Groups dialog box
5.) Click the Object Types… button and ensure Computers is selected in the Object Types dialog box. Click OK to return to the Select Users, Computers and Groups dialog box
6.) If the From this location field in the Select Users, Computers and Groups dialog box does not show the domain that the Configuration Manager site server is in, click the Locations… button and select the correct domain
7.) In the field labelled Enter the object names to select, type the computer name of the Configuration Manager site server. Click the Check Names to confirm that the name has been recognised
8.) Click OK

SCCM_DB_01    SCCM_DB_02    SCCM_DB_03

SCCM_DB_04

Exchange 2007/2010 and dynamic Distribution Groups

With dynamic distribution groups, group membership is determined by the result of an LDAP query. You can create a dynamic distribution group and define the query parameters by completing the following steps:

1.) Open the Exchange Management Console
2.) Navigate to Recipient Configuration, Distribution Group
3.) Click New Dynamic Distribution Group
4.) Give up  a Name and Alias
5.) Change the Filter settings. In this example I’m using the Active Directory attribute Department
6.) Give up the Filter Condition. To see a preview of all the effected users, click Preview
7.) Click New to finish the last step

E2K10_DDG_01    E2K10_DDG_02    E2K10_DDG_03

E2K10_DDG_04    E2K10_DDG_05    E2K10_DDG_06

E2K10_DDG_07

Update Rollup 1 for Exchange Server 2007 Service Pack 2

Update Rollup 1 for Exchange Server 2007 Service Pack 2 (SP2) resolves issues that were found in Exchange Server 2007 SP2 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP2 customers.
For a list of changes that are included in this update rollup, see KB971534.

This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.

Download details Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534)

Exchange Server 2010 released

Microsoft announced the release of Exchange Server 2010 today at Microsoft TechEd 2009 in Berlin. The release marks the first version of Exchange Server designed for the cloud, and provides customers the option of deploying it on-premises, the way Exchange Server has always been deployed, or use it as a service hosted by Microsoft, or a combination of the two.

This version of Exchange is just really cool stuff!!

For more information, you can read this article on msexchangeteam.com
Exchange_2010_RTM

TechEd 2009 @ Berlin….here we come!

This sunday I’ll fly to Germany (Berlin) for the TechEd 2009! I’m looking forward to see high level presentations, doing some hands-on labs and watch great demonstrations! Here’s a list of some nice speakers:

Robert Beauchemin
David Chappell
John Craddock
Tess Ferrandez
Rafal Lukawiecki
Andy Malone
Mark Minasi
Mark Russinovich
Ilse Van Criekinge
Maciej Pilecki

See you in Berlin…in the new efficiency!

TechEd_2009_Berlin

Supporting Exchange 2007 on Windows Server 2008 R2

This week, Kevin Allison posted a hopefull article on the Microsoft Exchange Team Blog. Let’s have a look on that…

——————————————-
We always talk about listening to customers and sometimes this is written off by many as ‘marketing speak’.  In fact, we do take feedback seriously and no input is more important to our engineering processes than your voice.

Earlier this year we made a decision in one direction, and due to the feedback we have received on this blog and elsewhere, we have reconsidered. In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2. We heard from many customers that this was important for streamlining their operations and reducing administrative challenges, so we have changed course and will add R2 support.  We are still working through the specifics and will let you know once we have more to share on the timing of this update.

So, keep the feedback coming.  We are listening.

Kevin Allison
GM Exchange Customer Experience

——————————————-

So within a copple of months, there will be proberly full support for Exchange 2007 on Windows Server 2008 R2! This will be a great start of the new year 2010 ;)

Changing OWA time out on an Exchange 2007 Server

By default the Outlook Web Access (OWA) will automatically time out for the security purposes. This feature has been designed to restrict unauthorized access to any mailbox when the user is using a public or shared computer. You can select this option before you logon to your mailbox.

OWA_TO_01    OWA_TO_02

Though this feature is good for security reasons it may be annoying for many users who use OWA regularly and they may not want to enter the password several times after the time out. This can settled down with a simple registry tweak on the CAS server that runs your Internet facing OWA site. This can be done by following registry modification:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOWA
Name: PublicTimeout
Type: DWORD
Value: {value in minutes} (This value is 15 minutes by default)

The above suggestion applies only when the user selects the Public Computer option from the OWA logon screen. For the user who select the Private Computer from the logon screen you might want to modify:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeOWA
Name: PrivateTimeout
Type: DWORD
Value: {value in minutes} (This value is 8 hours by default)

If you don’t see the DWORD values named, PublicTimeout and PrivateTimeout then you have create then manually.

How to: Migrate from Exchange 2007 SP2 to Exchange 2010

In this article I’m going to migrate my Exchange 2007 SP2 environment to Exchange 2010. This is my environment:

Server 1
Name: SRV-E2K10DC-01
OS: Microsoft Windows 2008 R2 x64
IP: 172.16.1.10
Roles: DC/DNS

Server 2
Name: SRV-E2K7-01
OS: Microsoft Windows 2008 SP2 x64
IP: 172.16.1.11
Roles: Exchange 2007 SP2 HT/CAS/MBX

Server 3
Name: SRV-E2K10-01
OS: Microsoft Windows 2008 R2 x64
IP: 172.16.1.12
Roles: Exchange 2010 HT/CAS/MBX

Domain FQDN: EXCHANGE.LOCAL
Forest Functional Level: Windows Server 2008 R2
Domain Functional Level: Windows Server 2008 R2

1.) First I’ve installed all the prerequisites for Exchange 2007 SP2 on server SRV-E2K7-01
Command: servermanagercmd -ip exchange-typical.xml
2.) Install all the prerequistes for Exchange 2010 on server SRV-E2K10-01
Command: servermanagercmd -ip exchange-typical.xml
3.) After rebooting server SRV-E2K7-01, you can install Exchange 2007 SP2
4.) After succesfully installing Exchange 2007 SP2, you can install Exchange 2010 on server SRV-E2K10-01
5.) Open the Exchange Management Console on server SRV-E2K7-01
6.) I’ve created some user account (100) and all mailbox enabled
7.) Open the Exchange Management Console on server SRV-E2K10-01
8.) As you can see, all the mailboxes are vissible!
9.) The next step is to move the mailboxes from Exchange 2007 to Exchange 2010
10.) Return to the Exchange 2010 server and open the Exchange Management Console
11.) Navigate to Recipient Configuration, Mailbox
12.) Select the mailboxes you want to migrate and right-click
13.) Choose “New Local Move Request”
14.) Select the new Mailbox Database
15.) Wait until the users are migrated to the new Mailbox Server
16.) Select all the completed move requests and select Clear Move Request

The users are now migrated to the new Exchange 2010 environment. In the next post we are going to de-install the Exchange 2007 environment.

E2K7_E2K10_01    E2K7_E2K10_02    E2K7_E2K10_03

E2K7_E2K10_04    E2K7_E2K10_05    E2K7_E2K10_06

E2K7_E2K10_07    E2K7_E2K10_08    E2K7_E2K10_09

E2K7_E2K10_10    E2K7_E2K10_11    E2K7_E2K10_12

E2K7_E2K10_13    E2K7_E2K10_14