[NTISP] Moving from the NT SAM

Sam Lowe ( (no email) )
Sat, 6 Mar 1999 11:30:36 -0600

This is a multi-part message in MIME format.

------=_NextPart_000_00EA_01BE67C4.C1494CD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greeting to the List...

Do any of you fine computer type professional know of a utility that =
will allow us to migrate from our current NT SAM-based authentication to =
one that would be based on an external database file (like with =
RadiusNT).

I believe we can dump the a list of the users, but not the passwords. I =
was hoping that the NT UNIX password sync would help, but that is not =
the case.

We have a lot of our early users that we have no password on record for =
(yes, we screwed up), and we really don't want to key all those user =
passwords in manually.

Alternatively, does anyone know of a way to make a TotalControl look at =
an alternative radius file, if it cannot find the user name in the =
primary location? We can make it look at a secondary location if the =
primary is down, but that won't help if we have to migrate these users =
manually.

Any ideas would be appreciated.

Samuel S. Lowe
Director, Data Network Services
UniversalCom, Inc.
slowe@universalcom.net

------=_NextPart_000_00EA_01BE67C4.C1494CD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

Greeting to the List...
 
Do any of you fine computer type professional know =of a=20utility that will allow us to migrate from our current NT SAM-based=20authentication to one that would be based on an external database file =(like=20with RadiusNT).
 
I believe we can dump the a list of the users, but =not the=20passwords.  I was hoping that the NT UNIX password sync would help, =but=20that is not the case.
 
We have a lot of our early users that we have no =password on=20record for (yes, we screwed up), and we really don't want to key all =those user=20passwords in manually.
 
Alternatively, does anyone know of a way to make a=20TotalControl look at an alternative radius file, if it cannot find the =user name=20in the primary location?  We can make it look at a secondary =location if=20the primary is down, but that won't help if we have to migrate these =users=20manually.
 
Any ideas would be appreciated.

Samuel S. Lowe
Director, Data Network=20Services
UniversalCom,=20Inc.
slowe@universalcom.net
------=_NextPart_000_00EA_01BE67C4.C1494CD0--