
-----------------------------------------------------------------------
NVCL-NT.DOC -- 19980302 -- Email thread on the NT Requestor for NetWare
-----------------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Wed, 14 Aug 1996 16:54:03 -0800
From: Mark Schoonover <Mark_Schoonover@CCMAIL.SGO.SONY.COM>
Subject: NT Running Logon Scripts to Access NW - The Ultimate Kludge!

I was tired of running around to all of my NT boxes because I made
a simple change to a login script. I finally figured out a way to have
an NT workstation process a logon script, capture printers, map drives
and run an inventory program. As everyone on this list has figured out,
NT won't process Netware container or personal scripts. The setup here
is NT Japanese accessing NDS using the Novell NT client. Here's what
I've done and hopefully others can use this information. Some
background first:

The terms login and logon have two different meanings. Login means
4.1, logon means NT scripts. There are two ways to map drives and capture
Netware services under NT -- one is to go through file or print manager
respectively. The other way is to use the NET USE command at the prompt.
What I did essentially was put a batch file that contains these commands
into the startup group for the NT computer, not the personal startup group,
that points to a locally stored copy of NTSCRIPT.BAT. Here's a snippet from
the NTSCRIPT.BAT I'm currently using:


	echo off
	net use f: \\tva_eng\sys >> NUL
	net use g: \\tva_eng\sys\grp_data >> NUL
	net use h: \\tva_eng\sys\users\%USERNAME% >> NUL
	net use i: \\tva_eng\sys\common\iso_docs >> NUL
	net use m: \\mail2\mail >> NUL
	net use n: \\tva_eng\sys\common >> NUL
	net use s: \\tva_eng\sys\winapps >> NUL
	net use t: \\tva_eng\sys\transfer >> NUL
	net use z: \\tva_eng\sys\public >> NUL

	net use lpt1 \\tva_eng\lj4mv_pq1 >> NUL
	net use lpt3 \\tva_eng\lj4mdss_pq1 >> NUL

	f:\mcafeesm\siteinv\agent\ntequip /noshow

	copy /v f:\login\ntscript.bat %systemroot%\system32\repl\import\scripts\.


The syntax is NET USE x: \\<file_server>\<volume>\<directory>
for mapping drive letters and NET USE lpt# \\<file_server>\<print_queue>.
AFAIK, there isn't a way to map root, but there is a way to map to the next
available drive letter.

The NTSCRIPT.BAT file is stored in the
%systemroot%\system32\repl\import\scripts directory and is copied down
from the server everytime it is run. That way I can make changes to just
one file and have it distributed to the computer. The NT username and
password are the same to logon to the NT workstation and to login to NDS.
It would be possible to 'attach' and map drives to other servers, even if
it requires a seperate userid and password. Also, it would be possible to
call another batch file with the command CALL %USERNAME%.BAT for a
'personal' script -- I haven't tested this though. Currently, this setup
does generate a system 85 error message that says the current network
service is already in use -- hence the >> NUL. I'm having problems with
the /persistent switch. I don't want the mappings to stay permanent, they
need to be remapped or NET USEd everytime a user logs on. That way if the
user removed this file from the startup group, they would have to find me
to get back on the network. Also, when changes are made to the file, the
user needs to logon twice -- once to copy it down and again to run the new
version. I've thought of moving the copy command to the top of the batch
file, but haven't tested it yet and I haven't tried using any of the
Netware script variables inside the NTSCRIPT.BAT file. They may work. Like
I said, this is the ultimate kludge, but so far it seems to be working
just fine.

P.S. Now that I think about it, It may be possible to have one persistant
connection to the network, where the NTSCRIPT.BAT file in the startup group
just points to a single copy located on the server. No copying and the user
could only delete the icon from startup. Will also try this idea later.

------------------------------

Date: Mon, 26 Aug 1996 09:04:32 -0800
From: Mark Schoonover <Mark_Schoonover@CCMAIL.SGO.SONY.COM>
Subject: Re: NT Client Beta

>Anyone had any luck in getting the nt35b1 client running on NT 4.0.
>Mine has come up with the blue screen of death and an
>'INVALID_KERNEL_HANDLE' message among other things.  According to the
>documentation the client should run on NT 4.0 beta.  I am using the
>release version of NT4.  This is on a IBM PC750-P90 with 32mb Ram and a
>NE2000 (or compatible) network card.
>
>I would like to log a NT workstation into a Netware 4.0 server.  I
>used the Microsoft client and it logged in ok but my understanding is
>it does not support NWAdmin (I did not try and run it).  I did not
>try and do this with 3.51 but may have to just to test it and wait
>for the release of the NT client.

I've had one machine develop the same error as you describe, but it
was on a 3.51 workstation. The problem hasn't happened again, so I
don't have any pattern for the problem. I have used the NWAdmin on
another 3.51 system without a problem using the beta client. So far,
I've been able to gather the following information:

	Requestor       v4.00a
	ShellType       v4.00a
	DOS Version     v3.51

Will post more as time goes on.

------------------------------

Date: Thu, 29 Aug 1996 15:05:00 NZST+1200
From: Alister Leask <ALeask@ORAKEI.AIT.AC.NZ>
Subject: NT 3.51 and Netware Client

What you have said appears to be true!

I am currently using 3.51 with the Client 32 for Netware - and I like
it very much!

I have found that you can log in separately to the workstation and
the network. The second or third tab in that login window allows you
to select whether you want a Workstation login only or Workstation
and network.

We will probably use this feature in our open access labs with a
generic login for the workstation (that protects the improtant areas)
and allow the users to login to the server and get all the usual
drive mappings.

------------------------------

Date: Tue, 17 Sep 1996 09:37:01 -0400
From: Dick Cook <cookd@SERVEND.COM>
Subject: Client32 for NT Beta

I remember some discussion a few weeks (?) ago about NT client passwords
and concern for having to support two user bases (or something like that).
I don't remember the answers though.

While I was looking for some info on nprinter for NT (did not find any) I
came across a document called "Managing Passwords with NetWare NT Client".
The AutoAdminLogon feature (NT's I guess) is detailed in this doc.  I
haven't tried it yet but, it looks like it may have helped whoever asked
the original question. (If this was already mentioned then I apologize)

The TID is 2912680.
the URL is http://support.novell.com/cgi-bin/search/tidfinder.cgi?2912680

------------------------------

Date: Thu, 19 Sep 1996 13:58:52 -0800
From: Mark Schoonover <Mark_Schoonover@CCMAIL.SGO.SONY.COM>
Subject: More Client32 Information for NT and WIN95

Netware Client32 4.00 Beta Information for NT. The
Registry information contained here is all found under:

HKEY_LOCAL_MACHINE\SOFTWARE\Novell unless otherwise noted.


1. Where is the login date and time stored in the registry?

   It can be found under key name \Graphical Login\Results Pos
   under Last Write Time.

2. How can I determine installation date?

   This can be found \NetWareWorkstation, Last Write Time.

3. Where are the default tree name, bindery server, login script
   Netware User Name, ProfileScript etc, stored?

   These all can be found in the key \NWGINA\Login Screen
   section.

4. Can I change the animated Netware cursor?

   Yes -- there looks to be two ways. One, edit the registry
   under the key \NWGINA\Login Screen\NWLoginCursor to the
   *.ANI file you want, or rename the NOVELL.ANI file
   NOVELL.BAK and rename the file you want as your cursor
   to NOVELL.ANI. NOVELL.ANI is in the %systemroot% directory.

5. Can I change the Client32 Welcome Screen?

   Nope. On initial trial following the directions for
   changing the *.ANI file, it still starts with the
   default Netware login file.

6. How can I change the NWLANGUAGE?

   It's under \Parameters, value 1 name: NWLANGUAGE.

7. How can I determine which code pages are installed?

   Look under
   Key Name: HKEY_LOCAL_MACHINE\CLONE\CLONE\Control\Nls\CodePage

8. What is the requestor and shelltype versions being report?

   Requestor:      v4.00a
   ShellType:      v4.00a


95 and Netware Client32 Information. The
Registry information contained here is all found under:

[HKEY_LOCAL_MACHINE]\Network\Novell, unless otherwise noted.


1. Where is the path saved for client32?

   It's in \System Config\Install\Target Path\

2. Where are the multiple [trees, contexts, profiles, variables,
   scripts, servers] stored in the 95 registry?

   They can be found under:
	   \System Config\Network Provider\Graphical Login\ section.

3. How can I change the NWLANGUAGE?

   It can be found under \System Config\Language\NWLANGUAGE

4. What is the requestor and shelltype versions being report?

   Requestor:      v0.01
   ShellType:      v0.01


Version |Name                      |Date           |E-mail Address
---------------------------------------------------------------
1.00       Mark Schoonover         09/19/96        schoon@cts.com

------------------------------

Date: Fri, 27 Sep 1996 14:33:31 EST
From: David Potelle <Pote@HER-CHER.ORG>
Subject: Client32 for WinNT Open Beta

Has anyone tried this client and NOT experienced severe DOS box
instability?

Any DOS utility (3rd Party, Novell, or otherwise) that accesses
network resources in a DOS box locks the BOX almost immediately.  The
box cannot be closed, and NT cannot shut down normally?

------------------------------

Date: Fri, 15 Nov 1996 12:56:12 +0000
From: "Benito Antonio N. Bajuyo Jr." <bbajuyo@CORP.NSC.COM>
Subject: Re: Novell WinNT4.0 client problems

>One of the workstations here running WinNT4.0 has just had the
>new Novell client32 installed and is having some problems....
>
>1) Drive mappings in the login script are all being ROOT mapped
>despite NOT being specified as such.  The simple workaround was,
>of course, to remap the drives to the volume but I have not been
>able to find this behaviour documented anywhere.

still haven't found a work around or cause for this...

>2) The environment PATH value is not being set correctly.  After
>booting and logging on the PATH comprises only
>\WINDOWS\SYSTEM32\ and the Netware search drives. However, if
>the system control panel/environment tab is selected, the PATH
>entry highlighted (but not changed) and the "Set" button
>pressed, the PATH then includes all the application directories
>as specified in AUTOEXEC.BAT.

NT does not read the Autoexec.BAT. It uses its own autoexec file
(autoexec.nt) found in \winnt\system32. Same is true for the
config.sys -> config.nt

>Prior to installing the netware client this workstation was
>using the MS client with none of these problems. (There were
>other problems, particularly with passwords.)  I didn't do the
>client install myself, so don't know what, if any, options were
>selected.
>
>This is the only workstation using this client - most
>workstations are still WIN3.1/DOS with the VLM client or
>Client32, a few are Win95 with Client32, plus a few other WinNT
>with the MS client.  The servers are Netware 4.01.  The
>workstation is a 486DX2-50 with 16MB ram.  There are no other
>apparent problems.

------------------------------

Date: Wed, 20 Nov 1996 09:45:00 -0500
From: "QUIBELL: MARC" <txh8205@TEXCOM-HOOD.ARMY.MIL>
Subject: MS Client

>Why are so many Client 32 (Novell) problems reported to this group and
>so few MS Client for Netware problems reported? Is there a message here
>about Novell's Client 32 software versus Microsoft's?

The answer is simple: No one is dumb enough to be using the MS client. It
is flat broke. Just wait 'til you get ahold of Windows NT 4.0--It's MS
client is kaput right out of the box, no "First network drive" setting,
in fact no customizable settings at all, and NDS support is way bad.
I suggest a download of the 13MB Novell Client32 for NT before you even
start NT 4.0. It works seemlessly with NT, and full NDS support.

Microsoft should be ashamed of this feeble attempt to support our Novell
network with their MS Client for Netware junk.

------------------------------

Date: Sat, 28 Dec 1996 16:40:59 -0500
From: Larry Hansford <hansford@ERINET.COM>
Subject: Windows NT Service Pack 2

For those who are running Windows NT 4.0  Workstation PCs on their
Netware network, Microsoft has released a Service Pack 2 that fixes a
couple programs with this OS.  Namely, they have fixed the problem with
the Novell Client-32 for Windows NT not seeing the FPNW volume, and
they have eliminated the 32-volume limit for workstations on Netware.

They have also fixed a number of problems with laptops running Windows
NT 4.0 Workstation.

The service pack is at:

	ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes

then follow the paths to the correct country and version.  This is a large
file -- about 15 Mb worth -- and there is a separate text file with
instructions for installing it.

------------------------------

Date: Tue, 18 Mar 1997 07:26:05 -0500
From: Dennis Large <wdlarg01@homer.louisville.edu>
To: netw4-l@ecnet.net
Subject: Re: WinNT Client32

>>Has anyone gotten Novell's Client32 for WinNT working?
>
>Yes, i am running it on several workstation successfully, but on NT4, not
>3.51 . Just installed, set preferences (tree, context, banners, etc.) and
>off it went.
>
>Johan Reinalda

Ditto here, incl 3.51. I'm not a heavy user myself, this was done at
another of our departments that is using NT extensively. I'm just glad
it worked as well as it did.

------------------------------

Date: Tue, 25 Mar 1997 00:38:23 -0500
From: Larry Hansford <hansford@ERINET.COM>
Subject: Re: CLient 32 for NT

>Has anybody successfully installed the NTclient32?  I get it
>installed, and then when I try to login it takes about 5-10 minutes
>before I get to the desktop screen.  I am running NT workstation 4.0

Yes, we are running Novell's Client 32 for NT on all of our Windows
NT 4.0 Workstations, and not experiencing any problems at all.  I have
not seen a single workstation having any problems connecting with
the network or with mapping drives as it boots.

---------

Date: Tue, 25 Mar 1997 08:13:26 +0100
From: Eckardt <eckardt@EADQ.IZFP.FHG.DE>
Subject: Re: CLient 32 for NT

>Has anybody successfully installed the NTclient32?  I get it
>installed, and then when I try to login it takes about 5-10 minutes
>before I get to the desktop screen.  I am running NT workstation 4.0

I have installed ServicePack2 of NT4.0. It fixes a lot of NT4.0-errors
and I think with this ServicePack NT4.0 comes out of the Beta-phase ;-).
I have installed the NTclient32 (ntenu41n) and it works OK.

------------------------------

Date: Fri, 18 Apr 1997 21:22:28 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client32 and Win 95 Shared Install

>>	I'm not trying to sell an approach, but I am trying to clarify the
>>technical environment just a little.
>>	Joe D.
>
>Joe, can you confirm that your comments about WIN95 & VLMs vs C32 apply
>equally to WIN/NT?
--------
	No, not directly I can't because I discarded my latest copy of
NT (3.50). NT does have an elaborate MS-networking style remote boot
procedure, whose directions I have in some NT developer's material
(not distributable) and which I think must be released by now. But
from what I do surmise the strategic problems are nearly the same.
	That is, the GUI stuff rolls along inspecting the system and only
most of the way through that process does it reinitialize the lan adapter
hardware and start up the network connection. What Microsoft has done
in Win95, and apparently in NT too, is boot to real mode NDIS drivers,
stuff connection information into setmdir (yeah, that item does many strange
jobs) as a bridge, and then at the appropriate late moment kill the real
mode drivers and load the protected mode kind.
	The strategy is probe the machine, init hardware, and after the main
GUI has stabilized in protected mode then start networking (needs the GUI
for popup menus etc). It is going on two years since I looked into the MS
material, so please forgive the errors.
	There are certain advantages to being the creators of that muddle
rather than trying to outwit it by reverse engineering (which is basically
what Novell faces). However, we see a *possible* similar strategy for Novell,
if they were to pursue it fully. Needless to say, it too would be messy. You
can increase their awarness of such need for a remote bootable Client32 by
making constructive noises to your Novell area representative for relaying
to Provo. The programming effort would be substantial, and hence in
competition for resources devoted to similar projects (NT client being the
lastest such effort).
	[I say this having just finished yet another quick re-reading of
ODI remote boot rom code for DOS. Difficult stuff, that.]
	I'd be happy seeing say TLMs (Top Level Modules), which would be the
VLM material put on top of DOS as a true shell (NETX style) rather than
beneath the surface as a formal redirector, and hence able to play the long
filename game fully while being real-mode remote bootable. But we know that
as soon as something like that appeared there would be suddenly a Win95C
which is mysteriously incompatible with that approach...
	Joe D.

------------------------------

Date: Fri, 6 Jun 1997 10:34:41 -0700
From: Andrew Bynum <abynum@PC-SUPPORT.COM>
Subject: Re: Win NT Client Install Help

>I'm looking for instructions on how to install the Novell
>Netware Win NT client.  I've read the instructions in the
>Netware client help file, and am not finding what I want
>to know.
>
>I have Netware 3.x servers, new PCs with Win NT installed.
>I've looking for basic instructions on what steps to follow
>for installing the necessary network support, WITHOUT
>ending up with these PCs shooting useless packets all over
>the place.  There are no NT servers here, and I have no
>desire to share any NT resources.
>
>What I tried to do was.
>1.  Installed the network card, and then went to Control
>Panel, Networks, (said no to loading WIN NT network
>support.  The NW NT Client help file doesn't say to load,
>or not to load this stuff), and added the card driver.
>Restarted the PC.
>
>2.  Ran the Novell Netware Client for Windows NT Setup
>program.  It complained a couple of times about not finding
>a necessary file, but copied them from the NT system CD
>when provided.
>
>3.  Set things up for Ethernet_II, preferred server etc.
>And things worked OK on the IPX/SPX side.
>
>4.  Added TCPIP support from Control Panels/Network (again
>declining to install Windows NT network stuff).  Got the
>TCPIP added, and added IP address, mask, and gtwy. (no DHCP
>or WINS here).  When exiting, NT complained that it
>couldn't update a file, but seemed to save the settings
>anyway.
>
>Although things seemed to work OK for TCP/IP and IPX/SPX, I
>get persistant complaints from NT anytime I go into the
>Network Settings (can't update file, "Don't I want to
>install Win NT networking").
>
>So I finally gave in and installed the Win NT networking
>support, and then reinstalled the Netware Client.  The
>errors are gone, but I wonder what "unneeded" stuff I'm now
>carrying.
>
>Under Control Panel Network
>Services: Computer Browser, NetBIOS Interface, Novell
> Intranetware Client for Windows NT, RPC Configuration,
> Server, Workstation.
>Protocols: NWLink IPX/SPX Compatible Transport, NWLink
> NetBIOS, TCP/IP Protocol
>Adapters: [1] ODI EtherExpress PRO/10 LAN Adapter
>Bindings:
>-NetBIOS
> +NWLink NetBIOS
> +WINS Client (TCP/IP)
>-Novell Intranetware Client for Windows NT
> +NWLink IPX/SPX Compatible Transport
>-Server
> +NWLink NetBIOS
> +NWLink IPX/SPX Compatible Transport
> +WINS Client (TCP/IP)
>-Workstation
> +NWLink NetBIOS
> +WINS Client (TCP/IP)
>
>Looks like I'm losing this battle.  Is it possible to setup
>Windows NT as a Netware Client, with TCP/IP support, AND
>NOT have it trying to participate in the Windows NT
>networks?  Anyone have their own installation procedures
>for putting Windows NT PCs just on a Netware network?
>Plenty of courses and books available for NT, and for
>migrating from Netware to NT.  But I haven't found any
>good resources yet on how to integrate Windows NT Clients
>into a Netware network.  Is there perhaps a dynatext file
>for this somewhere (I only have the 3.12 dynatext)?

The INW client for NT is primarily for NetWare networks that utilize
NDS, but are capable of logging into 3.x servers for backwards
compatibility.  Also, the client assumes that the NT client already has
networking installed (as this was a late addition to Novell's arsenal
for integrating NT), and part of the installation process utilizes some
of the basic networking components of NT (such as some of the DLL's that
are used for network calls).  I would recommend that when you install
NT, you go ahead and install the native network components as though the
machine was going to utilize the NetWare server (NWLink & CSNW).  When
you install the INW client for NT, then the installation process will
remove the unnecessary components, and keep the ones that it needs.

One important note, the INW Client for NT replaces the NT GINA
(Graphical Identification and Authentication) with a NW GINA.  This NW
GINA can be set to either utilize the NT workstation's SAM (Security
Account Manager) or obtain information from the Novell NDS tree as to
user rights, and profiles.  If you are only using NW 3.x, then you have
to make sure that all of the security information comes from the NT
machine itself.  As for easier integration, upgrade to
IntranetWare........this should make it a lot easier.  Feel free to
contact me if you have any further questions.

Oh yeah, so far as I know (and I have been searching diligently) there
aren't any real technical documents that deal with this type of
integration fully.  But hopefully, someone will write a book soon.

------------------------------

Date: Tue, 15 Jul 1997 08:37:49 +1000
From: Greg J Priestley <Greg_J_Priestley%PKF@PKF.COM.AU>
Subject: Re: client32 and banners and NT

There is a patch available for the Intranetware Client for NT called
NTIT5.EXE which does something about some problems in this area.

------------------------------

Date: Wed, 30 Jul 1997 13:04:00 -0700
From: Kevin Miller <kevinm@UHS.BERKELEY.EDU>
Subject: Re: Novell Clients, NT 4.0 Server w/FPNW ????

There is a bug (rather, an implementation error) in Microsoft's FPSW
that makes it incompatible with Client 32 clients.  There is a patch
for this on Microsoft's WWW site.

------------------------------

Date: Wed, 6 Aug 1997 17:00:49 +0200
From: Hans Nellissen <dbphilos@UNI-DUESSELDORF.DE>
Subject: Re: <help> How to synch NT 4.0 WS time to server clock?

If you know the mac-address from NT workstation, then you can do
a station-specific:
	net time \\server /set /y
in the login-script.

------------------------------

Date: Thu, 14 Aug 1997 09:43:57 +1000
From: Michael Strasser <M.Strasser@MAILBOX.UQ.EDU.AU>
Subject: Re: Client32 for NT/Win95 and login scripts

>We run a number of external programs in our login scripts, which has
>worked well for DOS logins, but not so well for NT and Win95 logins.
>I'm checking ways of combining all of the output from login script
>commands and external programs into a single window. Some questions:
>
>1. Has anyone found a slick way of doing this?

No. I found that only the script processor can write to the
"Login results" window. I have a simple Win32 program that
counts new mail messages (*.CNM in SYS:MAIL/xxxxxxxx) and puts
up an alert. It is very crude and relies on being passed the
user ID as an argument. (This is on NW 4.11 but we still use
Mercury and Pegasus in bindery mode.)

>2. Is there any way to control the size of the window created by the
>   login program?

The size and position is saved in the registry in:

	[HKEY_LOCAL_MACHINE\Network\Novell\System Config\Network
	  Provider\Graphical Login\Results Pos]

so any changes you make are 'remembered' (regardless of the
"Save settings on exiting Login" settings on the Client 32
Properties login tab). I guess you could change them in advance
if you had a registry-poking tool.

>3. Is there any way to control the font used - I want to use
>   a non-proportional font.

Not as far as I know.

------------------------------

Date: Wed, 8 Oct 1997 09:27:13 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NT wkstation protocols

>We are setting up NT 4.0 workstations. We use a netware 4.10 server for
>file/print/cdrom sharing services mainly. So far we have used the
>netware 4.10 client (and also the 4.11a on a few stations, some problems
>there, though it may solve more that it created). Joe D. posted a note in
>the last digest mentioning network protocols to use for communicating
>between nt wkst. and netware servers, mentioning that IPX was not a good
>idea. If anyone could elaborate with some more detail on the correct protocols
>to use I would find that very helpful.
---------
	Just about every time I respond to this item I also list the two
alternatives: NetBEUI (not routable) and RFC-NetBIOS (NetBIOS over TCP/IP,
routable).
	Joe D.

------------------------------

Date: Thu, 9 Oct 1997 10:42:15 -0700
From: Brandon Fouts <BrandonF@WSHA.ORG>
Subject: NT Integration with Netware

This is for all those people adding NT to their Netware
Networks. A lot of tools to help manage NT - both
workstations & servers. They aren't magic, but they keep
getting better and more powerful.

	http://www.novell.com/intranetware/ntint

------------------------------

Date: Wed, 15 Oct 1997 09:05:13 +1000
From: Michael Bednarek <mb@DOH.HEALTH.NSW.GOV.AU>
Subject: Re: Login Scripts & Roaming Profiles on NT?

>We have been working with Novell Tech support for over a month to diagnose a
>problem where the login scripts don't run on NT 4.0 if the user has only
>"user" rights to the local workstation.  If the user has "administrator"
>access to the local workstation, login scripts run fine.
>
>Yesterday, I discovered that the culprit was roaming profiles.  If they were
>turned on, login scripts failed, if they were off they ran.  I'm thinking the
>problem may be in the way that the roaming profiles are defined.  We have the
>roaming profiles defined on the local C: drive, rather than on the network.
>
>In the Roaming Profiles (for NT 4.0) field, we have the following entry:
>
>C:\WINNT\Profiles\Default User\
>
>Is there any reason this wouldn't work?
>
>We are using Novell NT Client 4.10 (Workstation Manager 1.0), NT 4.0 SP1, FAT
>NT partition, INW Server.

SP1 and FAT make it a bit more difficult to guess the cause of your
problem.  Get SP3 and convert to NTFS.

Anyway: I think a user needs "Full Control" permission for her own
profile.  "Everyone" has only "Read" permission to the directory
"Default User".

Change the roaming profile to one where the user has "Full Control"
permission.

---------

Date: Wed, 15 Oct 1997 09:16:11 -0500
From: Gilbert Armour <garmour@FRAMATECH.COM>
Subject: Re: Login Scripts & Roaming Profiles on NT?

First, you are not using "roaming profiles".  Roaming profiles stores
each user's profile on a server so that no matter where they log on
they get the same desktop.

Second, Default Profile is for users that don't have a profile
defined.  NT uses default profile the first time and then saves the
profile under the person's user name at logout.  Only the
administrator can change the default profile.

Users do have to have full rights to their profile, whether it is
a roaming profile on a server or a local profile on C:.  The only
exception is using mandatory profiles.  Users cannot change them.

Either take out the roaming profile entry or change it to a directory
on a server.  If you want mandatory profile put it in common accessed
directory.  If each person can change own profile, then suggest their
home directory.  In any case, read the NT docs on profiles.  There is
more to it than I can put in this message.

---------

Date: Wed, 15 Oct 1997 10:15:33 PST
From: Kevin Miller <kevinm@UHS.BERKELEY.EDU>
Subject: Re[2]: Login Scripts & Roaming Profiles on NT?

I understand the intended use of profiles, but here is my dilemma.  We
are using the "volatile users" feature of Workstation manager.  We
don't want to store profiles on the server.  If we don't store them
SOMEWHERE, changes made by a user will be deleted when that user logs
out, and their account (and profile) are removed from the system.

So, rather than putting a "roaming" profile on a server, we have opted
to put it on the local drive.  That way, changes made to the desktop
stay only on that PC, in much the same way that Win 3.1 works.

------------------------------

Date: Wed, 29 Oct 1997 21:26:57 -0500
From: Bud Durland <ndurland@CAPITAL.NET>
Subject: Re: WinNT 4.0 Client

>I'm thinking of switching from Win95 for our users'  O/S to WinNT 4.0
>Workstation on a 4.10 server.

Do you have a compelling reason to do so?  Make sure you review what
software you are (or will be) using to make sure it will run under
NT 4.x

>Does anyone have any feedback on this scenario? I'm mainly
>wondering about connectivity hassles with the Novell client
>for NT and speed.  I have heard horror stories about NT Workstation
>running slow on a Novell server.

I've run NT/ws 4.0 on a Novell 4.11 network with no problems.  The
performance problems I had were directly related to my workstation;
i.e., when I installed 64Mb of RAM, NT ran about as fast as Win95
did in 32Mb.  NT has some additional security features, as well as
HTFS, etc, which will tend to make it slower than Win95.  As far as
connectivity goes, I didn't have any problems with the Novell
client, and network performance seemed quite good.

---------

Date: Wed, 29 Oct 1997 22:17:02 MST/MDT
From: "Benjamin E. Fore" <benf@BADGER.SNOW.EDU>
Subject: Re: WinNT 4.0 Client

This is also of great interest to me because we just switched one of
our machines today from win95 to NT.

So far, I have noticed a -slight- difference in log in speed.

There has also been a -slight- difference in p-mail speed.

The real difference has come when 'closing all programs and logging
on as a different user'.  This has at times taken several minutes.
I have noticed, however, that if I go to network neighborhood -first-
and detach from all servers, -then- "close all programs and log on as a
different user", there is very little delay -- at any time during the
process described above.

As to processing speed in general for applications, I have seen very
little difference.  (The machine is a P133 w/32 meg. RAM.)

This may not be the general case however--I say that because we have
heard only one other complaint so far from our NT users on campus of
slow logout time.

------------------------------

Date: Thu, 30 Oct 1997 19:23:10 -0500
From: "Philip P. Obbard" <Philip_Obbard@BOSCAT.COM>
Subject: Re: WinNT 4.0 Client

We've got a 25 user 4.11 LAN, and to be honest, we've had much better
success with NT Workstation clients than we have with Windowss 95 clients.
This has also been true as far as Novell connectivity goes. Not only is
Novell's Client for NT actually *faster* (especially when it first starts)
than Microsoft's built-in client, but in general, NT's networking
capabilities are more robust than Windows 95. Likewise, the Client for NT
has not been plagued with the bugs and performance issues of Client32 for
Windows 95.

But, as another poster said, the important issue when switching from 95 to
NT is not "How will it work with Netware?", but, "Will all my applications
still work?"

---------

Date: Thu, 30 Oct 1997 15:02:08 -0700
From: Robert Seifert <seifert@GWC.MARICOPA.EDU>
Subject: Re: WinNT 4.0 Client

I have Win NT 4.0 w/s installed, using Microsoft's Client Service for
NetWare, and connecting to an INW 4.11 server.

The only speed degradation I have noticed is when NT initially discovers
the server.  Before and after, all seems fine.

Other factors would play a part, but with both Win95 and NT 4.0
installed on the same machine, I see little if any difference in
connection speed between the two.

------------------------------

Date: Sat, 15 Nov 1997 14:09:51 -0500
From: "Philip P. Obbard" <Philip_Obbard@BOSCAT.COM>
Subject: Re: nprint under Client32 for NT- ntvdm?

My guess is that you are using Windows NT 4.0, with Service Pack 3 applied.
Service Pack 3 introduces a bug into the NTVDM.EXE (which stands for NT
Virtual DOS Machine, the 16-bit subsystem NT uses to run all 16bit DOS and
Windows applications). This is documented in the MS Knowledge Base, but no
fix is available (other than clicking "Abort" or inserting *any* floppy
into the A: drive).

Basically, any DOS-based program that requires disk access (to any drive)
automatically causes NTVDM.EXE to try and access the floppy drive (A:).
Hence the message you see. I have never used NPRINT, but I get the same
problem when running FILER.EXE inside an NT DOS session on any NT4 machine
with Service Pack 3 installed.

If you *really* want to have some fun, try installing MS Office 4.3 on the
same machine... you'll get about twenty such messages before you give up
and force quit the Install...

------------------------------

Date: Mon, 24 Nov 1997 14:18:54 -0500
From: George Spack <gspack@NVTC.STATE.VA.US>
Subject: Re: Novell 4.1 with NT 3.51 WKS

>I am running Novell 4.1 server with NT 3.51 Clients when I try to log
>on it says that I can't be authenticated on the the Server
>Server1, would you like to pick another preferred server, when I say no
>and try to connect to Server1 again, I can, and all network drives map
>fine...What would cause this from happening in the first place.

I get this problem from my users several times a day. Here it is caused by
users hitting the [Enter] key when they type in their username instead of
tabbing or clicking down to the password field. The initial login attempt
without a password is caught as a failed login, but when the login window
returns, the username is then filled in and the cursor is at the password
field. This problem happens because many of our PCs are used by different
people throughout the day and the previous user's username is in the login
window.

------------------------------

Date: Fri, 28 Nov 1997 10:09:51 +0200
From: Patrick Medhurst <pmedhurs@CTCC.GOV.ZA>
Subject: Re: Unattended NT Intranetware Client Install

>I have been working with NT4.0 workstation unattended installations
>and I am at the stage where I can fully install every application
>including Intranetware Client for NT in fully unattended mode,
>except that the Intranetware Client brings up a license agreement
>and you have to click on Yes.  This is still the case in unattended
>mode ( with the /u switch).  This is preventing my installations from
>being fully automated and unattended.

Under the [NovellNetWareClientParameters] section in the unattend.txt
file put the following key:

!AcceptLicenseAgreement = YES

---------

Date: Sat, 29 Nov 1997 11:39:26 +1100
From: Dave Cottle <d.cottle@CSC.CANTERBURY.AC.NZ>
Subject: Re: Unattended NT Intranetware Client Install

These options are the ones you might be missing, Dale. If you want more
advice, let me know. Which version of the NT intranw client are you using
to do your unattended installs? I have had best results with 4.10 - the
4.11 and 4.11a releases don't seem to work as well for me.

It seems like your unattended installs aren't installing the netware
client right in the same stage that the MS client stuff is installed (the
GUI phase where it joins the domain automatically). The following is part
of my unattended installation. It installs the netware client
automatically. You can even get it to auto-logon afterwards so that you
can run extra installation options afterwards (use a logon script or
similar to automate those pieces). Note that the netware client is stored
in the
	$oem$\net\nwfsnt
directory - not the recommended one. The reason for doing that is that
the directory path becomes too long to fit into a DOS command buffer (68
chars allowed maximum) if you wish to use disk duplication and you stick
with the recommended name. Somewhere inside the install files is a text
file (unattend.txt) which contains more info on doing this.

[Unattended]
OemSkipEula = yes
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = ConvertNTFS
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = WinNT
OverwriteOemFilesOnUpgrade = No

[OEM_Ads]
Banner = "CSC PC Package Installation (Windows NT)"
Background = deep.bmp

[UserData]
FullName = "PC Package Installation"
OrgName = "University of Canterbury"

[GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT+12:00) Wellington"

[Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 800
YResolution = 600
VRefresh = 60
AutoConfirm = 1

[Network]
DetectAdapters = ""
InstallProtocols = Protocols
InstallServices = Services
JoinDomain = UOCNT
CreateComputerAccount = account, password

[Protocols]
NWLNKIPX = NWLNKIPXParams
TC = TCPIPParams

[NWLNKIPXParams]

[TCPIPParams]
etcetera

[Services]
TCPPRINT = TCPIPPrinting
NWFS = NovellNetWareClientParameters, \$OEM$\NET\NWFSNT

[TCPIPPrinting]

[SetupNWInstallOptions]
!DisplayInitialScreen = NO
!AskReboot = NO

[NovellNetWareClientParameters]
!AcceptLicenseAgreement = Yes
!Preferred_Bindery_Server = CantNX
!Preferred_Bindery_Server_OverWriteValue = Yes

------------------------------

Date: Fri, 12 Dec 1997 09:01:00 GMT
From: Kens Mail List Host <MAIL@DRL.OX.AC.UK>
Subject: Re: Intranetware Client 4.10 and office - Path not found

>Running Intranetware Servers with the long namespace and NT 4.0
>Workstations. Workstations run Intranetware Client 4.11
>
>Situation...
>User stores documents in directory "....\Private Things\..."
>(i.e. directory name has a space in it...

We too saw this problem and reverted back to the 4.10 client and all works
well. Apart from the other things that neither of the clients fix like
not being able to have passwords longer than 15 characters (an NT limit).

------------------------------

Date: Fri, 9 Jan 1998 10:43:55 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Novell Client & MS Client trouble

>I am trying to have my Win95/WinNT workstations "see"  my NW 4.X\3.X and
>NT 4.0 server at the same time.  I have Novell client 32 & MS Networking
>client set up.
>
>On my WIn95 workstation I can see only the NetWare servers & Tree even
>though it is set up for both types of servers and log into NT domain is
>checked.
>
>On my WinNT 4.0 Workstation I can see the NetWare server and windows
>Networking but no NT servers or domains.
>
>Client 32 is latest version, Win95 950.A & Win95Sr2
>NT 4.0 Workstation w/SP

If you like the idea of having one login account for each user
instead of two (one for NDS, and one for the NT Domain), then install
NDS for NT on the NT server and make it part of the NDS tree.

------------------------------

Date: Wed, 18 Feb 1998 06:36:46 +0100
From: Rainer Scheppelmann <rs@MERLIN.HB.UUNET.DE>
Subject: Re: Local NT Login and IntranetWare Client

>without the IntranetWare Client for NT, I'm able to select wether
>I'm a local user on a NT Machine or a domain user. If the
>IntranetWare Client is installed, this option disapears at login and
>only domain logins are possible. This is a horrible behaviour. I had
>to change the Ethernet Card of a NT Computer. Different type, no
>Network connections, no login possible, no install of Ethernet Card
>-> deadlock. Result: Floppy boot, complete NT ReInstall :-((( For
>luck not a production machine at the moment, but.......
>
>Is there a way, to get the local NT login back. My first try, to
>select NT login only, no NetWare login failed. Even in this
>configuration only the domain login ist possible.

Once the network setup is not working, you are locked out also from
console login.

See TID 2924995 about how to (temporarily!) remove Intranetware
Client for NT without reinstalling NT server.

Basically you have to access the file system somehow -- (maybe you
install another NT4 WS on the same disk for maintenance? - or you
look into NTFSDOS Tools (http://www.winternals.com/ntfstool.html), a
89$ addon to the free NTFSDOS driver that gives you full NTFS read
access from DOS ;-) )
-- and copy system32\MSGINA.DLL to system32\NWGINA.DLL, then you get
the MS authenticator back.

---------

Date: Wed, 18 Feb 1998 01:30:39 -0800
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Local NT Login and IntranetWare Client

>Basically you have to access the file system somehow -- (maybe you
>install another NT4 WS on the same disk for maintenance? - or you
>look into NTFSDOS Tools (http://www.winternals.com/ntfstool.html), a
>89$ addon to the free NTFSDOS driver that gives you full NTFS read
>access from DOS ;-) )

Why not just user a Linux boot disk?  Then you'll get read/write
access.

---------

Date: Wed, 18 Feb 1998 09:10:58 -0500
From: "Jeffrey A. Tinch" <jtinch@FUSE.NET>
Subject: Re: Local NT Login and IntranetWare Client

>> without the IntranetWare Client for NT, I'm able to select wether
>> I'm a local user on a NT Machine or a domain user. If the
>> IntranetWare Client is installed, this option disapears at login and
>> only domain logins are possible. This is a horrible behaviour. I had
>> to change the Ethernet Card of a NT Computer. Different type, no
>> Network connections, no login possible, no install of Ethernet Card
>> -> deadlock. Result: Floppy boot, complete NT ReInstall :-((( For
>> luck not a production machine at the moment, but.......
>>
>> Is there a way, to get the local NT login back. My first try, to
>> select NT login only, no NetWare login failed. Even in this
>> configuration only the domain login ist possible.
>
>Once the network setup is not working, you are locked out also from
>console login.
>
>See TID 2924995 about how to (temporarily!) remove Intranetware
>Client for NT without reinstalling NT server.
>
>Basically you have to access the file system somehow -- (maybe you
>install another NT4 WS on the same disk for maintenance? - or you
>look into NTFSDOS Tools (http://www.winternals.com/ntfstool.html), a
>89$ addon to the free NTFSDOS driver that gives you full NTFS read
>access from DOS ;-) )
>-- and copy system32\MSGINA.DLL to system32\NWGINA.DLL, then you get
>the MS authenticator back.

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current\Version\Winlogon

Value Name GinaDLL

Novell changes this to NWGINA.DLL if you change it back to MSGINA.DLL the
logon will behave as Microsoft intended. It will also allow tweakui to work
correctly.

------------------------------

Date: Mon, 2 Mar 1998 10:38:58 -0500
From: CHENGD1 <CHENGD1@WESTAT.COM>
Subject: Re: NT4 Policies and INW

>I'm starting out with NT4, I'm a Netware guy from way back.
>I want to set up some NT4 workstations running INW client 4.11a so
>that students (in the context 'students') cannot alter anything, or
>run anything, but staff (in context 'staff') can run other specified
>apps.  I know I need to create 2 different policies/profiles, but
>knowing where to start is messy.  Microsoft docs refer only to MS,
>while NW docs are few and far between and assume lots of MS
>knowledge.
>
>If anyone has a simple step-by-step, I'd really appreciate it.

Try the NT FAQ at:
	http://www.savilltech.com
Also see:
	http://www.microsoft.com/ntworkstation
And the Novell AppNote:
	http://developer.novell.com/research/appnotes/1997/a9704.htm

---------

Date: Mon, 2 Mar 1998 17:08:32 +0100
From: Ard Blenke <blenke@ITC.NL>
Subject: Re: NT4 Policies and INW

Install/enable the workstation manager (included in NT client 4.1 and
4.11a), it you did not enable the workstation manager during
installation you can enable it in the network configuration.

Create with NWadmin the NT client configuration objects in the NDS. This
can only be done with the NT version of NWadmin. The NT client
configuration object holds the rights a user has on the workstation, ie
you can make the user administrator on the workstation or give it just
the rights of the NT user group. Note that when installing a NT
workstation all users have full controll over the file system, you must
change on each NT workstation the rights to read.

In the NT client configuration you can also add a profile for this
object. However in the NT workstation a profile editor is not included
you can copy it from a NT server.

Enable roaming profile for the NT client configuration. Make sure you
have long file name support on the Netware server where the users home
directory is located.

Now assign the users or a container to the NT client configuration, they
can now log in to the NT workstation without an NT account, the NT
accounts will be created at log in.

Simply put, all the settings for NT workstations are stored in the NT
client configuration object.

------------------------------

