[ms office - 2010] Problems installing Office 2010

[DLW13]

Hi,

 

We have recently deployed Office 2010 Professional Plus school-wide using a batch file.

 

The batch file removes all previous versions of Office (We had Office 2007 installed) then installs Office 2010 silently.

 

Overall the deployment went well, however we have had problems with 4-5 PCs.

 

The PCs that were not successful either; Still have Office 2007 installed and broken links to Office 2010 or Have neither Office 2007 or Office 2010 installed.

 

Things we have tried:

 

Uninstalling remaining traces of Office 2007 using Revo Uninstaller

Running CCleaner (Cleapup & Registry clean)

Using Windows Cleanup

Re-installing Office 2007 then attempting an upgrade to Office 2010 manually (Installer gets 3/4 of the way through then displays 'Microsoft Office Professional Plus 2010 encountered an error during setup)

Attempting to install Office 2010 manually (displays 'Microsoft Office Professional Plus 2010 encountered an error during setup)

GPUPDATE /FORCE to force the install again

Running the Microsoft Fixit scripts

 

Does anybody have any other suggestions?

 

We do have the capabilities to re-image these machines, however if there are more PCs than we are already aware of this could become a big task.

 

Thanks!

Edited March 4, 2011 by ZeroHour

[cromertech]

I had this too but couldn't be bothered to fix, just reimaged the faulty computers (although it was only 2 and both were msi wind netbooks)

[DLW13]

Managed to get it to work by following this: Repairing and re-registering the WMI

[mickeyh080]

Hi,

I am planning to role out Office 2010 site wide this summer and have started testing. Unfortunately the startup script available from the Microsoft site seems to fail in our current set up with error code 0. A manual install from the network share works fine. Would you mind sharing your method for the install as have to attempt this role out on a tight budget so install via script or Batch file would reduce the cost of buying in System Center Essentials.

[sukh]

Hi

 

Have read here.

 

Deploy Office 2010 by using Group Policy computer startup scripts

 

Sukh

[mickeyh080]

Thanks Sukh for the reply.

 

Yes I have used the info from this link and altered the desired settings in the script for the network share location and have tweaked the GPO time out settings to 2700 (plenty of time for the install). Have tested the install maunually on a test desktop and the install works fine logged on as local admin the OCT file even cutomises the install as required. Its just I don't really want to manually install on a few hundred computers so need to get the start up script to work. On observing the test machine on start up it goes through the normal screens setting up network connections, apply computer policy and then as normal goes to the login screen with minimal delay.

 

The error in the log files folder just states "11/04/2011 8:42:26.64 Setup ended with error code 0."

 

This doesnt really help me much so any ideas would be much appreciated.

[sukh]

Hi

 

Can you see if the GPO is actually being applied? Run gpresults /z >c:\policy.txt on a PC joined to the domain and post/pm

 

Sukh

[mickeyh080]

Hi

 

Yes Sukh, had tried this and yes the policy is being applied.

 

Microsoft ® Windows ® XP Operating System Group Policy Result tool v2.0

Copyright © Microsoft Corp. 1981-2001

 

Created On 11/04/2011 at 13:06:30

 

 

 

RSOP results for ADMIN-017\Administrator on ADMIN-017 : Logging Mode

---------------------------------------------------------------------

 

OS Type: Microsoft Windows XP Professional

OS Configuration: Member Workstation

OS Version: 5.1.2600

Domain Name: School

Domain Type: Windows 2000

Site Name: School

Roaming Profile:

Local Profile: C:\Documents and Settings\Administrator

Connected over a slow link?: No

 

 

COMPUTER SETTINGS

------------------

 

Last time Group Policy was applied: 11/04/2011 at 12:48:40

Group Policy was applied from: SRV-001.domainname

Group Policy slow link threshold: 500 kbps

 

Applied Group Policy Objects

-----------------------------

Office 2010 Deployment Script Policy

Default Computer Policy

Default Domain Policy

 

The following GPOs were not applied because they were filtered out

-------------------------------------------------------------------

Local Group Policy

Filtering: Not Applied (Empty)

 

The computer is a part of the following security groups:

--------------------------------------------------------

BUILTIN\Administrators

Everyone

BUILTIN\Users

NT AUTHORITY\NETWORK

NT AUTHORITY\Authenticated Users

ADMIN-017$

Domain Computers

CERTSVC_DCOM_ACCESS

 

Resultant Set Of Policies for Computer:

----------------------------------------

 

Software Installations

----------------------

N/A

 

Startup Scripts

---------------

GPO: Office 2010 Deployment Script Policy

Name: Office2010startupscript.bat

Parameters:

LastExecuted: 11:48:47

[sukh]

Hi

 

When you mention a manual install, did you execute the "Office2010startupscript.bat" ?

Did you run the actual bat file used by the startup script? login as a user, try a domain user with sufficient rights to install application (power users may work) and execute the file?

Does this work?

 

Sukh

[mickeyh080]

Sukh

 

Slightly confused as I thought this script is run before a login is available hence its installed under a computer account not a user. Therefore running as a user would only proove that the install files are working correctly, already proven by local admin account. If the startup script is running but not installing whilst the machine starts up could this be a permission problem. My question therefore is what permissions should be set on both the GPO and the individual startup script.

[sukh]

Hi

 

This is exactly what I wanted to test. To see if the batchfile worked, this would rule out the script. As you have tested using local admin then and confirmed that all works, then I assume there are no errors with the actual scrip and therefore points towards the GPO.

 

Can you ensure that your Office 2010 Deployment Script Policy has domain computers applied to it for security filtering and then test.

 

If you are using the MSFT script on technet, have you also checked the log files for that computer?

 

Have you also, tested this GPO on another PC (to rule out a 'messy pc')?

 

Sukh

[mickeyh080]

Hi

 

Thanks for the help. Have run the script from a workstation and it runs correctly installing with customisations as per OCT file. The GPO is set to run with Domain/Computers in the filtering. The log file folder displays an entry for the test machine but just gives the following per attempt:

 

11/04/2011 15:12:32.37 Setup ended with error code 0.

 

Not sure where to go from here. But will try another computer tomorrow when back in work just as you say to make sure its not an individual pc problem.

[sukh]

Hi

 

Error code 0 means it's installed or there's another error.

 

Can you also run the Windows Installer Cleanup Utility and ensure any previous versions have been completly removed?

 

Sukh

[mickeyh080]

Hi

 

Have re-imaged the test computer and removed the previous version of office 2003. Tested this machine and again on a reboot the script still fails to install office 2010. Same error again in the log file.

[sukh]

Hi

 

Can you check to see if the domain computers or at least the computer you are deploying office to has at least read and execute permission where your office 2010 source files are on the network. Also, if the folder is shared out, make sure everyone has full control on share permission

 

Sukh

[mickeyh080]

Hi

 

The office 2010 source files have been copied to a network share (srv-001\deploy$\Office14) folder. The share permissions are Domain Computers Full Access. Security settings are Domain Computers have Read & Excecute, List Folder Contents, Read permissions. The computer when restarted starts fairly quickly i.e within a couple of minutes the login screen is available and the new entry appears in the logfiles. The script appears to be running as it generates the log entry which is at the end of the script but it seems to error for some reason hence not installing Office 2010. It would help if I could see more info on what the error 0 in the log actually refers to as having the same code for both succesful install and an error seems strange to me.

[sukh]

Hi

 

Error code 0 is fairly generic, eithet it means successful or some other error has occured. It's not detailed enough. You images, do they have a version of office installed?

 

Sukh

[eddyc]

We found it eaiser to update the image to roll out Office 2010 - the roll out via GPO\Script was taking too long and causing endless complaints. We then reimaged the whole site last summer.

[mickeyh080]

Office 2003 Professional together with the Office compatability pack

[mickeyh080]

ect

 

If I can get it to work via the script I would hope to roll it out overnight or at the weekend remotely as have full remote access to most computers. Hopefully this would not raise any issues of time. Did you have any other issues with your start up script apart from time.

[sukh]

Can you try to set the logging in your config.xml file to Verbose, under the section Logging section?

 

What is it currently set to?

 

Sukh

[sukh]

Also can you make sure that authenticated users have at least read permission to the share and files?

[mickeyh080]

Currently logging set to standard, have changed it to verbose.

 

I was wondering can the logging level of the actual startup script be changed as I believe this would give more of an idea as to whats not happening. Does the config.xml file only affect the actual office install and currently it looks like this is not even starting.

Edited April 13, 2011 by mickeyh080

[mickeyh080]

Also can you make sure that authenticated users have at least read permission to the share and files?

Already set.

[sukh]

Anything new in the logfile?

 

Also can you change Run startup scripts asynchronously and set disabled and test.

 

Sukh