Office 2013 update KB 2726958 Problem

Our pcs applied the latest round of Windows Updates yesterday and the Office Update KB2726958 caused the macros in Excel 2013 spreadsheets to stop working. Uninstalling just this update returned full functionality to Excel.
These are all Windows 7 64 bit machines connected to an AD domain with 32-bit Office 2013 Professional or Pro Plus.
Any machine that had applied the latest updates released on Tuesday suffered from this problem. Opening a .xlsm spreadsheet looked fine but users were unable to click on Macro buttons to e.g. load a userform.
I have spent 28 minutes on the phone trying to speak to somebody, anybody, in Support but no-one was interested so I am trying this forum instead.

Performing the steps in the link (http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/13/forms-controls-stop-working-after-december-2014-updates-.aspx) does
restore the ability to run button driven macros as well as add controls and buttons.
However, a task as simple as:
Creating a new workbook.
Saving as macro enabled workbook.
Adding ActiveX form toggle button.
Adding: msgbox "Toggle this!" to the change even of the newly added toggle button.
Saving the workbook.
Everything works great on this machine.
When the workbook is opened on another machine (I've tried several that can open and use other macro enabled workbooks with buttons and such.), the button appears, but the button and macro are not functional. Deleting the sheet
in the workbook causes Excel to crash.
Once I uninstalled KB2726958 on the machine where the workbook is created, I am able to perform the above with no issues. Of course, this is a temporary work around that will be clobbered by policy driven Windows /Office Updates the next time I restart.
HALP!
MrMikeV

Similar Messages

Office 2013 updates fail on computers with Access 2013 installed

I have about 10 workstations with the combination of Windows 7 enterprise 32 bit, Access 2013 and Office 2007 installed.
SCCM offers up both Office 2007 and Office 2013 updates to these machines, but the Office 2013 updates, fail to install.
The same thing happens when I go to Microsoft updates and manually install the required Office 2013 updates.
I read that one of the updates required Office 2013 sp1.
But when I downloaded it, it won't install: KB2817430 "The expected version of this product was not found on the system."
This is the second month I've had the failures. I removed KB2878316 and KB2889927 from my deployments and packages to stop repeated install attempts.
But this month I've got a new on failing, KB2899493.
Is there a way around this problem?

Thanks, I couldn't really find anything but it looks as though this could be just the way it is.
from http://support.microsoft.com/kb/2784668
When you start a version of Access on a computer that has multiple versions of Access installed, the Windows Installer may start, and
a message that states that the Windows Installer is preparing to install Access may be displayed before Access starts.
Every time that you start Access 2003, Access 2007, or Access 2010 after you use Access 2013, the Windows Installer repair operation registers
that version of Access. Similarly, the Windows Installer repair operation registers Access 2010 every time that you start it after you use an earlier version of Access. This does not occur when you start Access 2002, nor does it occur when you start the same
version of Access again.
Is this likely to also apply even when running App-V?

Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

Hi,
I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily.
I just installed Office 2013 on this system and have activated it as necessary. The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM. I have other systems with
Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
What can I check to try and determine what the problem is?
Thanks in advance,
Nick

Yes, the 8.1 system is a member of collection where the update deployment is targeted.
Are there any specific logs I should check in the client? If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office 2013 Updates Error - Mapped Drive

Event ID 11327
Product: Microsoft Office Professional Plus 2013 -- Error 1327. Invalid Drive: V:\
Event ID 1023:
Product: Microsoft Office Professional Plus 2013 - Update 'Update for Microsoft Office 2013 (KB2956177) 32-Bit Edition' could not be installed. Error code 1603
Error within Software Center: The software change returned error code 0x80070643.
These errors only occur while updating through SCCM 2012 R2 automatic software updates. I can download the update directly from the Microsoft site and install without any errors. I am a new to SCCM, but was able to push out updates for Windows 7 and Office
2010 without errors. After further testing I found that editing the Office 2013 install with the customization tool would allow the update to run. My MSP file custom install has "Remove Files" set to delete links on a mapped network drive (V:\).
I am not sure how Office 2013 updates through SCCM (only) would care about a custom install portion that should be unrelated.
I plan to exclude the V drive file removals from the custom install and just do it from a script. However, I am not sure what to do about updating the machines which currently have 2013 installed and constantly error while updating through SCCM.

you are getting into different things here. Creating the ADR and runs every-time ? Microsoft do not release patches everyday and there is no point running the ADR everytime.coming to the question , how did you create and update the MSP for the Office Update
file ? using ADR ,for deploying the updates,you will not have facility to control the command line options . for the drive letter issue (Product:
Microsoft Office Professional Plus 2013 -- Error 1327), you can refer
http://support.microsoft.com/en-us/kb/327763. you can try installing the MS office 2013 on a PC without any drive mappings and try the update. I suppose the issue could be with the drive mapping something related.
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr

Office 2013 Pro-Plus installation problem on Windows 8

Downloaded OfficeProfessionalPlus_x86_en-us.img from TechNet on my brand new Dell PC.
When double clicked, Windows complains 'Sorry, There was a problem mounting the file".
Used 7Zip and saw a Setup.exe
When I ran Setup.exe it complains "The specified module could not be found"
I have removed Office 2010.
- Jayawanth

Hi
We recommend you download it from the website and extract it again to make sure your source install is complete.
Run setup.exe as administrator then try the install.
If the issue persists, refer to the article on General troubleshooting for installing Office 2013 and Office 365:
http://support.microsoft.com/kb/2822317
Regards
Tylor Wang
TechNet Community Support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SharePoint 2013 Update Workflow Manager problems after Service Pack 1

Hello guys,
I've installed the service pack 1 for SharePoint 2013 and then I tried to update the workflow manager, but I always get an error message that the workflow manager could not be updated!
Is the installing order wrong? should I first install the update for the worklfow manager and then the update for SharePoint 2013?
Best regards
Matthias

The error message see below for "Cumulative Update for Workflow Manager 1.0 (KB2799754)
"One of the custom actions failed. The installation cannot continue. See log for details!"
[06/06/14 09:48:44] Performing install.
[06/06/14 09:48:44] At least one of the product packages has been detected.
[06/06/14 09:48:44] preReqUpdateDisplayName is :
[06/06/14 09:48:44]
[06/06/14 09:48:44] Wizard mode on.
The following products will be enhanced:
Workflow Manager 1.0
Attempting to open cached Msi package for product code: {04A7199E-565D-4654-88A3-80A9A7BADDD9}
Successfully opened cached Msi package.
[06/06/14 09:48:48] Opening Service Control Manager...
[06/06/14 09:48:48] Operation succeeded.
[06/06/14 09:48:48] Copying files...
[06/06/14 09:48:48] Checking and creating target directory C:\ProgramData\Microsoft\E-Business Servers Updates\Updates\Uninstall2799754.
[06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
[06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
[06/06/14 09:48:48] Package Workflow Manager 1.0 is installed.
[06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file TargetWFVersion.txt ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file UnifiedWFHotfixUpgrade.PS1 ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file Setup.xml ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file Setup.exe ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Package Workflow Manager 1.0 is installed.
[06/06/14 09:48:49] Package code is {04A7199E-565D-4654-88A3-80A9A7BADDD9}.
[06/06/14 09:48:49] Executing preinstall custom actions. 1 actions to execute.
[06/06/14 09:48:49] Starting process "C:\Windows\system32\..\sysnative\windowspowershell\v1.0\powershell.exe" -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File UnifiedWFHotfixUpgrade.PS1 -HotfixType "CS" -PackageType
"server" -opcode "PatchBefore" -platform "x64" ...
[06/06/14 09:48:50] Process exit code is -1.
get-itemproperty : Cannot find path 'HKLM:\Software\Microsoft\Service Bus\1.0'
because it does not exist.
At C:\ProgramData\Microsoft\E-Business Servers
Updates\Updates\Uninstall2799754\UnifiedWFHotfixUpgrade.PS1:971 char:21
+ $sbinstallpath = (get-itemproperty "HKLM:\Software\Microsoft\Service
Bus\1.0" ...
That's the log file
Best regards
Matthias

Office 2013 latest update broke new profile creation on all network computers

Hi,
Reporting a bug here!
Setup details:
We're using samba 3 as our backend and all workstation are Windows 7 Pro x64.
Office 2013 Home and Business Retail (en-us) Click 2 Run version
Context:
Deployed to the whole network of one of our client using the Office Deployement Tool.
We update their base update (no updates) to the latest update 15.0.4569.1508
Everything was working alright after initial Office 2013 installation with no updates. After updating the all the PCs to the latest version as of 31/03/2014, the user profile creation broke for newly created user.
Symptoms and causes:
Trying to log on as a new user on the machine would give the following error on Logon before automatically loging off because it cannot copy the following file to the new user profile:
D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_00.sqm
D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm
D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_02.sqm
The Bici folder has Read and Execute permissions for everyone but the _XX.sqm files inside only have permissions (Full Control) for SYSTEM and Administrators and LOCAL SERVICE with the all permissions EXCEPT:
- FULL CONTROL
- TRAVERSE FOLDERS/EXECUTE FILES
- CHANGE PERMISSIONS
- TAKE OWNERSHIP
Solution:
I gave "everyone" Read and Execute permission on those files and the new user could log in and his profile got created alright.
The files with broken permissions time stamp shows they've been modified during the Office 2013 update and Bici seems to be a OneDrive related service. This bug should get fixed ASAP.
Event log error:
Windows cannot copy file \\?\D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm to location \\?\D:\Users\TEMP\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm. This error may be caused by network problems or insufficient security rights.
DETAIL - Access is denied.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-User Profiles General" Guid="{DB00DFB6-29F9-4A9C-9B3B-1F4F9E7D9770}" />
<EventID>1509</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-04T07:15:51.922563800Z" />
<EventRecordID>9615</EventRecordID>
<Correlation />
<Execution ProcessID="940" ThreadID="1764" />
<Channel>Application</Channel>
<Computer>F00241D1DAAAD</Computer>
<Security UserID="S-1-5-21-1582357797-4105456612-768596941-1206" />
</System>
- <EventData Name="EVENT_COPYERROR">
<Data Name="Source">\\?\D:\Users\Default\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm</Data>
<Data Name="Target">\\?\D:\Users\TEMP\AppData\Local\Microsoft\Windows Live\Bici\_01.sqm</Data>
<Data Name="Error">Access is denied.</Data>
</EventData>
</Event>

Hi dude,
I appreciate that your sharing your experience and solution here. And, I would report it through our internal channel. Thanks again.
Tony Chen
TechNet Community Support

Office 2013: where the heck are the security updates hiding?

I built a deployment for Office 2013 yesterday. The source files were downloaded from Microsoft, with SP1 integrated. This is *not* a "Click to Run" deployment. I used the Office Customization Tool to make a few changes (we're
not using OneDrive, so that piece isn't getting installed. I disabled the "First Run" and Customer Experience stuff, and disabled RSS Feeds and SharePoint integration. And I put in our volume license key. Overall it's a pretty vanilla
build.)
I wanted to include all available security updates since SP1 has been released, and stick them into the "Updates" folder of my deployment. So after I installed Office 2013 x64 on my Windows 7 x64 system (the base package that I built installs
just fine), I went to Windows Update to see what was available. There is nothing there. I rebooted, and tried again. Still nothing. If I go into one of the Office 2013 apps, and go to File -> Account, I do *not* have any "Update"
buttons or options.
If I go to Windows Update in my Control Panel, and click "Change Settings", I have two things checked. "Give me recommended updates the same way I receive important updates", and "Allow all users to install updates on this
computer." There are no other options to look for alternative Microsoft products, or at least no options that I can find. This is Windows 7 x64 SP1, fully patched.
I know that there have been security updates released for Office 2013 since SP1 came out in February 2014. I manually downloaded a security patch for Lync 2013, and installed that MSP onto this test system with no
issues. So there are applicable security updates out there. So why in the world can't I find the updates through the normal mechanisms? Ideally, we'd want for end users to be able to install security updates manually in an
emergency, but either I'm missing something, or that is not possible in Office 2013. Hopefully distributing Office 2013 updates through SCCM will work, but from what I'm seeing so far, I'm not sure the machines will be "detected" as having
Office 2013, because right now it can't even scan itself against Windows Update for that product.
Thanks for any input...I'm quite baffled at how the update routine is supposed to be functioning in Office 2013. I think the missing link is why I can't choose to search for "other" Microsoft products from the Windows Update panel.
The option/checkbox is totally gone.

Hi,
By default Windows Update only updates Windows itself. To get updates for Office and for any other Microsoft products as well, you will need to upgrade your Windows Update to Microsoft Update.
On Windows Update panel, click "Find out more" link to install Microsoft Update.
Hope this helps.
Thanks,
Ethan Hua CHN
TechNet Community Support

Office 2013 search folder not showing any updates?

Hi,
I am trying to create a search folder for Office 2013 updates but nothing is populating within the folder.
I have ticked the "Search all folders" box too and still nothing? any ideas at all? All of the other search folders are working...
Bulleting ID = MS
Product = Office 2013
Superceded = No
Expired = No
Any help would be appreciated, thanks.
Niall
Niall Carter

Hi,If you remove the Bulletin ID, does it work then? the search above searches for a buletin called "MS" and there are none.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Office 2013 Rollout - Collect missing updates

I have dialed in my custom installer for Office 2013. What's the easiest way to gather all missing Office 2013 updates post-SP1 so I can drop them in the update folder?

@DonPick
I'm still making a final decision on whether or not to include all the patches at install time. If I wait for the Software Updates to come through then the user's first experience will not include everything. I'm concerned they may discover issues that are
directly related to the patch content, giving the user a false sense that IT doesn't know what they're doing =)
On a Windows 7 VM (1 CPU / 2 GB Memory) a complete uninstall of Office 2010 and install of Office 2013 32-Bit w/ SP1 took ~11 minutes to complete. This includes all the follow-up patches through May 2014. Of course my install package grew from ~850 MB to
~2 GB. Another issue I'm going to have to face....

I have a problem when installing Office 2013

Dear Microsoft support team!
I have a problem when installing Office 2013 as follows:
"A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. when setup microsoft office 2013"
I don't know why it is so. Pls help me!
Thanks and best regards!

Have your tried to perform the common troubleshooting steps for installing Office 2013 as the following article?
http://support.microsoft.com/kb/2822317/en-us
If not, please try it first. Feel free to post back. Thanks.
Tony Chen
TechNet Community Support

Office 2013, click icon nothing happens, no errors, no eventlog, MANY clients with this issue

We're an IT solutions provider for companies of all sizes as well, as residential users, and we've been plagued by a new Microsoft-caused issue that's seriously affecting our client's perception of us since it seems like 'you didn't fix it the first
time' or 'you sold us the computer', so it's our responsibility to fix for free.
We've experienced this with 17 people so far, ranging from residential clients with systems that have come from big box stores and from systems we've sold with Microsoft Office 2013 and basically the entire suite stops working.
If you click an icon, you may see an hour glass for a few seconds and nothing happens (but usually nothing happens at all, as though you didn't click it).
Diagnostic steps:
No errors in eventlog, neither under system or application.
No third party add-ins, sometimes it's a stock install on a new / fresh system.
Starting Microsoft Office applications in safe mode, like winword /safe, has no effect.
A quick repair or an online repair will not resolve the issue, it will say it's done but issue still exists.
Microsoft Office 2013 cannot be uninstalled, we always receive the same error code: 0-4
Some systems do not have third party antivirus, some are simply using Microsoft Security Essentials.
This affects all Microsoft Office applications, including Outlook.
Makes no difference if you use another user account or run-as admin.
All Microsoft Office 2013 updates have been installed.
The installation source is undetermined but recent issues stemmed from a physical media (.ISO) install from Microsoft's latest source.
You cannot start the software by clicking on documents created with Office applications.
The only way to remove Microsoft Office 2013 is with the removal tool "O15CTRRemove.diagcab".
The problem returns after a random period of days and no client can relay the actual cause of the issue, it seems random in nature. After the issue is experienced, we go through the same steps including the necessity to utilize the removal tool.
This seems to be a new issue that's come out of the blue within the past few weeks, at least on our end. When 17 random people call out of the blue with the same problem, it suggests it's Windows Update related.
I'm really hoping someone has some insight into this Microsoft glitch and knows of a secret hotfix or special trick to prevent it. I attempted to call Microsoft and it would be more enjoyable to punch a concrete wall since you're dealing with useless people
in a foreign country who can't really comprehend the seriousness or technicality of the issue, and don't really care, and aren't skilled enough to provide
insight.
Does anyone know about this problem?

Thank you for the reply.
I understand the flash you are receiving while launching Excel or Word is very fast. However just wanted to check if it is possible to get a screenshot of it.
Also, are you able to work fine on Excel or Word even after receiving the flash.
It seems the Office installation might have not been done properly.
There is a possibility, everytime you Uninstall any application, there are still some patches left behind which could cause an issue while Installing the same application again or even after Installation is successful, it sometimes gives
issue while launching the application.
If you want to give a try, you may try to Uninstall the product using Offscrub by clicking on the below link & then can have a fresh installation again.
http://support.microsoft.com/kb/2739501
Please let me know the status update once done
Abhijeet, the box flash happens too fast for me to capture a screenshot of it but I believe it's similar to the smaller box activation process (enter your email).
Word and Excel work fine whenever this is observed.
I'm skeptical that this is a "not done properly" kind of scenario, especially when it applies to so many people and many have brand new computers. How can you take a Microsoft Office disc and install it improperly on a new PC? Or how can a person
go through Microsoft's https://officesetup.getmicrosoftkey.com/ setup, use the software for months and suddenly it stops working? If this is a 'not done properly' scenario, then this is a failing of Microsoft's
installation source. I can't reiterate this enough, the software works fine for people since installation date and then randomly stops working at a much later date (but many of them failed last month and this is a newer issue).
I'm starting to get frustrated again as I'd already stated we've used your linked removal tool in my first post and the problem has returned for another user by which I'd used it and reinstalled the product. The client who's PC we have now, one we'd sold
them, needs to be returned to them and while Microsoft Office is currently working, I was told that if this happens again, they're "going to throw the f#(*@ computer in the river". No joke.
If we're at the point where we've moved past evaluating logs, registry keys, or file versions or anything along the lines of a developer determining how this Microsoft bug occurs, then I'll return the system back to the client and hope for the best.
Three strikes and I'm out with this one but perhaps the delayed startup is the final solution... I just wish I knew for sure as we've had a bad year taking a beating for Microsoft's products and their support is the worst in the industry.
It's further frustrating that since I'd touched base with Microsoft via phone calls, the only person who's been able to provide any insight into the issue is me.

CTR programs (Office 2013) and WSUS

I want to take issue with Microsoft on this inability to update Office 2013 using Windows Server Update Services. We purchase computers with Office 2013 pre-installed which features the click to run (CTR) version. While WSUS can download office 2013 updates
they don't get installed to the client machines. Only way for these systems to stay updated is to allow the update function in the office program.
Whoever designed this feature and ok'd it should be fired. What is an organization supposed to do when they have hundreds or even thousands of computers tying up all the network bandwidth downloading office 2013 updates? I can't believe the designers never
considered this to be a problem in the office environment. I expect to see this SEVERE problem corrected in a future patch.
There's big money for Microsoft to be made with their Office software suite. It is I.T. administrators like myself that influence purchasing decisions. If this problem is not changed, I along with many other administrators will be making every effort to
use alternatives in the future.

I want to take issue with Microsoft on this inability to update Office 2013 using Windows Server Update Services. We purchase computers with Office 2013 pre-installed which features the click to run (CTR) version.
And the Click-To-Run version is a cloud-based Software-As-A-Service and is updated by the service provider, not the end user.
Only way for these systems to stay updated is to allow the update function in the office program.
Exactly! That is the inherent design of Software-As-A-Service.
What is an organization supposed to do when they have hundreds or even thousands of computers tying up all the network bandwidth downloading office 2013 updates?
You assume that the computer are actually downloading updates.
I expect to see this SEVERE problem corrected in a future patch.
There's big money for Microsoft to be made with their Office software suite. It is I.T. administrators like myself that influence purchasing decisions. If this problem is not changed, I along with many other administrators will be making every effort to
use alternatives in the future.
Sigh.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile:
http://mvp.support.microsoft.com/profile/Lawrence.Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Reboot before sysprep when I want to add an installation task with Office 2013

Hi all,
I want to buid a reference computer with a genuine Win7 wim file, correct drivers, uptodate patches, and usefull applications. So I use a “Build and Capture Task Sequence”. The new reference image captured, I can use it with WDS or a media
to any computers, using a second and different “Build and Capture Task Sequence.”
All things were right, I could add Acrobat Reader, Java and some others application, but it failed when I tried to add “Add Application Task” with Office 2013. I could import the software, I discovered the new panel to configure config.xml
and mychoice.msp, but when I run the Tasq sequence, when it begin to sysprep the OS, a few time before the capture, the computer reboots. Sysprep does not run, and the image is not captured.
I can add any software installation in the Tasq sequence but not one with Office 2013.
What do you think about this issue?

Hi,
Some pieces of advice, since I have managed to create a Windows 7 WIM file with Office 2013 embedded without any problems:
Build your reference image in a virtual machine, not on physical hardware, to prevent a gigantic driverstore with drivers for one or more models, and having to rebuild your image every single time you use a new model. This is not how MDT works, MDT works
hardware agnostic, since it inject's drivers of hardware for each model before the WIM file is applied to your target computer.
Do you really want to embed applications like Adobe Reader and Java in the image? They have a release every month. Do you want to (or is there room for) updating your image every single month? Put them in the deployment phase of your task sequence. This
way these applications are left out the WIM file, but are installed after the WIM file is applied to your system. Yes this takes a little bit more time when deploying a machine, but that's time you'll save on not managing your WIM file every single month
Check your
log files, make sure your machine is not Domain Joined, since that is the biggest mistake people make when sysprepping a machine. And check
Setuperr.log for any sysprep errors. Guaranteed it has noting to do with Office 2013
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Office 2013 deployment customisation

Hello,
just added O2013 to applications. Used OCT, placed msp to Updates. Run litetouch from test VM.
Installation run silently. 100% success.
Here are the points that I would like to adjust:
1. When first started Word. I got the Windows with update chooses.
The truth that I don't deploy Office updates by WSUS. But probably will do.
After OS deployment WSUS update is enabled. So no problems with OS.
Let's assume that my WSUS will deploy Office 2013 updates. So I can probably enable post Application updates.
Currently I do post OS updates.
Is there a step in OCP to skip the Updates screen on first Office start?
Can activation window be suppressed if product key is inserted in OCT? Kind of automatic activation try?
This is not difficult one click but would like to leave Office without any "welcome" screens.
Please specify the step in OCT where I can to customize that.
Also my Office 2013 contains SP1. So probably I can keep Office 2013 patches on WSUS starting January 2014 since SP1 dated
Feb 2014. Is it right assumption?
Thanks.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Please follow the instructions here. Open OCT. Navigate to Features-Modify User Settings.
Select Microsoft Office 2013-->Privacy--> Trust Center
Disable Opt-in Wizard on first run-> Set to ENABLED
Enable Customer Experience Improvement Program--> set to DISABLED
Automatically receive small updates to improve reliability--> DISABLED
Then under Microsoft Office 2013--> Miscellaneous
Suppress recommended settings dialog--> set to ENABLED
Activation depends on if your using KMS or MAK keys. What are you using so I can assist you further...

Office 2013 update KB 2726958 Problem

Similar Messages

Maybe you are looking for