• Subject: RE: Client access/NT - many users on one workstation
  • From: "Grau, Barry" <Grau@xxxxxxxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 30 Oct 1997 17:31:14 -0600

Thanks to those who answered, both on Midrange-L and in
comp.sys.ibm.as400.misc.

A shared workstation ID wasn't really a viable solution because then the
clients wouldn't have access to their e-mail or home directories. 

In the "Control Panel's" "Passwords" "User Profiles" you can specify
"All users of this PC use the same preferences" or something like that.
Thanks to Neil Palmer for this. Our network guys restricted access to
this tab so that individual preferences follow our users from machine to
machine. Mok Chi Kin and Pete Hall suggested fiddling around with the
Windows Registry so I did. I found a setting -
HKEY_LOCAL_MACHINE\Network\Logon\UserProfiles - which is a switch that,
when flipped, allowed access to the "User Profiles" tab. That's how I
verified that this does indeed work. My organization prefers to have
users' preferences follow them from machine to machine. 

While I was fiddling with the registry, I tried making the description
of client access in the HKEY_USERS\.Default user look like the client
access description of a user who had access to CA, figuring that it
would get copied into any new users' registry entries. This worked up to
a point. The relevant key was
"HKEY_USERS\.Default\Software\IBM\ClientAccess|CurrentVersion\Internal_C
omponents\Communication\Environments\PrimaryEnvironment\as400hostname"
where as400hostname contained a description of the as400 connection. The
whole key, except for the as400hostname part was copied into the new
user's registry entries. The user couldn't access the AS/400 in
question. Exporting, editing (by changing ".Default" to the users login
ID) and importing the new registry entries gave the user access (after a
re-boot).

Given what I've learned, I think I can work with my network and desktop
people to solve the problem. 

Thanks

-bwg

> ----------
> From:         peteh@earth.inwave.com[SMTP:peteh@earth.inwave.com]
> Sent:         Tuesday, October 28, 1997 9:02 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Client access/NT - many users on one workstation
> 
> >>  When a second user logs on, CA
> won't let him connect - it complains that the connection isn't found
> in
> the current environment. I really want to configure connections only
> 10
> times, not 10*20 times. Is there any way to configure a connection in
> the primary environment and have it be shared among all users of the
> workstation? <<
> 
> I'm really not sure, but you could try creating the CA registry
> entries
> in HKEY_LOCAL_MACHINE instead of HKEY_CURRENT_USER. I know that's the
> difference between user and system data sources for ODBC. If you're
> going to muck with the registry though, back it up first (SYSTEM.DAT
> and
> USER.DAT). When you install CA, are you logged in as administrator?
> I'm
> a little more than curious, as I need to install CA on two NT
> workstations next week.
> 
> Pete
> 
> 
> --
>  - Pete Hall peteh@earth.inwave.com
> http://www.inwave.com/~peteh/
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to
> "MIDRANGE-L@midrange.com".
> | To unsubscribe from this list send email to MAJORDOMO@midrange.com
> |    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].