Autodesk Technology Managers Forum
Share your knowledge, ask questions, and engage with fellow CAD/BIM Managers.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AutoDesk 2002 Products and Winows 2000

4 REPLIES 4
Reply
Message 1 of 5
Anonymous
206 Views, 4 Replies

AutoDesk 2002 Products and Winows 2000

I have been working on installing ADT 3.3 and the Building Electrical and
Mechanical Packages. I have run into the registry issues with the software.
Maybe I am old school, but I have a real hard time making a user a Power
User on their Workstation. A Power User can make themselves and
Administrator on the Workstation. To me, a setup such as this is totally
contrary to the manner in which a Network should be configured. I guess my
questions are:

1. Has anyone had any success in the migration and implementation of the
ACL in Windows 2000 that is supposed to provide the default user with the
same privileges and rights as NT 4.0?
2. Are administrators out there comfortable with provide administrative
privileges to the user of their workstations?
3. Has anyone found an install sequence that eliminates the issues???

Thoughts, opinions and comments greatly appreciated.....

--
Phillip C. Roberts
CADD Manager
DuBois & King, Inc.
CADDManager@DuBois-King.com
4 REPLIES 4
Message 2 of 5
Anonymous
in reply to: Anonymous

I belive your referring to Minows 2000... its a new fishing bate software.
=)

drew

"CAD Guy" wrote in message
news:808CAFA779A74C8FCDA502B6BF85809A@in.WebX.maYIadrTaRb...
> I have been working on installing ADT 3.3 and the Building Electrical and
> Mechanical Packages. I have run into the registry issues with the
software.
> Maybe I am old school, but I have a real hard time making a user a Power
> User on their Workstation. A Power User can make themselves and
> Administrator on the Workstation. To me, a setup such as this is totally
> contrary to the manner in which a Network should be configured. I guess
my
> questions are:
>
> 1. Has anyone had any success in the migration and implementation of the
> ACL in Windows 2000 that is supposed to provide the default user with the
> same privileges and rights as NT 4.0?
> 2. Are administrators out there comfortable with provide administrative
> privileges to the user of their workstations?
> 3. Has anyone found an install sequence that eliminates the issues???
>
> Thoughts, opinions and comments greatly appreciated.....
>
> --
> Phillip C. Roberts
> CADD Manager
> DuBois & King, Inc.
> CADDManager@DuBois-King.com
>
>
Message 3 of 5
Anonymous
in reply to: Anonymous

On Tue, 12 Mar 2002 15:21:36 -0800, "CAD Guy"
wrote:

>I have been working on installing ADT 3.3 and the Building Electrical and
>Mechanical Packages. I have run into the registry issues with the software.
>Maybe I am old school, but I have a real hard time making a user a Power
>User on their Workstation... To me, a setup such as this is totally
>contrary to the manner in which a Network should be configured.

No, I don't believe this is correct. Local power and network power should be
separate, but as long as things are kept on the server and security is
implemented _there_, the local machine is almost secondary. I let my users know
they can wreak havok on their machine, and if they break something it's no
biggie to do a reinstall from a Ghosted image or some other mechanism.

>2. Are administrators out there comfortable with provide administrative
>privileges to the user of their workstations?

I'm personally very comfortable with it. I know that when I restrict their
abilities, all kinds of weird stuff happens - apps don't run, pieces that
require Admin/Power User control won't self install, and I get tons of support
calls - which I really don't need,

Being a local administrator is no big deal, even for idiots. As long as you are
careful about what groups users are in across the domain, the user account
active at the workstation should be AT LEAST at the Power User level.

Simply assign to the local Administrators or Power Users groups the Domain Users
security group from the domain.

Matt
mstachoni@comcast.net
mstachoni@beyerdesign.com
Message 4 of 5
Anonymous
in reply to: Anonymous

I agree.
What's the worst that can happen when you allow administrative privelages?
They screw up their own computer, but hopefully you save stuff to a network
server.

I used to allow Power User rights (in a diff office) but this new office has
responsible users, and all the machines are already setup with
administrative rights to their local machine.


"Matt Stachoni" wrote in message
news:7ggt8u0klrkfjo9m9cp5o1hoff4k9kacon@4ax.com...
> On Tue, 12 Mar 2002 15:21:36 -0800, "CAD Guy"
> wrote:
>
> >I have been working on installing ADT 3.3 and the Building Electrical and
> >Mechanical Packages. I have run into the registry issues with the
software.
> >Maybe I am old school, but I have a real hard time making a user a Power
> >User on their Workstation... To me, a setup such as this is totally
> >contrary to the manner in which a Network should be configured.
>
> No, I don't believe this is correct. Local power and network power should
be
> separate, but as long as things are kept on the server and security is
> implemented _there_, the local machine is almost secondary. I let my users
know
> they can wreak havok on their machine, and if they break something it's no
> biggie to do a reinstall from a Ghosted image or some other mechanism.
>
> >2. Are administrators out there comfortable with provide administrative
> >privileges to the user of their workstations?
>
> I'm personally very comfortable with it. I know that when I restrict their
> abilities, all kinds of weird stuff happens - apps don't run, pieces that
> require Admin/Power User control won't self install, and I get tons of
support
> calls - which I really don't need,
>
> Being a local administrator is no big deal, even for idiots. As long as
you are
> careful about what groups users are in across the domain, the user account
> active at the workstation should be AT LEAST at the Power User level.
>
> Simply assign to the local Administrators or Power Users groups the Domain
Users
> security group from the domain.
>
> Matt
> mstachoni@comcast.net
> mstachoni@beyerdesign.com
>
>
Message 5 of 5
Anonymous
in reply to: Anonymous

We have a more control system at our place. All the workstations are setup
as Power Users. The only people that has Administrator rights are the upper
managements and IT groups. We setup one sample station that has all the
applications needed. With that one station, we could push the applications
to any workstations we would like without having to installing it on every
single stations one by one. The pushing process takes only about 2 to 10
minutes. All the setting would match exactly with that one sample station.
Our main purpose on doing this is to keep all the stations the same. No one
can change their properties as well. We also lock the privileges of
installing software.

"F. Gump" wrote in message
news:2BD6010B7B91E24146C3675E10A12D2D@in.WebX.maYIadrTaRb...
> I agree.
> What's the worst that can happen when you allow administrative privelages?
> They screw up their own computer, but hopefully you save stuff to a
network
> server.
>
> I used to allow Power User rights (in a diff office) but this new office
has
> responsible users, and all the machines are already setup with
> administrative rights to their local machine.
>
>
> "Matt Stachoni" wrote in message
> news:7ggt8u0klrkfjo9m9cp5o1hoff4k9kacon@4ax.com...
> > On Tue, 12 Mar 2002 15:21:36 -0800, "CAD Guy"

> > wrote:
> >
> > >I have been working on installing ADT 3.3 and the Building Electrical
and
> > >Mechanical Packages. I have run into the registry issues with the
> software.
> > >Maybe I am old school, but I have a real hard time making a user a
Power
> > >User on their Workstation... To me, a setup such as this is totally
> > >contrary to the manner in which a Network should be configured.
> >
> > No, I don't believe this is correct. Local power and network power
should
> be
> > separate, but as long as things are kept on the server and security is
> > implemented _there_, the local machine is almost secondary. I let my use
rs
> know
> > they can wreak havok on their machine, and if they break something it's
no
> > biggie to do a reinstall from a Ghosted image or some other mechanism.
> >
> > >2. Are administrators out there comfortable with provide
administrative
> > >privileges to the user of their workstations?
> >
> > I'm personally very comfortable with it. I know that when I restrict
their
> > abilities, all kinds of weird stuff happens - apps don't run, pieces
that
> > require Admin/Power User control won't self install, and I get tons of
> support
> > calls - which I really don't need,
> >
> > Being a local administrator is no big deal, even for idiots. As long as
> you are
> > careful about what groups users are in across the domain, the user
account
> > active at the workstation should be AT LEAST at the Power User level.
> >
> > Simply assign to the local Administrators or Power Users groups the
Domain
> Users
> > security group from the domain.
> >
> > Matt
> > mstachoni@comcast.net
> > mstachoni@beyerdesign.com
> >
> >
>
>

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report