Hello!

I'm trying to change the installdir for a captured installation of a app, what I want to achieve is the following:
Currently the app is installed to C:\Manufacturer\Appname\
I want to change this to an variable so the end result will be: %USERPROFILE%\Manufacturer\Appname\ aka C:\Users\Username\Manufacturer\Appname\

If it is of any interest the app will only be deployed/installed on Windows 7 OS

I've browsed the forum and found a similar post: http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning4351&mpage=1&key=&#44351
However the solution was not posted sadly..
What I have done is the following,

Captured the apps installation using setup capture in wise (the app is currently a exe file)
Tried to use the set property custom action to [%USERPROFILE%]\Manufacturer\Appname\
This only creates C:\%userprofile%\Manufacturer\Appname\ and thas was not what I had in mind :)

If my description is bad please let me know!

Thank!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
You may wish to re-read what I said in that thread about using the percentage sign (%) when using environment variables as properties in Windows Installer.

BTW, what's wrong with using a folder beneath '%SystemDrive%\Program Files' as the INSTALLDIR? That's the recommended location for programs. I suspect it's because the brain-dead application needs write access to the folder? If so, you can permission the folder using SetACL or similar in a Custom Action.
Answered 07/13/2010 by: VBScab
Red Belt

Please log in to comment
0
If it is of any interest the app will only be deployed/installed on Windows 7 OS

You do realise this package will also never be installable by any distribution system that uses credentials other than that of the logged on user (like say LOCALSYSTEM)?
Answered 07/13/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
Oh sorry, it seems I read that post to fast :) I'll try it out

The reason I'm trying to install it to the users private profile is because the app connects to a remote database server.
All the users Settings for the app (Printers,save location etc) is saved in the apps folder

And since we are using roaming profiles on the desktop computers and trying to implement the idea not to have fixed workstation I was just thinking that it could be a nice idea to save the whole app down to the users profile and thus eliminating the need for the user to readjust the settings if he uses a different computer.
Answered 07/13/2010 by: napandee
Yellow Belt

Please log in to comment
0
ORIGINAL: pjgeutjens

If it is of any interest the app will only be deployed/installed on Windows 7 OS

You do realise this package will also never be installable by any distribution system that uses credentials other than that of the logged on user (like say LOCALSYSTEM)?



We are atm using SCCM 2007 for deployment will this still be a issue?
Answered 07/13/2010 by: napandee
Yellow Belt

Please log in to comment
0
We are atm using SCCM 2007 for deployment will this still be a issue?

short answer: yes

The reason I'm trying to install it to the users private profile is because the app connects to a remote database server.
All the users Settings for the app (Printers,save location etc) is saved in the apps folder


this sounds like something you'll want to leave to Windows Installer's self-healing functionality or Active Setup. basic idea is to 'repair' these settings into every user's profile when they first logon/start the application.

Ian (VBScab) will undoubtedly be able to link you to Phil Wilson's book on Windows Installer (Definitive Guide to Windows Installer), since by now I'm sure he has a notepad standby at all times with the links, just in case [;)]. If not, Google is your friend. Look up that book, and look up Active Setup on this site.
Answered 07/13/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
ORIGINAL: pjgeutjens

We are atm using SCCM 2007 for deployment will this still be a issue?

short answer: yes


Hmm I see I'm rater new at this so thank for your quick responses and insight, I'll try and rethink this or just go with the old usual installation path

Thanks!
Answered 07/13/2010 by: napandee
Yellow Belt

Please log in to comment
0
be sure to reread my previous post which I so painstakingly edited [:)]

PJ
Answered 07/13/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
You could have a go at this:

http://blogs.msdn.com/b/windows_installer_team/archive/2009/09/02/authoring-a-single-package-for-per-user-or-per-machine-installation-context-in-windows-7.aspx

But again the install's would have to be in a user context

and it will probably leave you with a management nightmare. Just another option to consider though
Answered 07/13/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
just go with the old usual installation path...and assign write permissions for either all users [shudder] or create a domain group and assign that group the appropriate permissions.
Answered 07/13/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity