WhiskeyMan
MIS
I have been tasked to take an R&D coding group into AD. Currently they work on a private network, with access to all other resources via routing to the main network. The issue is that we have UID's on the main network that do not match the UID's (UNIX, Linux, etc.) on the private. I wanted to try and use Windows Services for UNIX 3.5 to do user name mapping and password syncronization for the front office users (I'm not so worried about the developers having to remember their UNIX ID's). They currently use a Change Management system that if they use their AD ID's, you have no way of knowing who may have Checked out/Checked in some code, so we want to keep the UNIX ID's as they're based upon their name, not their employee number
When I approached the primary IT team they said that it would require changing the Schema, which they are not willing to do. They have already created a seperate OU for us to use, but it is my understanding that a child domain would be a better option, as then we can have a one way trust from their domain to ours so if we mess up, it will not impact there setup.
Am I close in my thinking here? Could anybody give me some hints, tips, etc...
Thanks,
Bruce
When I approached the primary IT team they said that it would require changing the Schema, which they are not willing to do. They have already created a seperate OU for us to use, but it is my understanding that a child domain would be a better option, as then we can have a one way trust from their domain to ours so if we mess up, it will not impact there setup.
Am I close in my thinking here? Could anybody give me some hints, tips, etc...
Thanks,
Bruce
