I guess I am confused about what you are trying to do...
I apologize. End of the day brain rot is terrible for explaining things. :)
Do you want:
a) submit jobs from windows that will run on linux machines
b) submit jobs from windows that will run on windows machines
c) both a and b
I'm looking to be able to do 'c'. In the future hopefully users will be
submitting from both linux and windows, but for the moment linux is
only running on the backend so for now I'm working on a scenario where users will be starting jobs on windows workstations to a pool that consists of both Linux and Windows machines.
In all cases you want the job to run as the user who submitted the job,
This is correct. I'm considering work arounds for my proof-of-concept, but ultimately jobs will need access of an nfs share as the user who submitted the job. We are using the hummingbird nfs client which maps our windows usernames to our ldap information (uid and such is correctly handled in this case then). Our windows domains are syncronized with our unix accounts which use ldap. We have hooks in place when accounts are created and when users change their passwords so that usernames and passwords are the same regardless of the kind of computer you choose to login to. We rely on the nfs client to handle any UID and GID issues on the windows side when nfs is concerned.
If the answer is (c), you then need the credd for part (b).
So this means that submitting my job from windows should by default run as owner under linux? If so, then I assume then some other aspect of my windows configuration is incorrect as well. :)
Pardon me if I jump ahead here for a second. Would this mean also that Credd should only be run on windows machines? I ask because our central manager is a linux machine and I have been attempting to run credd on it as CREDD_HOST.
I can try to help more once you clarify what you are trying to do ....
Thanks for your patience.