Bruce

Thanks for the suggestions. I was hoping for a completely automatic process. All I would need to do is put the new files on the server and tell the Installer program how to install them. No need for the very busy system admins to visit all 150 user's machines.

One question. What is SMS?

Thanks.

>>I have an installer program that is written in VFP. It makes sure that the current required VFP files are installed on the client machine and then runs the actual VFP application EXE. It can copy files from the server to the client machine OK. But, on locked down machines it can not register DLLs. Is there any way to give it temporary admin rights?
>
>Yeah, I think you've got some options, though maybe none too good:
>
>1) Use SMS to do the work, it'll handle everything under the System account. Of course this assumes you have SMS installed, and know how to use it. Any big corp should have SMS for deployment nowadays, what with lockdowns so common now. This is the preferred technique for any large deployments.
>
>2) For small number of users, just do manuals by an Admin - for NT, this is easy.
>
>But for XP, you may have trouble with your own installer app even when an admin does the installs. You'll have to test if you have XP machines, see how it goes.
>
>3) If you have good remote workstation controlling, you could have admins sit comfortably in an easy-chair and logon remotely to do the installs with their admin accounts.
>
>These are 3 ways I use, anyway, with #1 SMS being by far the best for general deploying, except in a very few cases where SMS doesn't work real well.
>
>4) A 4th way which security people don't like, but is otherwise often doable, is to have an entire domain group (already on the machines, hopefully) elevated to Admin-level temporarily for users to do the installs, then knock the group back down to User-level. (I doubt you'll get security folks to go for this, however, even if it's possible with your policy-setup :-)