[871] in resnet
Re: Windows XP/Novell Login
daemon@ATHENA.MIT.EDU (Jeremy Mlazovsky)
Fri Feb 22 08:45:22 2002
Message-ID: <200202221343.IAA26207@listserv.nd.edu>
Date: Fri, 22 Feb 2002 08:43:26 -0500
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: Jeremy Mlazovsky <mlazovjp@NOTES.UDAYTON.EDU>
To: RESNET-L@listserv.nd.edu
On Thu, 21 Feb 2002 14:50:11 -0500, DIANE SALAMONE <salamone@LYCOMING.EDU>
wrote:
>I will be upgrading our computer labs from Windows 98 to Windows XP
Professional for the Fall Semester.
>
>I would like to get some input on how schools are handling the dual login
issue with a NetWare network. Essentially, I want to bypass the Windows
XP login and only use the NetWare login. I am currently trying to set up
a computer using Novell's solution: AutoAdminLogon for Windows
Workstation. However, every time I set the registry and restart the
computer it changes the AutoAdminLogon key back to 0 (disable).
>
>If you are using NetWare and have been able to bypass the Windows XP
logon I would appreciate some input.
At the University of Dayton, we require the students to purchase one of
three models of PC from our contracted vendor. I build a hard drive image
for each of the three PCs, ship it to our vendor, and they copy those onto
the machines; the PCs are shipped to UD in the summer, and we unpack the
PCs and do minor customizations (such as finish the Lotus Notes client
install, change workstation name to their username, create local accounts
for them, change Administrator password, etc).
I wrote a number of scripts and a GUI front end that drastically cuts down
on the amount of post-unpacking work that we need to do once we get the
student's PC out of the box. The primary scripting tool that I use is
called AutoIt (http://www.hiddensoft.co.uk); I write scripts files that I
compile into .exe's that do most of the work for me. The scripting
language does things such as press buttons for me when certain windows
popup, run installation programs, randomize the SID, etc. I highly
recommend it for any kind of repetitive installs, especially if it cannot
be scripted any other way. It's freeware, too :)
The 2000 and 2001 PCs came with Windows 2000 installed on them, along with
Novell Client32. In 2000, we had Novell's ZEN Works 2.0 on our network,
and we created user policy packages in the Novell tree and associated them
with the students. One of the policies in the package was dynamic local
user, which allowed that student to login to any Windows NT/2k PC with
Client32 installed, and after successful authentication into NDS created a
local Windows account with the same username and password as their Novell
account. This worked well until we realized that not all lab
administrators liked the idea of students being able to bypass their
workstation security settings.
For the 2001 PCs, we had Novell's ZEN Works 3.0 SP1 on our network. Our
current approach is to login to Novell (no more dynamic local user
policies exist for students), login to Windows as Administrator (with an
initially blank password), and run the first "phase" of my script, which
does the following:
1.) Creates a new local user with full admin access, using the same
username and password as the Novell account.
2.) Updates Client32 via the registry the following: sets the default
local workstation login username to be their newly created local username
and then unchecks the checkbox that saves the name of the last person to
login (since the student owns their PC it makes sense to always default to
the owner's login name).
3.) Logs off
The next step of the script is to login again to NDS and Windows; this
time, because the username and password for both Novell and Windows are
the same and Client32 now defaults to attempting to login locally using
the same username as Novell, once successful authentication to NDS takes
place, it blows right through the Windows login.
That might be a little confusing. If you have any more questions, let me
know.
Jeremy Mlazovsky
PC/Network Specialist
UD IT
University of Dayton
Office: 937-229-4019
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
