Hi All,
I'm to the board here. Super cool there is so much information here!
Im currently working on a Windows 7 migration and I've noticed Wise package studio 8 is capturing way too many registry keys with windows 7. (these are clean packaging machines BTW) For example, I did a setup capture on yahoo messenger 9 and it captured approx 170,000 keys. I contacted symantec about this and they said WPS has a "known defect" in that its exclusion list doesn't support windows 7. I've downloaded a trial version of adminstudio and found that its setup capture worked just fine (approx 1500 registry keys captured on yahoo messenger 9) So apparently their exclusion list is up to date. I've grabbed adminstudios exclusion list (default.ini) in hopes of using it with wise's. It looks like it will be a tedious process to merge the two.
Just wondering if any of you have run into the same issues or know of a current exclusion list that someone's created.
or maybe I'm headed dowm the wrong path completely
As a current workaround solution untill I get a better exclusion list built, I've just added the following to Wise's exclusion list (WisePSSC.ini).

C:\Windows\winsxs\*
HKEY_LOCAL_MACHINE\COMPONENTS\\<ignore entire subtree>
HKEY_LOCAL_MACHINE\Schema\<ignore entire subtree>

My packaging machines system info is: VMware workstation version 7.1.3. Windows 7 enterprise (32bit) clean machine (no other apps installed, all windows features, firewall, Defender, UAC, etc. turned off)
Wise Package Studio 8. Setup capture done with Enhanced File and registry key association turned off. Retain registry information as is selected and Use snapshot comparisons only selected.
Any ideas or suggestions would be greatly appriciated.
Thanks,
Nephi
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
Nephi,

While doing the SetCapture option there is a setting option dont remember exactly where it is on WPS , click on that and add the exclusion list referring to the exclusion found by Adminstudio , it will directly make chnages to the file
once you are done (instead of doing it manually) then you can copy the ini file and keep it on the server whenever you are performing the setup capture.
Answered 02/17/2011 by: shweta_kar
Blue Belt

Please log in to comment
0
Thanks Shewta,
I can point wise to the Install shield exclusiom list, but unfortunatey the syntax\logic in the .ini file is slightly different. WPS isn't able to interpret this.
At this point it looks like I'll be doing it manually.
Answered 02/18/2011 by: nephievans
Yellow Belt

Please log in to comment
0
I added the 3 lines from the first post to the WisePSSC.ini file, and Wise does see them when you look in the exclusion list, however during the scanning process the keys are still scanned. And scanning takes ages thanks to it. I am now waiting already 20 minutes and still see scanning HKLM\COMPONENTS. Really annoying. Does anyone have a fix/update or servicepack for this important bug in Wise Package Studio 8?
Answered 07/28/2011 by: funnyproffy2
Senior Yellow Belt

Please log in to comment
0
You'll be a very old man if you plan to wait for Symantec to update pretty much anything in the Wise product family. You would best be advised to work around the shortcomings.
Answered 08/04/2011 by: VBScab
Red Belt

Please log in to comment
0
When trying to add:
HKEY_LOCAL_MACHINE\COMPONENTS\\<ignore entire subtree>
HKEY_LOCAL_MACHINE\Schema\<ignore entire subtree>
to the exclusion list they do not appear as options.

Is there some way to manually add them?
Answered 10/23/2011 by: jorey
Yellow Belt

Please log in to comment
0
Hint:
[WiseShare]Repackage.INI
%SystemRoot%\WisePSSC.INI
Answered 10/31/2011 by: VBScab
Red Belt

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