Wise Package Builder and Default User Profile
As a newbie packager, I downloaded the trial for Wise Package Builder 10 SP3, and went along with the free Appdeploy.com training video for using SetupCapture. I've been using Firefox 3.0.1 as my test. Everything went well while using the video tutorial, except one (important) thing. The resulting MSI package that SetupCapture builds does not deploy the changes that I made during the snapshot to the Default User profile. The changes that I made were to simply copy the Mozilla folder out of Application Data, into the Default user's Application Data folder. The SetupCapture summary of the files showed that this change would take place as a part of package, but when I deployed the package, Windows Installer ran and Firefox's profile wizard ran for any new users with no profiles on the test machine. Since I am packing for a lab environment, I need the Mozilla profile to be copied into the Default User profile, so that new users will not have to go through the Firefox profile wizard. How do I capture changes to the Default User profile (C:\Documents and Settings\Default User)?
Thanks,
Dan
Thanks,
Dan
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
AngelD
15 years ago
Hi Dan,
You need to read up regarding profile-fix (aka resiliency, repair, healing) so the user related files/registry will be written during first launch.
You need to read up regarding profile-fix (aka resiliency, repair, healing) so the user related files/registry will be written during first launch.
Posted by:
danpixley
15 years ago
Thank you! I will take a look at this. Out of curiosity, is there no way to force SetupCapture to capture the changes made to the Default User folder/file structure? Does Admin Studio have better functionality for this?
Posted by:
anonymous_9363
15 years ago
I'm not aware that Wise didn't capture there but it may have been added to the Exclusion list(s).
In any event, what sort of idiot vendor makes changes there? It's only relevant when new users are created locally. Just replicate what changes it makes to the current user and then follow the advice re: self-healing/repair. John Mc Fayden has a very useful blog about self-healing: I'm surprised no-one posted a link to it. Use AppDeploy's Search to turn it up.
In any event, what sort of idiot vendor makes changes there? It's only relevant when new users are created locally. Just replicate what changes it makes to the current user and then follow the advice re: self-healing/repair. John Mc Fayden has a very useful blog about self-healing: I'm surprised no-one posted a link to it. Use AppDeploy's Search to turn it up.
Posted by:
AngelD
15 years ago
Here is the link http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!123.entry
What I've seen during captured applications whenever a ".DEFAULT\" registry entry was captured there was also a HKCU entry for it too so it may be the same for files.
What I've seen during captured applications whenever a ".DEFAULT\" registry entry was captured there was also a HKCU entry for it too so it may be the same for files.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.