I am trying to set up a miktex installation that can be rolled out to
thousands of computers and users in a campus environment. In short,
students will not have their own workstations but rather switch from
day to day to different boxes. The %APPDATA% for the users are stored
on the network shares, so they should have the same "Application Data
\MikTeX\2.6" folder on each system that they log into.
After digging into the miktex documentation and doing some test, I get
the feeling that the default installation will not work for our case.
If anybody has specific pointers to websites dealing with this issue,
I would be glad with any links.
As far as I can tell, there are user-specific trees and a "main" tree
which can only be written by Administrator. This is much like the
$HOME/.texmf tree and /usr/share/texmf tree that I knew from *nix
installations. However, there is also a CommonData and CommonConfig
tree that apparently stores (per-computer) files that get generated by
initexmf, such as psfonts.map. These "Common" are stored in the "All
Users" directory structure by default.
What I want is the following:
(1) a default installation on each computer (in Program Files) that is
(2) users can install packages (perferably using the GUI) in their
UserConfig and UserData trees. This is already possible using
mpm --install-root="c:\Documents and Settings\joeuser\Local Settings
\Application Data\MiKTeX\2.6\" --package=somepackage
but this is awkward in comparison with the GUI. Can the GUI (with a
registry setting or environment variable or so) point to the user
tree, rather than the one in "Program Files"?
(3) All initexmf-generated config files go the UserConfig and UserData
directory trees. In other words, I want to delete (ie not use) the
CommonData and CommonConfig trees. I tried this in the GUI, but I
cannot delete these root-trees. Also, there is no switch for
setupwiz.opt that prevents the creation of these trees.
With this setup, I think MiKTeX would work just fine. I think it would
allow users to maintain their own trees and use their customizations
on each computer. On not? Does anybody know how to achieve (1), (2)
and (3)? Alternatively, if someone has solved a network multiuser roll-
out of miktex in a different way, I would be interested in their
thanks - Michiel Kreutzer
PS: this is cross-posted at comp.text.tex, I hope that is acceptable in this