Installation Environment:
Window Server 2012 DataCenter + Microsoft SQL 2012（sp1） + SharePoint Server 2013
basic introduction:
A. Install Windows 2012 operating system (in VMWare 9.0)
B. Simple configuration: change the machine name, access the Internet, disable IE enhanced configuration, static IP, IIS, FM3.5, AD (install DNS in between)
C. Install SQL2012
D. Online installation of necessary programs
E. Install SharePoint Server 2013
F. Solve two small problems encountered after installation
Installation process:
1. First install the operating system, as shown in the figure below for the installation program of Windows Server 2012
2. Select the data center version with GUI (graphical interface), this standard version is also available.
3. Copy the files and wait for the installation, wait patiently, and install the system for a little more than half an hour.
4. The installed "Server Manager", we add roles and functions, all need to be added here.
5. Install the virtual machine tool, I use VMWare WorkStation 9.0 version, because other versions do not have the option of window2012.
6. In the preliminary preparation, modify the machine name, otherwise AD has been built. After the installation is completed, there will be some problems in modifying the machine name.
7. Configure the network so that it can access the external network. I use the NAT method. Of course, different environments can use the Host or bridge method. I use the host to access the Internet, so choose NAT.
8. Turn off the enhanced configuration of IE, it feels very boring, and you need to add a security area every time you surf the Internet.
9. After the configuration is completed, you can visit the Baidu homepage (swear to the lamp, there is absolutely no intention to advertise to Baidu).
10. Configure a static IP address, because it is a server, the IP address always changes, how can others find you, not to mention AD and Dns.
11. According to the network configuration from IPconfig, configure static IP.
12. Add the fm3.5 function. Don't add it like this. Maybe because Windows 2012 comes with 4.5, it will report an error and cannot be added. We use the next one, the command line method.
13. Use the command line to read the file of the system disk, add fm3.5, the command is as follows, source is the location of the fm3.5 installation file.
dism.exe /online /enable-feature /all /featurename:NetFX3 /Source:e/:source/sxs
14. Install IIS, it is recommended to install one by one, otherwise the installation process goes wrong, which is a very troublesome thing.
15. I only checked windows authentication, because as we all know, sharepoint requires windows authentication.
16. Installing the AD environment and adding functions is basically the next step.
17. Prepare for the next step, and that's it.
18. The function installation is complete, and it is ready to be promoted as a domain controller. You can directly click the blue word to promote this server to a domain controller.
19. If you accidentally closed it in the previous step, open the server manager, find the following place, and perform the promotion of the domain control operation. Of course, I am in a single server environment. If you are in a farm environment, you don't need each commissioned domain controller, you just need to join AD.
20. Just click the link in the red circle.
21. Give our AD a name, don't make it too long, because we will often have to type the domain name in the future.
22. Enter the restore password. When backing up and restoring AD in the future, you will need this password, so keep it in mind!
23. The delegation of the DNS server could not be created because we did not install DNS in advance. It's okay, it will automatically install DNS for us in a while. Of course, if you install DNS in advance, this prompt will not appear.
24. NetBIOS name, just fill in, nothing special.
25. Prerequisite checks, warnings can be ignored.
26. DNS installation automatically inserted in between.
27. The domain controller configuration is OK. The administrator between us is the administrator of the domain controller in the future, that is, sp\administartor. Just restart.
28. The process of installing sql.
29. Enter the secret key, don't ask me, I don't know either.
30. Check it and go to the next step directly. Don't think I'm long-winded, I don't want to do this either.
31. It is not recommended to check the update. I just updated N because of the speed of the network. The flowers are all thankful and have not been updated yet, ╮(╯▽╰)╭.
32. Installation detection, warnings can also be ignored. Ha ha.
33. You can choose the first one. I don't have too deep research on sql.
34. Choose what you need, because I still want to try the reporting service, I chose a few more, you guys, see your mood.
35. Next step.
36, still the next step.
37. Get used to adding an Ad account, because future management will require an AD account.
38. The reason is the same as above.
39. Next step.
40. Click "Install" to enter the long wait.
41. After the installed sql, enter our sharepoint installation. Of course, we need to use the "sharepoint 2013 product preparation tool", which needs to be installed online.
42. During the installation process, wait patiently, during which there will be a restart.
43. After the installation is complete, after restarting, you can install sharepoint2013.
44. After restarting, run the configuration wizard.
45. The interface is very familiar, right?
46. We create a new server farm.
47. Fill in the database server name and access account password.
48. Fill in the security setting password.
49. Configure ports and security settings.
50. Enter the progress bar in the next step.
51. The installation is successful.
52. In the management center, configure the server farm. It is recommended not to open too many services, otherwise it will be very stuck.
53. Create a site collection
Note: After installing SharePoint, the following error may appear
Just hit the sp1 patch of sql 2012, thanks to the friends in the technical group.
Click to check the problem, mine is about the problem that "Security Token Service" is unavailable, it is said to restart the token service in iis, I changed the net to 2.0, it's fine, and then changed back to 4.0, and there is also a problem , for your reference.
180-day trial key: NQTMW-K63MQ-39G6H-B2CH9-FRDWJ