Close Menu
    Trending

    How-to: Deploying Microsoft Office 2013 using SCCM 2012

    61
    By on Uncategorized

    This Step-by-step guide describes how to prepare and add Microsoft Office 2013 Professional Plus to the Application library of System Center 2012 Configuration Manager (SCCM), by using the designated functions for doing this in the Configuration Manager Console interface.

    Download the complete guide here in PDF format or read the the guide here. If I later decide to update this guide, I’ll only update the document. Not this blog post.

    Prepare Office 2013 for deployment

    Overview

    This procedure describes how to prepare Microsoft Office Professional Plus 2013 to be installed unattended. The aim of this procedure is to create and prepare the installation source folder, for use with System Center 2012 Configuration Manager.

    This procedure does not cover:

    • Download the Volume License Edition of Microsoft Office 2013 installation files.

    Pre-requirements

    In order for the operator to perform the steps describes below, the following requirements must be in place:

    • The operator must have access to the volume license edition of Microsoft Office Professional Plus 2013.

    Process Steps

    1. Copy all content from the Microsoft Office 2013 DVD to a source share like: \\SCCM01\Source$\Applications\Microsoft Office Professional Plus 2013 ENU\DT-MSI_x86\
    (We need to create a subfolder for each deployment type).

    2. Start the Office Customization Tool (OCT), by running Setup.exe /admin, from the source folder. (The OCT is available only with the volume license editions of Office).

    clip_image001[4]

    3. If required click OK to the User Account Control (UAC) prompt.

    4. Verify that the correct product and version is selected, and click OK.

    clip_image002[4]

    5. In the Default File Types, pop-up, select the format you wish to use. The default is “Keep Current Settings”. In this example, I’ll select Office Open XML formats, and then click OK.

    clip_image003[4]

    6. In the Microsoft Office Customization Tool wizard, you can customize almost all available settings, but in this example, I’ll only configure a few of these settings, to make the installation unattended, and to provide a simple user experience to users, when they install Office 2013 from the System Center 2012 Application Catalog.

    7. Select Install location and organization name, and fill-in your company name.

    clip_image004[4]

    8. Select Licensing and user interface, and select “I accept the terms in the License Agreement”. In the Display level, select Basic, and select both Suppress modal, and No cancel.

    Note: If you do not plan to use KMS or Active Directory-Based activation, you should also specify the MAK product key on this page.

    clip_image006[4]

    9. Select Modify Setup properties, and click Add…

    10. In the Add/Modify Property Value dialog box add the following information, and click OK:

    Name: SETUP_REBOOT

    Value: Never

    clip_image007[4]

    clip_image008[4]

    11. To disable the Office 2013 Welcome screen, select Modify user settings, expand Microsoft Office 2013, Privacy and Trust Center. Select Disable Opt-In Wizard on first, and double click on the setting and select Enable.

    clip_image010[4]

    12. That’s it… Click File and then Save, and then save the MSP file in the Updates folder in the source folder.

    clip_image011[4]

    13. The source folder is now prepared for unattended installation, and if you run setup.exe, from the source folder, the installation should be 100% silent.

    Create/import the Application for Office 2013

    Overview

    This chapter describes how to create an application in System Center 2012 Configuration Manager.

    Pre-requirements

    In order for the operator to perform the steps describes below, the following requirements must be in place:

    • The operator must have access to a system running the Configuration Manager Administration Console
    • The operator must be logged in with a user account with permissions to create and deploy applications.

    Process Steps

    1. In the Configuration Manager Console, navigate to Software Library / Overview / Application Management / Applications.

    clip_image012[4]

    2. In the ribbon menu, click Create Application.

    clip_image013[4]

    3. In the Create Application Wizard, verify that automatically detect information is selected and that the Type is Windows Installer (*.msi file), and click Browse…

    clip_image015[4]

    4. Navigate to the source folder (by using the UNC share path). \\SCCM01\Source$\Applications\Microsoft Office Professional Plus 2013 ENU\DT-MSI_x86\ProPlus.WW\, and select the ProPlusWW.msi file, and click Open.
    Note: Microsoft Office Professional Plus 2013, should not be deployed as a native MSI file, but by selecting the MSI file when we create the application, things like deployemt type and detection methods are created automatically.

    clip_image016[4]

    5. On the General page of the Create Application Wizard page, click Next.

    6. Verify that the imported information is correct, and that the import was successful, and click Next.

    7. On the General Information page, verify that the Name is displayed like you would prefer to see it in the Console. Fill-in the Manufacturer (Microsoft), and the Software version (2013).

    clip_image018[4]

    8. In the installation program, delete the default value (msiexec.exe /i “ProPlusWW.msi” /q), and type Setup.exe.

    clip_image019[4]

    9. Verify that Install behavior is configured to Install for System, and click Next.

    10. On the Summary Page, click Next.

    11. On the Completion page, verify that the application was imported successful, and click Close.

    12. In the Configuration Manager console, select Microsoft Office Professional Plus 2013.

    clip_image021[4]

    13. Select the Deployment Types tab.

    clip_image022[4]

    14. Right-click the deployment type Microsoft Office Professional Plus 2013 – Windows Installer (*.msi file), and select Properties.

    clip_image023[4]

    15. Select the Content tab, and change the content location to \\SCCM01\Source$\Applications\Microsoft Office Professional Plus 2013 ENU\DT-MSI_x86\, by removing the “\proplusww” in the end of the pre-configured location.

    clip_image025[4]

    16. Select the Programs tab and change the Uninstall program command to Setup.exe /uninstall.

    clip_image026[4]

    17. Select the Detection Method tab, and verify that a detection method for the MSI Product Code had been created.

    clip_image027[4]

    18. Select the Requirements tab, and click Add…

    Note: You can create lots of requirement rules, but in this example, I’ll provide three common examples on requirement rules, you can use to target the right deployment type for the right system.

    19. Create a Requirement rule with the following settings, and click OK.

    a. Category = Device

    b. Condition = Total physical memory

    c. Rule Type = Value

    d. Operator = Greater than or equal to

    e. Vaule (MB)= 2048

    clip_image028[4]

    20. Click Add..

    21. Create a Requirement rule with the following settings, and click OK.

    a. Category = Device

    b. Condition = Disk Space

    c. Rule Type = Value

    d. Select local logical drive = System drive

    e. Operator = Greater than or equal to

    f. Vaule (MB)= 2000

    clip_image029[4]

    22. Click Add…

    23. Create a Requirement rule with the following settings, and click OK.

    a. Category = Device

    b. Condition = Operating System

    c. Rule Type = Value

    d. Operator = One of

    Windows 7

    Windows 8

    clip_image030[4]

    24. Click OK.

    clip_image031[4]

    Deploy Microsoft Office 2013

    Overview

    This chapter describes how to deploy Microsoft Office Professional Plus 2013 using System Center 2012 Configuration Manager.

    Pre-requirements

    In order for the operator to perform the steps describes below, the following requirements must be in place:

    • The operator must have access to a system running the Configuration Manager Administration Console
    • The operator must be logged in with a user account with permissions to create and deploy applications.

    Process Steps

    1. In the Configuration Manager Console, navigate to Software Library / Overview / Application Management / Applications.

    2. Select Microsoft Office 2013 Professional Plus 2013.

    clip_image032[4]

    3. In the ribbon, Select the Home tab, and click Deploy.

    clip_image034[4]

    4. On the General Page, click Browse… to select the target collection.

    clip_image035[6]

    5. Select All Users, and click OK.

    clip_image036[6]

    6. Click Next.

    7. On the Content tab, click Add and then Distribution Point.

    clip_image038[6]

    8. Select the Distribution Point, and click OK.

    clip_image039[6]

    9. Click Next.

    10. Complete the wizard, by Next 6 times and then Close.

    End User Experience

    Overview

    This chapter describes the end user experience when deploying Microsoft Office Professional Plus 2013 using System Center 2012 Configuration Manager.

    Pre-requirements

    In order for the operator to perform the steps describes below, the following requirements must be in place:

    • The operator must have access to a Windows 7 or Windows 8 client system with the System Center 2012 Configuration Manager Client Agent installed.
    • The Windows Client must be joined to the same Active Directory forest as the Configuration Manager Site Server
    • The operator must be logged in with a domain user account that is a member of the All Users Collection in System Center 2012 Configuration Manager

    Process Steps

    1. Login to the Windows client, and start Internet Explorer.

    Note: If you are using a Windows 8 client, you should start Internet Explorer from the Desktop. Not from the Modern UI Interface.

    2. Open http://sccm01/CMApplicationCatalog.

    3. Select Microsoft Office Professional Plus 2013, and click Install.

    clip_image041[6]

    4. On the Application Installation pop-up notification click YES.

    clip_image042[6]

    5. Verify that the application installation has started, and wait for the Installation to complete.

    clip_image044[6]

    6. When the software installation is completed, click OK.

    clip_image045[6]

    7. Start Microsoft Word, to verify that Microsoft Office has been installed successfully, and that the settings configured in the Office Customization Wizard, had been applied successfully.

    The latest version of this document can be downloaded here:
    https://www.ronnipedersen.com/configmgr-2012-guides/

    /Enjoy

    +Ronni Pedersen

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    61 Comments

    1. Mohammed on

      2 question 🙂

      1) i have Microsoft office 2007 already installed before, but after installing office 2013 the software center requires me to reboot the system, can i prevent this message (i mean i want to deploy the office but run at time after installing no need to restart).

      2) can you guide me to the best practice for software deployments for clients, for example is it better to make it silently 100 & required or available, should it be non silent… etc.
      i know it depends on the organization and the requested software’s but there is a general principles for the best practice where you force the clients to follow your roles.

      & thank you very much

      Reply
      • Ronni Pedersen on

        Hi Mohammed,
        1. If you add the SETUP_REBOOT=Never to the custom properties (view the first part of the article), you should be just fine.
        2. As you state it really depends on the organization and the requirements, but my experience is that when customers start to use the Application Catalog, they find that users can help them themself alot more if we give them the change, by making applications available to them.
        And the best part is, that we (the Guys in IT) don’t have to spend valuable time adding users or computers to Collections every time someone needs an app.

        Reply
        • Moahmmed on

          Ronni

          i need a help in this issue, i feel it is easy but for some reason i tried to solve it but no succeed

          i created Application (available not required) for Adobe Pro (the latest version) (with uninstall choice) and i assigned it to a user, the APP showed in the application catalog (and it is working fine installing and running), but also it showed in software center (list).

          the issue:
          i removed the application beginning by deleting deployment( that assigned to the user) then deleting the deployment type then deleting the application (it self) from SCCM (right click & Delete).

          it disappeared from the Application Catalog (that’s good), but it did not disappear from the software center list.

          i tried to find away to do it but no succeed, all the websites talks about uninstalling the application (but i already configured it ), but my issue is that i removed the application (delete it totally) and still stuck in the software center
          is there a way to remove it totally from software center list.

          thank you & regards

          Reply
    2. Ronni Pedersen on

      Hi Moahmmed,

      I think this is by design that the application will remain in the software center as long as the application is installed on the client. The reason is that the user can use the software center to uninstall the application again if it’s no longer required.

      Are you using SCCM 2012 RTM or SP1 ?

      Reply
    3. Moahmmed on

      i think i am using SCCM 2012 RTM and soon the release of SP1 i will install it, but for CAS it is SP1

      it have gone, but it took too long to go from software center.
      it goes in the next day, and each time i create Application and install and remove,it will be removed totally form software ceneter in the next day.

      it is noisy because each time you make a test you should use many names for the file or you wait for next day for to be removed and retest again.

      Reply
    4. Moahmmed on

      i have posted but unsure, any way i am using as i think SCCM 2012 RTM

      it have gone but in the next day, and continues like that…!

      Reply
    6. Ian Burnell on

      Hi Ronni – great document. Thanks for taking the time to share it

      Couple of question around Office 2013

      1. You place the MSP into the Updates folder. I’ve always put it into the root folder and then called setup.exe /adminfile xxx. I tried putting the .MSP into the x86 folder with the above command but it failed
      2. Do MS now recommend using the X64 subfolder for 64 and same for X86 – previously it was recommended to use the 32-bit flavour even on 64 bit?. Again how does this fit in with the MSP on the root folder i.e. is the msp independent of the O/S type or do you have to have a separate one in each sub-folder?

      Reply
    7. Rob on

      Hi,

      On the client I get the following error:
      Software Center: the software change returned error code 0x87d00607 (-2016410105)
      Eventviewer: application failed to download content with error code of -2016410105

      the software is located on a server/share that is not the SCCM server.

      regards,
      Rob

      Reply
    8. Sascha on

      Hi Rob

      du you got a Resolution of this Problem? i have the same error message.

      many thanks for your feedback

      Reply
    9. Brian Hampson on

      Nice clear and concise article with good pictures!

      I know this post is old now, and it’s possible you may not see this, but…. I have a question.. what if I want to do to different installs with different customizations? Do I need to copy the entire source tree and drop in a new MSP? Seems a bit painful.

      Reply
    10. Jesper on

      Hey Ronnie, Great Article
      my questions are on the end user side, when they got the program installed (in my case lync 2013) they get asked if they want to use recommended settings or not, in regards to updates, and they get prompted to activate the program by phone or internet.
      I added the Product key with the OCT, is there a way to make the programs automatically be activated and not prompt for the recommended settings?

      Reply

    11. Pingback: Deploying Office 2013 with SCCM 2012 SP1 CU2 | Rhidian's IT space

    12. MARCELO FORNAZARI on

      Hello Ronni, okay?

      Excellent article and quality. Really good. I would like to ask you whether it is possible automatizarmos this facility so that the user does not interact any longer and get automatically installed on his machine? What options should I check?

      Thanks and a hug,
      Marcelo

      Reply
      • Ronni Pedersen on

        Hi Marcelo,

        Just deploy the application as required to the user (or device) and it should be installed automaticlly.

        Reply
    13. Carrie Waite on

      Is anyone else having issues with upgrading from Office 2010? My MSP is set to remove all old office applications but it is not properly uninstalling Outlook 2010. I’ve tried having SCCM run a bat that taskkills all office apps before running setup.exe, but 90% of our upgrade deployments have experienced this. did not have this problem going from 2007 to 2010.

      Reply
      • jason on

        Carrie,
        I had these problems as well. After testing with this script the install works much better.

        taskkill.exe /f /im winword.exe
        taskkill.exe /f /im excel.exe
        taskkill.exe /f /im msaccess.exe
        taskkill.exe /f /im outlook.exe
        taskkill.exe /f /im officelivesignin.exe
        taskkill.exe /f /im infopath.exe
        taskkill.exe /f /im onenote.exe
        taskkill.exe /f /im onenotem.exe
        taskkill.exe /f /im powerpnt.exe
        taskkill.exe /f /im mspub.exe
        taskkill.exe /f /im mspscan.exe
        taskkill.exe /f /im mspview.exe
        taskkill.exe /f /im ois.exe
        Taskkill.exe /IM osaui.exe /F
        taskkill.exe /f /im communicator.exe /t
        taskkill.exe /f /im ucmapi.exe /t

        Wmic product where “name like ‘%%Microsoft%%Lync%%2010%%'” call uninstall /nointeractive
        msiexec /qn /x {90120000-0020-0409-0000-0000000FF1CE}

        Jason Oliphant

        Reply
    14. Gary on

      Ronni,
      Thanks for the great common sense article.
      Can you tell me how to tell SCCM to run from DP instead of downloading this huge content to each machine in corp.?
      I know of the setting for slow networks to run from DP but what if I want it to run from DP to ALL machines regardless of network speed?
      Thnks in Advance. If I posted twice sorry.

      Reply

    15. Pingback: Deploying Office 2013 Using SCCM 2012 | System Center Stuff

    16. Mercy on

      Hi Ronni!
      Fine instruction for Office 2013 deploy. I have one question.
      We deployed Office 2013 without MS-Access. Some of our colleague needs MS-Access. What is the best way to deploy only Access on an existing Office2013?
      Thank you for your Info!
      BR Mercy

      Reply
      • Ronni Pedersen on

        You need to make a custom XML file that will add access to the existing installation.
        You also need to add a check for access to your detection method

        Reply
    17. Jason Hall on

      Just came across this article while looking into setting up Office 2013 as an application rather than a package.
      Have you tried leaving the detected uninstall program (msiexec /x blah /q)? As that matches the uninstall string in the registry (minus the /q), so presume it should work…

      Also, does the ‘technology’ being set to Windows Installer when using this method cause any problems?

      Cheers
      Jay

      Reply
      • Ronni Pedersen on

        No I dont use the msi as the uninstall command, and I don’t think it’s supported. But you can test if you like.
        The main reason for me to use the Windows Installer deployment type insted of the script deployment type, is to make the wizard simpler, and it will create detection methods for you.
        Anthoner thing is that MSI deployment types at default supported by the MDT UDI wizard for detection.

        Reply
    18. Andrew on

      Great guide worked like a charm.

      I had no idea you could just type things like setup.exe into the Installation Program, as it only lets you search for MSIs… this is awesome.

      Reply

    19. Pingback: Microsoft Outlook 2007: Disable the prompt for RSS feeds » RONNIPEDERSEN.COM

    20. Dana on

      Great article, thank you very much for creating it. It worked first time out with no problems at all. I used your article to setup a deployment of Office 2013 32 bit. However if I try to deploy to a computer that has a 64 bit version of Office on it then it fail. Any suggestions as to how to handle this?

      Thanks again. All and any comments are greatly appreciated.
      D

      Reply
      • Ronni Pedersen on

        I have not tested that specific scenario.
        But I would suggest that you create a new application for the 64-bit version of office, and then use the uninstall deployment before installing the 32-bit version (I dont think they can co-exist og the same machine).

        Reply
        • Dana on

          Hi Ronni;

          Thanks for your reply, I’m pretty sure they can’t co-exist either nor do I want them to. However I’ve yet to figure out a way to get the old Office uninstalled and then install the new office.

          I’ve tried a Task Sequence that has a command line to uninstall the Office and then an application install but this keeps failing. The command line I’m using works from a command prompt.

          Thanks again

          Reply
    21. Jason Hall on

      How would we go about installing just Lync2013 on a computer which is running Office2010?
      Then later how would we update Office2010 to Office2013? From memory you can’t re-run the “setup.exe /adminfile ***.msp” to modify an already installed instance of Office.

      Cheers

      Reply
    22. Ian Burnell on

      How do you deal with multiple .MSP files for different features of Office. You can create different deployment types in SCCM but how can you force it to the one you want – particularly during OSD build?. With a package/program you could “hard-code” to select the MSP file you want but not sure how an Application/deployment type can cope??

      Reply
      • Andrew on

        Deployment types are really meant to be used for things like managing different operating systems or other basic hardware/software based configurations. You can’t just pick a specific deployment type when deploying an application like you do a package. (kinda really annoying sometimes I must admit, but it has other benefits)

        So I would create separate applications for the individual .msp file’s you want to use for maximum flexibility in OSD. In situations like this I create a folder that contains all of these separate applications that relate to one common sort of ‘package’ just for administrative ease.

        Reply
    23. Jasper McLarrin on

      Hey, Ronnie!! Great article!!

      Just one issue.. It’s not completely deleting everything for Office 2010 Pro Plus. Any ideas on how to get it to delete everything? We have an install for 2010 through SCCM as well.. Here’s is the uninstall string: setup /uninstall ProPlus /config proplus.wwsilentuninstallconfig.xml

      Any ideas how to incorporate that in?

      Reply
    24. Chris G. on

      I’d like to add something for the step below.. (not sure if it applies to everyone.)

      ***17. Select the Detection Method tab, and verify that a detection method for the MSI Product Code had been created.***

      The reason being, we had instances where we didn’t install Office 2013 via SCCM, instead we used a network share/media. For whatever reason the versions were different than what was on SCCM. What was happening was that SCCM was scanning the machines and uninstall the existing Office 2013 only to reinstall the version of Office 2013 that was in SCCM. Making the changes below yielded an “Already Compliant!” App state message and would not cause a reinstall to occur.

      Fix:
      Edit the detection clause and change the radial button to: “This MSI Product code must exist on the target machine and the following conditions must be met to indicate presence of this application:

      MSI Property: Version
      Operator: Greater than or equal to
      Value: (Depends on your environment.) We used 15.0

      Reply

    25. Pingback: Deploying Office 2013 SP1 and Office Proofing Tools 2013 SP1 with SCCM 2012 R2 | A random blog from a sysadmin

    26. TJ Robinson on

      I know I am doing something wrong just not sure what it is…The deployment is not installing for me and I am getting “Did not detect app deployment type Microsoft Office Professional Plus 2013” in AppDiscovery log file…I fell like I have followed the guide properly just not sure where I am going wrong. Can you think of anything I might be doing wrong?

      Thanks.

      Reply
    27. Sooraj on

      Hi Ronni

      Thanks for the wonderful article.

      I was trying to deploy office 2013×86 along with Arabic Language pack using config file. Status is showing installing in software center but it is not getting installed on the client machine. Any idea?

      I use the below command line.

      setup.exe /config config.xml

      below is my config file

      Reply
    28. Mujahid on

      When client start downloading got this Error:::The software change returned error code 0x80070005(-2147024891)

      Any one can help me out

      Reply
    29. Sudhakar on

      Hi Ronni,
      I am facing issue while deployment of Visio 2013(32-Bit) on Window 8(x64) Surface Pro thorugh SCCM 2012 Push Method.
      Pull method and manual Install working fine.

      It get hang at the below point

      2015/04/06 14:41:41:240::[9716] Using setup controller dll at [C:Windowsccmcache3dSourcex86visstd.wwOSETUP.DLL].
      2015/04/06 14:41:41:240::[9716] PERF: TickCount=25384234 Name=OBootStrapper::Run Description=Calling RunSetup

      Reply
    30. Emort on

      +hi
      Great guide!
      any plans to extend it with office proofing tools 2013 with specifics languages e.g danish, Norwegian, Swedish ?

      again Thanks for the guide.

      Reply
    31. Dana on

      Hi there;

      Could you do a guide on deploying Visio 2013 with SCCM 2012 R2. I’ve tried following this guide and substituting Visio in place of Office but it doesn’t work. I have the Volume License version of Visio 2013 SP1. I’ve created the msp file like you suggested.

      The deployment pushes the software to the computers but then it sits there waiting to install, if you go into the software center and tell it to install then it begins installing and never stops until it eventually times out. The deployment is set as required and to install whether a user is logged on or not. It’s also set to install for System.

      I’ve been over this guide a dozen times and can not figure out why this isn’t working. On a positive note, it worked perfectly for Office and MS Project Pro.

      Reply

    32. Pingback: Deploying Office 2016 and Office Proofing Tools Kit 2016 / Office 2016 language packs with SCCM 2012 R2 | A random blog from a sysadmin

    33. Chris on

      I am trying to follow your instructions here to set up a Office 2016 deployment.
      I get all the way thru and when I go do that actual install on the Client the Software Center states that is downloading at 0%. Sat there all weekend like that since I kicked it off before I left for the weekend. Any idea what may be causing it to act like this?

      Reply
    34. Tiger on

      hi, Ronni
      I have success deploy office 2016 by the SCCM2012R2 to client side, but I don’t want to automatic restart computer when office 2016 installation complete. I have read your office deployment guide and add SETUP_REBOOT with Never parameter to office OCT file, but client still restart automaticlly when install finished. Could you help me to solve this issue. thank you.

      Reply

    35. Pingback: Microsoft System Center Configuration Manager : MOREnet Blogs

    36. Tommy on

      Hi Ronnie,

      Whilst we prepare the site for a SCCM 1602/Win10 upgrade, I still have the arduous task of supporting the existing 2007 environment. I am trying to do an Office 2010 to 2013 SP1 upgrade using TS but it spits out a couple errors. It doesn’t look like the Service pack is applying if running from the task sequence with KB errors in the Event log. However when you open Outlook and check the version numbers, it shows the correct version. When running the program on its own through a normal advertisement, it installs fine with no errors. Does the TS handle the install in a different way to a single install?

      Task sequence execution failed with error code 80004005 TSManager 25/05/2016 16:16:09 9556 (0x2554)

      Windows Installer installed an update. Product Name: Microsoft Office Professional Plus 2013. Product Version: 15.0.4569.1506. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: Update for Microsoft Office 2013 (KB2826004) 32-Bit Edition. Installation success or error status: 1603.

      Product: Microsoft Office Professional Plus 2013 — Error 2902.An internal error has occurred. (ixfAssemblyCopy ) Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, seePSS10R.CHM.

      Is this something you may have seen before? I slipstreamed the SP into the install by extracting the contents and copying into the Updates folder.

      Thanking in advance.

      Reply

    37. Pingback: How To Deploy Office 2013 Using Sccm 2007 | Khmer Bank

    Leave A Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.