Windows Essential Business Server Release Notes
Applies To: Windows Essential Business Server
These release notes address late-breaking issues and information about Windows® Essential Business Server software.
Copyright
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Internet Explorer, SQL Server, Forefront, Windows Server, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
Installing Windows Essential Business Server in a Windows Small Business Server Environment
If you are installing Windows EBS in an existing Windows Small Business Server environment, follow the steps in "Migrating from Windows Small Business Server 2003 to Windows Essential Business Server" at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=123374).
Credentials for running the Planning Wizard
If you plan to install Windows EBS in an existing Active Directory domain, the computer that you use to run the Windows Essential Business Server Planning Wizard must be joined to the domain. If you run the wizard by using an account that does not have sufficient privileges, you are prompted to type domain administrator credentials when the wizard connects to the Active Directory domain to save the planning data.
If you run the Planning Wizard on a Windows Server 2008 domain controller that holds primary operator roles, the wizard may prompt you for domain administrator credentials even when you are logged on to the computer with an account that is in the Domain Admins group. If the wizard cannot connect to the domain using your domain administrator credentials, you should try one of the following:
When prompted to connect to the Active Directory domain from the Planning Wizard, type the credentials for the built-in Administrator account (the default domain administrator account).
Cancel the wizard, and then start the wizard with elevated privileges. Right-click the icon or the shortcut for the Planning Wizard, and then click Run as administrator.
Cancel the wizard, and then log off the computer. Log on to the computer by using the built-in Administrator account. Start the Planning Wizard to complete the planning steps.
Additional information about preparing for the deployment of Windows EBS is available at the Microsoft Web site (https://go.microsoft.com/fwlink/?LinkId=122157).
Modify the Antivirus Engines that Are Enabled in Forefront Security for Exchange Server
The following antivirus engines are enabled by default in Forefront Security for Exchange Server in Windows EBS:
CA Vet
Microsoft Antimalware Engine
Norman Virus Control
Sophos Virus Detection Engine
You can enable other antivirus engines in Forefront Security for Exchange Server to scan e-mail messages and attachments. Ideally, you should use at least three engines, and you can select up to five engines.
To modify the virus-scanning engines that are enabled
Log on to the Management Server by using an account that is a member of the Domain Admins group.
Click Start, click All Programs, click Windows Essential Business Server, and then click Windows Essential Business Server Administration Console.
Click the Security tab, click E-mail anti-malware, and then in the tasks pane, click Start Forefront Server Security Administrator console.
In the Connect to Server dialog box, type the name of your Windows EBS Messaging Server, and then click OK.
In the Shuttle Navigator, click SETTINGS, and then click Antivirus.
In the list of scan jobs, click Transport Scan Job.
In File Scanners, select up to five antivirus engines, and then click Save.
Repeat steps 6 and 7 for Realtime Scan Job and Manual Scan Job.
Note
You can select and change the antivirus engines at any time.
Russian only: Incorrect mailbox alias created for Administrator mailbox
During installation of the Russian version of Windows EBS, in some cases an incorrect alias is created for the Administrator mailbox on the Messaging Server. Because of an issue in Exchange Server, an e-mail alias cannot contain Cyrillic characters. If Cyrillic characters are used to create the alias, the alias contains only question-mark characters. As a result, mail cannot be addressed properly to the mailbox.
This issue occurs if a new mailbox for the Administrator is created automatically during the installation of Windows EBS, either because a new domain is created or because the Administrator account in an existing domain does not have a mailbox.
To correct an erroneous e-mail alias that is created for the Administrator, change the mailbox alias in Exchange Server on the Messaging Server. You can do this by changing the properties of the mailbox in Exchange Management Console or by using the Set-Mailbox command in Exchange Management Shell.
For information about changing the properties of a mailbox, see Exchange Server Help: On the Messaging Server, in the Exchange Management Console, press F1.
In addition, you should configure the correct alias in Forefront Security for Exchange Server so that the Administrator receives e-mail notifications. You should make the following modifications for Forefront Security for Exchange Server on the Messaging Server:
Modify the ServerProfile value in the registry.
Configure administrative e-mail notifications in Forefront Security for Exchange Server.
Use the following two procedures to make these modifications.
Warning
Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
To modify the ServerProfile registry value
Log on to the Management Server by using an account that is a member of the Domain Admins group.
Click Start, click All Programs, click Windows Essential Business Server, and then click Windows Essential Business Server Administration Console.
Click the Computers and Devices tab, click the name of your Messaging Server, and then in the tasks pane, click Connect to computer. Type your credentials to start Remote Desktop Connection.
On the Messaging Server, start Registry Editor and navigate to the following node:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\Exchange Server
Change the value of ServerProfile to Administrator@YourDomainName.com.
Click OK, and then close Registry Editor.
To configure administrative e-mail notifications in Forefront Security for Exchange Server
On the Messaging Server, click Start, click All Programs, click Microsoft Forefront Server Security, click Exchange Server, and then click Forefront Server Security Administrator.
-or-
In the Windows EBS Administration Console, click the Security tab, click E-mail anti-malware, and then in the tasks pane, click Start Forefront Server Security Administrator console.
In the Connect to Server dialog box, type the name of your Windows EBS Messaging Server, and then click OK.
In the Shuttle Navigator, click REPORT, and then click Notification.
Click Virus Administrators, and then in the To text box, type a valid e-mail address for the Administrator. You can configure more than one recipient.
Repeat step 4 for the File Administrators, Worm Administrators, Content Administrators, and Keyword Administrators notifications.
For more information about e-mail notifications, see Forefront Security for Exchange Server Help: On the Messaging Server, in the Forefront Security Administrator console, press F1.
Forward E-mail to Other Subnets During Installation
E-mail is interrupted during the installation of Windows EBS when the existing mail server is not located on the same subnet as the Windows EBS servers. If the existing mail server is located on another subnet, you can enter the IP address for the router. This configures Security Server to communicate with the existing mail server and forward the e-mail during the installation.
When you are running the Installation Wizard, on the Set the internal IP addresses page, perform the following procedure to forward the e-mail.
To forward e-mail
On the Set the internal IP address page, click Manually configure the internal IP address.
In the Default Gateway text box, type the IP address of the router that spans the two subnets, and then click Next.
On the Set the external IP address page, select how you want the external address to be assigned. If you select Manually configure the external IP address, type the appropriate information in the IP address text box, the Subnet mask text box, and the Default gateway text box, and then click Next.
On the Choose an Administrator password page, in the Password text box, type the password for the local Administrator account on your Security Server. Then type the password in the Confirm password text box and click Next.
On the Set the e-mail gateway page, select I want to forward e-mail to this IP address during install, and then type the IP address of the existing mail server.
Finish the Installation Wizard.
Modify the WMI filter query to exclude Security Server
When you migrate from Windows SBS 2008 to Windows EBS, the installation of Security Server will fail during the Forefront Threat Management Gateway (TMG) installation if a Group Policy setting exists on Windows SBS 2008 that prevents disabling Windows Firewall. To change a Group Policy setting in Windows SBS 2008 to disable Windows Firewall, before you install Security Server, you must modify the Windows Management Instrumentation (WMI) filter query so that it excludes Security Server.
To modify the WMI filter query
On Windows SBS 2008, click Start, point to Administrative Tools, and then click Group Policy Management.
In User Account Control, click Continue.
Under Group Policy Management, expand the following in the console tree: Forest:<domain>, Domains, <domain>, WMI Filters.
Under WMI Filters, click Windows SBS Client, and then click Edit Filter.
In Windows SBS Client, click Edit, and then append the following text to the WMI query: and OperatingSystemSKU!=31.
In WMI Query, click OK.
In Windows SBS Client, click Save.
Close Group Policy Management.
Note
The installation of Security Server may also fail for other Windows operating system migrations if the administrator has modified a Group Policy setting to prevent users from disabling Windows Firewall. Before you install Security Server, locate all WMI filters that affect Windows Firewall settings and append the WMI query as described in the previous procedure.