Hi Joey

I'd say that this is unsupported...

I don't see how it can work unless you lock it all down.
Consider what will happen with default.xsipref:

User A changes a preference and exits. That updates default.xsipref.
Then user B changes that same preference to something else, and maybe some other preferences, and exits. The xsipref file is again updated. User A starts Softimage again and their preference changes are gone, so they do them again.
And so on and so on...

You may or may not get away without a lock file problem.

Off the top of my head, couldn't XSI.bat call a script on a server, and that script writes out a standard custom.xsipref file to the local User location?







On 08/03/2013 11:11 AM, Ponthieux, Joseph G. (LARC-E1A)[LITES] wrote:

Stephen,

I realize that user profiles are intended to be centric to the user, but I think I would like to have my user profile propagated to other machines. If that's possible without being reckless.

As for workgroups the .wkg looks interesting but I'm not really having any issues with the workgroup itself.

The question really is can 2+ instances of Softimage, on 2+ separate machines, safely read and write to a single profile located on a central server for the intentional purpose of propagating a single user profile across multiple machines?

--

Joey Ponthieux

LaRC Information Technology Enhanced Services (LITES)

Mymic Technical Services

NASA Langley Research Center

__________________________________________________

Opinions stated here-in are strictly those of the author and do not

represent the opinions of NASA or any other party.

*From:*[email protected] [mailto:[email protected]] *On Behalf Of *Stephen Blair
*Sent:* Thursday, March 07, 2013 4:06 PM
*To:* [email protected]
*Subject:* Re: XSI_USERHOME and Workgroups

Hi

User profiles are more per-user than a workgroup. For example, user preferences are stored in the user profile (defaults.xsipref).

That's where your workgroups are listed. For example:
data_management.workgroup_appl_path = C:\Users\SOLIDANGLE\Documents\Workgroups\sitoa-2.7.1-2013

XSI.exe updates the prefs on exit, so you may want to make the user location read-only if you are going to share one User location between multiple machines.

For workgroups, you could use a .wkg file instead, and that can go either in the Factory Data location or the User Data location.





On 07/03/2013 3:28 PM, Ponthieux, Joseph G. (LARC-E1A)[LITES] wrote:

    I'm setting up multiple machines to run Softimage 2013 SP1. I've
    come to a question which I'm unsure how to address.

    I set my workgroup to a central location all systems point to a
    single workgroup. It dawned on me though that I still had a user
    profile which was now being replicated on multiple machines. That
    user profile set by

    set XSI_USERHOME=%XSI_USERROOT%\Autodesk\Softimage_2013_SP1

    which is the install location. The thought occurred to me that I
    could also move the user profile to a central location and have
    all machines point to it.

    I realize that workgroups and user profiles are similar, but since
    I can't find a parameter  in the setenv.bat that points to
    workgroups I have to assume that the workgroup is defined in the
    user profile.

    So the question is this. Is there any danger to pointing to a
    single user profile from multiple machines? Will simultaneously
    instances of Soft on different machines club settings in the
    centralized profile?

    I realize the point of Workgroups was to have a central single
    location that plugin and other resources could be propagated to
    multiple machines, but is that also the case with the user
    profile?  Are there any experiences where this was discovered to
    be an issue?

    --

    Joey Ponthieux

    LaRC Information Technology Enhanced Services (LITES)

    Mymic Technical Services

    NASA Langley Research Center

    __________________________________________________

    Opinions stated here-in are strictly those of the author and do not

    represent the opinions of NASA or any other party.


Reply via email to