On 24-Sep-2002 at 15:41:10 Furnish, Trever G wrote: > Well then why not just schedule the export on the windows box. Just > script up whatever the process is for dumping the data from AD and make a > scheduled task for it. Then pull or push it over to your *nix box and do > whatever needs doing. > Unfortunately the server team that looks after the Windows servers have enough problems. It was the reason I was asked to see if we could sort out this one problem - the ldap output will be used to generate email addresses - from the unix side. (The central mailhubs, linux/unix boxes are using the exim mta.) In that respect we'd rather not ask the server team or the exchange servers themselves to do anything else. Make of that what you will! :-) It's all politics.
> Better yet, given the number of users you are talking about, you'd > probably want to keep two copies on the original server and script up the > process of comparing them so that you only send a new copy if something > changed. Better still, only send the changes. > Good idea; noted. A thought also was to (simply??) run a basic ldap server on the mailhub(s) which replicates the exchange servers. We can then get what info we want. Having said that I doubt the server team would want or allow us to get the entire info off their server. A list of users yes, everything else maybe not. I'd also rather not run a server alongside the mta just to solve this one problem if possible. John. ------------------------------------------------------------------------ John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 E-mail: [EMAIL PROTECTED] PGP key available from public key servers -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
