The web directory alone is not a complete IIS inventory. A website also has bindings, applications, identities and external data. On Windows Server2003, distinguish the old IIS6 management interface from newer IIS instructions.
1. Confirm version and target
Record server name, Windows edition, architecture, service pack and installed IIS version. Open IIS Manager through Administrative Tools and verify the selected server. Record the existing isolation mode where known; IIS5 compatibility mode differs from IIS6 worker process isolation. If an application-pool node is absent, do not switch modes pre-emptively. Use authorized access and existing backups.
2. Identify each website
Under Web Sites, record name or description, ID and displayed state. Read existing bindings in Properties: IP address, port and host header, with separate rows for multiple bindings. Document HTTPS separately and note certificate association and expiry without changing certificates or private keys. A responding server name does not prove that the correct site was reached. Do not start, stop or create sites.
3. Map applications and paths
From Home Directory, record the actual local or UNC path and redirects. List virtual directories and their own targets separately. For each defined application, record its assigned pool and account for inherited settings. Inventory script/framework versions and extensions from existing configuration without enabling extensions or installing packages. Data outside the visible web root also belongs in the backup plan.
4. Link pools, identities and dependencies
In worker process isolation mode, open existing pool properties. Record pool name, displayed identity and relevant recycling and performance values. Keep anonymous website identity separate from pool identity; they serve different purposes. Add databases, shares, certificates and licensing components from application documentation. Do not include passwords or connection tokens. Close with Cancel; do not recycle pools.
5. Make the later test verifiable
Link site ID, binding, application path, pool and responsible owner. Mark missing installation files and unknown dependencies. Plan replacement tests in a separate environment with correct host names and representative application functions; a static HTTP200 is insufficient. DNS cutover and production migration are later separate steps. The inventory leaves content and IIS settings unchanged.
