penngos

Hello, all. I am attempting to push an ancient piece of software called eCopy. Instead of using the registry, it still stores configuration info in an INI file.

The information that must be customized is a file path: \\<server>\<share>\<username>

How do I get the variable represented by <username> to write to the INI file? I have tried putting in the path and using %UserName%, but that doesn't work.


Using Wise's Windows Installer Editor, how can I create a transform that updates this file with the user's ID on installation?

Thanks,
Patrick Burnett

jdean

I would think that you would need to create a custom action that runs a vbscript to make the modification changes needed.

How adept are you with wise? Custom actions can get a bit tricky if you've never done them before.

appdeploy.com has some really good info about custom actions if you need to do some research.

__________________
IT Factotum * Altiris Addict * Wise Monger * VBScript Zealot

Jereme Dean
Orange County, CA
jdean33442@gmail.com

tammy104

I like to keep things simple (may not always be the best way) but this is how I would do it:

Get Registry Key Value
Variable=UID
Key=SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Value Name=DefaultUserName

EDIT INI FILE

[FILE]
filepath=\\server\share\%uid%

That should do it...

penngos

I'm embarrassed to admit that I need more instruction. I'm not sure how to grab that variable from the registry within the confines of Wise Packaging?

Brandon

If you do a Wise SetupCapture it should be smart enough to change that value to the Windows property [LogonUser] .

Then each time a new users clicks on an advertised entry point (the shortcut) it should self-heal for them and populate that ini file within their profile and use their name since they are the user performing the install(self-heal).

The end location of that file/component is in %USERPROFILE% right?

__________________
Brandon