Deploying MS Office 2013 with GPO

OK i would like to deploy office 2013 via GPO, i finally have been able to get the script to work however there is one more detail i need to get figured out.... How can i incorporate into the script so that it will only run once...  my script is below
and does the following, it uninstalls office 2010 whether it be 32bit or 64bit then silently installs office 2013 as a startup GPO... how would the script look if i'd like to add so that it looks for a specific txt file that if its there it does nothing and
if it's not it runs install script and perhaps at end of install script maybe it creates that txt file... I need help on the best way to just "RUNONCE"
here is my script:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
"C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
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.PROPLUS
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\****\Office13
REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\****\Office13\ProPlus.WW\config.xml
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\****\Office13\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 2010 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 DeployOffice) else (goto End)
REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
echo %date% %time% %ComputerName% "Has Run the install Process" >> %LogLocation%\HasRunInstall.txt
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% %computername% Setup ended with error code %errorlevel%. >> %LogLocation%\FinishedInstall.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal

The problem with Office 2010 and later is that it is not designed to be installed remotely or by a script. You need to create an install spec and set up some prerequisites fist.  If you ten follow the instructions for using a GPO to deploy Office
you will not need to  use a "RunOnce" key or anything else.
Note that eh RunOnce key take a command or batch and command and is deleted as soon as it is executed.  The problem you have to solve is how to set the RunOnce key to begin with.
You really must use the information in the links posted for Office deployment.  You cannot do an end run around this with any success.  If you search for forum posts on this you will see that many have been exactly where you are.  Don't wast
your time.  Follow the instructions as posted in the Office forum and on the TechNet link.  YOu will find it is actually quite easy and very flexible once you understand the steps.
\_(ツ)_/

Similar Messages

  • Deploying Custom Office 2013, Uninstalling Office 2010

    We've just recently moved to SCCM for application and OS deployment, so we're setting up applications to be deployed through SCCM for the very first time. I've read a few guides to deploying Office 2013, and the majority of them follow the same procedure:
    Customize Office 2013 with OCT
    Create an application in SCCM by selecting proplusww.msi
    Edit the deployment type and replace proplusww.msi with setup.exe
    Some guides reference the .msp in the setup.exe command, some don't. e.g. "setup.exe /adminfile custom.msp"
    So, a few questions:
    Why should I use setup.exe vs proplusww.msi? I understood that the application model gives us more control, better autodetection, and less manual configuration. i.e. use MSI for applications
    If I should use setup.exe, do I really need to reference .msp? e.g. setup.exe /adminfile custom.msp I thought that when you customize the installer, and place the msp in the \updates folder, running the setup.exe still utilizes the msp file. 
    Some guides say I should also used an xml file for help with uninstalling Office 2013. e.g. An xml file with Display Level, SuppressModal, and AcceptEula set, then using the command "setup.exe /uninstall proplusr /config .\proplusr.ww\unisntall.xml".
    What instances would I need the xml, and which instances would I not?
    Finally, I would possibly like to install Office 2013 during OSD. Would that change any recommendations on how I create the Office 2013 SCCM application?
    I'd appreciate any help/advice anyone can give. I was not able to find any info directly from Microsoft on how best to deploy Office with SCCM. Nor was I able to find any info on using proplusww.msi vs setup.exe for deployment. Thanks.

    If you place the .MSP file in the Updates folder, the Setup.exe program will automatically process it without the need to specify in the command line.  The .XML and OCT .MSP are two different means of customizing the installation.  I typically
    use the OCT to create the .MSP and drop it in the Updates folder, then just call setup.exe with no switches to perform the silent install.
    Make sure you set the SETUP_REBOOT property to Never in the OCT, otherwise the install may perform an unexpected reboot that could potentially cause issues with ConfigMgr (especially if it's during imaging).
    Thanks for the info. What about proplusww.msi vs using setup.exe? I still haven't been able to find any documentation on using one vs the other when deploying through SCCM (as to why you should use one over the other). Almost every SCCM application deployment
    guide I come across always wants you to use the MSI, sometimes going to great lengths to find one, just to avoid using an exe. So, why does almost every SCCM Office deployment guide tell me to use setup.exe? Also, is it just me, or is there really not official
    best practice form Microsoft when deploying Office through SCCM?

  • How to Install Visual Studio 2010 on a PC with Microsoft Office 2013 with 64 bits

    I am with problems to have acess to the link: http://www.microsoft.com/en-us/download/details.aspx?id=12187
    Why?
    I want do install Visual Studio 2010 on a PC with Microsoft Office 2013 with 64 bits. How can I do it?
    Thanks.

    Hello Carla Sofia,
    Visual Studio installation do not depends on Microsoft Office 2013. They do not have relationship here. I think your problem is that you cannot find the link to install Visual Studio 2010.
    In order to know why, please see here:
    https://support.microsoft.com/en-us/lifecycle/search/default.aspx?sort=PN&alpha=Visual%20Studio%202010&Filter=FilterNO
    The mainstream support for Visual Studio 2010 is already expired and that is why you cannot open any link about Visual Studio 2010 Setup.(I cannot verify whether that link is about VS2010 Setup.)
    I think you need to think about the following:
    1. If you need Visual Studio 2010, you may have to consider some other channels. For example, official site you can try use MSDN Subscription. For non-official site. Sorry I cannot provide any place for you
    2. You can use other latest version of Visual Studio, for example, we have Visual Studio 2012, 2013, 2015 for you to use. You can also use Visual Studio Express 2010 version. It is still available for download.
    Best regards,
    Barry
    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.
    Click
    HERE to participate the survey.

  • 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 :))

  • 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

  • Office 2013 with Visio and Project Error - Package manifest is invalid

    In July I successfully created an App-V install of Office 2013 VL using the ODT. This week I decided to try just doing Visio as we don't install it or Project on all systems. I used my same customconfig.xml and just changed the ProPlusVolume to VisioProVolume
    and changed the source path. Everything downloaded and packaged fine. I was able to import into SCCM just fine and create a deployment to my test collection. However when I run the install out of Software Center I get (as part of a much longer error) the message
    in AppEnforce.log that the package manifest is invalid. Thinking that maybe I had to include Office as long with Visio I tried packaing all three items but still get the same error. Has anyone else seen this behavior and/or ideas how to fix it? Can I sequence
    just Visio or just Project? I'm including my config.xml just in case I've got something wrong with it that I haven't caught. Thanks
     <Configuration>
      <Add SourcePath="<networkpath>\Microsoft\AppVOffice2013\Sept\" OfficeClientEdition="32" >
        <Product ID="ProPlusVolume">
        <Language ID="en-us" />
        </Product>
        <Product ID="VisioProVolume">
        <Language ID="en-us" />
        </Product>
        <Product ID="ProjectProVolume">
        <Language ID="en-us" />
        </Product>
      </Add>
      <Display Level="None" AcceptEULA="TRUE" />
      <Logging Name="OfficeSetup.txt" Path="%temp%" />
      <Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>

    Hy. I'm having the same problema.
    I'm trying to create na app-v package (v.5 SP2) of Office 2013.
    I downloaded the Office Deployment Tool for Click-to-Run from here:
    http://www.microsoft.com/en-us/download/details.aspx?id=36778
    I installed it into C:\Office2013pck shared that folder as 
    \\APPVMANAGER\Office2013 and mapped as Z:\.
    I changed the configuration.xml file to:
    <Configuration>
    <Add OfficeClientEdition="32" >
    <Product ID="ProPlusVolume">
    <Language ID="en-us" />
    </Product>
    <Product ID="VisioProVolume">
    <Language ID="en-us" />
    </Product>
    </Add>
    </Configuration>
    Then I ran in na elevated cmd:
    >Z:
    >\\APPV-CL-WIN7DEF\Office2013\setup.exe /download
    \\APPV-CL-WIN7DEF\Office2013\configuration.xml
    and
    >\\APPV-CL-WIN7DEF\Office2013\setup.exe /packager
    \\APPV-CL-WIN7DEF\Office2013\configuration.xml
    \\APPV-CL-WIN7DEF\Office2013\Appv
    Everything seemed to work fine.
    The creted folder had Office\Data\15.0.4649.1001 folder (I guessed this is a version number)
    When I tried to add the package to App-V Server (in the Console) I get the following error:
    An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
    I tryied to publish it from powershell, getting the same error message agalluci image post shows.
    From the Event Log I got this additional information:
    There was a problem retrieving the requested package \\APPVMANAGER\AppVpck\Office\VisioProVolume_ProPlusVolume_en-us_x86.appv for import. Error message: Unspecified error
    Element '{http://schemas.microsoft.com/appv/2010/manifest}UsedKnownFolders' is unexpected according to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Package'.
    I haven't found any indication of which file is the manifest app-v file.
    I also haven't found any .xml with the "UsedKnownFolders" tag (I changed the .appv package extension to .zip and explored some of the files).
    I tryied creating a package for 32 and 64 bits, only office, office and visio, and office visio and project running Windos 7 and Windows 2012.
    Thanks in advance for any help.

  • App-V 5.0: Adding Visio 2013 and Project 2013 to a previously deployed virtual Office 2013

    Good morning.
    I can successfully deploy Office 2013 via PowerShell and App-V v5.0 without difficulty.  I've read the document at
    http://support.microsoft.com/kb/2915745/en-us and followed all instructions successfully.
    My question is this:  If Office 2013 without Visio 2013 or Project 2013 is virtually deployed, how can those components be added later?
    For instance, we may have 100 users that acquire a virtualized Office 2013 without Project or Visio.  We then may have 25 users that require a virtualized Office and Visio without Project and, perhaps, another 15 that require Office and Project without
    Visio.
    Currently, when I attempt a second virtual deployment of one of these components, it removes Office 2013 making it inaccessible.
    How can Project and/or Visio be deployed to an already existing virtually deployed Office 2013?
    Thanks very much.
    John
    IAmStrings

    As a part of MDOP, you'll also have access to UE-V which will provide a mechanism of moving user preferences across the same applications from difference packages.
    It will require planning, configuration and deployment, but will ensure you don't face the same issue in the future.
    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
    answer your question). This can be beneficial to other community members reading the thread.
    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
    Twitter:
    @stealthpuppy | Blog:
    stealthpuppy.com |
    The Definitive Guide to Delivering Microsoft Office with App-V

  • Office 2013 with Service Pack 1 installation error about "search path"

    I have an automated installation technique that has worked fine with Office 2010 Pro Plus (32-bit), incorporating the latest Service Pack into the network administrative installation point (under \updates), adding 10 foreign languages to the network administrative
    installation point, creating a custom .msp with the OCT (that goes into \updates too), editing the config.xml files, and then running setup.exe from that network administrative installation point. This works on 32-bit Windows XP clients and on 32- and 64-bit
    Windows 7 clients.
    For Office 2013 Pro Plus, I have built the network administrative installation point exactly the same way (original DVD files + languages + SP1 updates + config.xml updates), but the installation is failing with every type of client, all with
    the same error message. The network administrative installation point is readable by the normal installing account, but I even get the same error when I login as me and initiate setup.exe manually, and I have all rights to this point.
    Here's the critical point from a log file:
    2014/03/11 11:53:49:691::[2372] DistributionPoint parsed.  The distribution point is now set to: \\archive.ads.college.edu\archive\KBOXalt\Office2013
    2014/03/11 11:53:49:691::[2372] COMPANYNAME specified in config.xml.
    2014/03/11 11:53:49:691::[2372] USERNAME specified in config.xml.
    2014/03/11 11:53:49:800::[2372] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
    2014/03/11 11:53:49:910::[2372] Searching for default versions of resource files under the folder [\\archive.ads.college.edu\archive\KBOXalt\Office2013].
    2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
    ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
    2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
    Type: 34::InvalidDirectory.
    2014/03/11 11:53:50:019::[2372] WER element [SuppressModal] is set to value [true]
    2014/03/11 11:53:50:019::[2372] WER element [P4] is set to value [InvalidDirectory]
    2014/03/11 11:53:50:019::[2372] Catalyst execution finished: 03/11/2014 11:53:50.  Return code: 30034.  Exception caught: InvalidDirectory.
    2014/03/11 11:53:50:019::[2372] PERF: TickCount=894821 Name=RunSetup Description=End function
    I cannot find any references to this exact error anywhere on the Internet. Can anyone tell me what this means, and how I fix it?

    As automated, the utility that runs setup.exe maps a drive letter to
    \\archive.ads.college.edu\archive\KBOXalt using a kboxmap AD account, which has read access to the whole \KBOXalt tree. I used that same kboxmap AD account manually to simulate what the utility does, and hit the same problem. But here's what's
    odd: right next to that
    \\archive.ads.college.edu\archive\KBOXalt\Office2013 directory is an
    \\archive.ads.college.edu\archive\KBOXalt\Office2010 directory, both created the same way, and the Office 2010 installation has always worked perfectly using the kboxmap AD account. I don't understand why Office 2013 is only working for an account with
    read/write access, where Office 2010 worked fine for an account with only read access. Especially when the Office 2013 resource kit documentation clearly states that the account running the installation should only have read access, nothing more. (All this
    KBOX stuff comes from the fact that our deployment environment is a Dell KACE KBOX 1000. However, that plays no part in the problem: ignoring the KBOX 1000, I can manually recreate the problem every time.)

  • Cannot Save Word files as a PDF in Office 2013 with Office customization tool

    Hello
    I'm deploying office 2013 as a part of a post clone task.  Using the customization tool I created an msp with the full installation (without outlook,Link, or skydrive) I noticed that I cannot save or export files as PDF files.  If I do a manual
    install (without MSP) I can save files as pdf.  I can't find anywhere in the customization tool that allows me to choose different "save as" file types. In office 2010 I used to be able to save word files as PDF files.  Any ideas would
    be greatly appreciated.
    Charles

    Hi,
    In regarding the issue, could you give me more information? Did you test to install the Office 2013 by using MSP and manual installation in the same computer? Did the other Office suits can not save files as pdf?
    Let's do some test to narrow down the issue:
    If you use the only one computer to test, please export a new MSP file include all the suits and use the all the default setting. Then we follow the
    link to deploy again.
    If the issue still exists, please try to change a computer, and update Adobe programs to install the new MSP file to test.
    If you get some error message when you save as pdf through Word, please upload, I'll do more deeply research.
    Regards,
    George Zhao
    TechNet Community Support

  • OEM Deployment of Office 2013 on Offline System, Deployment Strategy

    Hello,
    Since Office 2010 is no longer offered by Microsoft we have been forced to go to Office 2013, however we are running into major problems with deployment. We configure systems for utilities (Power and Process) which generally are not connected to the internet.
    So far we have run into a multitude of problems with deploying Office 2013 basically revolving around having to create an account with Microsoft for our customer and connect the machines to the internet. We have found that the MSDN image of Office Professional
    Plus 2013 with an MSDN key will install correctly offline with the typical phone activation. So a few questions:
    1) Does the product key determine if it needs to be activated online? For example: Is there a difference between the OEM / Retail / VL keys and or installers?
    2) Can I use my MSDN installer with a retail license of Office Professional 2013? Or do I need to get the specific volume license?
    3) Will there be MSDN installers for the other versions of Office such as the standalone Excel retail or Office Professional (OEM or Retail)?
    3) Is there anyway to install Office 2013 and not activate it until it resides with the End Customer if you have a retail version?
    4) Is there any offline method for installing or re-installing Office 2013 if you have a retail version?
    5) Is there an OEM or VL version of standalone products available (such as Excel)?
    Thanks

    Hi,
    Microsoft now no longer offers an Office 2010 download from their site, however, if you already have a product key of Office 2010, you can still get Office 2010 installation package from this website:
    http://office.microsoft.com/en-us/products/microsoft-office-2010-backup-FX101853122.aspx.
    Office OEM is a version of the Microsoft Application Suite sold with new computers. Office 2013 are available from Office 2013 suites and Office 365 subscription which is associated with the Microsoft account, when Office 2013 suites are activated by the
    traditional method with a 25-character product key.
    For the license issues, we suggest you to contact your local Microsoft customer support to get more information.
    More reference about Office 2013 activation:
    http://technet.microsoft.com/en-us/library/ee705504(v=office.15).aspx
    http://office.microsoft.com/en-us/word-help/activate-office-2013-programs-HA102819770.aspx
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

  • Office 2013 with OneDrive Desktop sync conflicts

    I am using Office 2013, and I am on Windows 8.1 with OneDrive setup. I keep some files Offline and OneDrive syncs it for me which is cool. But when I installed Office 2013, when I edit Excel files, I notice that there's an Uploading to OneDrive message at
    the bottom while saving. Then I was prompted with a conflict during the sync. Isn't this because OneDrive is already syncing it and Excel is syncing it again that's why this happening?
    How do I disable Excel (or probably Word as well and other apps in Office) to stop saving directly to OneDrive? How do I disable the Office Upload Center that keeps on popping in the System Tray? I am already fine with the sync being done by the OneDrive
    Desktop. Previously, there was an option to disable Office sync from the OneDrive Desktop icon in the System Tray, but it is now gone and I couldn't find it anywhere else. Where do I find it now?

    To disable/configure this open up the Task Scheduler and click on the
    Task Scheduler Library node. You should see a task here labelled
    Microsoft Office 15 Sync Maintenance for USERNAME.
    Disable the whole trigger (right click and choose disable) or change the Properties of this to amend the trigger that starts the job. For instance, you can delete the trigger that starts on user log on.
    The other way is to find MSOSYNC.EXE and OSPPSVC.EXE on Disk C:, delete them:
    1. Open task manager and kill MSOSYNC.EXE and OSPPSVC.EXE
    2.  Search C: for MSOSYNC.EXE and note which one is the actual Office folder, then delete them all
    3. Go to the Office folder and create a MSOSYNC.txt file and edit it to put the quit command in it.
    4.  Rename the file to MSOSYNC.EXE and then change the permissions so the user owns it, and remove all permissions except for the user which should have all except WRITE.
    5.  Reboot
    This method above is like cheating, you can make fake MSOSYNC.EXE and OSPPSVC.EXE so that they can't even run.
    Anyway, Microsoft doesn't recommend you disable the Upload center.
    -Jeff

  • Office 2013 with Lexmark printer - Cannot change printer settings

    I have a Lexmark x4650 and I can open the printer settings within all of the Office 2013 applications (Windows 7 64-bit). But after I change the settings to what I want, I cannot exit the printer settings dialog. If I click OK, nothing happens. If I click
    Cancel, nothing happens. If I click the X in the upper right of the window, nothing happens. The only way to close the printer settings dialog is to force the Office application to close through the Windows task manager. I've tried re-installing both Office
    and the Lexmark print driver/applications with no success. Has anyone else experienced this problem? Does anyone have a solution?
    Thanks,
    John

    We need to narrow down the issue, to see if the root cause is on Office side or Printer side. Please try below steps for troubleshooting:
    1. Try obtaining an updated printer driver from the printer's manufacturer. And update your PC, restart and try again.
    2. Try to select another printer in Printer
    drop-down list in any Office application, and try again to see if we have the same issue.
    Printing is primarily controlled by settings in Microsoft Windows:
    3. Please try to print a file outside the Office application, say a .pdf file to determine whether your printer setup in Windows is correct or using the Windows Printing
    Troubleshooter.
    Hope this can help you. Thanks.

  • Office 2013 with Acrobat XI Patch 11.0.05

    After installing Office 2013 on computer with Adobe Acrobat XI with Patch 11.0.05 already installed, the acrobat tab is gone.  Everything I have read says to install the latest patches.  Do the patches need to be reinstalled since Acrobat was updated prior to the install of 2013?  If som which patch specifically?

    You shouldn't need to reinstall but try doing a repair of the Acrobat install from under the Help menu. Also, check to make sure the PDFMaker Add-on is enabled in Office 2013.

  • Sharing 5-license Office 2013 with another PC

    I bought 5-license Office 2013 in December, and even shared with with my secondary PC, but my memory of how to do it has disappeared. Can you give me instructions or a pointer?
    Pete Jacobsen

    Wrong forum - this is for Windows Home Server. Try at answers.microsoft.com
    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

  • Auto deploying branch office printers with Direct Access

    Hello there
    I am implementing my first Direct Access topology and have a question. We will have branch offices with workstations deployed using Direct Access for administrative purposes. We have staff moving around from branch to branch with the goal to
    make logging on to the network and accessing resources for users as automated as possible. One of the questions I have regards auto configuring branch printers for users using Group Policy. The branch offices have workstations, printers and NAT modem/routers
    with DHCP - but no servers.
    If we have a stand alone network printer, how do we list that printer in Active Directory allowing the user to auto-configure it using group policy? If we install it on a server at Head Office, would the print job travel there first and then back to
    the branch? Obviously this is not ideal. Or can it be directed straight to the printer using a script or something?
    Alternatively we can install and share it on a branch workstation and list it in the directory, but would this not be same the problem as above? This is not ideal either as it would depend on the workstation being always on and available.
    Any input Direct Access gurus?
    Thanks in advance
    MIS5000

    Hi,
    Thanks for your post.
    We could have 2 possible solutions for natively deploy printers using Group Policy without the need for any scripting:
    1) Group Policy Preferences – available in Windows Server 2008 and later
    2) Print Management – available in Windows Server 2003 R2 and later
    http://blog.powershell.no/2009/11/08/deploying-printers-using-group-policy/
    Did you try to use the Print Management? You can share printers on a network and centralize print server and network printer management tasks using the Print Management Microsoft Management Console (MMC) snap-in. Print Management helps you to monitor print
    queues and receive notifications when print queues stop processing print jobs. It also enables you to migrate print servers and deploy printer connections using Group Policy.
    https://technet.microsoft.com/en-us/library/cc731857.aspx
    Meanwhile, if you have any Direct Access related issue, I think you may ask in network forums:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverNIS
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maybe you are looking for