Search the Community
Showing results for tags 'office 2013'.
-
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?
-
Hi, all. I noticed today that the disk space on our Config Manager server was getting a bit more filled up than I'd like. Dumping the .wim.bak files left over from offline servicing helped, but when I fired up Treesize, it pointed out that our Office 2013 updates are taking up a TON of space. Right now, that number is right around 63GB. This for an app that's only three years old, while a 6 year old OS's (Win7) updates are only taking up around 11GB. September's Office 2013 updates alone comprise 231 folders and files worth of stuff, out of 7416 total folders and files. We've only got 139 updates currently deployed that aren't expired or superseded, and they span years worth of stuff, so I'm not sure where all the extra stuff's coming from. I'd imagine most/every update would have two files - 32 and 64 bit - but not tens of files. A lot, maybe a majority of the files appear to be language packs (e.g. proof-zh-tw.cab) that we have zero use for, even though we're only set to download English packages. Anyone know if this is normal for Office 2013? Seems a bit excessive, but I've got nothing to compare against.
- 4 replies
-
- office
- office 2013
-
(and 3 more)
Tagged with:
-
Hi everyone, I have packaged Office 2013 Enterprise software and I keep getting error code 0x756B (30059) Now I know this code is related to licence keys so I copied the software to a space laptop. Created an MSP file and dumped it in the updates folder. Then I run the setup.exe locally and it works. When I copy that software to a share and package it it doesn't work and get the above code. Any suggestions? Thanks in advance.
- 1 reply
-
- office 2013
- sccm 2012
- (and 4 more)
-
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
-
First off I'd like to state that although I've searched for this error on numerous forums I only find that the error most similar to mine is "Execution status received: 24". I have a Task Sequence that deploys Windows 8.1 Enterprise with Bitlocker enabled. I have a standard Install Application step which installs Office 2013 Pro. When it gets to this step sometimes (rarely, 1 out 15 so far) it succeeds. More often than not is fails. Below is the section of the SMSTS.log that pertains to the application install. On most forums the folks have found that the issue just resolved itself without changing anything. This hasn't been the case for me thus far. Also most errors pertain to the "Execution status received: 24" error. Which is a download error. Mine says the application is available and ready to go. After that though it immediately fails with the generic code 0x80004005 . This application successfully installs outside the OSD TS. I'm having to go behind each machine and manually install Office on each one. I have the program available outside to deploy even when not advertised. I have deployment options set to Download and run locally. Execution status received: 3 (Application is available for installation ) InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)App install failed. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Setting TSEnv variable '_TSAppInstallStatus'='Error' InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_ECA3CCCE-5DBC-47E0-BB14-0D211004E0C9/Application_32f1e4bc-f0ae-49cf-be38-c33f76e7815c'='' InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Completed installation job. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Step 2 out of 2 complete InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Install application action failed: 'Microsoft Office Professional Plus 2013'. Error Code 0x80004005 InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Sending error status message InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10) Setting URL = http://OCS12.ocboe.local, Ports = 80,443, CRL = false InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10) Setting Server Certificates. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10) Setting Authenticator. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Set authenticator in transport InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10) Setting Media Certificate. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Sending StatusMessage InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Setting message signatures. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Setting the authenticator. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)CLibSMSMessageWinHttpTransport::Send: URL: OCS12.ocboe.local:80 CCM_POST /ccm_system/request InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10)Request was successful. InstallApplication 6/5/2014 11:06:01 AM 2576 (0x0A10) Any ideas? I can also supply more logs if necessary.
- 3 replies
-
- sccm 2012 r2
- office 2013
-
(and 1 more)
Tagged with: