Software Deployment

I am sorry for asking, but why would you need to place files in Default User?
Does not all users already have a created profile?

/Jonas

Good question.

Because the developers of this application have included a configuration utility that updates an XML file in the Default User profile, so we would want new users to receive any changes made to this file after the installation, rather than the original version from the MSI.

Not ideal at all, but that's the way they have coded it.

There's a "built in" directory in the "directory table" - AppDataFolder

So you'd just need to create your folder and file off this

ORIGINAL: timmsie

There's a "built in" directory in the "directory table" - AppDataFolder

So you'd just need to create your folder and file off this


But wouldn't this just create my folder under All User\Application Data or <Current User>\Application Data?

<Current User>\Application Data folder. Which is what you want isn't it?

create a new wsi and test it. Create a component and set the installtion directory to "Windows\Profiles\Application Data" (which is AppDataFolder)

I Understand your question, but I don't really see any reason for having the new users into the new XML while the old users has the old XML.

If I really needs to use the Default User, I would have used the [WindowsVolume] and created a subfolder named Documents and settings and so on in the MSI-project.

/Jonas

ORIGINAL: jonasm

I Understand your question, but I don't really see any reason for having the new users into the new XML while the old users has the old XML.

If I really needs to use the Default User, I would have used the [WindowsVolume] and created a subfolder named Documents and settings and so on in the MSI-project.

/Jonas


The old users will have their config files updated by the application based on the time/date stamp on the XMLs in the Default User profile. Call it bad coding, but I'm just the packager. [8D]

The only problem with that solution is that Documents and Settings will not necessarily reside on the Windows volume, right?

For future reference I found a solution, albeit not a bulletproof one.

1. Created a folder named "Default User" in the root of my install.

2. Used the System Search page in Wise to check for the existance of ntuser.dat under \Documents and Settings\All Users\ on both C: and D: drives.

3. Used a Set Directory custom action before InstallInitialize to redirect my Default User folder accordingly, by checking the properties set in step 2.

Of course this would all probably go up in flames in a Citrix environment for example. Oh well.