A Global Channel Exchange - PowerPoint PPT Presentation

1 / 31
About This Presentation
Title:

A Global Channel Exchange

Description:

When used with NetWare 5, no IPX is needed ... At Least one NetWare 5 server. NDS for NT 2.01 (on separate ... NetWare, Novell Directory Services , and ZENworks ... – PowerPoint PPT presentation

Number of Views:50
Avg rating:3.0/5.0
Slides: 32
Provided by: nove50
Category:

less

Transcript and Presenter's Notes

Title: A Global Channel Exchange


1
A Global Channel Exchange
  • May 17, 1999

2
Novell and Citrix Integration Readiness
  • Roy Lopez, Senior SE, rlopez_at_novell.com
  • Bruce Huber, Senior SE, bruceh_at_citrix.com
  • Arlo Paranhos, SE, arlop_at_citrix.com

.
3
Agenda
  • I. It Works!
  • II. Citrix Synergy with NDS and ZENworks
  • III. How to...
  • a. The Basics
  • b. Domainless Load Balancing (no PN)
  • c. PN w/ NDS for NT
  • d. ZENworks for Enterprise Application
    Distribution
  • IV. Q A

4
I. Novell/Citrix Integration Progress
  • Citrix moved code out of GINA into WinLogon.exe
  • All Novell NT Clients Since Oct 98 are
    Multi-user Aware
  • TSE SP4 includes additional apis
  • Upcoming Update (B9CSP1.exe) to the Novell Client
    will allow selective access to Terminal Logon
    Path and Terminal Profile Path variables
  • Next version of NWAdmin/Console1 will include TSE
    profile path and home dir gui as well as config
    button info

5
I. What Is democity.novell.com?
Publicly Accessible Citrix Server
Farm Demonstrate Directory- enabled Solutions
Built by Novell and partners Web-based training
6
I. Whats behind Democity?
7
II. Citrix Synergy with NDS and ZENworks
8
II. ZENworks Capabilities
  • Application Management
  • Software Metering
  • Desktop policies and profiles
  • Printer driver mgmt.
  • Location Profiles
  • Remote control
  • Helpdesk interface
  • Y2k Testing

9
II. Benefits of Integration
  • Admins gain access to NWAdmin and now have a
    single solution to administer desktops and
    thin-clients
  • Users get same look and feel on fat and
    thin-clients
  • When used with NetWare 5, no IPX is needed
  • Novells ZENworks and NDS for NT further decrease
    the costs of administering the networks with
    thin-client servers

10
II. ZENworks Features in WinFrame Integration
  • Application management
  • Novell Application Launcher (NAL) 2.7 or higher
    is recommended
  • Software Metering
  • Desktop maintenance
  • Remote control of terminal server
  • Help request system
  • Desktop managementWorkstation Manager 1.0
  • Dynamic local user
  • Path to Microsoft policy and profile
  • Automatic client update

11
II. ZENworks features WTS/MetaFrame Integration
  • Application management
  • All of the WinFrame features
  • Desktop maintenance
  • All of the WinFrame features
  • Desktop management - Workstation Manager 1.1
  • All the 1.0 features plus...
  • Microsoft policy and profile management in NDS
  • Printer and printer driver management
  • Client configuration
  • Desktop preferences
  • Login restrictions
  • Hardware inventory

12
III. How to...
  • a. The Basics
  • b. Domainless Load Balancing
  • (no PN)
  • c. PN w/ NDS for NT
  • d. ZENworks for Enterprise
  • Application Distribution

13
IIIa. Novell Client Integration
  • MetaFrame
  • Requires Novell Client v4.5 for Windows NT or
    later
  • Best Case
  • TSE SP4
  • Novell NT Client 4.6 SP1
  • At Least one NetWare 5 server
  • NDS for NT 2.01 (on separate NT DC)
  • ZENworks 2.0 (1.1 w/update)
  • WinFrame
  • For WinFrame v1.7, apply Hot Fix SE17B058
  • Hot Fix integrated into WinFrame v1.8
  • Requires Novell NT Client v4.11b
  • Apply SE17B093 (NW5)

14
IIIb. Server Farms without Domains
  • How do I Load Balance Citrix without deploying NT
    domains?
  • Install Novell Client v4.5 for Windows NT or
    higher
  • Create a ZENworks user policy package and enabled
    dynamic local user
  • Publish application through thin-client server
    utilities
  • Modify registry
  • Place the server name in the LocalGroupList
    instead of the domain name
  • Null the GroupList
  • Export registry hive from initial server for
    published application then import hive to each
    server in the load-balanced farm
  • Thats all there is to it

15
IIIb. Deploying Citrix Server Farms without NT
Domains
  • By default the GroupList registry key contains
    the name of the NT domain

16
IIIb. Deploying Citrix Server Farms without NT
Domains
  • Simply null the GroupList key and input the
    server name\Users in the LocalGroupList registry
    key on each server in the server farm

17
IIIb. Deploying Citrix Server Farms without NT
Domains
Under the application that has been published
enter the name of each server in the server farm
under the ServerList registry key.
18
IIIb. Deploying Citrix Server Farms without NT
Domains
Create a registry key for each server in the
server farm with the InitialProgram and Work
Directory values.
19
IIIb. How Does Dynamic Local User Function?
  • Within NDS administrators create a ZENworks
    policy that grants users access to specific NT
    workstations and servers
  • As users authenticate to NDS the DLU policy is
    read to identify the workstations and access
    level that has been granted to the user through
    NDS
  • ZENworks dynamically creates the user an account
    on the NT workstation or Server

20
IIIb. How To Setup Dynamic Local User Policy?
NT user account is created using NDS credentials
Through NDS you can define NT group member-ships
and create custom groups
User account can be volatile or non-volatile
21
IIIc. Integrating PN using NDS for NT
  • With NDS for NT v2
  • Not supported on multi-user NT
  • Recommended configuration is to configure the
    thin-client servers as member servers, not
    PDC/BDC
  • Only IPX Support
  • With NDS for NT v2.01
  • Installing MetaFrame and Windows Terminal Server
    on the same server as NDS for NT will be
    supported
  • Pure IP Supported

22
IIIc. NDS for NT Components
  • Single DLL goes on each NT PDC, BDC
  • directs domain info to NDS database instead of
    Domain database
  • reduced hardware costs because of NDS fault
    tolerance
  • NT Domain Object Snap-ins reflect domains as
    objects in NWAdmin
  • NT Client for NDS communications

23
IIIc.NT Server Domain architecture
24
IIIc. NDS for NT redirection
25
IIIc. Publish Apps to NDS User Accounts
  • NDS for NT redirects the PAM samsrv.dll call to
    the NDS name space

26
Case Study Brunswick Outdoor Recreation Group
  • Previous Client Environment
  • No Novell services/technologies deployed
  • Majority Windows 95 desktops
  • No centralized configuration
  • Drive mappings and printer connections all done
    locally on workstation (persistent mappings
    performed at logon)
  • Microsoft Windows networking-based
  • Windows NT Server
  • Windows NT SNA Server
  • Windows NT Print Servers

27
Todays Customer Environment
  • MetaFrame servers deploying server farm doing
    load balancing without NT domains
  • Microsoft Windows Terminal Server (application
    servers)
  • Citrix MetaFrame and load-balancing software
    (clustering of application servers)
  • NetWare, Novell Directory Services, and ZENworks
  • User profile and policy management, dynamic local
    user creation, desktop preferences, printer
    definitions, and creation
  • Published Novell Application Launcher
  • End user presented with NAL windows onlynot
    entire desktop
  • End user TCP/IP accessno IPX/SPX

28
Frequently Asked Questions
  • How do I manage the different users contexts
    with the thin-client products?
  • Contextless login is the best solution
  • Can only be used with MetaFrame and WTS since it
    requires the Novell Client v4.5 for Windows NT
    and NetWare 5
  • Location profiles
  • Can only be used with MetaFrame and WTS since it
    requires the Novell Client v4.5 for Windows NT
  • In the intraNetWare Client v4.11b for Windows NT
    (WinFrame solution) the context/username pair is
    stored per server once the user has successfully
    authenticated to the network

29
Frequently Asked Questions (cont.)
  • Why are the WinFrame/MetaFrame profile path and
    home directory settings not read when the Novell
    Client for Windows NT is installed?
  • Novell in working with both Microsoft and Citrix
    have jointly resolve this issue
  • Does the thin-client solution integrate with NDS
    for NT? Yes
  • It is recommended from Novell, Microsoft, and
    Citrix that the thin-client servers not be
    configured as PDCs or BDCs
  • Required for Program Neighborhood

30
Current Novell Technical Information Docs (TIDs)
  • 2945422 Current Novell Client Versions
  • 2943151 Novell Client w/MS Terminal Server
    Summary
  • 2943813 NDS4NT and a BDC with MetaFrame
  • 2943961 Citrix MetaFrame and Context Issues
  • 2950353 First Login cant Launch NAL on MetaFrame
  • 2950750 Citrix Patch required to login to NW5
    Servers
  • 2947624 4.11b Client-WinFrame cant login
    remotely (SE17B074)
  • 2946246 Novell Server Locking up with Citrix
  • 2950815 Previously logged in User
  • For more information visit www.novell.com/product
    s/nds/zenworks/thinclient.html
  • www.democity.com
  • support.novell.com
  • www.citrix.com/support
  • www.novell.com/passport

31
(No Transcript)
32
Continuing WorldWide Through August 99
Write a Comment
User Comments (0)
About PowerShow.com