Scripting - Verifying 64 bit reg keys
I'm trying to deploy the CRM Outlook client in one script and I have to do a few things before deployment. CRM comes in a 32 bit client as well as a 64 bit client. 32 bit versions of windows are not a problem but 64 bit versions are cause you can install a 32 bit office on a 64 bit version of Win7.
So I need to check which version of Office they are running via the "Bitness" value in the reg but also need to check if CRM is installed which can be in HKLM under wow64 or the normal Windows uninstall path in the reg.
How can I "Verify" both keys and "Remediate" depending on the answer. If the client is already installed then I don't want to do anything. If its not then I need to install the the correct package pertaining to either the 32 or 64 bit version of office. Just need to set this up.
Thanks!
So I need to check which version of Office they are running via the "Bitness" value in the reg but also need to check if CRM is installed which can be in HKLM under wow64 or the normal Windows uninstall path in the reg.
How can I "Verify" both keys and "Remediate" depending on the answer. If the client is already installed then I don't want to do anything. If its not then I need to install the the correct package pertaining to either the 32 or 64 bit version of office. Just need to set this up.
Thanks!
1 Comment
[ + ] Show comment
-
Wow I am bumping an old post but I'm curious if you get this licked, jestes? I'm having the same issue. - vmann 11 years ago
Answers (1)
Please log in to answer
Posted by:
dchristian
13 years ago
You could use a custom inventory rule to check the"bitness" reg key.
Once you know that, you can build smart labels to install the software.
Once you know that, you can build smart labels to install the software.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
