Office 2010 setup thru computer startup script

I am trying to install Office 2010 (sp2 seperate in the updates folder) thru group policy startup script and configured with OCT .msp file. Also try to start Access Runtime 2010 with SP2 update in the updates folder.
In group policy set run scripts asynchronisely disabled and run scripts visible enabled otherwise i could not see what the system was doiing also not when configiguring OCT with full display. The gpo settings lets the screens show during install so the user
can see what happens.
There is another problem that rises however: I have made 2 batchfiles and both are starting as a computer startup script in seperate gpo's (that is in another post). First the Accessruntime is installing, after that Office 2010 is running. Both are installed
after login but only one of the 2 have SP2 installed (7015) in this case Accessruntime has it. When i run only the Office 2010 install and not the Accesruntime 2010 then Office 2010 standard has also SP2 installed (version 7015). When running both only Runtime
has this sp2 and Office has 4763 this is without sp2 i believe.
In both folders (Office en Runtime) are the update files .msp in the updates folder of the installation, so thats ok.
Why is only 1 of the 2 installing the SP2 when running both?
A second thing is when restarting the system and before the login screen appears a message: Upgradepatch cannot be installed by Windows installer becasue the upgraded program does not excist of the upgradepatch is not suitable for this program?
Here is part of the batchfile:
IF EXIST "c:\program files\Microsoft Office\Office14\WINWORD.EXE" (goto mkfile) ELSE (goto DeployOffice)
:mkfile
ECHO Office 2010 is reeds geinstalleerd>c:\temp\office.txt
goto end
:DeployOffice
call cscript \\sharename\office2010\Offscrub03.vbs ALL /bypass 1 /q /s /NoCancel
start /wait %DeployServer%\setup.exe /adminfile %DeployServer%\officeconfig.msp
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
Another batchfile
start \\sharename\accessruntime2010\setup.exe /config \\share\accessruntime2010\config.xml
REM echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
freddie
after installing both runtime and office both have SP2 in updates folder:
runtime 4763
Office 2010: 7015
So in this example runtme is installed without the SP2. installing runtime alone gives with SP2...
The message is gone. There was a other policy inherited from above that caused the message. The only problem now is that when installing both, runtime 2010 with SP2 files and Office 2010 with SP2 files, then one of the two don't get the Sp2 installed, why
is that?

> In the bat file, I have a line that records if the install completes
> successfully or failed. I don't have any other logging in my
> script. Are you referring to something like GPO logging? I know that
> the script runs because when I am looking at one of the PCs, I can
So it is NOT GP related but rather your script fails?!? Put some "echo
%~n0 %date% %time%>>Log-File-Of-Your-Choice.txt" in it to check what's
going on. And put ">>Log-File-Of-Your-Choice.txt 2>&1" at the end of
critical commands to capture their output.
> I ran the gpresult /h command which shows all User Configuration
> policies, but NOTHING appears under the Computer Configuration section.
Admin commandline? If not, you don't see computer settings :)
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 :))
Martin,
I still did not figure out why the installation script did not work for some of the PCs, even though the PCs have the same image. For the ones that don't work, I will install manually. Can you please look at the screenshots of the GPO
settings I am using, and let me know if there is any settings that I need to remove or add?
Thanks

Similar Messages

Gpo computer startup scripts not running

Hi,
I´m making some test with a windows 7 pro 64 bit computer and a 2008 r2 domain controller where I have created a computer startup script. I give you more info:
Domain functional level: 2008 R2
DC: 2008 R2
Client: Windows 7 pro x64
Gpo: Computer configuration -> Windows configuration -> Script -> Startup
Type of script: bat file copied on \\domain_name\SysVol\domain_name\Policies\{461E688A-E8F8-4C9B-8419-FE83DCDD4C26}\Machine\Scripts\Startup
The windows 7 machine is full updated, windows firewall disabled, uac disabled, windows defender disabled.
The bat file works and the gpo is applying, i have seen it via gpresult, another gpo which is in a top level works fine.
I need some help please, because I don´t know what to try.
Thanks in advance.

Hello Egoitz28,
Do you mean that you add the bat file in the startup group policy and gpresult shows that it is applied, but the bat is not run?
Please share us the bat file to test.
Logon/Logoff scripts could only be applied to users, whereas Start-up/Shutdown scripts applies to computers.
I create a test.bat start %windir%\system32\notepad.exe, and add it to the User Configuration->Policies->windows Settings->Scripts->Logon in the Default domain policy. And it works.
If I create in the startup policy in Computer configuration, I can see it in the gpresult, but it doesn’t work.
Please test if the bat works in the Logon policy.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Group Policy - Computer Startup Scripts - Add/Set Default printer

Good Morning.
Let's say we have 2 offices, A and B, and only 1 user. The user is using Roaming Profiles. Each office has its own printer.
What I am trying to do, is make a Startup script that is specific to the COMPUTER being logged into so when any user logs into that computer, they get the printer in that office defined and set as default.
I am able to do this successfully with my script but ONLY if i have the script be on the USER side of GP (i.e. in the Logon script section)
That is great that that is working however, when my user goes to Office B, they still get mapped to Office A's printer if I use that method.
So I figured I could just modify my GP and run the same script from the STARTUP section of the computer, rather than the LOGON section of the user. It does not work.
Here is my script:
Set WRFCUNetwork = CreateObject("Wscript.Network")
PrinterPath = "\\fileserver\MAINTELLER"
PrinterDriver = "PrinterDriver"
WRFCUNetwork.AddWindowsPrinterConnection PrinterPath, PrinterDriver
WRFCUNetwork.SetDefaultPrinter "\\fileserver\MAINTELLER"
This is where I Have the script placed:
     Computer Configuration -> Windows Settings -> Scripts(Startup/Shutdown)
Once i'm in there, I double click Startup, click Add, and select my script which is named:
     MainPrinterSetup.vbs
I have this GP applied to ONE OU, and that OU has ONE computer in it (my test computer)
I login with a brand new user called "testuser" (creative, huh?) and basically nothing happens
except they log in and have some Microsoft Document Image Writer printer set as default (which by the way sure does slow the PC down to the point of it almost being broke if anyone actually tries to print to that by accident)
No Main Teller Printer, no anything.
The strangest part about this is, if i apply this script to the user LOGON scripts, it works fine, the printer is there, and is set as default. (but see above why that wont work for my situation)
So obviously the script works fine, but I guess i'm missing something when it comes to applying GP's to Computers rather than Users.
Can anyone shed some light as to why the script is not running (i'm guessing the script isn't even attempting to run, rather than failing, but i have no way to know that)
Thank you in advance!!
Derek Conlon
Network Administrator
WRFCU
EDIT: Here are the PC's info that i'm working on:
     Server: Windows Server 2003 Standard Edition (where my GP's are created and managed with AD)
     Target PC: Windows XP Professional SP3
EDIT #2: I manually navigated to the Script file after logging in and "opened" it and it added and set the default printer no problem. the issue is definately with the script running at startup.

I wanted to clarify a few things:
1. While it is true that printer connections are usually per user, it is definitely possible to create "global printers". There are a number of ways to do this, but two methods that come to mind are using:
a. "Rundll32 printui.dll,PrintUIEntry" option with the "/ga" switch. The "/ga" switch is the key here since it allows you to deploy printers "per machine" instead of "per user". More information
about this is available at:
http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm
http://technet.microsoft.com/en-us/library/ee624057%28WS.10%29.aspx
http://www.computerperformance.co.uk/Logon/logon_printer_computer.htm
http://www.robvanderwoude.com/2kprintcontrol.php
b. The Print Management console that is available in Windows 2003 R2 and higher can help you deploy printers "per machine" in addition to "per user". More information about this is available at:
http://www.czsolution.com/print-management/print-management/print-management-console.htm#DeployingPrintersByGroupPolicy
http://technet.microsoft.com/en-us/library/cc753109%28WS.10%29.aspx
2. As Guy mentioned, Group Policy Preferences can help set the default printer. But there is another way to accomplish this. The problem with the computer startup portion is that it runs before the user logs in. And applying this script
in the login script section would not work per computer unless you used loopback processing. So another way to do this is to place a script that sets the default printer into the "All Users" startup folder. Items in the "All Users"
startup folder run for any user that logs into the computer, but it runs in the user's context. So, this script would effectively set the default printer on a "per machine" basis. The script method is a cruder way to approach the problem,
but it will help get the job done. Here are some resources on setting the default printer via script:
http://www.intelliadmin.com/index.php/2007/08/set-default-printer-from-a-script
http://www.computerperformance.co.uk/ezine/ezine17.htm

Deploy Office 2010 gpo/oct activation

I am trying to deploy Office 2010 Standard through group policy startup computer script. A batchfile runs which starts the setup off Office and a msp file. First office 2003 gets deinstalled and Office 2010 installed. This all go fine but the activation
fails. When i start a Office program the program wants to activate.
Reading on the Internet about this problem comes with a lot of solutions which do not work. Solutions like AUTO_ACTIVATE and ospp /act in the oct configuration already tried without luck.
We use a proxy server in our orginisation but the proxy server is set in Internet Explorer. The difference is that the installation runs as a system user when set as computer startup script policy. Maybe that is the issue that the system user cannot reach
the internet....
Off course when i login as the user and start for example excel then he cannot activate because of the user rights. A prompt appears of UAC that a username and password must be given but that can not be left over to the users....
We use a MAK key and not KMS (not a solution because MAK key is chosen..)
Also tried to activate remotly thru ospp but then a error appears 0x80072ee2. According to Microsoft this has something to do with rights, but how to overcome this problems.
I would like a silent install thru GPO and no user intervention, including activating....
What is the best way to solve this problem?
freddie

I have almost the complete silent install however struggling with activation. Tried the above command in OCT with the cmd.exe /c etc switch but nothing happens because after starting a office programm activation requered coms in. It could be do that the installation
is in a batchfile and runs in a computer GPO maybe the system user has no rights to activate….
I cannot find a log file in %temp% to see what errors are…
I have also tried to set a batchfile at computer startup the runonce and even force in the OCT to start the machine up after Office 2010 is installed but then i need to restart the machine again because the runonce batchfile is put there after a restart is
taken place i guess so the machine needs to reboot the second time for the activation batchfile runs.
I am now seeking a easy way to activate silently and automatically without user intervention.
Summarize what i have tried:
configure office thru OCT in the OCT tried AUTO_ACTIVATE =1 and add registry keys which adds a key in the runonce to start a batchfile which suppoce to activate Office. But after install office the machine restarts and after login the batch is not started,
it is started next reboot....
Als tried in OCT to run cscript OSPP /act as a command post installation.
Non of the above works. Auto_activate and the direct script OSPP does nothing. The batchfile in the runonce starts the OSPP command but after a new restart so it needs 2 restarts.
The msp file is saved on a shared resource and the command to start the msp file is put in a batchfile which runs at startup script thru gpo, so maybe the local system user which runs the installation then cannot access the internet or whatever but thatswhy
i made batchfile in the runonce so that batch is started under the user, but if only the batchfile would start after the installation and reboot of Office 2010 and not reboot again to start it...
What else can i do to activate Office automatically?
freddie

Office 2010 SP2 deploy several systems

We are deploying Office 2010 Standard thru Group Policy. SP2 i downloaded later so there are a dozen systems already installed office without the SP2. The meaning is to also install the SP2 Office to the machines which have gotton Office 2010 without SP2.
The quistion i have is: how do i deploy SP2 Office update thru GPO to several machines which already got the Office 2010 Standard installed. How to install Updates office thru GPO? This is not a setup file but all MSP files in the SP2?
I have already seen that one can do it by script but how?
freddie

Hi,
Your require could be done via script. I think you need to add some if-else sentences in the script. We could use version number to determine which machines need to install SP2.
The version number of Office 2010 SP2 is greater than or equal to 14.0.7015.1000.
The version number of Office 2010 SP1 is greater than or equal to 14.0.6029.1000 but less than
14.0.7015.1000.
The version number of the original RTM release of Office 2010 (that is, with no service pack) is greater than or equal to
14.0.4763.1000 but less than 14.0.6029.1000.
http://support.microsoft.com/kb/2687455/en-us
If you need more help about writing the script, please post your qusetion to script center forum:
http://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?category=scripting
Here is a sample for "Deploying Office 2010 by using Group Policy computer startup scripts"
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 "office14." as a prefix.
set ProductName=Office14.PROPLUS
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\FS\Office2010SourceFiles
REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\FS\Office2010SourceFiles\ProPlus.WW\config.xml
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\FS\Office2010LogFiles
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
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal
More
reference:
http://technet.microsoft.com/en-us/library/ff602181(v=office.14).aspx
Regards,
George Zhao
TechNet Community Support

Deploying Office 2010 with SP2 / Access runtime 2010

I am trying to install Office 2010 thru OCT / GPO. Starting a computerstartup script which runs a batchfile. The batchfile is starting the deinstalltion of Office 2003 and installs Office 2010. In the updates folder is also SP2 integrated so that SP2 is
also installed.
In another batchfile and another policy i also install Access Runtime 2010.
The problem i have is that the installation of office 2010 is starting and installs, however the SP2 is often not. Sometimes it does and sometimes it don't. That is also the fact for Runtime 2010. Sometimes it does and sometimes not, then only Office 2010
is installed without SP2.
because he sometimes installes access runtime 2010 and Office 2010 SP2 it makes it more difficult.
The batchfiles are running in computer startup script so before the user can log in to their W7 systems.
Here is part of the latest logfile from Office:
MSI (s) (7C:24) [15:36:23:509]: Product: Microsoft Office Standard 2010. Bestand C:\Program Files\Microsoft Office\Office14\MAPISHELL.DLL wordt gebruikt door het volgende proces: naam: SearchFilterHost , id 2492.
MSI (s) (7C:24) [15:36:23:713]: Product: Microsoft Office Standard 2010. Bestand C:\Program Files\Microsoft Office\Office14\OLMAPI32.DLL wordt gebruikt door het volgende proces: naam: SearchProtocolHost , id 3252.
MSI (s) (7C:24) [15:36:23:729]: Product: Microsoft Office Standard 2010. Bestand C:\Program Files\Microsoft Office\Office14\MAPIPH.DLL wordt gebruikt door het volgende proces: naam: SearchProtocolHost , id 3252.
MSI (s) (7C:24) [15:36:24:098]: Product: Microsoft Office Standard 2010. Bestand C:\Program Files\Common Files\Microsoft Shared\OFFICE14\MSO.DLL wordt gebruikt door het volgende proces: naam: SearchProtocolHost , id 3252.
MSI (s) (7C:24) [15:36:24:231]: Product: Microsoft Office Standard 2010. Bestand C:\Program Files\Common Files\Microsoft Shared\OFFICE14\RICHED20.DLL wordt gebruikt door het volgende proces: naam: Skype , id 344.
MSI (s) (7C:24) [15:36:24:232]: Product: Microsoft Office Standard 2010. Bestand C:\Program Files\Common Files\Microsoft Shared\OFFICE14\RICHED20.DLL wordt gebruikt door het volgende proces: naam: SnagitEditor , id 2592.
MSI (s) (7C:24) [15:36:26:675]: Error: cannot register 64 bit component {C2B260C7-949D-4BCB-9572-99A3F39A4E5A} on 32 bit system. KeyPath: C:\Program Files\Microsoft Office\Office14\
MSI (s) (7C:24) [15:36:27:406]: Product: Microsoft Office Standard 2010 - Update 'Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition' kan niet worden geïnstalleerd. Foutcode: 1603. Meer informatie is beschikbaar in logboekbestand C:\Windows\TEMP\MSI3e356.LOG.
MSI (s) (7C:24) [15:36:27:407]: Een update is geïnstalleerd. Productnaam: Microsoft Office Standard 2010. Productversie: 14.0.7015.1000. Producttaal: 0. Fabrikant: Microsoft Corporation. Naam van update: Service Pack 2 for Microsoft Office 2010 (KB2687455)
32-Bit Edition. Status van geslaagde/mislukte installatie: 1603.
MSI (s) (7C:24) [15:36:27:407]: Product: Microsoft Office Standard 2010 -- Configureren mislukt.
MSI (s) (7C:24) [15:36:27:408]: Het product is opnieuw geconfigureerd. Productnaam: Microsoft Office Standard 2010. Productversie: 14.0.7015.1000. Producttaal: 0. Fabrikant: Microsoft Corporation. Status van geslaagd/mislukt opnieuw configureren: 1603.
freddie

Nobody has a idea why the update is goiing wrong?
freddie

Errors x86 and x64 reinstalling MS Office 2010. Same problem with Trial MS Office 2013

Hi. I lost MS Office 2010 3 weeks ago, after I tried to rename my Owner username in the registry, following steps I found online. I have not been able to restore MS Office at all. I received Office I have attempted to uninstall
and reinstall several times, and then attempted to download MS Office 2013 trial version. Nothing works. MS Office does not show as an installed program in my Control Panel. There are Microsoft Files on my computer. Please advise.
I have Windows 7 Home Premium 64-bit Operating System, Service Pack 1.
First Pop up is Single Image permission to run. Then...
Second pop-up is MS Office 2010 Extracting Files, please wait...
Third pop-up is Setup Errors. Setup is unable to proceed due to the following errors: To install and use this product, you must be running one of the following operating systems:
x86 platform Windows 7, Windows Vista SP1, Windows XP SP3, Windows Server 2003
x64 platform Windows 7, Windows Vista SP1, Windows Server 2008
Correct the errors listed above and re-run setup

Hello,
This issue occurs when one of the following conditions is true:
The operating system on which you are trying to install Office 2010 does not meet the system requirements for the product.
The Office 2010 Setup program (Setup.exe) is configured to run in compatibility mode.
Please check your environment to see if it meets the system requirements for Office 2010 or the Setup.exe is happen configured to run in compatibility mode.
Detailed steps, please refer to this page:
http://support.microsoft.com/kb/2267642/en-us
Thanks,
Ethan Hua CHN
TechNet Community Support

Osa.exe Missing From Office 2010

Has osa.exe been removed from Office 2010? I can't seem to locate it. My installation was done as a custom install and selecting all options except for Access and Visio Viewer. Office is installed on Win 7 Enterprise x64.
I tried to copy osa.exe from a machine with Office 2007 but when I run it with -n I get an error that says, "The operating system is not presently configured to run this application"
John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Nevermind, I found my own answer. I really like having "create new office document" pinned to my start menu. I guess that just no longer an option.
Office Startup Assistant
Although turned off by default in 2007 Microsoft Office system, the ability to create a new Office document from the
Start menu, or Office Startup Assistant (OSA), is completely removed in Microsoft Office 2010. Users can no longer manually turn on the feature in the
Start menu through Office 2010 setup or open a dialog box to create a new document in an Office 2010 application.
This feature is replaced by the ability to create a new Office document for each Office 2010 application from the Microsoft Office Backstage by clicking
New and then creating the document. In addition, the improved functionality is compatible with the 64-bit version of Office 2010.
John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

Upgrade Office 2010 Standard to Office 2010 Pro Plus using Config.xml

Hello,
I am upgrading Office 2010 Standard to Office 2010 Pro Plus. But after using the below config pro plus did get installed but both versions of Office 2010 ( Stand and Plus ) show up on the machines. I want only Office Pro plus to appear.
The second issue is that even after uninstalling Office 2010 Standard from the Control panel the Office shows activation of both ( Going to --File ---Help)
How can I edit this config.xml to remove office 2010 Standard first and then upgrade to Office 2010 Pro Plus?
<Configuration Product="ProPlus">
<Display Level="None" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />


<PIDKEY Value="aaaa-aaa-aaa-aaa" />
<COMPANYNAME Value="XYZ Co." />
<Setting Id="AUTO_ACTIVATE" Value="1" />







</Configuration>

Hi,
Here is not a Config.xml solution, but we can use it as a workaround, basically automate the uninstallation of Office 2010, reboot the computer and then deploy Office 2010. You may find the following article useful if you need more info on that.
http://blogs.technet.com/b/odsupport/archive/2011/04/06/how-to-perform-an-uninstall-upgrade-to-office-2010.aspx
Regards,
George Zhao
TechNet Community Support

Microsoft Mail not working with Windows 7 & MS-Office 2010

Dear All
I have a client who is using Microsoft Mail for their internal mailing. They have been using MSoffice ( Outlook) for this purpose for last so many years.
We have found that Microsoft Mail does not work with Windows 7 and MS Office 2010 combination.
When you try to configure it given error 0x8004110.
When we tried with different versions, we found that if you install Office 2007 it works. If you try Office 2007 and then Office 2010 and remove Office 2007, it still work. But Then it is treated as 2 installations of Msoffice on the same computer.
I need to know whether this is right from Licensing perspective. We 'll be using single copy of office but it may seems as we have installed Office 2007 & office 2010 on same computer.
--Shekhar

We have found that Microsoft Mail does not work with Windows 7 and MS Office 2010 combination.
When you try to configure it given error 0x8004110.
Windows 7 is a supported operation system for Office 2010. At what exactly point will you get the specific error?
Is that a Click-To-Run version of Office 2010? By default, for MSI-based version of Office, when you upgrade existing Office 2007 to Office 2010, the earlier version of Office will be removed:
http://office.microsoft.com/en-us/excel-help/keep-earlier-versions-of-office-programs-when-installing-office-2010-HA102597134.aspx
For licensing advice, as <Don> suggested above, you should contact your local Microsoft customer support or reseller.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Installation Malfunction (Windows Vista and Microsoft Office 2010)

I was uninstalling the program from my computer so I could clean it out completely and while I was uninstalling it the computer shut down (got unplugged) and then when I turned it back on it wouldn't let me finish uninstalling it. I tried to reinstall it
and it says I couldn't because it was still on there, and wouldn't let me uninstall it either. I uninstalled every part of it but the actual file "Microsoft Office Professional Plus 2010" and it will NOT allow me to uninstall it. When I click on
it a message pops up saying "The language of this installation package is not supported by your system."
I have a 2009 or 2010 Dell Inspiron with Windows Vista. I have enough space on my computer for the program and no viruses. I've been trying to reinstall this program all day, can someone please help me?

Your last uninstallation is not completed, and you are left with a partially Office 2010 on your computer. I would suggest you to use Microsoft Fix it tool to remove any Office 2010 traces。
For details, please refer to this article:
http://support.microsoft.com/kb/971179 (This article explains how to uninstall 2003, 2007 or 2010 Microsoft Office suite by using Fix it, if you cannot uninstall it by using the
Add or Remove Programs or Programs and Features
feature in Control Panel.)
Please have a try and let’s know if it works for you.
Thanks,
Ethan Hua CHN
TechNet Community Support

"An Office 2003 installation on your computer is corrupted and setup cannot continue" error on Office 2010 Pro install

I am currently trying to install Office 2010 Pro Plus onto my machine that has Access 97 and Access 2003, Visio 2003, Excel 2003, PowerPoint 2003, and Word 2003 installed. I need to keep the previous versions of Office installed as they are used for development
work. When I try installing Office 2010 I've stopped with the following error message: "An Office installation on your computer is corrupted and setup cannot continue. Remove or repair the Office 2003 product and re-run setup." I can't remove and
repair doesn't seem to do anything. Most posts suggest removing previous office versions or deleting/altering the MS Office registry keys (which would damage the previous versions of Office). Is there a solution to install Office 2010 independently of any
other version of Office installed?

I figured out a method to finally install Office 2010 bypassing the error stated in the title, by manually removing all the keys that included the term "Office 2003" from the Windows registry.
I share my fix with more details and pictures step by step here :
Link
Please note that you need to be very careful when manually editing the Windows registry as it may cause problems to your operating system and even cause a massive failure requiring you to re-format your disk.
Feel free to use my fix at your own risk. I will not be held responsible for any damage caused or data loss.

Microsoft Office 2010 encountered an error during setup: With No error codes/

Hello Everybody.
I am trying to deploy Office 2010 on a windows 7 Machine.. This machine has more then what it needs for hardware to run the software so I know it is not hardware related. At the end of the Install the installers hestiates and begins rolling back and finally
providing "Microsoft Office 2010 encountered an error during setup:" but does not provide any error codes what so ever.
I have tried upgrading, Fresh installs, side by side installs, Safe mode, Clean boot, Local admin accounts and other domain accounts. I have also tried numerous so called "fixes" but still get nothing. Sadly after the 2010 install fails 2007 no longer works
so each attempt is abit time consuming. Any Ideas out there that might solve issue ?

Hi,
First try uninstalling all your Addins include connector to test the result.
If not help, try the following steps:
1) Create a new administrator account.
2) Log on and launch the installer.
If things don't quite work perfectly now:
3) If you receive errors accessing your ProgramData folder, use the TakeOwnership registry hack to take control of the entire ProgramData folder, and if needed, create a "Microsoft Office"
folder with "Microsoft Office 2010 Tools" inside it under %programdata%\Microsoft\Windows\Start Menu.
4) Your error may return at the end of the installation, but don't worry, it's finished and Office is now installed. Switch user (don't log off!) and go back to your own user. Double-check
that everything works. Now, to turn off your computer, press and hold the power button for five seconds. This will force the computer to shut down instantly, which will close the installer with the error without giving it the opportunity to roll back its changes.
Sincerely,
Harry

Using Poweshell Add-Computer on Script startup

Is it possible to user Add-Computer in a Startup script in windows2008r2?
The script works after the computer has been boot, however when we added into the startup script it fails.
Any other way to do this on startup

Let me explain a little bit more the question, I know I wasn't clear.
I have a EC2 AMI (Amazon Image) which has things preinstalled. Windows instances are created using the image.
As part of the image we have some startup script that perform tasks given the instance. As part of this initial setup we want the instance "auto" register to the AD server.
Using a powershell script we able to detect whether the instance is part of the domain, if not we added to the domain using Add-Computer. This means that only when the instance is created the script will register to AD, otherwise it will ignore the command.
A snipped of the script is:
if ((gwmi win32_computersystem).partofdomain -eq $true) {
//DO other things since it is already joined
}else{
$username = 'user';
$domain = 'domain.com';
$password = 'pass';
$credential = (New-Object System.Management.Automation.PSCredential ($username, (ConvertTo-SecureString $password -AsPlainText -Force)))
add-computer -domain $domain -credential $credential -OUPath '#{node["ad"]["ou_string"]}'
The script is not the issue. The question is when/where to run the script on startup?
Any suggestions?

When trying to unistall office 2010 my computer restarts itself.... HELP!

When I try to uninstall office home and student 2010 my computer restarts itself approx. 1 min after. how do I get rid of this? I have a sony vaio t series.....

Hi,
We can try to use Program Install and Uninstall Troubleshooter
to uninstall Office. Or we can manually remove Office 2010. For more information, please refer:
http://office.microsoft.com/en-us/support/how-to-uninstall-or-remove-microsoft-office-2010-suites-HA104027750.aspx
Regards,
Steve Fan
TechNet Community Support

Office 2010 setup thru computer startup script

Similar Messages

Maybe you are looking for