Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I'm not sure if it's a good idea to run teh job processor on a server OS. It would mean to support the CAD systems on a server OS as well.
On a smaller scale though: Why not run the job processor as a service instead of a task? It would make administration easier since you don't need a dedicated Windows user who is logged into the job processor machine.
I'm curious about this point, now we have inventor server which runs as a headless application (and inventor full, server and truview) seem to have no issues on 2012 server why not. I imagine gpu performance is lower, but network performance, disk performance is increased, and within the server network where firewalling, virus check in can be reduced (if protected externally to the vault server and job server) performance gains are there too. The gpu I imagine impacts translation time, but from my setup, downloading and checking in is more of the job time than doing the work, for a large amount of files,only the very large assemblies and drawings, where this is reversed.
I'm curious how much effort to support cad software on a server is, as I've been running it quite happily for the last 6 years.
pls make JobProcessor run as service. In high security IT- workspaces it is not allowed to keep a client always logged in. normally It is a stanalone Jobprocessor client where no one is working but logged in.
We have the JobProcessor running on a server. Now I need to make sure I'm logged in to keep it up and running. IT regularly updates the server and I'm logged out again. This wouldn't be an issue if the JobProcessor could be run as a service.
Administrators describe the method of registering and operating the job processor as outdated. To use a job processor you have to be logged in with a Windows user, then start the application and the job processor runs after you have logged in accordingly. If the job processor client is automatically restarted, you can have the job processor start automatically after the Windows login and the job processor user logs in automatically = o.k. Criticism is the registration via a Windows user. In the case of automatic login, a password must be stored in plain text in the registry. In any case, we are currently not aware of any other method. It would be desirable to be able to run the job processor application as a kind of service without a Windows login. We are aware that the job processor requires additional applications in order to process the jobs correctly. Nevertheless, we would like Autodesk to investigate whether and, if so, how this vulnerability can be fixed.
It would be extremely helpful if Autodesk would look at this. For us, we have 3 vm’s that are dedicated job processors. We have adjusted the intervals to cover as much wait time as possible. The issue is for my company, vm’s are considered tier 4, this means they are NOT highly available, subject to random restarts for updates, and are not backed up.
We have Windows/Vault accounts that are used for log in, but we must monitor the vm’s and log back in to make sure the job processor is up and running every time a vm is rebooted, and in some cases, all 3 vm’s go down because they are in the same cluster.
Because we have so many users working in Vault, the que piles up with errors and we get a plethora of support tickets every time this happens.
The job processor should be a server-based service.
Any assistance/comments/suggestions are appreciated.
We recently migrated all of our separate vaults into a common Azure environment. It has been an ongoing nightmare to setup the job processor on a VM and get it running. Many of the processes seem to contradict modern IT policies and ultimately require someone to monitor the queues and check the Job Processor is up and running.
See the forum below of similar complaints (mainly the 2023 posts)
It is absolutely mindboggling that Autodesk is so stuck in the 1980's when it comes to this. This critical process should absolutely be able to run on a highly redundant server as and independant service that doesnt require desktop interaction. This is absurd. Autodesk, get your act together, come into the modern age!
I have been working with SC command with various command line arguments but not having great success. Also attempting some powershell scripts being called by task scheduler. Ill report back when i have completed doing Autodesks job....
The job processor is a critical component to effect process changes within our Engineering department integrating with the rest of the company. If we were only worried about a small group being disrupted this would be not as urgent - if the whole manufacturing process can be delayed then we have a bigger problem.
Also, most network management platforms support monitoring services, like SQL or IIS, natively. I have turned on the additional logging to the event log but now I would need to build special monitoring for the appropriate events. If this was a service, it would be monitored automatically without any deep knowledge of the platform.
Reiterating the importance of being able to run Job Processor as a service. With Windows 10+, updates and restarts can't be disabled, and IT policies tend to involve regular server reboots.
Perhaps Inventor Server etc could also run as a service?
We have the same issues with the current Job Processor set up. We really need to be running this as a service so it can be managed in a proper way. (see the previous two post for the reasons.
In this time of virtualisation and options for running scale sets of machines, It really needs to be a service to comply with current security requirements.
Curious why this went from future consideration to archived. I don't know how many times I come back from a long weekend or vacation and have to login to restart Job Processors. Make our life easier Autodesk. 😉
Come on Autodesk, we can't keep having "user" sessions running such important processes as job processor jobs. That is a practice some pursued between the 90s and the start of the millennium. The common consensus in IT is running your services on Windows as Microsoft Services not as user applications. You are not a small organization and someone in your company surely knows this, please find that someone so you can act upon this.
Just to be clear, here are in no particular order some arguments for this request (although it almost feels stupid pointing out the obvious)
- Security (no unsecure auto logon also from the 90s)
- Cost (far less human monitoring and maintenance required for a running Microsoft Service)
- Uptime (Microsoft services are designed for being able to run continuously were as user sessions are meant to be just that.. sessions )
- Monitoring (most if not all IT monitoring tools can monitor your services with little effort)
On a side note:
Please don't rush us in to the cloud. Like most responsible companies we would like to wait until the world wide data "sharing" frenzy has been contained.
Couldn't agree more with you @ed_de_boer_RGXQ26BG2C2K. For our team, this is 3 separate job processors that a maintained and monitored by 3 separate users (24/7). We're not central IT so the regular desktop/VM reboots, wipe out all 3 sometimes, other times it's 1 or 2 at random. We have a scheduled plan where each of the 3 monitors (users), go in and look at the job que in 2-hour intervals, just to make sure the jobs are getting processed. We even wrote a small app to install on the pc's that emails the 3...basically an hourly "heartbeat", and a shutdown notification. We record all of our JP issues in our ticketing system, and the time spent on this issue, is greater than 20 hours per week for all 3 users monitoring. This needs to be escalated, not bumped down in the list. One of the reasons that so many companies have issues with their Vault, is because they are forced to seek alternative processes due to job processor issues. This sets them up for future issues, which in turn become support requests to Autodesk. And cloud-based options are not an option, nor will they be for most utility companies, so that discussion needs to go away (for those groups).
