Management's view.... Admin vs. User

Management's view.... Admin vs. User

Post by Eric S. Zi » Fri, 19 Jun 1998 04:00:00



I think that it's no surprise that Management can come up with some
'interesting' mind-sets. I would be interested in getting a little
feedback on how 'your' company addresses this view point.

And just what 'is' this mind-set?... well, their position is that
everyone should have only 'one'  keyboard on their desk. That means
you can have "A" PC or "A" workstation of some sort but not more than
one.

Now for the Users out there, I don't see this to be a big problem,
typically a User is assigned a task to perform and it should be
relatively easy to determine what type or computational resource would
be best to accomplish that task.

What is really interesting is that this mind-set apparently makes no
differentiation  to the unique functional responsibilities of the
computer group's Admin. types. In a large company it is not uncommon
for there to be several thousand PCs* on the network as well as
Mainframes, Mini's, and a large pot full of printers and workstations.
You never seem to be fortunate enough to be dealing with a single
protocol so you have to deal with this mixed-bag of network chatter
all the while having to satisfy the Users 'connectivity requests' of
platform logins as well as NFS mount points etc.

The Computer group is chartered with the responsibility of keeping the
entire company computational enterprise functional, that much is a
given. Therefore I think that in order to gain and maintain your
proficiency in all the various platforms and O/Ss that are in use
within the company it is not unreasonable for the Admin. to have more
than a single keyboard "assigned" to them.

I would be interested in hearing how other companies address this
issue... what is the mind-set of your Management on this topic... (and
how do you deal with it in real life ;-).

Regards,

Eric

 
 
 

Management's view.... Admin vs. User

Post by Brentr Noru » Sun, 21 Jun 1998 04:00:00



> I think that it's no surprise that Management can come up with some
> 'interesting' mind-sets. I would be interested in getting a little
> feedback on how 'your' company addresses this view point.

> And just what 'is' this mind-set?... well, their position is that
> everyone should have only 'one'  keyboard on their desk. That means
> you can have "A" PC or "A" workstation of some sort but not more than
> one.

> Now for the Users out there, I don't see this to be a big problem,
> typically a User is assigned a task to perform and it should be
> relatively easy to determine what type or computational resource would
> be best to accomplish that task.

> What is really interesting is that this mind-set apparently makes no
> differentiation  to the unique functional responsibilities of the
> computer group's Admin. types. In a large company it is not uncommon
> for there to be several thousand PCs* on the network as well as
> Mainframes, Mini's, and a large pot full of printers and workstations.
> You never seem to be fortunate enough to be dealing with a single
> protocol so you have to deal with this mixed-bag of network chatter
> all the while having to satisfy the Users 'connectivity requests' of
> platform logins as well as NFS mount points etc.

> The Computer group is chartered with the responsibility of keeping the
> entire company computational enterprise functional, that much is a
> given. Therefore I think that in order to gain and maintain your
> proficiency in all the various platforms and O/Ss that are in use
> within the company it is not unreasonable for the Admin. to have more
> than a single keyboard "assigned" to them.

> I would be interested in hearing how other companies address this
> issue... what is the mind-set of your Management on this topic... (and
> how do you deal with it in real life ;-).

> Regards,

> Eric

Get a KVM switch box so you can use 1 or more CPU system units with the
same keyboard, monitor, and mouse -- management will never know the
difference, except for the cost ($200-300).

 
 
 

Management's view.... Admin vs. User

Post by Joseph E Doyl » Fri, 26 Jun 1998 04:00:00


Right now, I'm using a PC with Hummingbird Exceed and a  couple of
terminal emulator programs specific to my customer.
The exceed gives me the 3270 terminal emulation, as well as a suite of
Unix utilities for the PC (e.g, FTP, nslookup, traceroute, finger etc)
..  One person in our group also is using Linux on a PC

 
 
 

1. admin user can't admin non-admin groups

In the attributes for user profile "jean" I've specified "adminstrative
user=true" and "administrative group=staff".

In the "staff" group profile attributes I've specified "administrative
group=false" and "administrator list=jean".

The above were done as by "root".

When I then sign in as "jean" and look at the "staff" group attributes
(via SMIT) it shows "adminstrative group=true" and the "administrator
list=" parameter is blank.  If I try to make an addition, say, to
the "user list=" parameter and hit OK, SMIT dies and the change doesn't
get made.  Further, if I go into Application Manager as "jean" and try
to edit "staff" group I am told "you do not have access to edit this
dialoge."

Have I got a bug or am I doing something wrong in the way I set
up "jean" and "staff"?

Thanks.

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

2. Update of Documentation/magic-number.txt

3. User management: disable users to view mounted drives

4. Packets not sent to my linux

5. samba: 'net view \\server' works, 'net view' fails

6. Multi Serial Board/ Which ones?

7. NIS+ user management [Was: Re: root changing a user's password (NIS)]

8. AWE32 setup problem

9. X windows question 'root' vs 'user'

10. admin vs admin

11. Survey - GUI based admin. vs. text based admin

12. Cannot view my users' html page!!

13. OT SonicBlue ordered to track ReplayTV users' viewing choices