General discussion


local admin on every XP workstation

By bluecheese ·
Here?s our situation, we have been told to roll out XP to the desktop some time in the very near future, this we can do today and have been ready for some time. The issue is the 200 odd legacy applications.

The only solution we came up with in this time frame is to make each user a local admin on their workstation. No one in the department wants to do this, but it?s been driven by upper management.

What are the risks we are opening ourselves up to?

What strategies can you advise to get around this and move forward?

Our aim was to modify each app (script its installation so we can push it) and the security compatibility template for a controlled release onto our Win 2000 domain.

Now we are thrown for a loop, how can we extract some good out of a bad situation?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

RE Local admin

by deeda In reply to local admin on every XP ...

In our company we have quite a few people running XP and even 2000. When we set them up we make them the local admin. of that machine. That way if they want to change their preferences or need to install stuff they can do so. And then we have thedomain admin and that one is just for us. and we set that up so that the domain admin can be both the local admin and domain admin at the same time.
Hope this helps! Good luck!

Collapse -


by AusMentalCase In reply to local admin on every XP ...

What has more value? Maintaining the status quo to preserve two hundred applications (all discreete applications I presume) or changing ONE operating system and causing two hundred application problems for yourself?

What is the reasoning behind rolling out XP?? Is there some mysterious magical benefit which outweighs the hassle of updating an awful lot of applications?

Is the expense of purchasing XP licences for all your workstations PLUS the expense of modding 200 apps going to be recovered by some mythical gain in productivity? I'm sorry, but if you think XP is some touchstone that will make it all worthwhile then you are very sadly mistaken.

1) Leave things as they are....expense and learning curve....$Zero!

1) Change to XP.... Expense of new licences PLUS manhours taken to resolve 200 application issues....incredibly more than $Zero!

If it isn't broken...don't try and fix it!

Collapse -

I concur with Gordon

by GuruOfDos In reply to local admin on every XP ...

I have to ask the same questions. WHY?!!!

We had the same issues with 3.11 to 95, 95 to 98, etc. etc.

It costs to upgrade the OS's, takes hours to sort out all the application wrinkles, makes everyone work slower unless the hardware is upgraded AND 90% of users don't use any new features anyway, so why change? There HAS to be a GOOD reason to change something when the existing system works fine. Is it to justify having an IT department? Is it so that you have something to to to pass the time? Do you have spare cash to upgrade OS's unnecessarily AND troubleshoot all your applications?

Honestly....what do you NEED XP for that your existing setup CANNOT do?!!!!

Collapse -

W2K vs. XP

by Dee In reply to I concur with Gordon

Hi there,

am running both versions of the above in my company and so far do not really have much hassle - yet. The local profile can be a administrative profile, however this is not really required except if it comes down to a couple of applications and the only one that really requires admin right at the moment is Lotus Notes due to use in our firm. However, all applications must be installed under admin profile of the user, i.e. when upgrading/installing Office XP this must be done under the user`s profile. In this case the user must have admin privileges.

In itself XP is nice to work with, but of course as any other operating system does have it`s issues aswell.

With regards,


Collapse -

why XP ? because

by bluecheese In reply to I concur with Gordon

Decision was made several years ago to skip win 2000 and a hardware refresh, to wait for the next OS. Well now our hardware is out of maintenance, and costing us a fortune, the new hardware doesn?t support NT (plus support for NT ended this month), no point going to 2000,as it will have a limited life of support.

Collapse -

In that case

by GuruOfDos In reply to why XP ? because

If you are throwing the hardware AND OS out and want to start afresh, then I can see the point, especially if XP is bundled with the new hardware. The issue in this case becomes one of 'isn't it time to throw out the legacy software?'.

Collapse -

local admin

by rwomack In reply to local admin on every XP ...

Unless your users will be adding more software, the simplest thing would be to put them in power users, that way you're protecting yourselves somewhat and they can run their legacy apps.

Collapse -

power user will not work

by bluecheese In reply to local admin

we have tried that, and opening up the security template, the apps are still not getting the access they require to run.

Collapse -

by djent In reply to power user will not work

If you have tried power user I assume your using XP PRO. You can then grant users any rights to any file or set of files without compromising the rest. All you need to do is determine which files are needed. If you use XP Home all users have Admin rights.

Collapse -

counter the local admin with a group policy

by etheriault2 In reply to

We had the same issue with legacy programs. We gave the users local admin, then implemented the group policy locking down the desktop and regedit and so on in ads. Been using it this way for a year with no reprocussions so far.

Related Discussions

Related Forums