41 votesAnonymous commented
This is a great idea and would make me feel better instead of worrying about if all my various schedules I have for all our patches and scripts are going to collide and cause the universe to implode!
Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.Anonymous commented
[First, Ed, I suggest extracting the MSI and MST files from the SPSS .exe installers using the /b switch and installing with msiexec.]
However, dealing with 64-bit Windows via WOW64 due to a 32-bit agent is a royal pain.
First, you have to worry about if you referencing the proper folder with the various ProgramFiles environment variables:
There is then the issue about accessing the correct part of the registry, do I use HKLM64 or HKLM\Software\WOW6432Node ?
And of course there is always the great fun for all dealing with the File System Redirector:
It's all doable, but just a huge pain in the you know what.
Over the coming releases, we will be revamping our targeting and scheduling pages. This a great example of where we will extend your ability to control what you are targeting and when it should be delivered.