[THIN] Re: 64-bit 2003/Citrix w/SAP
- From: "Schneider, Chad M" <CMSchneider@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 15 Mar 2007 13:26:24 -0500
Worked, but not sure if it would long term.
I am able to get the users in, and have them change the reference file to the
proper (program files (x86).
Working now.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Greg Reese
Sent: Thursday, March 15, 2007 12:10 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: 64-bit 2003/Citrix w/SAP
on the other hand, what would happen if you just made a copy of the folder in
question in the "program files" folder. I know that Microsoft is trying to
keep things separate but it is just an organizational structure isn't it.
On 3/15/07, Greg Reese <gareese@xxxxxxxxx> wrote:
I agree, I don't think it is going to like it either but it would take two
seconds to try and who knows, you might get lucky.
I wonder how it would work out as a streamed application. Make the profile on
a 32 bit server then stream it to the 64, kind of ugly but maybe...
On 3/15/07, Landin, Mark <Mark.Landin@xxxxxxxxxxxxxxxx > wrote:
I don't think that's going to act like a "redirection" of a directory in one
directory tree to the same directory in another directory tree like Chad is
needing. That's more like the UNIX concept of a file link, where a given
directory or file object can be referenced by multiple names. To my knowledge,
shortcuts do not provide that kind of functionality. The closest kind of
functionality that I can think of is the old DOS SUBST command, and that too
isn't going to apply to this situation.
MS really caused headaches when they split up their own naming conventions (for
both file systems AND the registry) to have seperate but parallel locations for
32-bit vs 64-bit software. I kind of understand why they did it, but cannot
accept that this was their best option! I know a lot of other systems (say,
HP-UX, which is what I have experience with) that doesn't expose the user to
the difference between a 32-bit and 64-bit executable. The 800-lb gorilla,
wihere Microsoft's interests and priorities trump those of their customers,
strikes again.
Obviously, the application is at fault as well for hard-coding path names, but
MS very likely had the ability to shield us from these kinds of problems ...
they just chose not to.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto: thin-bounce@xxxxxxxxxxxxx
<mailto:thin-bounce@xxxxxxxxxxxxx> ] On Behalf Of Greg Reese
Sent: Thursday, March 15, 2007 11:00 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: 64-bit 2003/Citrix w/SAP
what happens if you put a shortcut in "program files" that points to the
location in "program files (x86)" that you need?
Greg
On 3/15/07, Schneider, Chad M <CMSchneider@xxxxxxxxx > wrote:
WE have SAP GUI running on 64-bit W2K3 and 64-bit Citrix PS 4.5. Works great.
What is not working is the BEX portion of SAP. It appears to have a hard coded
path to the "c:\program files" install path, yet when installed on a 64-bit
server, it installs to "c:\program files (x86)".
Any idea how to change BEX to use the proper path?
Chad Schneider
Technology Analyst/Citrix Admin.
Bemis Company, Inc.
920-303-7609
Other related posts:
