> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/virtual-machine-persistence.md).
# Virtual Machine Persistence for the Keeper Browser Extension
Persisting Keeper Browser Extension settings on virtualized desktops
## **Overview**
Some customers virtualize their workforce desktops with tools like VMware or Citrix. For the Keeper Browser extension to function properly on such desktops, certain directories may need to be persisted.
This applies to the extensions for Chrome and Edge. For each, three directories within the user's home directory must be persisted, as listed below.
## Extension ID
Some directory paths refer to an `.` Where the ID is referred to, you can opt to persist the entire parent directory, or you can find the ID in the table below.
For Chrome, the ID may be either of the Chrome IDs listed. For Edge, the ID may be either of the Edge IDs listed; or, if you installed on Edge using the Chrome Web store, the ID will be one of the two Chrome IDs.
Browser
Extension ID
Edge
lfochlioelphaglamdcakfjemolpichk OR mpfckamfocjknfipmpjdkkebpnieooca
Chrome / Edge
bfogiafebfohielmmehodmfbbebbbpei OR kbedblbpfmeicfpadihimgombbafaeeh
### Edge Locations
The following three directories should be persisted when using the Edge extension.
**Extension Installation:**
`C:\Users\%username%\AppData\Local\Microsoft\Edge\User Data\Default\Extensions\`
**Indexed DB:**
`C:\Users\%username%\AppData\Local\Microsoft\Edge\User Data\Default\IndexedDB\chrome-extension_`
**Storage:**
`C:\Users\%username%\AppData\Local\Microsoft\Edge\User Data\Default\Local Extension Settings\`
## Chrome Locations
The following three directories should be persisted when using the Chrome extension.
**Extension Installation:**
`C:\Users\%username%\AppData\Local\Google\Chrome\User Data\Default\Extensions\`
**Indexed DB:**
`C:\Users\%username%\AppData\Local\Google\Chrome\User Data\Default\IndexedDB\chrome-extension_`
**Storage:**
`C:\Users\%username%\AppData\Local\Google\Chrome\User Data\Default\Local Extension Settings\`
---
# 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://newdocs.keeper.io/en/enterprise-guide/deploying-keeper-to-end-users/keeper-fill/virtual-machine-persistence.md?ask=&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.
