[THIN] Re: Novell Integration
- From: "Ron Oglesby" <roglesby@xxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 9 Sep 2003 12:23:49 -0500
MetaDirectory is tooooo much for that.
In yoru case (needing Windows and Netware credentials) you generally
would not use the Netware/ZEN integration fro MetaFrame. Instead you
would put the Netware client on the Citrix server and manage the citrix
servers using windows accounts.
Citrix even states that the Netware ZEN support is only for environments
WITHOUT domains...
Ron Oglesby
Senior Technical Architect
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
-----Original Message-----
From: Matt Kosht [mailto:matt.kosht@xxxxxxxxxxxxxx]
Sent: Tuesday, September 09, 2003 10:37 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Integration
I pulled the trigger on Zen/Novell route myself this past weekend.
Still chasing down problems (printing mostly). Zen on paper looks great
in practice very buggy/problematic. Also had some apps that had to map
drive letters to Windows servers that's fun w/o any Windows credentials.
Microsoft has a product called Metadirectory service that can
supposedly sync the two directories AD and eDirectory.
I am thinking that might be the best option to solve this dilemma.
I am just wishing I could have pulled the plug on Novell altogether and
went pure AD but as John Belushi would say "Buuuttt Nooooo!".
>>> craig@xxxxxxxxxxxx 9/9/2003 12:25:01 AM >>>
BTW, I decided to go the AD/Novell route without the Zenworks piece.
It's going
to be a terrible pain, though, over the next few days as everyone has to
sync
their Novell password with their new Windows password. That's only 1500
students I get to deal with in a two day span.
What's even better about this setup is almost every app either has some
video,
audio or COM port mapping that goes along with it. Woooot!
Quoting craig@xxxxxxxxxxxx:
> How did I know that you were going to respond?
>
> I might take a look at both solutions, then, this weekend. I need to
get
> moving on this and I'm afraid that the Windows route is going to be a
bit too
>
> burdensome. At this point in time, the school has no plans to move
from
> NetWare any time soon. Actually, their servers have been rock solid
and have
>
> had no problems since their inception (knock on wood).
>
> I know NetWare enough to do whatever I need in NWAdmin. Outside of
that,
> though, I have to rely on others. We do have two guys though, that
know
> Novell
> stuff inside and out. So, I'm not too worried about the support.
>
> My biggest concern is not that one of these routes wont work - I know
that
> they
> will. My concern is about simplicity. Their "administrator" doesnt
know
> much
> in the way of network administration and thankfully she knows as much.
What
> I
> want is to be able to leave this project and know that Im not going to
get a
>
> call every 4 hours on how to do such and such. By adding in the
Windows
> component, I know that things will get a bit more complex than they
would
> have
> with the ZENWorks route.
>
> Anyway, thanks for the input. Ill take a look at the DLU/Zenworks
deal a bit
>
> more today.
>
> Quoting Ron Oglesby <roglesby@xxxxxxxxxxxx>:
>
> > Craig, Long time no see, or hear.....
> > Anyway, the Netware piece works but is not in use as much as the
windows
> > stuff obviously. So when something breaks or doesn't work it is hard
to
> > find help (or even good support) on it.
> >
> > If you don't know novell doing this is problematic. I have a real
good
> > novel guy on my team so it doesn't scrare me. But if I didn't I
would
> > recommend Windows every time.
> >
> > I guess the question is that if you HAVE to implement this and no
one
> > else you still have to do what is best for the customer. If they
don't
> > want windows use netware just be prepared to LEARN a lot.
> >
> > BTW the roaming profile is assigned as a User attribute just like
NT/2K
> > and DLU handles creating the local user and setting up profiles
etc....
> >
> > PS> Novell has decided netware is dead. No more development for that
> > network OS. Instead all of their development if for Linux. Why stay
with
> > a dead product.
> >
> >
> >
> > Ron Oglesby
> > Senior Technical Architect
> >
> > RapidApp
> > Office 312.372.7188
> > Mobile 815.325.7618
> > email roglesby@xxxxxxxxxxxx
> >
> >
> > -----Original Message-----
> > From: Craig M. Luchtefeld [mailto:craig@xxxxxxxxxxxx]
<mailto:craig@xxxxxxxxxxxx%5d>
> > Sent: Friday, September 05, 2003 7:56 AM
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] Novell Integration
> >
> > Does anyone have any thoughts about which Novell integration route
is
> > better
> > -- the ZENWorks/Dynamic Local User route or the simultaneous Windows
> > 2000
> > domain route with dual accounts?
> >
> > I've got a school I'm working with, approximately 1500 students with
the
> > environment holding anywhere from 150-200 concurrent sessions.
We're
> > still
> > in the 'testing' phase, so we can still go either route for
deployment.
> > My
> > problem with the Windows 2000/Novell route is that they're going to
have
> > to
> > create two accounts for every student, we're going to have to
sync/reset
> > all
> > their passwords, and they're going to have one more point of failure
(if
> > the
> > DC goes down).
> >
> > Honestly, I need to read up a bit more on how the ZENWorks deal
works,
> > but
> > if its creating a dynamic local user, my thought is how are roaming
> > profiles
> > going to work?
> >
> > Anyway, has anyone had the opportunity to take a look at both of
these
> > pieces and examine the advantages/disadvantages to both? From the
> > Advanced
> > Guide for FR3, I saw the integration steps for them both, but if I
> > remember
> > correctly, it didn't state advantages/disadvantages to either.
> >
> > Thanks in advance,
> >
> > Craig
> >
> > ********************************************************
> > This Week's Sponsor: ThinPrint
> > http://www.thinprint.com
> > **********************************************************
> > Useful Thin Client Computing Links are available at:
> > http://thethin.net/links.cfm
> >
> > For Archives, to Unsubscribe, Subscribe or
> > set Digest or Vacation mode use the below link:
> > http://thethin.net/citrixlist.cfm
> > ********************************************************
> > This Week's Sponsor: ThinPrint
> > http://www.thinprint.com
> > **********************************************************
> > Useful Thin Client Computing Links are available at:
> > http://thethin.net/links.cfm
> >
> > For Archives, to Unsubscribe, Subscribe or
> > set Digest or Vacation mode use the below link:
> > http://thethin.net/citrixlist.cfm
> >
>
>
>
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
********************************************************
This Week's Sponsor: ThinPrint
http://www.thinprint.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
