Thank you for the response.
For point 1.), I am trying to integrate this into an existing pool which already has a running windows CM, and I believe I have all of the correct ALLOW settings, since it’s been running for about 9 months now.
In point 2.) you brought up some points on which I would like a little clarification. What do you mean “be certain that ID’s are consistent across your domain”? What is the “slot_user” is this specific to a linux CM?
3.) I have a working credd host, which has been handling credentials on my pool. Are the daemon level authorizations different for jobs submitted from a linux scheduler than a windows one?
Again, thanks for your response.
When working in a mixed env there are some tricks to keep in mind:
1.) Make sure all nodes are still pointing to a consistent CM (Usually Linux is preferred for scalability), and have the correct ALLOW settings.
2.) When doing an initial setup(for feasibilty) it's sometimes easier to use CLAIM_TO_BE and have windows use the normal slot_user account. However you need to be certain that your ID's are consistent across your domain (namely for remote submission).
3.) If you want to use run_as_owner on your windows machines then a CREDD will need to be installed on a windows box and daemon level authorizations need to be correct.
Hope this helps,