Transfer Exchange 2003 to Exchange 2007 (P.7)

In the previous section, we have configured some of the necessary components in the Exchange 2007 environment, such as the CCR and Transport Dumpster configuration parameters. In this article, we will work with licenses, one of the main areas of Exchange 2007. We will first check the license of what has changed on the Client Access Server of Exchange 2007 through the paper-making process. permission.

>> Transfer Exchange 2003 to Exchange 2007 (Part 1)
>> Transfer Exchange 2003 to Exchange 2007 (Part 2)
>> Transfer Exchange 2003 to Exchange 2007 (Part 3)
>> Transfer Exchange 2003 to Exchange 2007 (P.4)
>> Transfer Exchange 2003 to Exchange 2007 (P.5)
>> Transfer Exchange 2003 to Exchange 2007 (P.6)

License of Client Access Server

By default, Exchange 2007 installs self-specified licenses that are allowed to use on the Hub Transport and Edge Transport function servers in most cases. However, there are exceptions, such as using Edge Transport server features, such as domain security features. However, self-appointed licenses are not suitable for some Client Access Server features such as Outlook Anywhere and the ability to use Outlook Web Access permanently. Therefore we need to replace the self-specified licenses installed on the Client Access Server servers. In the example of the article, Client Access Server and Hub Transport co-exist on the servers so we will have to replace the Hub Transport server license.

In an Active Directory environment there is a Windows Certificate Authority (CA) capable of creating the necessary licenses. In addition to Exchange 2007, there are many other Microsoft software that require the use of licenses, such as Office Communications Server 2007. Once the Windows CA has been installed, we can create the CA itself without the cost of the license from a Public CA. Of course licenses issued by a Public CA are required on ISA Server because it approves public service requests such as Oultlook Web Access, Outlook Anywhere, and so on.

To create a new license for the Client Access Server, we first need to create a license request with the New-ExchangeCertificate command. It should be noted that licenses will use different names. Because the license requires different names, we will use the Subject Alternate Name attribute. In this example we will use the following names:

1. The server's FQDN, including hubcas1.neilhobson.com and hubcas2.neilhobson.com .
2. NetBIOS name of the server, such as hubcas1 or hubcas2 . Setting up the NetBIOS name for the server is not required, but doing so will not require you to receive warnings when using the server's NetBIOS name.
3. Domain name used for the system (in this example is neilhobson.com ) is only a single domain name being used. However, in cases where the Accepted Domain Name is added, we need to specify a name for them. There is a simple method to do this in Exchange 2007 SP1, using the –IncludeAcceptedDomains parameter of the New-ExchangeCertificate cmdlet to ensure that all Accepted Domains we have defined appear in the authorization request.
4. Automatic domain search, like autodiscover.neilhobson.com. In fact, they will use the new parameter –IncludeAutodiscover of the New-ExchangeCertificate command to serve this purpose. As the –IncludeAcceptedDomains parameter, this parameter ensures that the auto-search name for every additional approved domain name is included in the licensing request. We do not need to use this parameter, but if we use it we will not miss an additional additional domain name.
5. The name the user will use to access remote mail, such as email.neilhobson.com .

Create a license

To create a permission request, we will run the New-ExchangeCertificate command with several different parameters. The syntax of the full command looks like this:

New-ExchangeCertificate –GenerateRequest –Path c: hubcas1.txt –SubjectName cn = hubcas1.neilhobson.com –DomainName email.neilhobson.com, hubcas1, hubcas1.neilhobson.com –IncludeAcceptedDomains –IncludeAutodiscover –PrivateKeyExportable $ true

Inside:

1. GenerateRequest parameter: allows creating a license request file rather than a self-specified license.
2. Path parameter: is the location that specifies the file containing the authorization request, namely c: hubcas1.txt .
3. SubjectName parameter: link the license to a server name. In this example the license will be sent to hubcas1.neilhobson.com .
4. DomainName parameter: We need to make sure this parameter contains the external access name, NetBIOS name and Fully Qualified Domain Name (FQDN). This means that all names will appear in the license.
5. IncludeAutodiscover parameter: As with Accepted Domains, this parameter ensures that the additional Autodiscover Domain name is appropriate.
6. PrivateKeyExportable parameter: This is a useful tool for exporting licenses, such as when copying this license to an ISA Server.

This command then displays a symbol (Thumbprint) and a Subject Name as shown in Figure 1.

---

---

Conclude