Hi!
I have a problem with a Custom Action in the Veritas Netbackup Client 6.5 mst file. This is for
the 64 bit Windows 2003 Server, and the problem occurs when I'm adding a custom action (.vbs ),
that adds Regvaules, the Regvalues ends up in the wow64 node instead of the "original" registry.
The application is 64 bit but the msi seems to run in 32bit mode.

My question is, can I force the added regvaules to be written in the 64 bit registry, or force the msi to run
in 64 bit mode?

kindly,
Piotr
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
I suspect that the script engine you're using cannot write to (and may in fact be unaware of the presence of) the 64-bit hives. As a work-around, can you have the CA import a .REG instead? Could it also be permission-related?
Answered 04/08/2008 by: VBScab
Red Belt

Please log in to comment
0
yeah, I was thinking about the .reg file workaround.... to have the vbs create a regfile, and then execute it under the msi-installation...
What about the install engine, wich should I use?

kindly,
Piotr
Answered 04/08/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
0
I don't think the WI engine version will matter but I believe, if your updates are, er, up-to-date, that WinSrv 2003 will have 3.1 v2 http://support.microsoft.com/Kb/893803
Answered 04/08/2008 by: VBScab
Red Belt

Please log in to comment
0
no your right...but shouldnt the vbs engine be correct if the server is up-to-date?
I assume that this msi-installer isn't the only one I will have to do on a 64 bit Server,
any other suggestions?

kindly,
Piotr
Answered 04/08/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
0
Piotr, are you using embedded script?
Answered 04/08/2008 by: VBScab
Red Belt

Please log in to comment
0
Yes, I am... if you mean embedded in the Wise package? Is there really a differance from having it run "from file"?

kindly,
Piotr
Answered 04/08/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
0
ORIGINAL: piotr.kuczkowski
Yes, I am... if you mean embedded in the Wise package? Is there really a differance from having it run "from file"?
Yes! When it's embedded, it will be using the Windows Installer's internal script host and not Windows Scripting host. This is why the 'WScript' directive needs to be removed from such scripts - the WI engine has no knowledge of what WScript is. However, when run from an installed file (or, if you don't want people to get access to the script when the install completes, from an extracted binary stream), it's just like a normal script and will use whatever Windows Scripting host is installed on the box.

Confusing, I know, but there you are. I have no clue why they're separate.
Answered 04/08/2008 by: VBScab
Red Belt

Please log in to comment
0
sorry for the late reply, has been ill for a couple of days...

It works great man, I ran the script lika a "call VBScritp from installation" and it worked perfectly.
Does anyone know what the X64 bit mode in wise is for? I tried to run the script "From embedded code" with the x64 bit mode checkboxe checked, I't didnt write the regfiles in the WOW64node part but on the other hand not in the place I wanted it to write....

thanks VBScab, couldnt do it without you...

kindly,
Piotr
Answered 04/11/2008 by: piotr.kuczkowski
Orange Belt

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