Deploying a Shim for Office 2010 on XP 64
Greetings,
My experience is a bit liimited with software packaging in general, but I've figured out that the only way to install Office 2010 x32 on an XP x64 workstation is with a "shim". I am trying to deploy x32 Office 2010, and have therefore created a x32 Shim with ACT 5.6 for the Setup.exe of Office 2010.
The trick is getting it deployed. Our users are locked down and not able to perform software installs, consequently installs are done using the system administrator account. I have not been able to find a method to install the .sdb file (invoking sdbinst.exe) with SCCM. The installs either fail, or just hang. Also, it does not seem to matter whether or not someone is logged in, not logged, or a logoff is forced. I have attempted these methods with direct advertisements and through a Task Sequence install with no success.
I'm guessing that by now I'm staring at a tree and can't see the forest, but I could sure use some advice.
Thanks in advance.
K
My experience is a bit liimited with software packaging in general, but I've figured out that the only way to install Office 2010 x32 on an XP x64 workstation is with a "shim". I am trying to deploy x32 Office 2010, and have therefore created a x32 Shim with ACT 5.6 for the Setup.exe of Office 2010.
The trick is getting it deployed. Our users are locked down and not able to perform software installs, consequently installs are done using the system administrator account. I have not been able to find a method to install the .sdb file (invoking sdbinst.exe) with SCCM. The installs either fail, or just hang. Also, it does not seem to matter whether or not someone is logged in, not logged, or a logoff is forced. I have attempted these methods with direct advertisements and through a Task Sequence install with no success.
I'm guessing that by now I'm staring at a tree and can't see the forest, but I could sure use some advice.
Thanks in advance.
K
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Ksuekihlman
12 years ago
It's interesting that nobody has ever dealt with this, but the solution was in the command string, and knowing that the sdbinst.exe is part of the XP X64 OS. This command string "sdbinst.exe -q 2010onXP64.sdb" does the trick (assuming this is the name of the .sdb file you created). I assume a similar string would work for any other program requiring a shim as well.
Should anyone actually care, I hope this helps. lol
Should anyone actually care, I hope this helps. lol
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.