Search the Community

Hi Guys, Ive been trying to deploy OneDrive application for the last few days without luck. I have followed few guides online but something (probably with the detection Method,) is not working. In addition to the application deployment, I need to start the OneDrive process and then associate it with the Business tenantid : https://support.office.com/en-us/article/Deploy-the-new-OneDrive-sync-client-in-an-enterprise-environment-3f3a511c-30c6-404a-98bf-76f95c519668 So the overall procedure would be: 1. Having suitable detection for OneDrive presence 2. Deploying OneDrive app 3. Start OneDrive process and associate it with the business tenant. Does someone has any experience with it? Appreciate any suggestions. Thanks!

Hi Everyone. First time here, thanks for reading. When I first deployed Office 2013 my org wanted nothing to do with OneDrive, so I removed OneDrive via OCT in "set feature installation states" and in addition, used the "block signing in to Office" setting found in the OCT under Features > Modify user settings > MS Office 2013 > Misc. Now, they want to use OneDrive. To reverse those earlier customizations, I need to make sure I change the right things. Here 's what I think I need to do: 1. Configure the "Org ID Only" setting via OCT in the MSP file used for Office deployments, then update the content on the DP. 2. Configure and enable the same setting via the User GPO found in User Config > Policies > Admin Templates > MS Office 2013/Misc > "Block signing into Office". The intent is that the first change affects new deployments going forward, and the second overrides that change in the MSP when GPO is applied. Is this right? Or, would the change to the MSP apply to existing installations after the content is updated on the DP and clients complete hardware inventory cycles? Do DP content updates to existing installations of software work like that? Or, would I need to send out a whole new deployment?

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