/build/static/layout/Breadcrumb_cap_w.png

Best practice to move registy keys in Wise Packagestudio

Can someone tell me how to move registry keys located in HKEY_CURRENT_USER\CLSID to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\clsid ???
Right now i'm editting the registry table with the replace function but it would be nice if i can use drag and drop somewhere. I know, i can export it as a .reg file and then make my modifications and import it again, but i want to do it in packastudio itself. Tips are welcome.
Thx in advance

0 Comments   [ + ] Show comments

Answers (13)

Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
1
Personally I'd crack it open in Orca, copy and paste the required rows into excel to manipulate the data, then bring them back in.

There is a search and replace function in Orca v4 too.

I don't know of and drag/drop function in WPS.
Posted by: timmsie 15 years ago
Fourth Degree Brown Belt
0
Insted's better [:D]
Posted by: anonymous_9363 15 years ago
Red Belt
0
What about using a WPS macro?
Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
0
Well you are entitled to your opinion. Even if it's wrong.

Don't kick off everyone it was a joke [:D]

But Orca is best.
Posted by: AngelD 15 years ago
Red Belt
0
Move it under HKCR instead and depend on the ALLUSERS property where the com info to be written instead.

WSIFile = Wscript.Arguments(0)

Set oWFWI = CreateObject("WfWi.Document")
oWFWI.Open(WSIFile)

Set tblRegistry = oWFWI.WTables("Registry")

For Each rowSource In tblRegistry.WRows ' process each row in Registry table
If rowSource("Root") = 1 AND Mid(rowSource("Key"), 1, Len("Software\Classes\")) Then
rowSource("Root") = 0
rowSource("Key") = Mid(rowSource("Key"), Len("Software\Classes\") + 1)
End If
Next

Call oWFWI.Save(WSIFile)
Posted by: AngelD 15 years ago
Red Belt
0
ORIGINAL: MSIPackager
But Orca is best.


Sure, but InstEd is better [;)]
Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
0
Nice solution - thinking out of the box - I like it :-)

Shame you undid your good work with the InstEd comment though [:)]
Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
0

For Each rowSource In tblWiseSourcePath.WRows ' process each row in WiseSourcePath table


Shouldn't that be;

For Each rowSource In tblRegistry.WRows ' process each row in Registry table

Though?
Posted by: AngelD 15 years ago
Red Belt
0
Thanks for the heads-up Rob!

Copy'n paste has its failures :D
I've edit the post
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
sweet! I just downloaded v4.5 thanks for that...
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
you'd need to find/replace 1 with 2 in the root column of the registry table for all the rows with that key. and replace CLSID with SOFTWARE\Classes\clsid
Posted by: AngelD 15 years ago
Red Belt
0
ORIGINAL: aogilmor

you'd need to find/replace 1 with 2 in the root column of the registry table for all the rows with that key.  and replace CLSID  with SOFTWARE\Classes\clsid

What happens if it's installed as per-user [;)]
Posted by: doak 15 years ago
Senior Yellow Belt
0
Thx for all the reply's. I never heard about InstEd, really helpfull :) It did the job with the wise replace function but that 's not how i will do it in the future after i read the reply's.
thx four sharing
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ