Notes for Vista Installation

When I installed Vista, I accidentally made a mistake: I didn't use the default administrator account, but I got another riccc account.
Vista's UAC: User Account Control. If the Account name you use is not administrator, Vista does not use the administrator permission to perform many operations even if the Account is in the administrators group, it is not clear what accounts and groups are used. This brings about a very serious problem. Many operations, especially in software installation and Development debugging, may encounter various inexplicable problems. In the final analysis, they may all be caused by permission issues.
Disable UAC. in the Local Security Policy, the account riccc is added independently in the places where the administrators group has the permission to perform operations. Many problems cannot be solved.

1. Install SQL Server 2005
At first, the SYSTEM prompts "SQL Server Setup was unable add user NT AUTHORITY \ SYSTEM to local group SQLServer2005MSFTEUser $ RICHIE $ SQL2K5 ", I checked SQLServer2005MSFTEUser $ RICHIE $ SQL2K5. This group was not created at all. So I created a group manually and added the SYSTEM account. During the reinstall, this step had passed, then there were another series of other problems, prompting that there was no permission to operate on any file, no matter how to set the security of the file and directory.

2. ASP. NET issues during VS2003 development and debugging
Refer to many articles on the Internet and install VS2003 to create ASP. NET Web Project, but it has been Unable to debug, and the prompt says "Error while trying to run project: Unable to start debugging on the web server. you do not have permissions to debug the server. verify that you are a member of the "Debugger Users" group on the server. ".

Enable the administrator account, switch the user to this account, and Install SQL Server 2005. The same error still occurs when debugging ASP. NET in VS2003. You can find a solution later.

The Vista permission mechanism has changed a lot, which will cause many problems for subsequent development and use.
From Windows 2000 to XP to Windows Server 2003, and from IIS 5.0 to 6.0, many problems have been solved during development and project implementation, most of which are related to permissions, however, the previous series of upgrades have little re-learning costs. On the one hand, the Operation setting interface has not changed much, so it is easy to find the settings. On the other hand, the Key Permission mechanisms of the operating system have not changed much. It seems that this time will take a considerable amount of time and project risk to successfully upgrade to Vista and Windows Server 2008.

IIS 5.0, Windows 2000, ASP: mainly issues with IUSR_machine_name account permissions and COM + permission configuration.
IIS 5.0/6.0, Windows 2000/XP/2003 ,. NET Framework 1.1: Mainly IUSR_machine_name and ASPNET account permissions. If Excel and other third-party COM + and DCOM components are used, the COM permissions are involved.
. NET Framework 2.0: Mainly used to change an account from ASPNET to network service.
Vista, IIS 7.0, Framework 2.0: still confused.