George,

Thanks for your follow-up. I guess the moral of the story is that any changes our software makes via WSH (or the FFC registry classe) to user based registry settings or special folder locations will be user specific vs. workstation global. I assume this principle would also apply to activex controls that get registered during setup?

For those of you monitoring this thread, I guess one approach to having our software update all user registery settings and all user special folder locations would be to package our registery and special folder updates as an InstallShield setup executable whose sole purpose would be to perform multi-account system updates - and then to run this type of special setup with the /V"ALLUSERS=2" command line parameter.

Any one have any thoughts on this last idea?

Regards,
Malcolm


>I'll just touch on one point, namely, regarding the WSH. Under Win2K, there is the user's desktop and all users desktop. While this was true back to at least Win98, the WSH couldn't be used to determine the all users. However, under Win2K

>oShell = CREATEOBJECT("WScript.Shell")
>* For me the statement below returns:
>* C:\Documents and Settings\gtasker\Desktop
>? oShell.SpecialFolders("Desktop")
>* Again the statement below returns:
>* C:\Documents and Settings\All Users\Desktop
>? oShell.SpecialFolders("AllUsersDesktop")

>>Recent threads in the Installation and Setup forum have pointed out that what gets installed on a workstation is dependent on who is doing the installation (enduser or administrator). I also learned that there is an option for an administrator to install software so that both the admininistrator and all users have access to the program, its shortcuts, etc.
>>
>>This has made we wonder about using the WSH to update registry entries or to gain access to Special Folders. When our application uses WSH, is it correct to assume that all the changes are taking place relative to the current user, i.e. we're updating the current user's registry branches and special folders, etc.?
>>
>>What if the user of our software has system admin priviledges? Can we use WSH or some other form of Windows API to determine that the current user has system admin priviledges, and if so, is there a special syntax we need to use to have the system administrator's registry and special folder updates apply to all users, i.e. similar in effect to InstallShield's Setup.exe /V"ALLUSERS=2" run mode? Or do we manually need to iterate each user's registry branch and/or special folders applying the global type changes we want to apply.