github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #7969] Administrative / silent install is borked #51611

New Issue
Open
opened 2026-04-28 20:38:17 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-28 20:38:17 -05:00
Owner
Copy Link

Originally created by @Lukas-UAUX on GitHub (Dec 6, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7969

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

For deployment scenarios like for classrooms or to regular managed devices the setup needs to perform an administrative / unattended install. For InnoSetup built installers this can normally be done via the command-line switches /SILENT (or /VERYSILENT) or via a response file via /LOADINF. (See: https://jrsoftware.org/ishelp/index.php?topic=setupcmdline )

If the setup can be performed by both, an unprivileged user and an administrator the switch "/ALLUSERS" helps to select the latter. If the install paths are (correctly) derived from the common environment variables this should automagically move the files to "C:\Program Files" or "C:\Program Files (x86)" instead of the users AppData folder.

Normally this would also lead the installer engine to register the application under the systems registry (HKLM:) and create a system wide start menu.

With Ollamas setup this does not work even though setting the install-path like mentioned in the documentation to 'C:\Program Files\Ollama' makes it look like it should.

Instead it creates a mix of both methods where the files are installed to the Program Files folder, but the registry and start menu entries are limited to the user (context) installing the software. And as most management system use a local system service as context this creates a rather weird state. And even if I could limit the permissions down - for a classroom for example I can never know which user will access the device...

OS

Windows

GPU

No response

CPU

No response

Ollama version

0.4.7

Originally created by @Lukas-UAUX on GitHub (Dec 6, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7969 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? For deployment scenarios like for classrooms or to regular managed devices the setup needs to perform an administrative / unattended install. For InnoSetup built installers this can normally be done via the command-line switches /SILENT (or /VERYSILENT) or via a response file via /LOADINF. (See: https://jrsoftware.org/ishelp/index.php?topic=setupcmdline ) If the setup can be performed by both, an unprivileged user and an administrator the switch "/ALLUSERS" helps to select the latter. If the install paths are (correctly) derived from the common environment variables this should automagically move the files to "C:\Program Files" or "C:\Program Files (x86)" instead of the users AppData folder. Normally this would also lead the installer engine to register the application under the systems registry (HKLM:) and create a system wide start menu. With Ollamas setup this does not work even though setting the install-path like mentioned in the documentation to 'C:\Program Files\Ollama' makes it look like it should. Instead it creates a mix of both methods where the files are installed to the Program Files folder, but the registry and start menu entries are limited to the user (context) installing the software. And as most management system use a local system service as context this creates a rather weird state. And even if I could limit the permissions down - for a classroom for example I can never know which user will access the device... ### OS Windows ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.4.7
GiteaMirror added the installfeature requestwindows labels 2026-04-28 20:38:17 -05:00
GiteaMirror commented 2026-04-28 20:38:20 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Dec 10, 2024):

Our setup based installer is currently optimized for individual installation. For system wide installation, please follow these instructions: https://github.com/ollama/ollama/blob/main/docs/windows.md#standalone-cli

<!-- gh-comment-id:2532358901 --> @dhiltgen commented on GitHub (Dec 10, 2024): Our setup based installer is currently optimized for individual installation. For system wide installation, please follow these instructions: https://github.com/ollama/ollama/blob/main/docs/windows.md#standalone-cli
GiteaMirror commented 2026-04-28 20:38:21 -05:00
Author
Owner
Copy Link

@nolme commented on GitHub (Mar 3, 2026):

Our setup based installer is currently optimized for individual installation. For system wide installation, please follow these instructions: https://github.com/ollama/ollama/blob/main/docs/windows.md#standalone-cli

Hello, in 2026, the link is 404.

<!-- gh-comment-id:3989272228 --> @nolme commented on GitHub (Mar 3, 2026): > Our setup based installer is currently optimized for individual installation. For system wide installation, please follow these instructions: https://github.com/ollama/ollama/blob/main/docs/windows.md#standalone-cli Hello, in 2026, the link is 404.
GiteaMirror commented 2026-04-28 20:38:21 -05:00
Author
Owner
Copy Link

@SirNate0 commented on GitHub (Mar 6, 2026):

https://github.com/ollama/ollama/blob/main/docs/windows.mdx#standalone-cli

<!-- gh-comment-id:4011866386 --> @SirNate0 commented on GitHub (Mar 6, 2026): https://github.com/ollama/ollama/blob/main/docs/windows.mdx#standalone-cli
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request install windows
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#51611
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?