A task can exist in Windows 7 Task Scheduler yet fail on a replacement computer. Executables, working directories, accounts and network destinations are part of the workflow. This inventory records the old state; it does not run, change or import tasks. Use an authorized account on the existing computer without reconnecting it to the internet for this purpose.
1. Record identity and ownership
Open Task Scheduler from Start search. Browse Task Scheduler Library and its subfolders. Select a relevant task and open Properties. Record the full folder path, task name, description, enabled or disabled state and responsible person. Identical names in different folders identify different tasks. Start with custom and application tasks; do not blindly transfer system tasks to another Windows version.
2. Read every properties tab
- General: execution account, whether logon is required, highest privileges and compatibility setting. Record account names, never passwords.
- Triggers: every trigger including start date, time, repetition and enabled state. Also record the old computer date, time and time zone without changing them.
- Actions: every action in sequence. For program launches, record executable path, arguments and “Start in” separately. Explicitly note an empty working directory.
- Conditions: idle, AC power, wake and network requirements. A correct schedule alone does not guarantee execution.
- Settings: missed starts, failure handling, runtime limits and handling of an already running instance. Close with Cancel afterwards.
3. Add dependencies
For each action identify the required application and version, scripts, configuration files, input and output folders. For mapped drive letters establish the actual share and the execution account permissions. Access from an interactive session does not prove access from a background task. Back up required files through the approved backup procedure; the task inventory does not contain them.
Arguments or scripts may contain credentials. Do not copy secrets into screenshots or ordinary documentation; record only the responsible protected storage. Mark unclear dependencies as unresolved instead of broadening permissions or changing accounts.
4. Interpret execution evidence
Record last run time, last result and next run time. Read existing events under History. Disabled or empty history does not prove the task never ran. This inventory does not enable history retroactively. A process reported as successful also does not prove that an expected file is complete or business processing is correct. Compare existing application logs and output with the responsible person.
Optionally, schtasks /Query /FO LIST /V in Command Prompt displays detailed task information. It starts no tasks and is not a restorable backup. Record access errors; in that case do not consider the visible list complete.
5. Handover without an uncontrolled trial run
For each task the handover records purpose, owner, all listed settings, files, permissions and unresolved issues. Define expected output and a responsible person for later isolated testing. Do not click Run for inventory purposes: tasks can send email, modify data or overwrite backups. Only a separately planned test on the destination establishes whether the workflow can migrate. Documentation alone is neither an XML export nor a successful migration test.