Some of the features of the. NET Framework are supported in Windows Server R2, including: subsets of. NET 2/3/3.5 and ASP. In addition, PowerShell is also available on Server Core. The missing features of IIS7 on Server Core are only the local management GUI, which can be managed remotely.
The installed Server Core supports the following roles:
. NET Framework 2.0, 3.0, and 3.5 subsets, including WCF, WF, and LINQ
PowerShell 2.0
Support 32-bit applications with WoW64
IIS 7.5 that supports ASP.
File Server Resource Manager (FSRM)
Certificate Services
The roles supported above are already in place on the installed Server Core server and can be enabled with the following command:
- Dism/online/enable-feature/featurename:<component>
The names of the above components are listed below, noting that the names are case-sensitive,
. NET Framework 2.0, 3.0, and 3.5 subset: Netfx3-servercore (requires installation of Netfx2-servercore first)
Windows Powershell:microsoftwindowspowershell
File Server Resource Manager (FSRM): Fsrm-infrastructure-core
Certificate Services: CertificateServices
IIS 7.5 that supports asp:
Iis-ftpextensibility
Iis-aspnet
Iis-netfxextensibility
Wcf-http-activation
Iis-webdav
Iis-managementservice
Iis-powershellprovider
Supports 32-bit applications with WoW64: SERVERCORE-WOW64
Additional WoW64 Support:
Failovercluster-core-wow64
Netfx2-servercore-wow64
MICROSOFTWINDOWSPOWERSHELL-WOW64 (requires first installation of NETFX2-SERVERCORE-WOW64)
Netfx3-servercore-wow64
Printing-servercore-role-wow64
Servercore-ea-ime-wow64
Suacore-wow64
The app looks at the components that have been installed by using the following command:
- Oclist | More
The app looks at the components that have been enabled by using the following command:
- dism/online/get-features/format:table | find/i Enabled
Use the following command to clarify the configuration status of the ASP.
- Dism/online/get-featureinfo/featurename:iis-aspnet
After describing the relevant commands, let's complete the related configuration to enable ASP. NET on Windows Server R2. Let's complete the related configuration to enable ASP. NET on Windows Server R2. The Servercore of Windows Server R2 contains a subset of. netframework2.0/3.0/3.5, which allows Servercore to support almost all of the features of ASP. But there are some limitations to note:
No built-in management console to configure and manage server The Aps.net site in core needs to be managed remotely on client computers that have the IIS management Console installed, or through the Appcmd tools in Servercore, using the command-line console to more comprehensively manage IIS sites and applications.
There is no system webmail namespace, because the Server core does not contain CDOSYS components and therefore does not support the Systemwebmail namespace, and the same functionality can be achieved using Systemnetmail.
The Windows server R2 Server Core does not support Web application tools (WAT).
Before installing the Web Server role, IIS and related dependencies, we must ensure that the. NET Framework is enabled by using the following two commands in DISM to configure the. NET Framework 2.0, 3.0, and 3.5 subsets:
- Dism/online/enable-feature/featurename:netfx2-servercore
- Dism/online/enable-feature/featurename:netfx3-servercore
To install IIS Web Server:
- Dism/online/enable-feature/featurename:iis-webserverrole
You must also start Iis-isapifilter, Iis-isapiextensions, iis-netfxextensibility before installing ASP. NET support for IIS:
- Dism/online/enable-feature/featurename:iis-isapifilter
- Dism/online/enable-feature/featurename:iis-isapiextensions
- Dism/online/enable-feature/featurename:iis-netfxextensibility
Now you can execute the following command to install ASP:
- Dism/online/enable-feature/featurename:iis-aspnet
Now that the Server Core server is ready to support ASP. NET applications, however, now Servercore does not have a GUI-like IIS management Console in Windows 2008, and if users need to create Web sites and Web apps, There are two ways to do this: the first is to use the Appcmd.exe command-line tool, which can be found in the Windows System folder, or to turn on the IIS Management Service, which is created through the IIS management console of the IIS remote client.
Execute the following command to install the IIS Remote Management Service:
- Dism/online/enable-feature/featurename:iis-managementservice
Need to install Was-windowsactivationservice and WAS-CONFIGURATIONAPI:
- dism/online/enable-feature/featurename:was-
Windowsactivationservice
- Dism/online/enable-feature/featurename:was-configurationapi
After successful installation, you will also need to change some registry keys to activate the management service:
- Reg ADD hklm\software\microsoft\webmanagement\
server/v enableremotemanagement/t reg_dword/d 1
The IIS remote Management Service is already installed, but it is important to note that the service is stopped by default, and if you need the IIS remote Management service to be turned on, you need to enable it through the Netstart command:
- net start Wmsvc
Now we can manage the IIS server on Server core through a remote computer and connect to Server Core via Windows Server 2008 with GUI or Windows 7 IIS console:
Enter Server Core name or IP:
The credentials to connect to the server are then required:
Then you need to enter an identity name, it is recommended to name the specification, a look at the server is known as IIS:
You can remotely manage your Server Core's IIS services on IIS.
During the installation process, the server only supports 64-bit applications, we also have a large number of 32-bit applications, enabling 32 for application support on Server Core is also simple, 32 for application support is through WOW64, can be installed by the following command:
- Dism/online/enable-feature/featurename:servercore-wow64
If you still need to use a 32-bit. NET assembly, execute the following command to install:
- Dism/online/enable-feature/featurename:netfx2-servercore
- Dism/online/enable-feature/featurename:netfx2-servercore-wow64
Finally, IIS is required to support 32-bit applications, and 32 support for applications needs to be enabled on IIS application pools.
ASP. NET environment in Windows Server R2