SCCM 2012 - Deploying Office 2013 Application - Setup Errors

dear SCCM admins,
i am trying to test deploying office 2013 to users in my company. i made the application and deployments. the application appeared in the software center and in the application catalog.
The problem is whenever a user "which is not a local administrator" tries to install this application, it gives me the setup errors message saying "You must have administrative privileges to install or uninstall this
product."
Is there any specific configuration to make to overcome this behavior???
appreciate your suggesstions
M.Zakaria

As you can see from the screenshot you need to add the ProductID after the uninstall command.
See here for finding the ProductID
http://blogmines.com/blog/2012/07/21/how-to-check-version-of-office-2013-products/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

  • SCCM 2012 R2 Office 2013 deploiement 64 bit and 32 bit versions

    We have some
    Windows 7 64bit os with office 2013 32 bit
    also
    Windows 7 32bit os with office 2013 32 bit
    We need to deploy office 2013 32 bit all over with sccm 2012 r2
    what's the best way for the deployment
    we also want to be sure to keep all user data for outlook. we don't want to loose that
    can I install a 32 bit office and in the setup /admin use uninstall and everything will work

    setup.exe /admin is the tool to use when customizing the deployment of Office; especially when deploying through SCCM.
    The way I saved user profile data is to set it to Use Existing Profile under Outlook Profile of setup /admin
    Yes, I have the default setup behavior box checked so it removes all previous Office version applications.

  • SCCM 2012 Deployment Packages and Applications deployment order

    Hello I have an application which deploys Office 2013 through SCCM 2012 I then want to copy some templates to two directories in Office. I have added a script the OFC tool which is suppose to run after the install. But the files don't appear. If I run the
    same script manually all the files are copied. I ended up creating a package just for the Office Template files, but I have to run this manually afterwards. Should I Persist with the script or is there a way to run the package automatically after the application
    deployed has run?

    Sounds like best solution is to create an MSI that can copy the template files and deploy as an application after Office Install. Is this something I can do in Install Shield?
    Seems weird that they would have an option in the MSP to run a script but it doesn't work.
    I wouldn't go to that trouble myself, but that's because I don't author MSIs as part of my role (we have a packaging team who do that task, and they seem to regard authoring an MSI as the solution for everything ;)
    the ConfigMgr AppModel happily caters for all kinds of payloads, despite referring to them as "applications" there is no requirement for the payload to be an MSI.
    MS have long documented that the "run scripts" and "chaining" features of the Office setup engine are "not robust" (i.e. not very tolerant, are a one-shot kind of thing). Some seem to work just fine, others have no joy with it. I don't use it myself, there
    are plenty of other methods, but I find it comes down to what you are comfortable/confident/familiar with. Everything has pros and cons, and above all else, I've found that it's my/our assumptions/understandings that tend to be why things go off-course.
    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!)

  • Deploying office 2013 Professional plus with SCCM

    Hello,
    I want to deploy office 2013 with SCCM 2012. I want to make an package but how can i
    download the office 2013 complete version ?<o:p></o:p>

    Hi,
    As far as I know, Microsoft now only provide MSI-based Office installer for Volume licensing Office. If you are a Volume Licensing customer, you can download the media via the Volume Licensing Service Center:
    http://www.microsoft.com/licensing/about-licensing/office.aspx
    More reference about how to deploy Microsoft Office 2013 using SCCM 2012:
    http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

  • Microsoft office 2013 encountered an error during setup in Window 8.1

    Initially, I got microsoft office 2013 64bit standard version installed in window 8.1. However, it suddenly got errors when opening office, and closed the program automatically. Therefore, I uninstalled it, and tried to re-install office.
    However, I got the error "microsoft office 2013 encountered an error during setup" everytime when I try to install it.
    I tried 32-bit and 64 bit version, and tried to install in clean boot, deleted registry, and modified the folder name "Microsoft Help", but none of them works. 

    Make sure you completely uninstall previous versions of Office. There may be remnants left behind, even after you uninstall Office using the normal procedure. I recommend using the “Fix It” utility to uninstall Office 2013 completely. Please refer to this
    article: http://support.microsoft.com/kb/2739501/en-us you might also follow the manual steps provided on the same page.
    If you still having problems, re-registering the Windows Installer and checking permissions on the %TEMP% folder and the C:\Windows\Installer folder to make sure you have full-control. To re-register the Windows Installer run the following commands:
    msiexec /unregister
    msiexec /register

  • Deploy Office 2013 - Uninstall Office 2010

    Hello,
    I am planing to deploy Office 2013 and created a MSP File (Setup /admin) for the silent Installation - everything works fine - except the uninstallation of Office 2010. In the OCT I´ve selected the Option to remove previous Versions of Office. I can
    remeber that this works perfect in Office 2010 to remove Office 2007 too.
    But in Office 2013 this doesn´t work anymore, the installed applications wizard (appwiz.cpl) Shows both Version of Office are installed. What is the best way to remove the old Version silently and install Office 2013? I would like to have all in one
    "Application" deployed via SCCM 2012 SP1. 

    Have you looked at this document, or it's online equivalents:
    http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
    In the section "Setup command-line options for Office 2013", they say:
    /uninstall [ProductID]
    Runs Setup to remove the specified product from the user’s
    computer. Look up the value of [ProductID] in the Setup.xml
    file for the product that you want to modify.
    Example
    \\server\share\Office15\setup.exe /uninstall ProPlus
    where:
    Office15 is the root of the network installation point.
    ProPlus is the
    [ProductID] ([ProductID]
    is equal to the ID attribute of the
    Setup element listed in
    \\server\share\Office15\ProPlus.WW\setup.xml), where
    ProPlus.WW is the location of the Office Professional Plus 2013 installation files.
    You can customize the
    /uninstall option by using it with
    /config and a modified Config.xml file. This is necessary if you want to run a
    “silent”
    uninstall. In enterprise deployments, we recommend that you run a silent uninstall to prevent prompting users to enter information, and to prevent the installation from waiting for user interactions, even when files are being used.
    To run a silent uninstall
    Using a text editor, edit the following element attributes in the
    \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml file:
    <Configuration Product="ProPlus">
    <Display Level="none"
    CompletionNotice="no" SuppressModal="yes"
    AcceptEula="yes" /> </Configuration>
    At the command line, use the following syntax:
    \\server\share\Office15\setup.exe /uninstall ProPlus /config \\server\share\Office15\ProPlus.WW\SilentUninstallConfig.xml
    Note:
    In Office 2013, just as in Office 2010 and Office 2007, you cannot use the Setup.exe command line to set Windows Installer properties, such as
    PIDKEY or DISPLAY. Setup does not pass these properties to Windows Installer. Instead, you make these customizations by using the Office Customization Tool or Config.xml. For a complete list of Setup properties, including blocked
    and unsupported properties, see Setup properties in Office 2010.
    The information also applies to Office 2013.
    Office Customization Tool (OCT) in Office 2013
    Config.xml file in Office 2013

  • Deploy Office 2013 with language pack

    Hi,
    We want to deploy Office 2013, for this I followed the tutorial:
    http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
    In the first step I need to make an MSP file, but this file doesn't get used in the deployment? I think this is a fault in the tutorial.
    Also the uninstall string is setuP.exe /uninstall. Is this correct?
    Second we want to deploy the dutch language pack with SCCM 2012, but I can't find out how. The package need to be installed but Office 2013 still need to be default language English.
    Can someone help me out with this?
    Thanks in advance.

    Some troubleshooting tips:
    Run the installation command locally using SYSTEM account (Get psexec.exe, open cmd, run "psexec.exe -s cmd", this will open a new command line window with SYSTEM privilege, try running your installation command there)
    Check the Office 2013 installation logfiles to see if your configurations are correct, more info on that here:
    http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx
    After those two steps are ready and you're sure your installation command works, you try it with ConfigMgr
    With ConfigMgr, check %windir%\ccm\logs\ -folder for AppEval.log, AppEnforce.log and AppDiscovery.log, more info on these logfiles you can find here:
    http://blogs.technet.com/b/configmgrdogs/archive/2012/05/26/new-logs-in-configmgr-2012-client-logs.aspx

  • Deploying Office 2013 with Group Policy

    I would like to deploy Office 2013 using group policy. I am new to group policy so am looking for some advice and guidance on the best way to deploy. I would like to deploy with no interaction with the user but yet display a message so that they
    know not to open Office. I would also like to create a custom registry setting so that if I need to re-install, all I have to do is delete the registry setting. I have tried a group policy for installing with OCT  settings (Basic, Suppress
    Model checked, No Cancel checked, Completion Notice checked) and modifying the Config.xml (<Display Level="Basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />) but I can not get it to display
    the installer screen so that users know it is installing. It does display the screen when running the setup.exe manually. I have a setting in the OCT that creates the registry setting and that is working correctly. My group policy is set to run the
    below bat file at startup in the Computer Configuration.
    setlocal
    REM *********************************************************************
    REM Environment customization begins here. Modify variables below.
    REM *********************************************************************
    REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
    set ProductName=Office15.Standard
    REM Set DeployServer to a network-accessible location containing the Office source files.
    set DeployServer="\\xxxxxx\setup.exe"
    REM Set LogLocation to a central directory to collect log files.
    set LogLocation=\\xxxxx\Logfiles
    REM *********************************************************************
    REM Deployment code begins here. Do not modify anything below this line.
    REM *********************************************************************
    IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
    REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
    :ARP64
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
    if NOT %errorlevel%==1 (goto End)
    REM Check for 32 and 64 bit versions of Office 2013 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
    :ARP86
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
    if %errorlevel%==1 (goto Office) else (goto End)
    REM If 1 returned, the product was not found. Run setup here.
    :Office
    %DeployServer%
    echo %date% %time% Setup ended with error code %errorlevel%. &gt;&gt; %LogLocation%\%computername%.txt
    REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
    :End
    Endlocal
    Any advice or guidance would be greatly appreciate on how to get a pop up message while software is installing or if there is a better way to deploy.

    > but I can not get it to display the installer screen so that users know
    > it is installing. It does display the screen when running the setup.exe
    > manually. I have a setting in the OCT that creates the registry setting
    > and that is working correctly. My group policy is set to run the
    > below bat file at startup in the Computer Configuration.
    Check http://gpsearch.azurewebsites.net/#2308 - if this is enabled, you
    will not be able to show "anything" in startup scripts...
    Martin
    Mal ein
    GUTES Buch über GPOs lesen?
    NO THEY ARE NOT EVIL, if you know what you are doing:
    Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))

  • Move a Excel 2010 Dokument Addin Project (Visual Studio 2012) to another devleopment machine with Visual Studio 2012 , but Office 2013

    Hi 
    we do have the following situation
    on computer A there is a Excel Document Addin development project , Visual Studio 2012, Office 2010 installed. All works fine.
    we would like to bring the project to another machine with Visual Studio 2012, but Office 2013 installed.
    Visual Studio can not build the project. It says that the application is not installed on the machine (though Excel 2013 is installed , but not Excel 2010) It seems to have a problem with the
    vbproj. 
    In other forums I found a hint that "Hostpackage = ..} needs to be set accordingly in the vbproj. I created then a "empty Excel-Addin project" under Visual Studio , looked at
    the Hostpackage entry, put that into the vbproj of "problem project. It still does not work.
    It would be great if anyone could help.
    Thomas

    Hello Eugene
    Problem is that it says that projectboard (the name of the main project) can not be loaded. All other projects in the solution can be loaded. Strange thing is , now that I try to create a empty excel Project it says that according to Excel security settings
    it can not be generated !? 
    I opened then Excel and set all Trust Center settings to "Default" - but no effect. I really have no idea what is wrong ..!? 
    Tom

  • Deploy Office 2013 using Group Policy

    Below are a list of questions I have regarding setting up Office 2013 deployment automation. We are looking to deploy Office 2013 Business Click-to-Run using a group policy. We have already setup the deployment using the Office Deployment Tool and have
    the configuration file all setup. The more automation we can provide the better to give the end users to best/fastest experience with this upgrade.
    How do we automate the deployment process using a group policy?
    Is there a way to have the Office 2013 deployment auto activate using the users credentials? We will be using the same password for all the user accounts for the deployment then having them change it later once everything is up and running. Would like to
    avoid having to go around and help each user activate the software as well.
    We would like to uninstall all previous versions of Office from the workstations that we're deploying Office 2013 to?
    Thank you!

    Below are a list of questions I have regarding setting up Office 2013 deployment automation. We are looking to deploy Office 2013 Business Click-to-Run using a group policy. We have already setup the deployment using the Office Deployment Tool and
    have the configuration file all setup. The more automation we can provide the better to give the end users to best/fastest experience with this upgrade.
    How do we automate the deployment process using a group policy?
    Is there a way to have the Office 2013 deployment auto activate using the users credentials? We will be using the same password for all the user accounts for the deployment then having them change it later once everything is up and running. Would like to
    avoid having to go around and help each user activate the software as well.
    We would like to uninstall all previous versions of Office from the workstations that we're deploying Office 2013 to?
    1. Because Office (in all forms) requires setup.exe to orchestrate the installations, classic Group Policy Software Installation (which requires an MSI file) is not suitable. This has been the case since Office2007. If you are constrained to use GP, you
    will need to use GP Startup Scripts. There is guidance for this, in the Office resource kit library on TechNet.
    http://technet.microsoft.com/en-us/library/ff602181(v=office.15).aspx
    2. Retail editions of Office, typically require you to login to the Microsoft Account where the license is associated, to validate the Office license. If you are using a product key method instead, you can use the PIDKEY element in your configuration.xml
    http://technet.microsoft.com/en-US/library/jj219426(v=office.15).aspx
    3. You'll need to tackle this yourself (there is no way to do this via C2R configuration). You could include the relevant uninstall-previous-version logic within your GP Startup Script (as a step prior to installing Office C2R). You'll need to cater for
    whatever previous-versions might exist in your environment, and whatever the relevant uninstallation methods are for each previous-version.
    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!)

  • Problem to generat an report on an SSRS for SCCM 2012 R2 SP1. I got error has occurred during report processing.

    Hi,
    Problem to generat an report on an SSRS for SCCM 2012 R2 SP1. I got error has occurred during report processing.
    In general it is no problem to generat SSRS reports, but an custom one i get issue with.
    The Error:
    An
    error has occurred during report processing. (rsProcessingAborted)
    Query
    execution failed for dataset 'DataSet1'. (rsErrorExecutingCommand)
    ExecuteReader:
    CommandText property has not been initialized

    Hi SaiTech,
    According to your description, when you render report on SCCM 2012 R2, you got the error message.
    According to my knowledge, the issue can be caused by following reasons:
    Select permission not granted to ConfigMgr reporting account. We need to open the SQL management console and open the properties dialog box of configmgr db, grant select and execute permission to ConfigMgr reporting account.
    Reporting Services Web Service URL or Report Manager is false. Make sure Web Service URL and Report Manager URL are correct. Restart SMS_Executive service and reinstall Reporting Service Point, then please render the report again.
    Report timeout. Increase query and report timeout.
    If the problem remain unresolved, please provide detailed information of SRSRP.log (default location: %programfiles%\Microsoft  and Configuration Manager\Logs) and reporting services error log(default location: %programfiles%\Microsoft SQL Server\<SQL
    Server Instance>\Reporting Services\LogFiles), it will help us move more quickly toward a solution.
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu
    If you have any feedback on our support, please click
    here.
    Wendy Fu
    TechNet Community Support

  • Adobe Flash appears to be installing with SCCM 2012 deployment, but ActiveX is missing

    I have found that even though SCCM 2012 deployment has installed flash, I later find that Active X is missing and that it is missing a registry key ?
    HKLM:\Software\Microsoft\Macromed\FlashPlayerActiveX
    Anybody have this problem?

    Yes, look at http://forums.adobe.com/thread/1447047

  • Deploying Office 2013 through SCCM 2012 SP1 leaves Office 2010 Tools and Sharepoint behind

    I apologize in advance, but I have searched similar topics to this, but I haven't seen an answer yet that describes where and how to accomplish this.  I'm also a bit new to SCCM and I'm still finding the nuances.
    Scenario:  Running SCCM 2012 SP1.  Office 2013 32bit is added as an application and deployed properly with an accompanied .msp file stored in the source folder.  The configuration is to have Office
    2010 uninstalled silently.  The deployment runs flawless and the user doesn't know otherwise.  Success in anyone's book, right?
    Except... Office 2010 Tools and SharePoint Workspace 2010 are left over.  Manual uninstallation is not an option.  This is for hundreds of PC's in several global locations. 
    I've seen it hinted to write a script.  That's fine I suppose, but what do I write, where do I store the script, and can I have SCCM2012 automatically run it before the installation of 2013? 
    Our favorite IT tool Google hasn't quite returned what I'm looking for.   Does anyone here have ideas or perhaps have experienced a similar issue?
    Thanks,

    1st, save the following content as a XML file on a server share, named as "config.xml".
    <Configuration Product="ProPlus">
    <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
    <Setting Id="SETUP_REBOOT" Value="Never" />
    </Configuration>
    Run the following script during or before the installation of Office 2013:
    "C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config \\servershare\Config.xml
    For more SCCM specific topics, we'd recommend you to visit the SCCM forums at:
    http://technet.microsoft.com/en-us/systemcenter/gg191847
    Max Meng
    TechNet Community Support

  • Deploy Office 2013 ProPlus Updates SCCM App-V

    Hi,
    I'm trying App-V and building the Office 2013 Pro Plus package worked fine, and to stop slow starting of applications I am (at the moment) looking at deploying App-V packages to stations during OSD in SCCM 2012 R2.  Deploying the applications is working
    great this way, except I can't find any information on how to deploy office updates to the App-V packages as they are released. 
    Usually with Office deployed the traditional way office updates are deployed through Software updates in SCCM.  But this doesn't happen when Office is deployed as an App-V package.  I don't really want to "stream" the packages to the
    internal stations.  Is there a way to automatically send out the updates to update the App-V office package that has been deployed to stations using the Install Application step of an SCCM OSD Task Sequence?  (Preferably Automated).
    Thanks,
    Andy

    As stated, you just have to generate and deploy a new Office package. Thankfully the client is clever enough to only stream down the blocks that have changed so you don't have to wait for users to re-download the entire package in order to apply the update!
    Deploying Office as App-V is fine... until you come across an application that integrates with Office but is incompatible with App-V. Also managing plugins with connection groups is difficult. I always recommend deploying Office locally unless you have good
    reasons to do otherwise.
    Dan Gough - UK App-V MVP
    Blog: packageology.com
    Twitter: @packageologist
    LinkedIn

  • SCCM 2012 Deploy --- Error = The software change returned error code 0x87D00324(-2016410844).

    Deployment to the client is successful but the error reported within Clients "SCCM Software Center"  
    The software change returned error code 0x87D00324(-2016410844).
    Also States on "Status" Past Due - Will be Retired"
    Can't figure this one out and I did some googling with no success in finding a solution?
    I am running an Adobe Flash install (.EXE)
    Any help or direction would be greatly appreciated
    RF

    Hi,
    Thank you for your response
    ""Wow6432Node is not valid on x86 systems."""
    Yes, that I am aware of that.....Windows on Windows, for running x86 apps on x64 Windows<o:p></o:p>
    When I first created the detection method I had only created the "WoW" Check
    for Flash value in the reg, which was running against both x86 & x64 Win 7
    systems, and forgot to include the x64 check/, either case, the error appeared
    on the WOW check. Presently I have 2 "Detection Clauses" one for x86
    and the second clause is x64 ( non WOW Path), and still receive the same erorrs
    on both x86 & x64 systems. ( and x64 system have both reg entries since Win 7 has both x86 & x64 versions of IE)
    Looking at the registry of an x64 Win 7 system I find the Adobe Flash registry entry is
    located in both Wow6432Node and also in the x64 sections of the reg.....<o:p></o:p>
    """"Also, why use the default value? I doubt there's anything in there (the default value is the
    value display in a key in regedit with the name of
    "@").""""<o:p></o:p>
    When Default Value is selected the boxes/options below that allow for more detailed
    information to be entered when performing the "reg check"? This is
    where I had been able to enter specific Build/Version to look for, Flash
    11.4.402.265, so that if it does not discover the build # it will proceed with
    the install.....<o:p></o:p>
    I figured having the option to check for Build/Version # would omit SCCM reinstalling on
    systems that have build 11.4.402.265 already?<o:p></o:p>
    From what I understand is that Adobe Flash x64 installs both versions x86 & x64 since Win 7 has both IE
    x86 & IE x64 bit versions by default, and this would explain the Wow6432Node reg
    entries and the true x64 reg entries in both locations when installing.
    Overall, I am thinking I may be heading in the wrong direction in resolving this, as x86 & x64 versions install on the systems, so this tells me it is detecting when / what needs to be installed, the issue seems to be how it reports back after installing......
    Looking further, I view the Content Status Page, and there reporting info in Asset Detail under [Success]  all others { / In Progresss / Error /Unknown } has no info......
    If this helps provide further details.....
    Thanks
    Regards,
    Ron
    RF

Maybe you are looking for