The certificate enrollment page you are attempting to access cannot be used with this version of Windows. To enable Web certificate enrollment for clients running Windows Vista, your administrator must update all Windows CA Web enrollment pages.

This is due to an ActiveX control used by the web enrollment pages that has been deprecated in Windows 7 and Windows Server 2008.

To fix the issue install this hotfix from Microsoft on the Windows Server 2003 server that has Certificate Services installed.

Related posts:

• Exchange 2010 FAQ: How to Install the Exchange 2003 System Manager Tools
• Exchange 2010 FAQ: How Do I Install the Exchange 2010 Management Tools?
• How to Issue a SAN Certificate to Exchange Server 2010 from a Private Certificate Authority
• Exchange 2000 and Windows Server 2008 Domain Controllers
• Installing Exchange Server 2010 Pre-Requisites on Windows Server 2008

This article Update Required for Windows 2003 Certificate Services Web Enrollment for Windows 7/2008 Clients is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

They are currently running Exchange Server 2000 with Windows Server 2000 domain controllers, and wish to transition to Exchange Server 2007 and Windows Server 2008 domain controllers.

Although you can transition from Exchange 2000 to 2007 the problem in this case is the move from Windows Server 2000 to Windows Server 2008.  Exchange 2000 will not work with Windows Server 2008 domain controllers, and Exchange 2007 will not work with Windows Server 2000 domain controllers.

From Microsoft:

Exchange 2000 Server Service Pack 3 and all previous versions of Microsoft Exchange are not for use with Windows Server 2008 directory servers. The following restrictions apply with respect to Exchange 2000 Server Service Pack 3:

• Exchange 2000 Server Service Pack 3 can exist in an Active Directory forest that contains Windows Server 2008 directory servers, but Windows Server 2008 directory servers should not be installed in Active Directory Sites that contain Exchange 2000 Server.
• If Windows Server 2008 directory servers must be deployed Active Directory Sites that contain Exchange 2000 Server you must first hard-code directory service access (DSAccess) on the Exchange 2000 Server servers in the site to point to directory servers running Windows Server 2003 or Windows 2000 Server.

In other words, at some point the reader will need to install a Windows Server 2003 domain controller to make the whole transition possible.

My recommendation is to use these general steps:

1. Install a Windows Server 2003 domain controller into the site(s) that will be hosting Exchange Server 2007, so that the environment pre-requisites for Exchange 2007 are met (ie, Windows Server 2003 SP1 DC/GC in the AD Site hosting Exchange 2007, plus the Schema Master must be Windows Server 2003 SP1)
2. Transition from Exchange Server 2000 to Exchange Server 2007
3. Introduce Windows Server 2008 domain controllers into the environment where required (upgrading the temporary Windows Server 2003 DC to 2008 is supported too)

Related posts:

• Installing Exchange Server 2007 pre-requisites on Windows Server 2008
• Exchange 2007 ADPrep Error Executing Ldifde.exe to Import Schema File
• Why Haven’t You Upgraded Your Exchange Servers Yet?
• Security descriptor error during Exchange Server 2007 schema extension
• Preparing for an Exchange Server 2007 Transition

This article Exchange 2000 and Windows Server 2008 Domain Controllers is © 2010 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

In this post I’ll walk through installing the pre-requisites for Exchange 2010 on Windows Server 2008.  If you’re looking for the Exchange 2010 pre-requisites for Windows Server 2008 R2 go here instead.

First, install the following software components.

1. .NET Framework 3.5 Service Pack 1
2. .NET Framework 3.5 Family Update
3. Windows Remote Management and Windows PowerShell 2.0
4. 2007 Office System Converter: Microsoft Filter Pack (for Hub Transport and Mailbox Server roles only)

Run the following from an elevated command prompt.

C:\>sc config NetTcpPortSharing start= auto

Next we need to install the operating system components.  The Exchange source files contain a series of ServerManagerCmd.exe answer files in XML format that can be used to install the operating system pre-requisites for each of the server roles.

Each file relates to a specific Exchange 2010 deployment scenario.

• exchange-all.xml – all server roles
• exchange-base.xml – only the requirements for Forest and Domain prep operations
• exchange-cadb.xml – Central Admin Database role
• exchange-cas.xml – Client Access Server role
• exchange-eca.xml – Central Admin role
• exchange-edge.xml – Edge Transport Server role
• exchange-hub.xml – Hub Transport Server role
• exchange-mbx.xml – Mailbox Server role
• exchange-typical.xml – Typical Exchange server (Client Access, Hub Transport, and Mailbox Server roles)
• exchange-um.xml – Unified Messaging role

For example, here is the contents of the exchange-cas.xml file.

Execute any of the answer files using ServerManagerCmd.exe and the -inputPath parameter (that can be shortened to -ip).  Here I am installing the pre-requisites for a “Typical” server.

C:\Admin\Exchange 2010\scripts>servermanagercmd -ip exchange-typical.xml
.............................

Start Installation...

Skipping [.NET Framework 3.0 Features] .NET Framework 3.0 Features because it is
 already installed on this computer.

[Installation] Succeeded: [.NET Framework 3.0 Features] WCF Activation.
[Installation] Succeeded: [Web Server (IIS)] Management Tools.
[Installation] Succeeded: [Web Server (IIS)] Web Server.
[Installation] Succeeded: [Remote Server Administration Tools] Feature Administr
ation Tools.
[Installation] Succeeded: [Remote Server Administration Tools] Role Administrati
on Tools.
[Installation] Succeeded: [Remote Server Administration Tools] Active Directory
Domain Services Tools.
[Installation] Succeeded: [Web Server (IIS)] Performance.
[Installation] Succeeded: [Web Server (IIS)] IIS 6 Management Compatibility.
[Installation] Succeeded: [Web Server (IIS)] Health and Diagnostics.
[Installation] Succeeded: [Web Server (IIS)] Application Development.
[Installation] Succeeded: [Web Server (IIS)] Security.
[Installation] Succeeded: [Web Server (IIS)] Common HTTP Features.
<100/100>

Success: A restart is required to complete the installation.

C:\Admin\Exchange 2010\scripts>

If you want the restart to happen automatically add the -restart option to the command.

C:\Admin\Exchange 2010\scripts>servermanagercmd -ip exchange-typical.xml -restart

The server is now ready for installation of Exchange Server 2010.

Related posts:

• The Case of the Hub Transport Server Load Imbalance
• Announcing Exchange 2010 Boot Camp PLUS
• How to Prevent Meeting Requests Appearing in Delegate’s Outlook Calendars
• Restricting Room Mailbox Bookings to Specific Groups in Exchange Server 2010
• Generate SMTP Error Statistics using Log Parser and Exchange Server 2010 Protocol Logs

This article Installing Exchange Server 2010 Pre-Requisites on Windows Server 2008 is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

Configuring a Static IP Address in Windows Server 2008 Core

Use Netsh to configure the static IP address:

netsh interface ipv4 set address name="Local Area Connection" source=static address=192.168.100.48 mask=255.255.255.0 gateway=192.168.100.254

Configuring the Primary DNS Server in Windows Server 2008 Core

Use Netsh again to configure the primary DNS server address:

netsh interface ipv4 set dns name="Local Area Connection" source=static address=192.168.100.49 primary

Configuring Additional DNS Servers in Windows Server 2008 Core

Use Netsh to configure a secondary DNS server address:

netsh interface ipv4 add dnsserver name="Local Area Connection" address=192.168.100.48 index=2

The static IP and DNS server configuration will now be shown in IPConfig:

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-31-9E-AC
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1884:ed1b:1548:43be%2(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.100.48(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.100.254
   DNS Servers . . . . . . . . . . . : 192.168.100.49
                                       192.168.100.48
   NetBIOS over Tcpip. . . . . . . . : Enabled

Related posts:

• Changing Screen Resolution on Windows Server 2008 Core
• Update Required for Windows 2003 Certificate Services Web Enrollment for Windows 7/2008 Clients
• Exchange 2000 and Windows Server 2008 Domain Controllers
• Installing Exchange Server 2010 Pre-Requisites on Windows Server 2008
• Installing VMWare Tools on Windows Server 2008 Core

This article How to Add Multiple DNS Servers to Windows Server 2008 Core is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

However the nature of the Core installation is that there is no graphical interface to modify the desktop resolution.  Fortunately the changes can be made via the registry.

Launch Regedit.exe from the command prompt.

Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Video\<GUID>\0000 where <GUID> is your video adapter (note: if there is more than one just check each one to see which matches the video hardware installed).

The desktop resolution is configured using the DefaultSettings.YResolution and DefaultSettings.XResolution keys.

Modify the settings to the desired setting, in my case 1024×768.

Exit Registry Editor and issue a shutdown -r command to reboot the server.

When the server restarts it will boot with the screen resolution that you configured in the registry.

Related posts:

• How to Add Multiple DNS Servers to Windows Server 2008 Core
• Update Required for Windows 2003 Certificate Services Web Enrollment for Windows 7/2008 Clients
• Exchange 2000 and Windows Server 2008 Domain Controllers
• Installing Exchange Server 2010 Pre-Requisites on Windows Server 2008
• Installing VMWare Tools on Windows Server 2008 Core

This article Changing Screen Resolution on Windows Server 2008 Core is © 2009 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

C:\>servermanagercmd -i telnet-client
.........

Start Installation...
[Installation] Succeeded: [Telnet Client].
<100/100>

Success: Installation succeeded.

Related posts:

• Email Fundamentals: How to Send Email via Telnet
• Windows Server 2008 ServerManagerCMD.exe command reference
• Generate SMTP Error Statistics using Log Parser and Exchange Server 2010 Protocol Logs
• How to Send SMTP Email Using PowerShell (Part 3)
• How to Send SMTP Email Using PowerShell (Part 2)

This article Install telnet on Windows Server 2008 is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

About 2 years ago, when the Exchange team started testing Exchange 2007 on Windows 2008, we found that the built-in backup application had changed dramatically. Decisions that drove that change by the Windows team are not the subject of this post, but it is fair to say that the Windows team did not make the decision lightly.

When we evaluated the features of Windows Server Backup, it was clear that the backup and restore experience on Windows 2008 would not be the experience that existing Exchange customers have been used to for so long. Because we had feedback from several customers who told us they would rather get a more full-featured backup solution for their Exchange servers, a decision was made not to provide an Exchange-aware backup solution for Windows 2008 in Exchange 2007 Service Pack 1.

This week they announced the following:

Although we can’t share all of the details now, we thought that this issue was important enough to announce a decision we recently made. We have decided to develop and release a VSS-based plug-in for Windows Server Backup that will enable you to properly backup and restore Exchange 2007 with a built-in Windows 2008 backup application.

This is good news for Exchange customers looking for inexpensive backup solutions.  I’m a bit curious though about this statement:

While you will be able to backup and restore Exchange 2007 on Windows 2008, you should not expect feature parity with the Windows 2003 NTBackup experience. There will not be the same level granularity and control that NTBackup provides and backups will be limited to the local server only.

NT Backup was about as featureless as you could get when it comes to Exchange backups, so I don’t quite understand how you can take a step backward from that.  It will be interesting to see the result when it ships thats for sure.

Related posts:

• Exchange 2000 and Windows Server 2008 Domain Controllers
• Installing Exchange Server 2007 pre-requisites on Windows Server 2008
• Generate SMTP Error Statistics using Log Parser and Exchange Server 2010 Protocol Logs
• Calculate Hourly Email Traffic using Message Tracking Logs and Log Parser
• Calculate Daily Email Traffic using Message Tracking Logs and Log Parser

This article Windows Server 2008 to receive Exchange Server 2007 backup capabilities is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

C:\>ServerManagerCmd.exe -i Web-Server Web-Asp-Net Web-Http-Redirect Web-Windows
-Auth Web-Metabase Web-WMI
............................................

Start Installation...
[Installation] Succeeded: [Web Server (IIS)] Management Tools.
[Installation] Succeeded: [Web Server (IIS)] Web Server.
[Installation] Succeeded: [Web Server (IIS)] Performance.
[Installation] Succeeded: [Web Server (IIS)] IIS 6 Management Compatibility.
[Installation] Succeeded: [Web Server (IIS)] Security.
[Installation] Succeeded: [Web Server (IIS)] Application Development.
[Installation] Succeeded: [Web Server (IIS)] Common HTTP Features.
[Installation] Succeeded: [Web Server (IIS)] Health and Diagnostics.
[Installation] Succeeded: [Web Server (IIS)] IIS 6 Metabase Compatibility.
[Installation] Succeeded: [Web Server (IIS)] IIS 6 WMI Compatibility.
[Installation] Succeeded: [Web Server (IIS)] IIS Management Console.
[Installation] Succeeded: [Web Server (IIS)] Directory Browsing.
[Installation] Succeeded: [Web Server (IIS)] Static Content.
[Installation] Succeeded: [Web Server (IIS)] Default Document.
[Installation] Succeeded: [Web Server (IIS)] ISAPI Filters.
[Installation] Succeeded: [Web Server (IIS)] HTTP Errors.
[Installation] Succeeded: [Web Server (IIS)] HTTP Logging.
[Installation] Succeeded: [Web Server (IIS)] HTTP Redirection.
[Installation] Succeeded: [Web Server (IIS)] ISAPI Extensions.
[Installation] Succeeded: [Web Server (IIS)] Request Filtering.
[Installation] Succeeded: [Web Server (IIS)] Static Content Compression.
[Installation] Succeeded: [Web Server (IIS)] Request Monitor.
[Installation] Succeeded: [Web Server (IIS)] Windows Authentication.
[Installation] Succeeded: [Web Server (IIS)] .NET Extensibility.
[Installation] Succeeded: [Web Server (IIS)] ASP.NET.
<100/100>

Success: Installation succeeded.

The components included in the command line are:

• Web-Server
• Web-Asp-Net
• Web-Http-Redirect
• Web-Windows-Auth
• Web-Metabase
• Web-WMI

SQL Server 2005 setup will now pass all pre-requisite checks when installing on Windows Server 2008.

Related posts:

• Update Required for Windows 2003 Certificate Services Web Enrollment for Windows 7/2008 Clients
• Exchange 2000 and Windows Server 2008 Domain Controllers
• Installing Exchange Server 2010 Pre-Requisites on Windows Server 2008
• How to Add Multiple DNS Servers to Windows Server 2008 Core
• Changing Screen Resolution on Windows Server 2008 Core

This article Installing SQL Server 2005 on Windows Server 2008 is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

One of the highlights is a complete list of the role, role service, and feature command identifiers for installing Windows Server 2008 components.

This is an excellent reference and very handy when configuring a Windows Server 2008 server.

Link: Overview of Server Manager Commands

Related posts:

• Install telnet on Windows Server 2008
• Update Required for Windows 2003 Certificate Services Web Enrollment for Windows 7/2008 Clients
• Exchange 2000 and Windows Server 2008 Domain Controllers
• Installing Exchange Server 2010 Pre-Requisites on Windows Server 2008
• How to Add Multiple DNS Servers to Windows Server 2008 Core

This article Windows Server 2008 ServerManagerCMD.exe command reference is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com

The components are installed using ServerManagerCmd.exe.  The following commands can be executed in a command shell to install each of the components.

Firstly, if you are intending to use the Windows Server 2008 server to extend the Active Directory Schema for Exchange Server 2007 you must install the Active Directory Domain Services remote management tools.  This usually requires a server restart.

C:\>ServerManagerCmd -i RSAT-ADDS
...........

Start Installation...
[Installation] Succeeded: [Remote Server Administration Tools] Role Administrati
on Tools.
[Installation] Succeeded: [Remote Server Administration Tools] Active Directory
Domain Services Tools.
Warning: [Installation] Succeeded: [Remote Server Administration Tools] Server f
or NIS Tools. You must restart this server to finish the installation process.

Warning: [Installation] Succeeded: [Remote Server Administration Tools] Active D
irectory Domain Controller Tools. You must restart this server to finish the ins
tallation process.

<100/100>

Success: A restart is required to complete the installation.

Once the server is restarted you can install the remaining components. You could install them by entering the commands one at a time, but I prefer to run them all at once like this.

ServerManagerCmd -i PowerShell Web-Server Web-ISAPI-Ext Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression RPC-over-HTTP-proxy 

The commands will execute in sequence and display output similar to this.

.

Start Installation...
[Installation] Succeeded: [Windows PowerShell].
<100/100>

Success: Installation succeeded.
....................

Start Installation...
[Installation] Succeeded: [Web Server (IIS)] Management Tools.
[Installation] Succeeded: [Web Server (IIS)] Web Server.
[Installation] Succeeded: [Web Server (IIS)] Common HTTP Features.
[Installation] Succeeded: [Web Server (IIS)] Health and Diagnostics.
[Installation] Succeeded: [Web Server (IIS)] Security.
[Installation] Succeeded: [Web Server (IIS)] Performance.
[Installation] Succeeded: [Windows Process Activation Service] Configuration API
s.
[Installation] Succeeded: [Windows Process Activation Service] Process Model.
[Installation] Succeeded: [Web Server (IIS)] IIS Management Console.
[Installation] Succeeded: [Web Server (IIS)] Request Monitor.
[Installation] Succeeded: [Web Server (IIS)] Static Content.
[Installation] Succeeded: [Web Server (IIS)] HTTP Logging.
[Installation] Succeeded: [Web Server (IIS)] Static Content Compression.
[Installation] Succeeded: [Web Server (IIS)] Request Filtering.
[Installation] Succeeded: [Web Server (IIS)] Default Document.
[Installation] Succeeded: [Web Server (IIS)] Directory Browsing.
[Installation] Succeeded: [Web Server (IIS)] HTTP Errors.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Application Development.
[Installation] Succeeded: [Web Server (IIS)] ISAPI Extensions.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] IIS 6 Management Compatibility.
[Installation] Succeeded: [Web Server (IIS)] IIS 6 Metabase Compatibility.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] IIS 6 Management Console.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Basic Authentication.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Digest Authentication.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Windows Authentication.
<100/100>

Success: Installation succeeded.
............

Start Installation...

[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Dynamic Content Compression.
<100/100>

Success: Installation succeeded.
............

Start Installation...
[Installation] Succeeded: .
[Installation] Succeeded: .
[Installation] Succeeded: .
[Installation] Succeeded: [Web Server (IIS)] Client Certificate Mapping Authenti
cation.
[Installation] Succeeded: [Web Server (IIS)] Tracing.
[Installation] Succeeded: [Web Server (IIS)] Logging Tools.
[Installation] Succeeded: [Web Server (IIS)] HTTP Redirection.
[Installation] Succeeded: [RPC over HTTP Proxy].
<100/100>

Success: Installation succeeded.

Your Windows Server 2008 host is now ready to install Exchange Server 2007.

References:

• How to Install Exchange 2007 SP1 Prerequisites on Windows Server 2008 or Windows Vista

Related posts:

• Exchange 2007 ADPrep Error Executing Ldifde.exe to Import Schema File
• Exchange 2000 and Windows Server 2008 Domain Controllers
• Security descriptor error during Exchange Server 2007 schema extension
• Exchange 2010 FAQ: Is Direct Exchange Migration from 2003 to 2010 Possible Without Upgrading to 2007?
• Preparing for an Exchange Server 2007 Transition

This article Installing Exchange Server 2007 pre-requisites on Windows Server 2008 is © 2008 ExchangeServerPro.com

Get more Exchange Server tips at ExchangeServerPro.com