Re: MiKTeX installation problem

On Thu, Jan 26, 2017 at 10:41:39PM +0100, Kristian Schilling wrote:
> Hello all, I am requesting assistance in setting up MiKTeX in a network 
> environment. After 10 years, I am figuring it is time for an update.
> 
> We have a number of workstations with identically mapped drives. To 
> date, the TeX system was located on the server, including all 
> executables and accessories, such as GhostScript etc. This made 
> maintenance easy and saved disc space on the client computers.
> 
> At first I thought the "Rollout MiKTeX in your organization" option was 
> fit for us, but it appears that only a repository is maintained on the 
> server, and a full 400 MB installation is made into every client system. 
> This is not what we want. I figured that a Basic Install *to a mapped 
> drive* is actually the right thing to do. By this, the executables and 
> all other TeX files will be on the server, and the correct locations of 
> all files will be present on a client after performing basic 
> installation and probably running initex. I guess one will have to run 
> through the full installation on *every* client once, but future updates 
> on the server structure will then reflect on every client, again, after 
> running initex.
> 
> The problem I encounter is obviously a hard coded path that cannot be 
> found for apparent reasons. I get this message near the end of the 
> installation procedure:
> 
> fileName="Q:\texmf\miktex/bin/x64\initexmf.exe", arguments="--force 
> --mklinks --admin --log-file=Q:\texmf\miktex/config\uninst.log 
> --verbose", exitCode="1"
> 
> There are some slashes where there should be backslashes, I don't think 
> I can do something about it.
> 
> I can probably circumvent this by running initexmf manually, but I do 
> not know what else might be necessary after this command which 
> apparently causes the setup program to abort.
> 
> Any advice is appreciated. Apologies if I might have overlooked 
> something while browsing the archives.

For our university, I am doing something like that with TeX Live; see
http://www.tug.org/texlive/w32client.html A complete TeX Live and
supporting programs are on a network drive, and a launcher program
contains menus and buttons to start programs, and also takes care of
configuration.

As to your problems: forward slashes often work fine.

The Q:-drive reminds me of application virtualization; a system to
ensure that programs do not see each other. As far as I can make
out, only the program itself can see inside such a directory.

But without knowing more, I may be totally wrong about this.

-- 
Siep Kroonenberg

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Q: How can I leave the mailing list?
A: See http://docs.miktex.org/faq/support.html#leavingml