Shulou(Shulou.com)06/03 Report--

Prerequisites for Exchagne-2013 deployment and complete installation process

Install the server2012 R2 system, fix ip to the computer, change the computer name, join the domain control, restart the server

Log in with administrator highest privileges

Install the IIS service, .net3.5 and .net4 services

Open windowspowershell with an administrator

Run the code (1) on Windows PowerShell and restart the server after installing the role. Install-WindowsFeature RSAT-ADDSInstall-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-ADDS, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

After the role installation is successful, install the following software in the following order: restart the server after the default installation

MicrosoftUnifiedCommunicationsManagedAPI4.0,CoreRuntime64-bit

(UcmaRuntimeSetup.exe)

MicrosoftOffice2010FilterPack64 bit

(FilterPack64bit.exe)

MicrosoftOffice2010FilterPackSP164 bit

(filterpack2010sp1-kb2460041-x64-fullfile-en-us.exe)

Software download connection address: https://pan.baidu.com/s/1O1z4RpdCnzfuYcTqkvCcvg extraction code: 9ind

Prepare the service image of Exchange-2013. I prepared mu_exchange_server_2013_with_sp1_x64_dvd_4059293 because the file is too large to place the cloud disk.

Start installing the Exchange-2013 service

Very good, very unsuccessfully reported wrong (by looking at the log we know that the FMSO role ownership is insufficient)

Solution: go to the domain control server, find server management, click tools-find active dirrctory sites and services

Find the server-DC01 domain control, copy the FMSO permissions, and click copy now. (here AD domain control and exchange are installed on two server 2012r2 respectively)

(there are two on my side, and one exchange server. )

After the problem is resolved, the installation begins normally.

Very good. Wrong report again. You can see the mailbox role when installing to step 8: transport service reported error.

Problem description error: run "$error.Clear (); $maxWait = New-TimeSpan-Minutes 8$ timeout = Get-Date; $timeout = $timeout.Add ($maxWait); $currTime = Get-Date; $successfullySetConfigDC = $false; while ($currTime-le $timeout) {$setSharedCDCErrors = @ () Try {Set-SharedConfigDC-DomainController $RoleDomainController-ErrorVariable setSharedCDCErrors-ErrorAction SilentlyContinue; $successfullySetConfigDC = ($setSharedCDCErrors.Count-eq 0); if ($successfullySetConfigDC) {break;} Write-ExchangeSetupLog-Info ("An error ocurred while setting shared config DC. Error: "+ $setSharedCDCErrors [0]);} catch {Write-ExchangeSetupLog-Info (" An exception ocurred while setting shared config DC. Exception: "+ $_ .Exception.Message);} Write-ExchangeSetupLog-Info (" Waiting 30 seconds before attempting again. "); Start-Sleep-Seconds 30; $currTime = Get-Date;} if (- not $successfullySetConfigDC) {Write-ExchangeSetupLog-Error" Unable to set shared config DC. " The following error is generated when} ":" Unable to set shared config DC. "

By looking at the data, it shows that it is caused by disabling IPV6, because I simulated it through a virtual machine. I started the ipv6 of the virtual machine host, and then rebooted the ipV6 of the server.

(it is worth noting that I succeeded in restarting ipv6 after one night. )

The operation steps are as follows: first, shut down all the virtual servers. Turn on the IPv6 function of the host. Third, first open the DC server, then open the exchange server, fourth, check whether all the server IPv6 is turned on, and fifth, install the exchange service again.

After the problem is resolved, you can start the normal installation again.

After two error reports, the installation is finally successful.

View the application, click Exchange Management Shell, and run the test to see if Exchange is successfully installed and can be used normally

From the picture below, you can see that you have connected to the exchange-01 server normally.

Exchange-2013 uses web to manage and control the background

Enter https://localhost/ecp to go to the exchange Management Center later.

And enter the administrator account of the domain control to log in.

Because the mailbox feature has not been enabled for users in the domain control, there is only one administrator for the recipient of the mailbox.

Enter https://localhost/owa on the web page to open the mailbox web version client mode, enter the administrator account password of the domain control, and send an email to yourself to see if sending and receiving is normal.

As you can see from the above picture, it is normal for us to send and receive email, so the exchange installation is completed normally.

Through the above steps, we completed the pre-deployment and installation of exchange, which also included two error reports. Overall, the installation went smoothly.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.