I'm currently getting to grips with SCCM 2012 R2, and have a pressing need to forcefully install OneDrive for Business to approximately 6000 devices.
I had a similar requirement to install Lync 2013 across the estate earlier, but our platform was inherited and very sketchy (failed DP's etc), therefore installation was very hit and miss.
Other than the flakey platform, I struggled with, Bitness detection of Office.
For example, you cannot install mixed-bitness Lync 2013, or OneDrive for Business clients. By this I mean, you cannot install 64 Bit Lync, with 32 Bit Office. But detecting 32 Bit Office is not straightforward, at least it's not to an SCCM newbie, and Microsoft don't seem to make things any easier!
We, are not alone I'm sure, in having such a mongrel userbase...
We have users running 64 bit Windows, with 32 bit Office, with 64 bit Outlook...
We have users running 64 bit Windows, with 32 bit Office 2010, with 64 bit Office 2013...
Detecting for a seamless, silent, successful install of these add-on applications, is pretty tricky!
At present my detection relies on Registry Entries...
x64 Detection
OS = 64bit
&
Office 64bit Detection = True (custom Condition)
( Office 2010 Bitness (Method 1) None of {x86, NULL} OR Office 2013 Bitness (Method 1) None of {x86, NULL} ) OR ( Office 2010 Bitness (Method 2) None of {x86, NULL} OR Office 2013 Bitness (Method 2) None of {x86, NULL} )
x86 Detection
( Office 2010 Bitness (Method 1) Does not contain {x64} OR Office 2013 Bitness (Method 1) Does not contain {x64} ) OR ( Office 2010 Bitness (Method 2) Does not contain {x64} OR Office 2013 Bitness (Method 2) Does not contain {x64} )
Those conditions mentioned above, look like this; (checks registry entries)
I'm currently getting to grips with SCCM 2012 R2, and have a pressing need to forcefully install OneDrive for Business to approximately 6000 devices.
I had a similar requirement to install Lync 2013 across the estate earlier, but our platform was inherited and very sketchy (failed DP's etc), therefore installation was very hit and miss.
Other than the flakey platform, I struggled with, Bitness detection of Office.
For example, you cannot install mixed-bitness Lync 2013, or OneDrive for Business clients. By this I mean, you cannot install 64 Bit Lync, with 32 Bit Office. But detecting 32 Bit Office is not straightforward, at least it's not to an SCCM newbie, and Microsoft don't seem to make things any easier!
We, are not alone I'm sure, in having such a mongrel userbase...
We have users running 64 bit Windows, with 32 bit Office, with 64 bit Outlook...
We have users running 64 bit Windows, with 32 bit Office 2010, with 64 bit Office 2013...
Detecting for a seamless, silent, successful install of these add-on applications, is pretty tricky!
At present my detection relies on Registry Entries...
x64 Detection
OS = 64bit
&
Office 64bit Detection = True (custom Condition)
( Office 2010 Bitness (Method 1) None of {x86, NULL} OR Office 2013 Bitness (Method 1) None of {x86, NULL} ) OR ( Office 2010 Bitness (Method 2) None of {x86, NULL} OR Office 2013 Bitness (Method 2) None of {x86, NULL} )x86 Detection
( Office 2010 Bitness (Method 1) Does not contain {x64} OR Office 2013 Bitness (Method 1) Does not contain {x64} ) OR ( Office 2010 Bitness (Method 2) Does not contain {x64} OR Office 2013 Bitness (Method 2) Does not contain {x64} )Those conditions mentioned above, look like this; (checks registry entries)
Office 2010 Bitness (Method 1) SOFTWARE\Microsoft\Office\14.0\Outlook\Bitness
Office 2013 Bitness (Method 1) SOFTWARE\Microsoft\Office\15.0\Outlook\Bitness
Office 2010 Bitness (Method 2) SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Outlook\Bitness
Office 2013 Bitness (Method 2) SOFTWARE\Wow6432Node\Microsoft\Office\15.0\Outlook\Bitness
How else might I achieve this? Other than uninstalling * Office and installing 2013 full phat
Share this post
Link to post
Share on other sites