Setting working directory of shortcut
Hi ,
We have a requirement of setting working directory of a shortcut to %Temp%.
The working directory gets sets properly in Admin user but when logged to user it takes the admin profile temp directory instead of user profile temp directory.
the package doesnot have any harding to admin profile temp directory..but it %temp% doesnot get resolve when logged in with users profile
please let me know how can i resolve the working directory in user profile
Thanks & Regards
Answers (2)
To help you there is a requirement for some extra info:
- what packagetype are you deploying (MSI, App-V, ZAV or other)
- with what distribution system
If it's an msi you could start checking if a different value for ALLUSERS could help you out.
Comments:
-
Its an msi package ...and as per our standards we set the ALLUSERS property as 1
but still it does not resolve the %temp% as user directory - Gary 11 years ago -
OK, so you are doing a per-machine installation. The %Temp% variable gets a real value for the user running the setup during the running of msiexec.exe. In this case you would be better served with a per-user installation.
You state that corporate policy is to install per-machine so this is not an option.
A way forward would then to create the required shortcut as a file (xxx.lnk) in the required location. - EVEEN 11 years ago
Just leave the working directory of your shortcut as %Temp% (put it as %Temp% literally) and it should be ok and app should be working. The main reason is that the hard-coding of that %Temp% you used is happening during the installation and not during the login. When you installed it via admin account, it gets resolved already that is why you see it also in the user's account.
If you insists, that shortcut might need a script every login to the machine and also don't forget setting up the access permission so users can change it.
