Common
Windows Configuration 1:
(Ansoft recommends
this option if remote machines will also be used as local machines.)
All local machine users should solve as a common
user on the remote machine (hereafter known as the remote process user).
The user name and password for the remote process user must be provided
to each local machine user.
Note: If any local or remote machines are
Unix-based, this configuration cannot be used.
|
a) Only the remote process user
must be configured on the remote machine.
b) Local analyses on the remote machine continue
to work as they did previously.
|
a) The license log file will show
that the remote process user checked out the license, regardless of
the local machine user.
|
Common
Windows Configuration 2:
(Ansoft recommends
this option if remote machines are not used as local machines; e.g.
compute farm.)
All local machine users should solve as a common
user on the remote machine (hereafter known as the remote process user).
The user name and password for the remote process user need not be provided to each local machine user;
it will be stored on the remote machine only.
|
a) The remote process user must
only be specified on the remote machine.
b) The password information for the remote process
user can be restricted.
|
a) Local analyses on the remote
machine can only be performed if the machine is treated as a remote
machine at runtime.
b) The license log file will show that the remote
process user checked out the license, regardless of the local machine
user.
|
Common
Windows Configuration 3:
Any local machine user should be able to solve as
themself on the remote machine.
|
a) There are no user restrictions
— anyone can solve on the remote machine.
b) License checkouts are performed as the user who
requested the analysis.
c) Each local machine user's individual configuration
(e.g., number of processors) is used only by that local machine user.
|
a) Each local machine user must
run the software one time on each remote machine to configure the settings
used when solving.
|