AW: ISA 2000 and Windows NT 4 domains
- From: "Christian Sommer" <christian@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 24 Jul 2001 22:19:28 +0200
Hi,
install ISA on W2K Server which is a normal member of your NT Domain.
You must install ISA on a W2K Server, but you need no Active Directory
Structure.
Christian
-----Ursprüngliche Nachricht-----
Von: gquintel@xxxxxxxxxxx [mailto:gquintel@xxxxxxxxxxx]
Gesendet: Dienstag, 24. Juli 2001 20:27
An: [ISAserver.org Discussion List]
Betreff: [isalist] ISA 2000 and Windows NT 4 domains
http://www.ISAserver.org
Hi All,
I am new to ISA discussion list and the ISA in general. I am hoping that
someone here and or perhaps Mr. Shinder may have the answer to this
question.
Here is the scenario: My company has several Win NT 4 domains they
represent functional business units within the company using Proxy server
with a third party plug-in providing content filtering. I have been
charged with the task to try to implement ISA 2000 into our network
environment without harming any productions servers or domains. Hence the
beginning of my dilemma, ISA 2000 will primarily act as a web cache for
internet users and also perform some web publishing in the near future.
My questions are as follows:
Can ISA as a web cache product be able to live on Win NT 4, all the info
that I have found suggests that it can but would merely reside in the
registry and I would not better off than keeping Proxy around in that
case. If that is false any info would be greatly appreciated.
Second if I would to create a separate win 2000 domain and have 2 way
trusts with all the other separate Win NT 4 domains would that give me the
benefits that I hope to harness from ISA. (If so would I have to keep win
2000 in native mode or in mixed mode.)
Thanks for any help in advance
GQ
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
christian@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
