Issues encountered with Windows Server 2012 deployment

One, install IIS Prompt "Server Manager winrm plugin may be corrupted or missing"

Solution:

1. Turn on the WinRM service and add IP monitoring

See if the WinRM service is turned on in the service, turn it on if it is not turned on, then open a command prompt, enter the Netsh http add iplisten 127.0.0.1, listen for the native IP address, and try again

Attention:

1) Netsh http add iplisten 127.0.0.1 will let IIS only listen to the intranet address, which will cause the external network address can not access IIS, so this time the external network Telnet Server 80 port is not reachable, want to be able to access the external network to delete the listener, By default, IIS listens for 0.0.0.0, which can be accessed via an extranet address and an intranet address:

2) How to use the Httpcfg tool:

Bind to a ip:httpcfg set iplisten-i 192.168.0.1

View Bindings ip:httpcfg Query Iplisten

Delete bindings ip:httpcfg Delete iplisten-i 192.168.0.1

2. Add a registry File

To open a CMD command prompt with administrator privileges, run the following command: WinRM quickconfig

Error:
Wsmanfault
Message = Access is denied.

Error Number: -2147024891 0x80070005
Access is denied.

Then run the following command:
REG ADD hklm\software\microsoft\windows\currentversion\policies\system/v localaccounttokenfilterpolicy/t REG_DWORD /d/F

Rerun command: WinRM quickconfig, if there is no exception, restart the server and try again to install IIS

Second, install IIS prompt "Insufficient storage space to process this command, error 0x80070008"

This exception is insufficient storage space, if the memory capacity is sufficient, that is because the virtual memory is not set

On the desktop right-click Computers, properties, high-level settings, high-performance panel, set up tab, advanced, virtual memory

• The minimum value for setting the paging file is 1 time times of memory and the maximum value is twice times the memory.
• Whenever possible, set the paging file on a non-system disk for better IO performance.
• Reasonable consideration of the system blue screen when the need to generate Memory.dmp.

Third, Telnet problem

We generally use Telnet to see if a port in the extranet is accessible, but there are some issues to be aware of

• If there is no record, the extranet access to port 80 is generally intercepted, that is, the extranet Telnet Server 80 port is unsuccessful.
• The port needs to be monitored, Telnet succeeds, and if the port is not monitored, it cannot be successfully telnet even if it is opened. When you install IIS, you will have a default site instance that listens to port 80 by default.
• Ports can be opened and closed through the firewall's inbound rules and outbound rules.
• IIS listens to 0.0.0.0 by default, which can be accessed via the extranet address and intranet address, if the local address (127.0.0.1 or local IP) is being monitored, only through the intranet.

Issues encountered with Windows Server 2012 deployment