Per User File Installation / C:\Windows\System32\config\systemprofile
Hello Everybody,
Ive just repackaged Enterprise Guide 4.1 for my company, but im running into some troubles now.
Ive to install some custom xml configuration files (repository configuration etc) into every user directory.
So i decided to use activesetup to fulfil this task.
ive put all custom files into a own feature called "ActiveSetup", and i install that
per user by running this command via ActiveSetup: "msiexec /i {14B18B91-2FB1-405B-9A3A-41ED037F58C3} REINSTALL=ActiveSetup REINSTALLMODE=p /qn"
This works well as long the user has NOT any administrator rights! As soon as i login with admin rights, my feature is being installed to C:\Windows\System32\config\systemprofile\Application Data\SAS
instead of %APPDATA%\SAS
Ive already tried to run this command with the "ALLUSERS=0" Property, but without any success.
Does anybody have an idea? i do not even know the purpose of the systemprofile folder.
any help would be appreciated,
thank you!
Ive just repackaged Enterprise Guide 4.1 for my company, but im running into some troubles now.
Ive to install some custom xml configuration files (repository configuration etc) into every user directory.
So i decided to use activesetup to fulfil this task.
ive put all custom files into a own feature called "ActiveSetup", and i install that
per user by running this command via ActiveSetup: "msiexec /i {14B18B91-2FB1-405B-9A3A-41ED037F58C3} REINSTALL=ActiveSetup REINSTALLMODE=p /qn"
This works well as long the user has NOT any administrator rights! As soon as i login with admin rights, my feature is being installed to C:\Windows\System32\config\systemprofile\Application Data\SAS
instead of %APPDATA%\SAS
Ive already tried to run this command with the "ALLUSERS=0" Property, but without any success.
Does anybody have an idea? i do not even know the purpose of the systemprofile folder.
any help would be appreciated,
thank you!
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Going out on a limb here...are you using a Wise product (e.g. Wise Package Studio) by any chance? Wise a reputation for faulty user profile location resolution, such that the Windows Application template we use has a bunch of CAs (shamelessly lifted from an InstallShield installation) which sets the User and AllUsers profile locations in the UI and Execute Immediate sequences. You'll find that Wise has resolved AllUsers to be the last path which it correctly resolved. Bizarrely, these tend to be folders beneath %SystemRoot% (well, they always have been in my experience.)
Having said that, even if you're NOT using Wise, it does look like the profile is being screwed anyway so the CAs below may be useful. Simply put, the CAs (in pseudo-code) look like this:
SetProperty USERPROFILE = [%USERSPROFILE]\
If VersionNT = 400 then
SetProperty ALLUSERSPROFILE = [%ALLUSERSPROFILE]\
End If
If VersionNT >= 500 then
SetProperty ALLUSERSPROFILE = [%SystemRoot]\Profiles\All Users\
End If
Having said that, even if you're NOT using Wise, it does look like the profile is being screwed anyway so the CAs below may be useful. Simply put, the CAs (in pseudo-code) look like this:
SetProperty USERPROFILE = [%USERSPROFILE]\
If VersionNT = 400 then
SetProperty ALLUSERSPROFILE = [%ALLUSERSPROFILE]\
End If
If VersionNT >= 500 then
SetProperty ALLUSERSPROFILE = [%SystemRoot]\Profiles\All Users\
End If
Posted by:
spartacus
16 years ago
[font="trebuchet ms"]Your ActiveSetup command appears a little unorthodox if you don't mind me saying.
[font="trebuchet ms"]
[font="trebuchet ms"]If your installation is set up as a per-machine installation (ALLUSERS=1) then you should be able to use the following ActiveSetup command to populate each users folder with the XML files.
[font="trebuchet ms"]
[font="trebuchet ms"]msiexec /fup {14B18B91-2FB1-405B-9A3A-41ED037F58C3} /qn
[font="trebuchet ms"]
[font="trebuchet ms"]Avoid using the %APPDATA% environment variable if possible because it won't be defined for anything running in LocalSystem context - instead, use the [AppDataFolder] property.
[font="trebuchet ms"]
[font="trebuchet ms"]Regards,
[font="trebuchet ms"]
[font="trebuchet ms"]Spartacus
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
Posted by:
neo2000
16 years ago
Have a look at ogeccut's topic here:
http://itninja.com/question/how-do-you-roll-out-new-machines?5925
I have the same issue, as does ogeccut if i'm not mistaken, with the local administrative rights, and yes, i'm using Wise Package Studio.. Seems like it somehow screws up the user environment when using active setup and having admin rights. (That is, if WPS/Wfwi is the culpreit)
I've run into this problem a couple of times now, and usually got away with an unorthodox vb script, which turnes something that's quick and easy like Active Setup into something dreadfully time consuming unfortunately..
http://itninja.com/question/how-do-you-roll-out-new-machines?5925
I have the same issue, as does ogeccut if i'm not mistaken, with the local administrative rights, and yes, i'm using Wise Package Studio.. Seems like it somehow screws up the user environment when using active setup and having admin rights. (That is, if WPS/Wfwi is the culpreit)
I've run into this problem a couple of times now, and usually got away with an unorthodox vb script, which turnes something that's quick and easy like Active Setup into something dreadfully time consuming unfortunately..
Posted by:
usachrisk
15 years ago
Has anyone gotten anywhere with this? I have templates going into the user profile and when I have the user self heal, they go right back to the SYSTEM account's profile.
Posted by:
AngelD
15 years ago
Please do not double-post!
You already have this question in your own thread.
You already have this question in your own thread.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
