W
wilsonc
Im not sure if this by design or perhaps a bug. Here is the scenario.
In our testing environment I have a 64bit 2k8 host running the web portal as well as being the primary TS config server. The point of this server is to not be used to publish apps, only to act as the farm gateway and redirect client requests to other servers. Previously I had two 64bit TS servers part of the farm. I removed those servers and added a 32bit server to the farm. The problem is, whenever I publish an app from the 32bit server (in this case excel 2007) I do it using the 32bit location ie: %ProgramFiles\Microsoft Office\Office12\EXCEL.EXE, however after applying the changes it keeps reverting to: %ProgramFiles(x86)%\Microsoft Office\Office12\EXCEL.EXE the 64 bit version path.
Its as if its inheriting the path from the gateway server. If that is the case this raises a concern. Is it not possible to mix and match 64 and 32bit servers in the same farm? Am I doing something incorrectly?
I removed the published app, restarted the gateway server and republished the app with the same results.
In our testing environment I have a 64bit 2k8 host running the web portal as well as being the primary TS config server. The point of this server is to not be used to publish apps, only to act as the farm gateway and redirect client requests to other servers. Previously I had two 64bit TS servers part of the farm. I removed those servers and added a 32bit server to the farm. The problem is, whenever I publish an app from the 32bit server (in this case excel 2007) I do it using the 32bit location ie: %ProgramFiles\Microsoft Office\Office12\EXCEL.EXE, however after applying the changes it keeps reverting to: %ProgramFiles(x86)%\Microsoft Office\Office12\EXCEL.EXE the 64 bit version path.
Its as if its inheriting the path from the gateway server. If that is the case this raises a concern. Is it not possible to mix and match 64 and 32bit servers in the same farm? Am I doing something incorrectly?
I removed the published app, restarted the gateway server and republished the app with the same results.