[MiKTeX] MiKTeX installation problem

[Kristian Schilling]

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.

[Siep Kroonenberg]

Post by Kristian Schilling
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
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.

[Kristian Schilling]

The point is that the installation program does not continue after this
error and states it was not successful. Also, I had similar problems
when attempting to install to a local drive. In both cases, the
directory specified does exist, if it was not for the forward slashes.

Thus, I am stuck at this point, as I cannot complete the installation.

Post by Siep Kroonenberg

Post by Kristian Schilling
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
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.

--
Nanolytics
Gesellschaft fuer Kolloidanalytik mbH
Dr. Kristian Schilling

Am Muehlenberg 11
D-14476 Potsdam
Tel: [phone]
Fax: [phone]
e-mail: ***@nanolytics.de
Internet: www.nanolytics.de
_______________________________________________
Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.