> For the complete documentation index, see [llms.txt](https://chunhthanhde.gitbook.io/google-learning-programs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chunhthanhde.gitbook.io/google-learning-programs/google-it-support-professional-certificate/course-4-system-admin-it-infrastructure/module-1-what-is-system-administration/3.applying-changes/3.recording-your-actions.md).

# Recording Your Actions 🖥️🎥

## Importance of Recording Actions 📋

When making changes to a system, it's crucial to have a clear plan and to document the actions taken. This practice helps in troubleshooting, maintaining records, and ensuring transparency.

## Methods for Recording Commands 📝

### 1. **Linux: Using `script` Command** 🐧

* **Command**: `script session.log`
* **Function**: Records the terminal session to `session.log`.
* **Stopping Recording**: Use `exit` or press `Ctrl-D`.
* **File Format**: ANSI format, which includes color codes. Convert to plain text or HTML using `ansi2txt` or `ansi2html` if needed.

### 2. **Windows: Using `Start-Transcript`** 💻

* **Command**: `Start-Transcript -Path C:\Transcript.txt`
* **Function**: Records the session to `C:\Transcript.txt`.
* **Stopping Recording**: Use `Stop-Transcript`.
* **File Format**: Plain text file containing commands and outputs.

## Recording Graphical Sessions 🎥

For actions performed through a graphical user interface:

* **Linux**: Use tools like `recordMyDesktop`.
* **General**: Utilize video recording tools such as OBS or VLC for documenting graphical actions.

## Summary 🗂️

Recording your system administration actions ensures clarity and accountability. Use `script` and `Start-Transcript` for terminal sessions, and graphical tools for GUI actions to maintain comprehensive records of your work.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://chunhthanhde.gitbook.io/google-learning-programs/google-it-support-professional-certificate/course-4-system-admin-it-infrastructure/module-1-what-is-system-administration/3.applying-changes/3.recording-your-actions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.