Online document preview of Microsoft Office Web Apps Server Setup (i)

Office Web Apps Installation

System requirements for Windows Server 2012,

Note: The conversion document requires two servers, one for the conversion server and one for the domain control server. (As for why two units, this please Google, Microsoft is so required, I do not understand)

The company's system is now using this implementation of the document online preview, in the near future will definitely be online. The following article I will attach to the upcoming document conversion service.

The pre-reproduction preview scheme used by the company was to convert the document into a PDF file and then convert it into a picture to achieve a preview. However, there is always a problem with synchronous conversion, the server memory consumption is serious, the Apache process is always full, causing the service to be inaccessible. Before that, we also learned about other scenarios, such as converting a document into a PDF file, and then implementing a preview of the document through other PDF plugins. In general, it can be achieved. But, it always feels unsatisfactory. After using Microsoft's Office Web Apps program, it suddenly felt tall.

Don't say much nonsense, you can follow me to try.

1. Conversion server

The whole process of self-build, the main steps to refer to this: http://www.cnblogs.com/poissonnotes/p/3238238.html

This step has been very detailed, the installation is mainly to download some files, the process is a little bit long. I'm not going to do the stickers anymore. According to this step-by-step, it is completely OK.

This article is very good, but for the students just contact, always think this is OK, you can achieve the document conversion. In fact, this is only half of the installation done. Keep looking at the following.

2. Domain-controlled server

Note: Many students use virtual machines to install, if the domain control also use the conversion server to export virtual space, then there will be some minor problems. But it can be solved by Google, and so am I.

I have also installed this process. Many of the pictures are pieced together, but do not affect everyone's installation.

(1) Open Server Manager, add roles and features (e.g.)

(2) The Add roles and features interface appears and the next step

(3) because it is based on a native installation, select Role-based or feature-based installation (e.g.)

(4) Since this experiment uses only one 2012 server, there is only one in the server pool

(5) Select Add AD domain service and add required features

(6) Follow the instructions, next

(7) Installation complete

3. Configure the Domain

(1) Click "AD DS" on the left side of Server Manager

(2) Click "Upgrade to Domain Controller"

(3) Go to the AD Domain Server Configuration Wizard, next (note: Fields are filled in)

(4) Fill in the password, next

(5) Prompt DNS cannot be created, no tube, continue next

(6) Installation path, default, Next

(7) View options, default, Next

(8) Click Install

(9) When the installation is complete, you will be prompted to cancel the restart

4. Join the conversion server to the domain control server

(1) Modify NDS to point to the domain control server

(2) In the computer properties, modify the computer name and add to the domain control server (such as), and then prompt to log off to restart the server

(3) In the Domain control server, select Add server, name fill in the computer name of Office Web Apps server, find Now. Then add to the right, OK.

(4) In the domain control server, all servers display two servers, and both are online to indicate success

At this point, the server installation is complete.

Online document preview of Microsoft Office Web Apps Server Setup (i)