From: "Jorge R . Csapo" <jorge@completo.com.br>
To: "Kumar, Pradeep (MED, TCS)" <Pradeep.Kumar@med.ge.com>
Cc: "'linux-admin@vger.kernel.org'" <linux-admin@vger.kernel.org>
Subject: Re: Integrating Linux Desktop With MS Exchange Server
Date: Fri, 13 Dec 2002 17:18:31 -0100 [thread overview]
Message-ID: <20021213171827.A388@completo.com.br> (raw)
In-Reply-To: <8608421EC5CBD511B5090002A55C00480478E219@uswaumsx04medge.med.ge.com>; from Pradeep.Kumar@med.ge.com on Fri, Dec 13, 2002 at 12:54:25PM -0600
According to Microsoft support in my area, the only way to do this is buying
SFU (Services For Unix, IIRC) and install that on your PDC, then use NIS on the
Linux side. The PDC shouls appear as a NIS Master Server.
Probably there's some way of doing this with Samba, though. I think you'd better
start with the Samba documentation.
Finally, my own opinion: this should probably be done the other way around, with
Linux as the authentication server.
Jorge
assim falou Kumar, Pradeep (MED, TCS) (em 13/12/2002):
> Hi,
> I am sorry if I am posting this to a wrong mailing list. In that case,
> please suggest me the correct one.
>
> We are currently running Microsoft Exchange 5.5 server. Now we would
> like to run Red Hat Linux on some desktops.
> But we would like to have a unified logon procedure i.e all the windows
> users should be able to login on the linux desktop
> with their windows username and passwords. Whenever a user wants to
> login to the linux desktop, the authentication
> should be redirected to the Windows Primary Domain Controller. As a
> whole , it is just putting a linux desktop into
> a Windows domain. But all the usernames and passwords are created and
> maintained on the Exchange Server database and
> and authentication of all users should be done on the Exchange server.
>
> Please help me how to proceed on this. I would appreciate any useful
> information provided. What should I do to achieve this?
> What and all should be ruuning at Linux side? How to achieve this
> integration?
>
> Thanks in anticipation,
>
> Regards,
> Pradeep
>
> S.Pradeep Kumar
> Pradeep.Kumar@med.ge.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jorge R. Csapo
--------------------------------------------------
/"\
\ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
/ \
--------------------------------------------------
http://www.completo.com.br/~jorge
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster
next prev parent reply other threads:[~2002-12-13 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 18:54 Integrating Linux Desktop With MS Exchange Server Kumar, Pradeep (MED, TCS)
2002-12-13 18:18 ` Jorge R . Csapo [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-13 20:10 Shaw, Marco
2002-12-13 20:36 Dan_Caulfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021213171827.A388@completo.com.br \
--to=jorge@completo.com.br \
--cc=Pradeep.Kumar@med.ge.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).