Windows Server 2003: inventory services and service accounts before replacement

An application may depend on several Windows services, accounts and remote data sources. A read-only service inventory helps before replacing Windows Server2003. A Running status alone proves neither application function nor recoverability.

1. Record target and scope

Note computer name, domain, edition, architecture, service pack and date. Open Services through Control Panel and Administrative Tools and verify whether the console targets this or another computer. Use authorized access and existing backups. Do not start, stop or change startup types for this inventory.

2. Separate names and configuration

Open a relevant service’s properties. On General, record internal service name, display name, description, executable path, startup type and current status. Display names can differ from internal names; use the internal name as the inventory key. Record only visible details. A stopped service is not automatically unnecessary: it may start on demand or through another component.

3. Map the logon account

Read the account shown on Log On. Distinguish built-in LocalSystem, LocalService or NetworkService from local and domain accounts. Record account name and responsible owner, never passwords. Do not reset the account, enter a trial password or change passwords as a test. Identical names on a replacement server do not automatically mean the same identity or access rights.

4. Read dependencies in both directions

Open Dependencies. Record required components and the listed services depending on this service. Close with Cancel. Add databases, shares, certificates, licensing services and remote endpoints from existing application documentation. Windows does not necessarily list every business dependency. Do not launch an application on an unprepared copy with production connections merely to try it.

5. Derive migration checks

Link service name, program version, account, dependencies and business owner in one row. Mark unresolved accounts and missing installation media as open issues. Plan later startup, network access, application-function and rollback tests in an appropriate isolated environment. Changes to accounts, permissions or services are separate implementation work; the inventory leaves the system unchanged.

Sources