MarkRiffey
03-18-2022, 02:59 PM
Friedrich,
When IT folks run our installs via SCCM or similar tools, they run the installs remotely in an automated fashion (and in silent mode) - and when they do this, these tools often run the installer as SYSTEM rather than as a regular windows login profile.
This can make quite a mess re: CSIDL folder locations. Sometimes the documents folder comes back blank, sometimes it comes back as somewhere in \windows\system32, its unpredictable.
If you could create a read-only variable that lets us detect when the user is SYSTEM (or other "special" Windows user profiles), that would be useful so that we could bypass script functions that create folders and registry info for that user, among other things.
Thanks in advance,
Mark
When IT folks run our installs via SCCM or similar tools, they run the installs remotely in an automated fashion (and in silent mode) - and when they do this, these tools often run the installer as SYSTEM rather than as a regular windows login profile.
This can make quite a mess re: CSIDL folder locations. Sometimes the documents folder comes back blank, sometimes it comes back as somewhere in \windows\system32, its unpredictable.
If you could create a read-only variable that lets us detect when the user is SYSTEM (or other "special" Windows user profiles), that would be useful so that we could bypass script functions that create folders and registry info for that user, among other things.
Thanks in advance,
Mark