> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/developer-tools/commander/older/commander-v16.9.19.md).

# コマンダー 16.9.19

GitHubでリリースを確認: <https://github.com/Keeper-Security/Commander/releases/tag/v16.9.19>

## 向上点

* [`enterprise-node`](/keeperpam/jp/commander-cli/command-reference/enterprise-management-commands.md#enterprise-node-command)\
  スイッチ`--logo-file`で、企業/ノードのロゴを設定できるようになりました。
* [`distributor info`](/keeperpam/jp/commander-cli/command-reference/msp-management-commands.md#distributor-info)\
  各MCの詳細情報が追加表示されるようになりました。
* [`team-approve`](/keeperpam/jp/commander-cli/command-reference/enterprise-management-commands.md#team-approve-command)\
  複数ユーザーのチーム承認を一括処理する際の性能を改善しました。
* [`verify-records`](/keeperpam/jp/commander-cli/command-reference/misc-commands.md#verify-records-command)\
  V2レコードの検証に対応しました。
  * これまではV3レコードの検証のみに対応していました。

## バグ修正

* [`scim`](/keeperpam/jp/commander-cli/command-reference/enterprise-management-commands.md#scim-command)\
  複数グループが存在する場合の処理を改善し、グループの一覧がある場合は最初のグループが選択されるように修正。
* その他軽微なバグ修正および改善。


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/developer-tools/commander/older/commander-v16.9.19.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.