First `` `Put your computer as a server, pay attention to the various restrictions of the system IIS` More'dEnses Windows XP Home Edition does not support any version of IIS, without any reliable way to run IIS. Windows XP Home Edition is not designed to develop a web application development platform. After upgrading to Windows XP Professional, you can install IIS 5.1 on your system to develop work with ASP.NET, although IIS 5.1 on Windows XP Professional is a full-featured web server, but it can only build 10 concurrent connections because it is just a workstation operating system instead of a server platform. Windows XP Home Edition has some other restrictions as Windows XP Professional because it is also a workstation operating system instead of a server operating system. Generally, you will find that in Windows 2000 Professional and Windows 2000 Server or Advanced Server IIS 5.0, these differences are similar. In any case, for use .NET Framework to develop web-based applications, Windows XP Professional is an excellent environment. Q: How to install IIS 5.0 in Microsoft Windows XP Home Edition?
A: First, you need to explain it, this is the risk, so it is best to clarify your behavior before you actually operate. And through the IIS that is installed, there may be some unknown defects in operation. Also, like the PROFESSIONAL version, IIS running in the home version also has 10 concurrent connections. Within the same time, you can only have 10 people to use the IIS service you provide. If you still want to continue, then look down.
Preparation conditions: A Windows 2000 Professional CD (assuming the optical drive is an F disk).
First enter "C: /Windows/inf/sysoc.inf" in the run, and the system will automatically open the Sysoc.inf file with Notepad. In sysoc.inf, "[Components]" is found, and continue to find a line similar to "IIS = IIS.DLL, OCENTRY, IIS.INF, HIDE, 7", replace this line to "IIS = Iis2.dll Ocentry, Iis2.inf ,, 7 ". Save and close it.
Insert the Windows 2000 Professional CD into the drive, and press the SHIFT button to prohibit the automatic operation of the drive. Enter "CMD" in the run and enter the command line mode. Enter the following two commands in the command line. Enter the return after each line of command:
Expand D: /i386/Iis.dl_ c: /windows/system32/setup/iis2.dll expand d: /i386/Iis.in_ c: /windows/inf/iis2.inf can you get it: How do I? IIS settings for backup? A: There are several ways to be used to complete this work. The attributes and values set in the Internet Information Services Manager Console (IIS plug-in) are stored in the metabase.bin file, default, this file is located in the "C: / WinNT / System32 / InetSrv" directory. In IIS 5.0, you can back up metadata from the built-in IIS plugin. If you need this job, select the computer icon on your desktop and click Right. Then select "Backup / Recovery Configuration". Then you can choose to back up existing metadata settings or restore the previous version. The same options can also be found in MetaEdit 2.2. When you save metadata in this way, your backup will be stored in the C: / WinNT / System32 / Instrv / Metaback folder in the format of the .md0 file. When you perform a backup, the file will use the name you specified, such as pre-lockdown.md0. If you use the same file name to create multiple backups, they will use the number of extensions, such as Backup.md0, Backup.md1, and more.
When your metadata is seriously damaged, you will not be able to start IIS. At this point, you cannot perform recovery operations from the IIS plug-in or metaEdit. If a similar situation happens, you can replace Metabase.bin by selecting the most appropriate .md0 (.md1) metadata backup file from the backup folder. If your backup file is not wrong, IIS will start immediately.
There are other two senses for backups for making metadata. You can use XCOPY, Scopy, or other replication programs to simply copy the metabase.bin file. You should first stop the Internet service to ensure that your metadata is the latest and is not in use.
Finally, we also offer two scripts - Metaback.VBS and Metarest.vbs - They are located in IIS SDK in IIS 5.0 in IIS Resource Kit / Utility / Admi Admin Scripts folder (if you have installed IIS 4.0 Resource Kit). These .vbs scripts use an ADSI command that is specifically provided for creating metadata backups.
Q: What tool can help me apply a load and perform the intensity test of the application? A: There are many tools that can be used to achieve this. And there are some features and very useful. You will find that there is a very much commercial tool for you to use fully equipped, and these tools are very useful. Microsoft provides Web Application Stress Tool, in most cases, for loading a load on a web server, and checks whether it can work properly under certain pressures When performing application intensity testing, view them. This tool is sufficient. Pre-performing test is a good idea, because the problem does not appear in the design of the application, unless it is loaded on this server - and you must not want to find anything on a product finished server. problem.
Web Application Stress Tool has several useful features that you can include the ability to record the playback script when you point to your pointing and click operations through the Web site. Then when you remotely monitor the performance monitoring counter on the server, you can replay this script in one or more clients. In addition, you can specify more information, such as user accounts used to test authentication authentication throughput, and delay between requests and test plan schedules. When you are installing the Web Application Stress Tool, it also has a service on your computer, named "WebTool" service. If you confirm that this tool is no longer required, you can uninstall the Web Application Stress Tool.
Q: What happened when LocalStart.asp returned a "in creation" response? A: This "Creating" page should appear when accessing the default Web site from a remote IP address. If you access from an internal IP address, IIS online documentation will be displayed. If you visit http: // localhost in Internet Explorer, and unset.htm or default.asp is installed, the Web site will run IISStart.asp. IISStart.asp will check the following two conditions:
Have you already knocked into "LocalHost". Whether the client's IP address matches the server-side IP address. In either case, you will be redirected to localstart.asp, then open the page you want.
Determine these files existing on your system, and call IISSTART.ASP in the Document tab tab. To determine these, you can try to write a short .asp web page to display the value of the server variable, as follows:
Your Local IP Address IS 207.46.249.190 The Client IP Address IS 210.82.106.28
If the IP address is not identified, it may be because the localstart.asp page is not called. Of course, you can always call it by using http://localhost/localstart.asp directly. If you do not configure the default document, you may have problems when you call LocalStart.asp. The script will return the message below:
Currently, you didn't set a default document for users. All currently trying to connect to this site will receive a page that is "created".
Q: Can ISAPI filters run in a single process space? A: There are special requirements for applications developed to work with Web Server. For example, you cannot call a NotePad.exe instance from a URL and want to see a Notepad window on the client's system. In order to interact with the request from IIS (not CGI), the program must be written using ISAPI. ISAPI is an abbreviation for Internet Server Application Programming Interface. There are two executable ISAPIs: extensions and filters.
ISAPI extensions can be called directly from one URL, such as http://localhost/myisapi.dll. Suppose you have configured IIS, allow scripts, and executables on the directory, and the user has permission to perform NTFS, the DLL will run. IIS allows you to specify that the application is running within the process (as an INetInfo section) or outside the process (as the MTX section on IIS 4.0, or as the DLLHOST of the IIS 5.x). When an application runs outside the process, INetInfo is isolated from the problem. If the application fails, the web server will fail. The ISAPI filter is another content. The ISAPI filter can change the data stream that enters or leaves IIS. Therefore, the ISAPI filter has a very powerful feature that can be used to implement customer log, verify, or change the data stream. For IIS 5.0, features implemented in the ISAPI filter include data compression, summary verification, and URLSCAN.
Because the filter plays such an important role in IIS, they always operate in the process of running in the INetInfo part. Therefore, the correct ISAPI filter structure is essential to the server's normal operation. You may want to work with Microsoft Product Support Services to determine the problem because it is possible to handle this exception.
Based on this consideration, there are two new technologies to make life easier, IIS 6.0 is one of them. Since it is a new architecture, all ISAPI filters are running outside the process. This will allow the web server from an unpredictable ISAPI filter, but this actually does not really solve the problem. In order to solve this problem, you can use the .NET language to do some work in ISAPI. With C Design ISAPI filters, use the .NET implementation of the same functionality to be greatly simple.
Q: Where can I get such an example code - it shows how to edit a document in the ASP using WebDAV? A: The best way to use WebDAV from the script on IIS is to use the ASP.NET WebClient class. If you are using Windows XP or Windows Server 2003, the WebDAV function is part of this operating system. This allows you to use HTTP to reference a file on a web server, just like using a UNC path name. For example, you can map a drive with NET Use * http: // servername / directory and then access this location by using the drive symbol. On the other hand, you can also create a COM object, which is a webDAV client. You can use this object to deliver WebDAV verbs to IIS 5.x or IIS 6.0.
Also, if you search for MSDN as a webdav, you will find some examples, which teach you how to use XML to construct a WebDAV query for Exchange and other Microsoft servers. There is a sample application for WebDav in Microsoft Exchange 2000 Server SDK.
Q: When I tried to access a database with ASP, I got a "refusal access" response. What is the reason? A: There is an excellent free tool called "Filemon", you can get it from sysinternals.com. You can use FileMon to quickly diagnose the vast majority of permissions, because it can display all file permissions on the server in real time, the result of the calling process name and access. Therefore, no matter how deep the hidden nesting or how embarking, any "refusal access" message can be easily identified.
When an application that can work properly on the previous operating system is problematic, it is powerful when there is a problem after the upgrade. However, this type of problem is still inspiring. One difference between IIS 4.0 and IIS 5.0 is related to a difference between COM and COM . In IIS 5.0, when a COM object represents a user access file, its default behavior is to complete these work using the user's security context environment. This is not something in IIS 4.0. Therefore, when migrating an application containing a COM from IIS 4.0, you may need to provide user permissions to files, and do not need in IIS 4.0. Although this is some inconvenient with previous, it is indeed a progress in improving application security design. Even if you cannot use a custom COM object to access the database, COM has been widely used in local IIS components. Here is an example that can help you understand this need. For example, you need to grant the request to use the Access temporary folder for users who are creating a database. For more information, please check Q210457 and Q271071 in Microsoft Knowledge Base.
Q: How do I run an IIS lock tool without recovering the original settings? A: IIS lock tool is very effective. This tool allows you to easily and significantly increase the security of the server. Once this tool is running, it stores the history of the activity to a file, the location of this file is% systemDrive% /% systemDir% / system32 / inetsrv. You will find this information in the following file:
Oblt-rep.log oblt-overce.md0 oblt-mb.md0 oblt-undone.log may also be the latest.
If you delete these files, the wizard will start, as if IIS LockDown Tool is not running. Repeating this process is not risking. Before you do this, you must make a copy of Metabase.bin.
Because when it is running, this process will make you run the lock tool, it seems that it has never been run, but does not "unlock" or reverse the locking tool for some settings, so this process It should be possible to work.
Q: How to deal with "Server-Side Include" syntax in my intranet environment without having to rename all files? Answer: IIS 4.0 and IIS 5.0 provide such an option, which does not need you change the extension of all files. The ASP processor can also handle the server-side include syntax, so it is not necessary to use .STM or .asp extension. So, what help does this? By creating an entry in the application configuration, you can map the .htm file to be processed by asp.dll, which is handled by the .htm extension file will be processed by asp.dll. By using this way, those .htm files that contain include ,htm files can be processed without rename. Now you may be considered: "This will not cause all the .htm files being processed like a script, reducing the system's performance?" In fact, in IIS 4.0, this is indeed a problem; however, In IIS 5.0, performance issues are not as large as you think, and in IIS 5.1, it will even be better. IIS 5.0 has a feature called "scripTless ASP" (no script ASP) to handle this special issue. If a file that does not contain a script is submitted to the ASP processor, it will not be parsed, just simply sending out as a static page - a useful feature in this particular case.
Q: When I visited from a customer workstation, how can I access the Iisadmin virtual directory in IIS 4.0 (Windows NT 4.0 Service Pack 6a without causing the server to restart? A: Because IIS 4.0 is released before Windows NT 4.0 Service Pack 6A (SP6A), you must reinstall SP6A and all required instant patches after installation IIS 4.0. Q: In Windows 2000 Professional, how do I do to let domain users to manage virtual directories so that domain users can create and manage their own virtual directory? A: The last thing you need to do is to join the domain users into the Power Users group, as this can be given to anyone who has user accounts in the domain. If each member in your trust domain can manage the system well, do nothing else, but for most computer users, this trust level is not suitable.
In order to create a virtual directory in IIS, users need administrator privileges. The reason why it is designed because anyone who could create a virtual directory on a Web site can also delete, rename, redirect, or other management work for virtual directories.
After realizing this, you may want to provide similar powers without providing administrators identity, there is a feature in the IIS plugin ("Operator" tag), let you specify a web site operator (not managing Create a virtual directory for the Web site. This feature is only available in Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 DataCenter Server. The same features can also be applied to IIS 4.0.
Also, you can also create a virtual directory inside the IIS Web site and map it to% systemroot% /% systemDir% / inetsrv / iisadmin. You should protect the security of this virtual directory, otherwise those who visit this site can manage this web site. It is also important to note that this is feasible to Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server (and IIS 4.0).
When you find that yourself grant the extension permissions according to the restriction of the operating system, you may need to install a server operating system when you try to use your workstation as a server.
Q: On Windows 2000 Server, when a site requires SSL, how can I use the host head on the same site? A: Let's review the problem of SSL and host heads, because for IIS, its problem has been in the first five in the common question.
When the customer issues an HTTP connection request to the IIS server, the client's request includes a field called Host:, which includes a web server request in the URL. For example, if your request takes http://www.microsoft.com as a destination, the browser sends it to the server and submits other information in the HTTP header, Host: http://www.microsoft.com . Because this field is "Host", and it is in the customer's HTTP header, so we call it "Host Head".
If the customer requests to establish an SSL connection, the host header field will still be included in the request, but it is included in the encryption section of this packet (in the application layer), the web server cannot decrypt it to determine that it should be Request to send to which one Web site. This produces a law: When using SSL, the host cannot use the primary means to identify a Web site.
What happens if you really want to use SSL with a host head? Consider this situation. You have two web sites, one of which does not use the main unit, and the other is used. Both sites use the same IP address and are all configured to use certificates. When you use SSL to access the site with the host header, the first Web site responds to this. This happens because: We use the IP address to identify the site you want to use to establish a connection, not the main unit. Because the first site reacts to the IP address and HTTPS, it accepts the request. If the first Web site requires a host head, and on a different IP address, or there is no certificate, the connection will fail.
Therefore, consider your configuration, on the same site you need SSL, as long as you don't use the host head, you can do anything you want to do.
