search for: provisin

..._ into my network and not run it as a part that manages my > network. > > Why not make it a domain member or standalone system with local users? > > > > > But if I would have to do this manually for every new system... > > You can script very easy around samba-tool the provisining, the join of > the second DC, user/group creation, etc. > > > And if you really want to work with cloning, then provision the first, > join the second, do all your change, take a snapshot of both. Then you > have the same setup again for the next customer. As long as the > c...

...network. >>> >>> Why not make it a domain member or standalone system with local users? >>> >>> >>> >>> But if I would have to do this manually for every new system... >>>> >>> You can script very easy around samba-tool the provisining, the join of >>> the second DC, user/group creation, etc. >>> >>> >>> And if you really want to work with cloning, then provision the first, >>> join the second, do all your change, take a snapshot of both. Then you >>> have the same setup ag...

...ipment is something I want to _integrate_ into my network and not run it as a part that manages my network. Why not make it a domain member or standalone system with local users? > But if I would have to do this manually for every new system... You can script very easy around samba-tool the provisining, the join of the second DC, user/group creation, etc. And if you really want to work with cloning, then provision the first, join the second, do all your change, take a snapshot of both. Then you have the same setup again for the next customer. As long as the customers never will met and two o...

...run it as a part that manages my >> network. >> >> Why not make it a domain member or standalone system with local users? >> >> >> >>> But if I would have to do this manually for every new system... >> You can script very easy around samba-tool the provisining, the join of >> the second DC, user/group creation, etc. >> >> >> And if you really want to work with cloning, then provision the first, >> join the second, do all your change, take a snapshot of both. Then you >> have the same setup again for the next custome...

Let me explain myself here. We ship video surveillance systems with build-in ad domain controllers on 2 servers. Right now we have 4 active projects and 3 more this year. Provisioning dc's by hand each time is a pain I would like to avoid. There's not much I want from a domain: groups 'video' and 'video admins' to exist, gpo's to auto redirect user profiles to network