> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/ja/configuration/gui-behavior/hide-tray-icon.md).

# トレイ アイコンを非表示

{% hint style="info" %}
このポリシーはバージョン 2.0 以降に適用されます
{% endhint %}

このポリシーは、KONNEKT がウィンドウのスタートバーのトレイ領域にアイコンを表示するかどうかを制御します。

ポリシーが有効な場合、トレイアイコンが表示されます。ポリシーが無効な場合、トレイアイコンは表示されません。ユーザーは、KONNEKT を `/ui` トレイアイコンを表示するためのオプション。

![](https://1902283602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FudcfsRI7uGYs7lmiU2qf%2F2021-10-27%2010_11_42-Windows%20Sandbox.png?alt=media\&token=525232fc-f401-4e6c-94f7-5c908bc96c89)

{% hint style="warning" %}
ポリシーを適用するには、再起動する必要があります **KONNEKT**
{% endhint %}

### **ポリシー情報:**

**ポリシー名：** トレイアイコン

### レジストリ

**キー名:** `ShowTrayIcon`\
**キーの種類:** REG\_DWORD（32 ビット値）<br>

## **ポリシーを適用する方法はいくつかあります:**

* マシンまたはユーザーのレジストリ設定の下でレジストリにキーを追加して手動で
* GPO で、参照 [GPO での設定](/ja/configuration/management-options/settings-via-gpo.md)
* Intune でポリシーを配信することで、参照 [Intune 管理対象デバイスの設定](/ja/configuration/management-options/setting-for-intune-managed-devices-1/intune-gui-settings.md#tray-icon)

**ポリシー** 保存先:

`HKEY_CURRENT_USER\SOFTWARE\Policies\glueckkanja\Konnekt`

`HKEY_LOCAL_MACHINE\SOFTWARE\Policies\glueckkanja\Konnekt`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konnekt.io/ja/configuration/gui-behavior/hide-tray-icon.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.