User-agent: MacSOUP/2.8 (Mac OS X version 10.4.8 (PPC))
Nigel Kersten <email@hidden> wrote:
> Well there are a couple of reasons I do it that way.
>
> Firstly I have an existing NetInfo database that gets pushed out via
> radmind, and it's not upgraded from "legacy", so dseditgroup won't
> work, even though nesting the group manually does work.
>
> Secondly due to NetInfo being a pain in the arse to manage
> atomically, I have a whole raft of NetInfo properties that I set at
> boot on my images, and they differ for each machine, so I set them
> all in a consistent manner.
Ok, I can understand your situation.
> I should have suggested this though. Ideally Workgroup Manager should
> let you add groups to the local NetInfo groups when you're viewing
> the NetInfo store as well.
Yep, but if you have a lot of computers to modify, pushing by a command
is much nicer than using WGM (even remotely) manually on each of them.
Of course, using radmind can be a good complement.
--
Laurent Pertois - ACT - ACSA
"Never forget: 2 + 2 = 5 for extremely large values of 2"
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
