Over the past few days, we have learned a lot about IIS servers. Today, we want to explain how the IIS server manually adds a unique security group to user permissions. I hope you can study it well.
Most user permission assignments through MSBP applications have been properly specified in the attached security template. However, some accounts and security groups on the IIS server cannot be included in the template because their Security Identifiers (SID) are specific to a Single Windows 2003 domain. The following describes the user permission allocation that must be manually configured.
WARNING The following table contains the Built-in Administrator account. Do not confuse the Administrator account with the built-in Administrators Security Group. If you have added any of the following Access Denied permissions to the Administrators security group, you must log on locally to correct this error.
In addition, the Built-in Administrator account may have been renamed based on some suggestions described in the Member Server benchmark of the Windows Server 2003 Server created by the module. When adding an Administrator account, be sure to specify a renamed account.
Manually added IIS server user permission assignment
The default value of the member server is the high security of the old client enterprise client.
Deny access to the computer through the network
Built-in Administrator account; Support_388945a0; Guest; all non-operating system service accounts
Built-in Administrator account; Support_388945a0; Guest; all non-operating system service accounts
Built-in Administrator account; Support_388945a0; Guest; all non-operating system service accounts
Warning all non-operating system service accounts include the service accounts used for specific applications across the enterprise. This does not include the built-in account local system, local service, or network service used by the operating SYSTEM. The knowledge of IIS servers is over today.