Advertisement

01.14.2008 at 09:31AM PST, ID: 23081388
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.2

Easiest & Simplest way to deploy (upgrade) Office 2007 on Windows XP client machines?

Asked by ThinkPaper in Deployment Software for Development, Microsoft Office Suite, Active Directory

Tags: , , , ,

Hey experts, I'm in charge of upgrading our client pcs from Office 2003 to Office 2007. I basically need a simple answer here. I don't have SMS and I'm hesitant to use BDD.. and was thinking of pushing this out thru GPO but read that there were issues with this as well?

What's the best (ahem simplest) way to push Office 2007 to all our pcs? Would it be logon script, straight GPO installation?
I'm relatively new to GPO and have only done some minor things here and there so I need a dumby down version here. I don't care too much about the customization besides the basics (automatic serial key, silent install)

From what I understand:
1) GPO - configure Config.xml and create GP and link to computer OU. What security setting do I need to configure to get this working? I'm confused as to what privileges are needed - authorized users, computers?? As I understand it, this doesn't remove Office 2003 but installs beside it?
2) Script - is this more reliable as we could possibly test for existance of Office 2k3/2k7 and install from there? Examples?
3) SMS -  I don't have SMS so no go.
4) BDD - or WIMs.. I'd rather not create an image just to get push out Office 2k7. I've had issues with BDD in the past and wouldn't like to use it until I get a full grasp on how to actually use and understand it properly.

Please don't start throwing me the standard links to MS Tech websites on Office 2k7 GPO deployment.. I've read them... =/

I have run some test GPOs with Office 2007 on a few machines but it doesn't seem to be running.. (i had it run once on my pc (with Office 2k7 already manually installed on it, GP kicked in and I saw the dialog boxes stating it's installing but came to find it out actually uninstalled my Office 2007 after reboot) so would appreciate any help you can offer.

My config.xml looks like this so far.. real basic...

<Configuration Product="Enterprise">

      <Display Level="Basic" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />
      
      <PIDKEY Value="ABACSDSFSDFDF" />

      <USERNAME Value="User" />
      
      <COMPANYNAME Value="MyCompany" />
      
      <DistributionPoint Location="\\swn005\Software\Installation Software\Office\Office 2007 Enterprise" />
      
      <Setting Id="Reboot" Value="IfNeeded" />
      
      <!--- <Command Path="msiexec.exe" Args="/i \\Software\Installation Software\Office\Office 2007 Enterprise\Enterprise.WW\EnterpriseWW.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --->

</Configuration>


BTW if i'm doing this via GP.. do I need to do something security wise to allow this to occur? I read conflicting things about adding Computernames vs Users to the security filter? (again i know nothing about that either). Why would I need to add computernames since I already linked the GP to a computer OU?! That didn't seem to make sense to me.

Help!Start Free Trial
[+][-]01.14.2008 at 09:40AM PST, ID: 20654841

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 14-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]01.14.2008 at 10:04AM PST, ID: 20655036

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 14-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]01.16.2008 at 09:49AM PST, ID: 20674160

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 14-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]03.04.2008 at 08:47AM PST, ID: 21042598

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 14-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]03.11.2008 at 11:33AM PDT, ID: 21098601

View this solution now by starting your 14-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Deployment Software for Development, Microsoft Office Suite, Active Directory
Tags: Microsoft, Office 2007, 2007, Deployment of Office 2007, upgrade from Office 2003 to 2007, GPO, script
Sign Up Now!
Solution Provided By: ThinkPaper
Participating Experts: 3
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-43 / EE_QW_2_20070628