Hey, guys.

I've recently started App-v sequencing for 64 bit OS and need some help. I've sequenced an app (it's a VFS install), which works great when streamed to a Windows 7 32bit client. As a test, I've also sequenced it on 64bit Server 2008 (using the 64-bit sequencer). When I streamed it down to a 2008 Terminal Server (64bit), I've run into problems.

I'm running a pre-launch dependency script, which runs an exe residing in the system32 folder. Anyway, basically it doesn't run (on 64bit OS - it works fine on 32bit OS) and I'm pretty sure it's to do with redirection on a 64bit OS.

My script simply calls the executable name. No path is specified because it sits in the System32 folder and that is set by the path environment variable etc.

<SCRIPT EVENT="LAUNCH" PROTECT="TRUE" WAIT="FALSE" TIMING="PRE">
<SCRIPTBODY>sample.exe</SCRIPTBODY>
</SCRIPT>


So I've opened up a command prompt in the System Guard and had a look around.

I've found that sample.exe file exists in:

C:\Windows\System32
C:\Windows\SysWOW64
Q:\test.app\VFS\CSIDL_SYSTEM

If I run the exe manually (in the command prompt) from C:\Windows\SysWOW64 or Q:\test.app\VFS\CSIDL_SYSTEM, it runs fine. If I run it from inside C:\Windows\System32 or from any other directory for that matter (thus relying on the Path env. variable to locate it), I get 'The system cannot find the file c:\windows\system32\ingwrap.exe' - even though it exists???

So, it seems that my script is trying to run the sample.exe in the System32 folder, as opposed to the SysWOW64 folder. If I change my script launching code to:

<SCRIPT EVENT="LAUNCH" PROTECT="TRUE" WAIT="FALSE" TIMING="PRE">
<SCRIPTBODY>c:\windows\syswow64\sample.exe</SCRIPTBODY>
</SCRIPT>


....then everything works fine. But it just concerns me why it isn't redirecting properly, and hardcoding this path isn't really the solution is it?

I'm just about to get procmon'ing, but I thought if anybody has encountered this issue before you can save me a big chunk of time which I don't have..... I've searched this forum and can't find much on the issue. I should mention that I've not been sequencing for too long, and I've not done much work on 64bit OS either, so I'm all ears.

Thanks.
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
Procmon didn't help me too much. I loaded a command prompt from a dependency script:

<SCRIPT EVENT="LAUNCH" PROTECT="TRUE" WAIT="FALSE" TIMING="PRE">
<SCRIPTBODY>cmd.exe</SCRIPTBODY>
</SCRIPT>

and in this command prompt, I ran Procmon.exe. Then I ran my sample.exe. Procmon returned the following (but the exe still didn't run):

QueryInformation........................c:\windows\syswow64\sample.exe..................NO SUCH FILE
.....
.....
QueryInformation.......................c:\test.app\VFS\CSIDL_SYSTEM\sample.exe...............SUCCESS

But then if I run 'c:\windows\syswow64\sample.exe' from the command prompt, it launches fine? Hmmm. I'm confused.
Answered 11/30/2010 by: captain_planet
Second Degree Brown Belt

Please log in to comment
0
I haven't really looked into any 64bit OS either, so I can't help you with that. However... Out of curiosity now, I do wonder what behavior it shows if you run the 32 bit sequence (which was working great on 32 bit OS) on a 64 bit OS.

According to this page that sort of thing is supported. And because the sequence from the inside looks quite different depending on whether you sequence it on 32 bit or 64 bit machines I really wonder what the 64 bit app-v client does to the 32 bit sequence.

It might either work like a charm, make it worse than it already is, or maybe doesn't change a thing... [;)]

All you have to do if you still have the 32 bit sequence:
Sequence the 32-bit app on a 32-bit OS using the 4.6 sequencer. Specify x86 and x64 platforms as targets as appropriate for clients.

Good luck!
Answered 11/30/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
Hey Rheuvel,

Yeah, I tried that. But it behaved exactly the same.....For now I can call '%windir%\SysWOW64\sample.exe' to get around the issue. I'm actually unable to fully test the app due to back-end connectivity etc, so it does concern me.....
Answered 12/01/2010 by: captain_planet
Second Degree Brown Belt

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