70-87 IIS Notes

Host headers cannot be used while using SSL, This is because Host Headers are included in the encrypted request.

SMTP and NNTP and Index Server have their own HTMLA.

To check files that need to be indexed

@unfiltered=true

After enabling SSL-change ext. to shtml & update links index server performace-large clusters copy web site to laptop-content analyzer,site copy

Index files on Novell

If you have Novell® NetWare® file servers, Index Server can index their contents as well. To do this, install and run Microsoft Windows NT Gateway Services for NetWare. For details about installing Gateway Services for NetWare, see the documentation for t

Install Windows NT Gateway Services for NetWare on the computer running Index Server. For details refer to the Gateway Services documentation. Index Server indexes the files on Novell NetWare file shares in one of two ways:

Through gateway redirection.

Through a UNC share.

To index files using gateway redirection

Create a Gateway to the NetWare share. Assume, for example, the Gateway assigns the drive letter Z to the remote NetWare share.

Add a virtual root in IIS pointing to drive Z. All documents on the remote NetWare share will be indexed by the Index Server.

You can also index files on NetWare volumes by using a UNC share. You can create this UNC share whether the server is part of a domain or not, as shown in the following examples.

For these examples, assume the following:

The UNC name for the share is \\NovellServer\Share1.

Index Server is running on a computer named Server A.

Server A is on Domain A when the server is part of a domain.

The user ID is WebUser, which can be any valid Windows NT user ID.

If Server A is part of a domain, follow these steps:

Create an account called WebUser on Domain A. This account should have the form DomainA\WebUser.

Give to the DomainA\WebUser account on Server A.

Make sure that DomainA\WebUser has Read permission on \\NovellServer\Share1.

Create a virtual root in IIS pointing to \\NovellServer\Share1. Specify DomainA\WebUser for the user name, and assign an appropriate password. Be sure to specify Domain A followed by a backslash (\) and then the actual user ID.

If Server A is not part of a domain, follow these steps:

Create an account called WebUser on ServerA. This account should have the form ServerA\WebUser.

Give to the ServerA\WebUser account on Server A.

Make sure that ServerA\WebUser has Read permission on \\NovellServer\Share1.

Create a virtual root in IIS pointing to \\NovellServer\Share1. Specify ServerA\WebUser for the user name, and assign an appropriate password. Be sure to specify ServerA followed by a backslash (\) and then the actual user ID.

Index Server then indexes the remote UNC \\NovellServer\Share1. If you want to index more remote NetWare files shares, repeat steps 3 and 4 for each of the shares.

SIMULATION NOTES:

a) Activating the Simulation MMC is accessible via a button labeled "Microsoft Management Console" from your question sheet. You do not need to click Start, Option Pack, etc.

b) To be safe, I suggest that you click Apply, then OK after changes.

c) You created virtual directories or sites are usually STOPPED; thus, you must right-click and start the created virtual directories or sites as appropriate.

d) Make sure that you check the site's physical path regardless of the stated objective. This means that if the test stated objective is to enable an HTTP keep-alives, make sure you check the physical path, i.e., c:\inetpub\wwwroot (given) and not c:\inetpub (default path in the Simulation MMC).

e) Be patient as the Simulation MMC engine is sluggish and erratic.

1>. read the question carefully, write down the site name they want you work with, parameters ( like IP address, directory name and path), pay close attention whether it us capital or normal characters.

2>. Open the MMC

3>. Put the exactly paramenters or discription on the right place. If there is a Browse button, click it. Don't try to type the path, because you may type it wrong due to carefuless.

4>. After you make the changes, ALWAYS click the Apply botton before click OK.

5>. Double check. Click the property tab, revew the changes you made to the property. If everything looks fine, Click OK.

6>. Open the file tab on the top, Click Exit. NEVER click the X sign to get out the MMC. it will sometimes cause the MMC hang. Meanwhile, you don't nead to stop and re-start the Web/FTP site you just work.

3. Study and pass TCP/IP first, it will help you to understand the centent of IIS 4.0

4. Pay close attention to Web, FTP and index services, the test didn't cover much about STMP & NNTP.

5. The Index server questions are kind of hard. especially the cross domain index. Please refer to IIS4.0 product document which is come with the IIS4.0 installation.

6. Understand the ODBC+SQL connection problems, such as authentication, NTFS permission, ODBC and DSN configurations. There are always three questions about that.

7. Study the IIS product document. It is good reference when you have question.

8. Study the IIS3.0 transcend test if you can find it. Believe me, its really helpful. Read the answer descriptions at least three time, try to find the logic and reasoning inside the descriptions. It will give you clue to answer some really tuff questions.

Know what you DON'T get if you install IIS on Win95 - I.E. my question was: You install IIS on Win95. You want to index your content - what do you do? I assume they could ask similar questions about Certificate server, SMTP service (I assume, since it requires NTFS), and security (NTFS ;-)... NT Server is the only platform that supports full functionality.