Jump to content


Office 2007 SP2 or SP3 not detected


10 replies to this topic

#1 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 04 May 2012 - 09:23 PM

EDIT2: Some more strangeness..., Office 2007 SP2 was downloaded by the Office 2007 script, but it's the Italian version I think (office2007sp2-kb953195-fullfile-it-it.exe) instead of the EN version for my system (office2007sp2-kb953195-fullfile-en-us.exe). Also, SP3 is nowhere to be found.

Is there anything I can do to help?

==============================================================================

EDIT: I did some closer looking (inside the SP1 file and in the registry location that the APM file pointed to) ... and the SP1 update is listed as it should be. It is detected by the AP installer, but there's no listing SP2 or SP3, or any of the more current updates...

Is anyone else seeing stuff like this?

My first post (below) still stands. When SP3 is installed and SP1 is not, then AP still thinks that I need to install SP1.

==============================================================================

I've been having issues getting Office 2007 SP1 to be detected by AP. I checked the APM file and it points to the following location:

Current location in APM: HKLM\SOFTWARE\Classes\Installer\Patches\1CCE4AC44DBD1954F8C4AA21DAD2E395\SourceList

but I found it here:

Alternate Location: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\00002109030000000000000000F01FEC\Patches\10E57EEBF3DDF5D49BC606E956834D91

Actually, the "alternate location" was one of 21 finds in the registry. They all say the same thing -- Office 2007 SP1.

The location where all 21 can be found (in my registry) is:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\00002109030000000000000000F01FEC

The pattern to find all 21 of them seems to be:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\00002109******************F01FEC

The first of the 21 results is "00002109030000000000000000F01FEC"
Within this one is 15 sub keys, only one of which is for Office 2007 SP1. The rest is for a bunch of other office updates.

Lastly, I checked the registry location in the APM, there are definitely references to office patches there, but Office 2007 SP1 isn't one of them.

Is this normal? Is any of this stuff automatically generated and therefore hard to track?

====================================

I first noticed this when checking for updates with AP when I already had Office 2007 SP3 installed (on a different machine). It showed SP1 as not being installed (which it wasn't, only SP3 was).

Is this normal? Or is Office 2007 giving you guys a run for you money?

In the meantime, I'm gonna do some testing on my end to see if I can find definite registry paths for these updates that are consistent across all my machines.

Edited by TheArkive, 04 May 2012 - 09:50 PM.


#2 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 04 May 2012 - 10:46 PM

Well while there are plenty of people who use our service ... not many are willing to donate some time to helping the scripts along. You seem to know your way around regedit. We could use help updating those scripts if your willing. I will see if I can get you in touch with someone who can help you get a start. I can't exactly help since I don't have word. I use star office. :)

#3 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 04 May 2012 - 11:28 PM

I'd love to help! Do you have any documentation I can look at? There's a few things I'm not sure about. I noticed there isn't much documentation on the autopatcher.exe or apup.exe posted on the forum. Is that on purpose? Can I ask specific questions about the scripts and APM files? Or should those be saved for email/PM?

#4 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 05 May 2012 - 06:30 AM

ohh no we are open and want people to help, the documents were online at one time... but, I guess through trimming the pages might have been snipped a long time ago. I have them in zip form. I think I will take some time now and make them as pages again.

#5 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 05 May 2012 - 07:13 AM

http://www.autopatch...-documentation/
This is the documentation.

#6 dkdk_it

    Release Manager God

  • Release Managers
  • PipPipPipPipPip
  • 517 posts
  • Gender:Male
  • Location:Italy

Posted 05 May 2012 - 09:27 AM

@TheArkive
Have you an instant messenger? I can follow you to compile new script.

#7 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 05 May 2012 - 01:11 PM

I'm away from the computer now. I'll be back later today.

#8 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 06 May 2012 - 08:10 PM

Exactly what do you want me to focus on? Writing the download scripts? The APM's? I have a bit more reading to do if I'm going to test scripts. Your scripts seem to be downloaded automatically from your servers, so I can't test them unless the command line lets me specify the scripts. Of course I can create and test APM files.

Please let me know where you want me to focus. After I learn what I can from the documentation, I'll focus on the APM files first. If you want me to do scripts I'll need to have some kind of other arrangements I'm guessing...

Good stuff btw... I love it. WSUS Offline is good, but you guys seem to have thought of everything. You built a good framework that is not too hard to follow. Hopefully I can fill the necessary gaps. I own most of the copies of windows that your software works with. Maybe I can do more than just Office 2007 Posted Image

EDIT: Ok I just read it, I can create a script and test it :-P ... so there it is! I'll see what I can do and I'll post my results. Please let me know if you prefer me to post these results in a specific forum.

Edited by TheArkive, 06 May 2012 - 08:51 PM.


#9 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 07 May 2012 - 11:20 AM

> When SP3 is installed and SP1 is not, then AP still thinks that I need to install SP1.
easy fixable. you need create an extra registry detection in the previews sp modules with the detection of the following ones. the problem: in order to this work, you must have at least one file detection (even a bogus one) or it will work in "this and this" module". to clarify, an sample taken from my personal module for adobe reader:
FilePath=progfiles:\Adobe\Reader 10.0\Reader
FileName=AcroRd32.exe
FileVersion=ANY

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1046-7B44-AA1000000001}
KeyName=DisplayVersion
KeyValue=10.1.0

RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1046-7B44-AA1000000001}
KeyName=DisplayVersion
KeyValue=10.1.1

RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1046-7B44-AA1000000001}
KeyName=DisplayVersion
KeyValue=10.1.2

RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1046-7B44-AA1000000001}
KeyName=DisplayVersion
KeyValue=10.1.3

so, if you do something similar, sp1 will know that sp2 and sp3 are in place. i've tried locate an suitable detection for the sp, but the closest thing that i've found was this (for office 2007 sp3):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\D94C8360B8BB1DC41B1950E0F8237563\00002119210000000000000000F01FEC
ComponentVersion
12.0.6607.1000

this detection will look for mso.dll. so, an idea for an file detection:
FilePath=commonfiles:\microsoft shared\OFFICE12
FileName=MSO.DLL
FileVersion=12.0.6607.1000

given that, i bet that you will have something similar for sp2 and sp1

sorry, right now, i don't have enough space to create an vm at home and look for an detection for sp1 and sp2

[]s

Edited by Cristiano, 07 May 2012 - 11:22 AM.


#10 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 07 May 2012 - 01:23 PM

I'm starting my trial and error now, to see if I can learn the APM stuff, download scripts, and messing with registry detection.

EDIT: *removed*

EDIT2: Sorry this should go in the documentation thread!

Edited by TheArkive, 07 May 2012 - 01:37 PM.


#11 TheArkive

    Member

  • Members
  • PipPip
  • 14 posts
  • Gender:Male
  • Location:The Construct

Posted 07 May 2012 - 06:57 PM

In Win7, the version of office suite installed can be confirmed in 3 reg keys (on my installation x64):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-002A-0000-1000-0000000FF1CE}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-002A-0409-1000-0000000FF1CE}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-0116-0409-1000-0000000FF1CE}

Each one of these mentions the version number and all should be the same. With the help of this page http://support.microsoft.com/kb/928116 ... that should make determining the version rather easy. Is this old news? If so I'm guessing the earlier versions of windows don't offer the same consistency (which would suck). I'll get around to making some virtual machines and finding out :-P

EDIT: In WinXP SP3 (x86) the key for the version of office installed seems to be:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{90120000-0030-0000-0000-0000000FF1CE}

Can anyone else confirm these keys as the same?

Edited by TheArkive, 07 May 2012 - 08:29 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users