Service User/Maxon One Questions

[JoelXvivo]

We're in the somewhat painful process of transitioning to Maxon One subscriptions for both C4D and Redshift, as our current node-locked Redshift perpetual licenses will eventually be going away. We also have a mix of farm/artist machines that require different license types and have been running into all sorts of licensing issues rendering jobs with RR. Some machines seem fine, while others throw RR licensing errors despite the license being verified locally.

Our current setup is something like this: artist machines utilize floating Maxon One with individual artist logins via the Maxon App, while farm machines have a separate account with only commandline and Redshift licenses assigned as needed. I ran the commandline on each farm machine to setup the account login and license assignment (via Maxon App).

My main question is, what effect does the rrService user have with this setup? If, for example, the service is running as a different user from the artist will RR jobs still utilize the artist's Maxon One login? Or do I need to ensure that the service user is the same as the one using that machine?

I guess my more general question (not just for Holger) is what is the most reliable way to setup the licensing in our situation? I'm aware of the different licensing options such as the in-house .rrEnv, a batch script with the mx1 tool, or licensing each machine individually. The RR docs currently have no mention of the Maxon App and I'm wondering if it's best to just bypass it somehow altogether. In any case, I can't seem to find a method that works reliably across the farm. Any input as for what I can try would be greatly appreciated.

[RR, Schoenberger]

Hi

 

As far as my test have been going, the MAXON login is saved for the machine.

I have tested that on our small company setup.

 

And then I managed the licenses on some larger farm.

There we used 2 logins.
For C4D it must be separated as you have UI and commandline licenses.

Artists used the MAXON app, in RR we used these env vars:

http://www.royalrender.de/help/Cinema4D.html

 

Note that the env vars work for C4D only.

But the farm used Houdini + Redshift as well.

Therefore we used the mx1 app to setup the login once.

It is linked to the MAXON app, but I am not sure if it saves the login at the same place in registry/user prefs/program data.

http://www.royalrender.de/help/Redshift.html

 

As it did not matter which login (renderfarm or artist) was used for Redshift, it worked.

And we did not test further.

 

 

PS:

>artist machines utilize floating Maxon One with individual artist logins via the Maxon App

An easier solution we used was to create one artist email that all artist use.

And afaik there was a way to automatically fill out the login with some text file.

Which does not interfere with the setenv setup of RR.

So artist do not have to remember the login.

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

[JoelXvivo]

Holger,

Thanks for your input. Sounds like I'll have to do some shuffling of the licenses and ensure that UI and commandline licenses remain separate. Part of the problem I think is that Maxon One includes commandline licenses so I'm trying to avoid pulling from the commandline group/user on the artist machines. From a cost standpoint it seems redundant to buy extra commandline/Redshift licenses for artist machines as Maxon One should cover all licenses needed. Ideally only the farm machines would need to pull from a commandline/Redshift license group. I'll do some more testing and see if I find a good way to "split" the licensing setup based on artist/farm machine.