I’m a big fan of Exchange, and I’m a bigger fan of PowerShell, so I taught hack…why not create a post that includes both. And here it is. I know some of you don’t like scripting, and command shells, and neither do I, but PowerShell…man ohh man it’s great. Ok enough about PowerShell, because this is about Exchange, so let’s get started.
My environment is like this:
• One Windows 2008 R2 with SP1 server acting as a DC
• Single forest/domain named vkernel.local
• One Windows2008 R2 with SP1 on witch we are going to install Exchange Server 2010 with SP1(named Ex2K10)
• All Exchange roles are on the same box
• Both servers are in the same site
• IP communication is working between servers
• Ex2K10 already joined to the domain
• Servers are up-to date
If you are using virtualization products like VMware Workstation or Hyper-V be shure this servers have different SIDs; this can happen when VMs are cloned, and in this situation you have to sysprep them.
Before with proceed with the Exchange installation, prerequisites are needed. Log on to Ex2K10 as an administrator and open a PowerShell window (just click Start and type powershell in the Search Programs box).
and hit ENTER. Next paste this line to install the necessary server and features roles. Your server will restart after the command is done installing the prerequisites.
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
Until the server restarts go to this link and download the package FilterPack64bit.exe. After download completes install the package. Before we start installing Exchange two more things needs to be done:
1. Set the Net. TCP Port Sharing Service service to automatic. For this open a PowerShell console and put the command:
Set-service NetTcpPortSharing -startuptype automatic
then hit ENTER.
Close the Services console.
2. Raise the domain and forest functional level to Windows 2003. Log on to your DC and go to Start > Administrative Tools > Active Directory Domain and Trusts. Here right click your domain and choose Raise Domain Functional Level.
Choose Windows Server 2003 and click the Raise button. A couple of messages appear informing the user that this changers will be replicated to all DCs in the domain, and they are irreversible. Just click OK ’till the end.
Don’t close the console yet because we need to raise the forest functional level too. Right click the Active Directory Domains and Trust and choose Raise Forest Functional Level.
Again select Windows Server 2003 and click Raise, and OK a couple of times.
Now we can start working on the Exchange installation. Insert your Exchange installation media in the DVD drive, or mount the ISO if you are working with virtualization products, witch I hope you are. Switch to the PowerShell console and change the path to you optical drive (usually D:), because the forest and domain needs to be prepared for Exchange to function. Put the command:
.setup /p /on:"vKernel Communications"
Do not type setup.exe because is setup.com actually. The other parameters are /p witch come from Prepare Active Directory. This parameter is preparing both, the forest and the domain. The /on parameter comes from Organization. Every Exchange organization need to have a name, and in my case is vKernel Communications. For more help type
Now we can begin with the actual installation of Exchange server. On PowerShell put this command:
.setup /mode:install /roles:c, h, m, t
The parameters are like this: we tell setup to “jump” in the installation mode, the we tell what roles to install. In this case we are installing the Client Access Server Role, Hub Server Role, Mailbox Server Role and the Management tools. If you need more help with this you can issue the command:
then press ENTER
After installation do a restart. To verify if the installation succeeded just open the Exchange Management Console. Go to Start > All Programs > Microsoft Exchange Server 2010 > Exchange Management Console.
Want content like this delivered right to your