Permissions question

  • Thread starter Thread starter Kim Stahnke
  • Start date Start date
K

Kim Stahnke

We recently started switching from our old NT-4 server to a new Win 2k
Server. We have installed the server and configured it as an AD Domain
Controller. Almost evrything works fine - we can access and use all disks,
files, printers and such, but when we on a connected Client computer (win
2k, standard user) try to create an ODBC System DSN and press OK, we get two
error-boxes: 1) "Error: The configuration process failed", and 2) "Driver's
ConfigDSN, ConfigDriver, or ConfigTranslator failed: Could not write to the
registry".
This does not happen when we log on to the old NT-4 server.
If we log in on the Client as Administrator, there are no problems creating
the DSN. We can then use the DSN from within the User.
Is this the normal behavior? And if not, can anyone give us a clue as to
where to begin looking for a remedy?

Regards,

Kim Stahnke
 
That is how it works. Same with printer setup. You need to log on as an
administrator and create the DSN & printers before the user can add them to
his profile. Has it's good points and bad.
 
Back
Top