Steven Westwell’s blog

My outlook on a few things of interest to me, and hopefully you.

Office 2007 + OSD + DFS issue

Posted by Steven Westwell on February 11, 2008

Issue

Whilst deploying office 2007 via SMS OSD, with an updates location specified in the config.xml set as a DFS path (Windows 2003 SP2), Office 2007 fails to install intermittantly. In the below situation Office 2007 has been cached in the LIS (Local Installation Source) of our Windows Vista Image / .wim. 

When deploying the image to a new machine we run c:\msocache\all users\{[insert guid later]}\setup.exe /config config.xml to install Office 2007 from the locally cached source.  This config.xml stipulates the language to install office in and the update locations to check for additional MSP files to be applied during the install.

Expected Behaviour 

Office 2007 parses remote supdatelocations listed in the config.xml then the locally cached msp files.

Synopsis 

The Office installer picks up all supdatelocations listed in the config.xml

Config.XML Extract:

<SetupUpdates CheckForSUpdates="Yes" SUpdateLocation\\DFSStore\ParentFolder\OfficeUpdates\ />
<AddLanguage Id="de-DE" ShellTransform="Yes" />
<Logging Type="Verbose" Path="c:\minint\" Template="MSOVerboseLog-(*).txt" /> 

The Beginning of the log file showing supdatelocations parsed:

PERF: TickCount=471325 Name=OBootStrapper::Run Description=Begin function
Operating System version: 6.0.6000 . Platform ID: 2
Running on a 32-bit operating system.
Command line: setup.exe /config "c:\msocache\config.xml"
Parsing command line.
Handling command line option: /config
Config XML file specified: c:\msocache\config.xml
Parsing config.xml at: c:\msocache\config.xml
Preferred product specified in config.xml to be: PROPLUS
Parsed AddLangauge: CultureTag with value: de-de in config.xml.
Parsed AddLanguage\ShellTransform: true.
Logging type verbose specified in config.xml.
Log directory: c:\minint\ specified in config.xml
Log file template: MSOVerboseLog-(*).txt specified in config.xml
Display level basic specified in config.xml.
Show modal dialogs specified in config.xml.
Hide completion notice specified in config.xml.
Auto accept license specified in config.xml.
PIDKEY element successfully parsed in config.xml
COMPANYNAME specified in config.xml.
SUpdateLocation path specified in config.xml: \\DFSStore\ParentFolder\OfficeUpdates\
Log level changed from: Standard to: Verbose
Searching for best setup controller dll to load...
Checking for setup controller dll at [\\DFSStore\ParentFolder\OfficeUpdates\].
Checking for setup controller dll at [c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\Updates].
Checking for setup controller dll at [c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C].
  Found setup controller dll at [c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\OSETUP.DLL].
  Version [12.0.4518.1014].
Verify file signature in "c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\setup.exe"
"c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\setup.exe" is verified to be a valid file
Verify file signature in "c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\OSETUP.DLL"
"c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\OSETUP.DLL" is verified to be a valid file
Using setup controller dll at [c:\MSOCache\All Users\{90120000-0011-0000-0000-0000000FF1CE}-C\OSETUP.DLL].
PERF: TickCount=489655 Name=OBootStrapper::Run Description=Calling RunSetup
Opening log file c:\minint\MSOVerboseLog-(20080128154209130).txt.
=========================================================================

However, Later, roughly 3470 lines further into the log, we see two different types of behaviour

a) Office installation suceeds

From the following log file it looks like the DFS share has not been searched, but the local MSP files have been applied.

Searching for patches in: c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000000.msp
Patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000000.msp is applicable for the current chained install.
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000001.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000002.msp
Patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000002.msp is applicable for the current chained install.
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000003.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000004.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000005.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000006.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000007.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000008.msp
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000009.msp
Patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch00000009.msp is applicable for the current chained install.
Discovered patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch0000000a.msp
Patch c:\MSOCache\All Users\PROPLUSOFFICE12PATCH-C\Patch0000000a.msp is applicable for the current chained install.

b) Office installation fails

We see that Office has attempted to read from the DFS share but errors.

Searching for patches in: \\DFSStore\ParentFolder\OfficeUpdates\
Error: file search failed ErrorCode: 5(0x5).
Error: file search failed ErrorCode: 5(0x5).
Catalyst execution finished: 01/28/2008 15:42:13.  Return code: 30015.  Exception caught: ErrorCodeOnly.
PERF: TickCount=494507 Name=RunSetup Description=End function
=========================================================================
Setup temp foler set to [C:\Windows\TEMP\Setup00000130].

Why?

In a word, permissions, the account SMS is attempting to install Office 2007 with does not have read access to the DFS share where the MSP files are stored.  By giving the “Domain Computers” group read permissions on the share Office installs without incident every time.

Other network share types tested show that a lack of permissions on a standard share logged as per the failed logs, except that the install continues on to search additional supdatelocation’s without failing.

This may only be an issue with DFS on Windows 2003 SP2, and possibly be due to other environmental circumstances i.e. poor network connectivity and time outs.

If anyone else experiences similar issues with the Office 2007 installer accessing DFS shares I would be interested to hear about it.

Steven

Posted in vista | Tagged: , , , , , , , | Leave a Comment »

Kodo

Posted by Steven Westwell on February 6, 2008

Kodohttp://www.kodo.or.jp 

 Last night we went to see Kodo, a group of Japanese Drummers, and they were great!

I got home from work and was shattered, not really feeling in the mood to be going to a concert, but tickets had been bought and I was interested to see Kodo live.

Considering we only picked up tickets last minute, our seats were central and we had a really good view of the stage.  The show was split into two halves entitled “Spirit” and “Dance”.

Spirit

the first half of the show appeared to focus more on the music, drumming and occasional singing.  all of which was very very good.  There were several very epic displays of what could be achieved with some very clever techniques, which both sounded and looked very awsome.

Dance

The second half of the show had a bit more ceremony about it and contained a bit more showmanship.  This half of the show also included a huge drum and a serious amount of stamina and strength which was very very impressive.

 The show ended with all 15 members of Kodo present that evening playing and several rounds of applause.

Summary

Awsome show!

Kodo Blog: http://heartbeat.cocolog-nifty.com/kodo_blog/

It’s definately worth catching Kodo live if they are playing in your area, and if they are not pick up their cd! 🙂

Steven

Posted in Japan | Tagged: , , , | Leave a Comment »

Japanese Keyboard on Vista

Posted by Steven Westwell on February 6, 2008

Problem?

so as part of our global deployment of Windows Vista, we found that the Japanese users of the Japanese IME had an issue with the keyboard layout being incorrect.  The hirigana, Katakana and romanji where correct for the most part, however the symbols “, @, (, ) and * etc were in the US locations, not as they should be on a Japanese keyboard.

Others in the UK will be familier with typing <shift> + 2 expecting ” and getting @, well this is the same thing fundamentally, just complicated with the IME layout not being something that can be switched by the users locale.

Solution?

After digging around I managed to find a few excellent posts on this problem and showing the solution for Windows NT, 2000, XP etc… It would appear to be one of those consistent issues that has been with the OS for a long time.

It was enough to point me in the right direction and I thought it was only fair to post the Vista specific solution here.

The problem is the IME seems to get its keyboard layout directly from the keyboard driver, rather than the keyboard locale settings that typically control layouts.  In order to fix this the Japanese keyboard driver must be selected manually.

below are the step by step instructions for an english OS, I may attempt to translate into Japanese soon, or at least include screenshots from a Japanese client to show the dialogue boxes:

  1. Open the Device Manager
    1. Open the start menu
    2. Right click on computer
    3. Select manage (Entering PA account details when prompted)
    4. Select device manager
  2. Change the Keyboard Driver
    1. Open the keyboard tree
    2. Right click the keyboard
    3. Select “update driver software…”
    4. Select “browse my computer for driver software”
    5. Then select “let me pick from a list of device drivers on my computer”
    6. Uncheck the “show compatible hardware” checkbox
    7. Then choose the (Standard Keyboards) as Manufacturer and Japanese PS/2 Keyboard (106/109 Key) as Model
    8. Then select next
    9. The driver will then be installed, then click close

After the next reboot the default layour will be the Japanese layout, and the ” symbol will be in the correct place when using the Japanese IME.

Thanks to:

Cameron Beccario: http://blogs.msdn.com/cambecc/archive/2005/01/24/359359.aspx / http://journal.nullschool.net/

and

Michael Eng: http://www.daydream.org.uk/meng/jpkbnt4/

Cameron’s blog was an interesting read, and also lead me to find a very cool and interesting to read about Japanese language school: http://www.yamasa.org/acjs/english/index.html

Regards,

Steven.

Posted in Japan, vista | Tagged: , , , , , , , , , , | Leave a Comment »