@thestraycat thanks for following up.
I feel your frustration, but at the moment being a workaround already there - you can start the different clients either using Scheduled Tasks or simply using the Start-Up folder in the ProgramData as mentioned above - I don't see it as a deal-breaker.
Rest assured that I've already notified our developers about the issue and hopefully based on our development prioritization.
Best, Riccardo
Strict Security GPO's make this a lot harder to do in an enterprise environment. Easier if it's just a PC under your desk..
@r_gigante - I take it there has been no progress or milestone date to return running the functionality of teamrender client running as a service (as of R21) going forward?
If so, this is a shame.
Due to our infosec requirements of being a larger company. Our Microsoft GPO policies stop us from running a foreground application as a logged in user due to it being a rather large security risk! As mentioned previously, there were added benefits for us running this as a service, not only was it a supported method of running an application, it also gave as resilience of our render service due to auto-starting failed agents due to things like memory leaks or bad jobs etc.
It also had fundamentally broken our monitoring and analytics pages that we expose to our user base that track the service running state.
It has also stopped us piping our service logs into log aggregation solutions like logarr and splunk.
It seems strange that the functionality existed. And now has been removed. I understand this may be in effect due to substantial re-writes but it seems an oversight to not keep the functionality or plan to return it. In essence, your making the product harder to run for larger organisations. It seems a bit counter productive.
Can someone explain the rationale behind the decision to remove the functionality?
Hi @thestraycat, I see your frustration but although the topic is still under my radar I can't give an estimation on when it will be addressed. Unfortunately this looks like a regression that has nothing to do with API or plugin development and I can only increase the awareness on the issue.
Rest assured that I'll try to keep you posted upon the discussion.
Best, R
I appreciate your reply @r_gigante
Should i be speaking to a different team? Can you recommend a good contact or any insight into how i can get this in front of the relevant people?
Hi @thestraycat thanks for following up.
@thestraycat said in Cinema 4D Client R21 Service Creation:
It seems strange that the functionality existed. And now has been removed. I understand this may be in effect due to substantial re-writes but it seems an oversight to not keep the functionality or plan to return it. In essence, your making the product harder to run for larger organisations. It seems a bit counter productive.
I've just opened a bug-report to confirm the regression, although it must be told that this was not a functionality intentionally added but something that by chance was simply working in past versions.
There's no other "better" team to contact because considering the technical level of the topic, it's likely you're going to be forwarded again here.
Best, R
Hi @thestraycat, quick follow-up: today I've internally discussed the issue and it's likely it will take a while (at least 6 weeks) before development resources can be spent on fixing it.
I'll get back on the topic as soon as I've fresh news.
@r_gigante Thank you for checking in and updating! I'll keep a keen eye on the thread, if you need me to test anything just shout.
@r_gigante - Hi R.
Some time has past and i was wondering what progress you guys may have made on this issue?
Hi @thestraycat, I'm sorry to disappoint you but the option to start the TeamRender Client via NSSM or SC or WinSW has not yet been restored.
I can only ask, to contact us via our official email address, to better describe the impact this issue is causing on your work to escalate the discussion.
Best, Riccardo