microsoft.public.windowsxp.security_admin

coopfab wrote:
> I ran Sysinternals and found perhaps 2 pertinent results, Name
> Collision and Path Not Found. Can you comment on these results and
> whether or not they are involved with the program not opening?
> Thanks for your continued support.

Sorry, no - you'll need to suss this out on your own.
>
>> coopfab wrote:
>>> We're running a SBS 2003 network using all XP workstations. The
>>> program we're having difficulty with is UPS Worldship and their tech
>>> support has given up on us. The program works fine on a workstation
>>> where the person is logged in as an administrator, but if a person
>>> is part of the User group, the program won't open. On the local
>>> drives, to the best of my ability, I have made sure that "Everyone"
>>> and each individual User has full control of the UPS directory and
>>> subdirectories and all files. The UPS program is setup where one
>>> workstation is the Administrator and all others are Remotes. The
>>> remotes do have to access the Administrator's workstation and again
>>> I have tried to ensure that everyone in the User group has full
>>> control of the directory, subdirectories and files in the UPS
>>> folders on the administrator workstation. I'm obviously missing
>>> something. How do I troubleshoot this? Thanks for your help.
>>
>> First thing to do, before worrying about your other network users,
>> is to make sure it runs properly as a limited user on that
>> workstation.
>>
>> Download Process Monitor from Sysinternals (now Microsoft). Log in
>> as a user. Launch Process Monitor using RunAs to run it as an
>> administrator. This should help you isolate the areas of the file
>> system & registry where the application expects to find access & is
>> getting denied.
>>
>> You should also holler at UPS support because this is just sloppy
>> code, and they ought to have simple list of instructions for you to
>> use as a workaround (and they should fix their stuff, in the long
>> term).
>>
>> PS: Don't use "everyone" and don't use individual user accounts when
>> assigning
>> permissions. Use the local Users group for this purpose - Domain
>> Users is a member of that group by default.