The Realm of the Verbal Processor

Jarvis's Ramblings

Installing Vista Games via CMD Line

By default when you install Vista Business, it does not install the built in games (Chess Titans, Freecell, Hearts, Inkball, Mahjong Titans, Minesweeper, Purble Place, Solitaire, and Spider Solitaire). Many businesses like it that way and want to keep it that way. I don’t. If someone has a laptop and they want to play Chess or Solitaire at home…I don’t care…knock yourself out. What I don’t want is someone coming to me complaining that the games aren’t there. I want the games to be part of our default install. (Other admins can argue that point if they wish…that’s the decision I made for my environment.)

So…with my default install being completely driven by SCCM Task Sequences…I need to find a way to put that in a task sequence. In a Task Sequence, I need to be able to do this with a “Run Command Line” task. So…what is that command line?

First..it’s not easy to locate. I hunted way to long for this bit of info. I found other cryptic webpages about similar items, but nothing specifically addressing this one…imagine that…not many people want to install Vista’s games via the command line…who woulda thunk it? I finally figured it out through a bit of trial and error. That magic command line is:

pkgmgr.exe /iu:InboxGames /quiet

Note: “InboxGames” is case sensitive.

[Note: I have also found another command line for this: “ocsetup.exe InboxGames /quiet”. ]

What I would really like at this point is to have a command line way of uninstalling “Purble Place”. While I don’t mind if our staff play chess, solitaire, etc…I really don’t want them letting their kids play Purble Place on their work laptop. Anyone know how to do this?

Also…the way to point and click to do this is by opening up “Programs and Features” from the Control Panel, then clicking on “Turn Windows features on or off”, then checking the Games checkbox.

March 8, 2008 Posted by | computers, ConfigMgr | , , , , | Leave a comment

Build and Capture Task Sequence Failure

I have fought with this before and didn’t figure it out. Been fighting with it again and finally made an educated guess that has since been backed up by finding a thread to support my findings.

I created a Task Sequence in SCCM to “Build and capture a reference operating system image”. I am using the Vista SP1 DVD that I imported into Operating System Install Packages. It gets part of the way through the install, and then fails. By opening a command prompt on the machine running the Task Sequence (F8), I was able to look at the log files. In looking at the x:windowstempsmstslogsmsts.log log file, I saw an entry that stated “Windows Setup Failed, code 31”. That was followed by “Exiting with code 80004005“. Not a lot of help. Then I found the x:\windows\temp\smstslog\windowssetuplogs\setuperr.log log file. That contained the following lines:

Callback_Productkey_Validate: EditionID for product key was NULL.
Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
Callback_Productkey_Validate_Unattend:Invalid product key; halting Setup.[gle=0x00000490]
Callback_Productkey_Validate_Unattend: An error occurred preventing setup from being able to validate the product key; hr = 0x80300006[gle=0x00000490]

Now…I know that my volume license product key is good. I’ve been using it for a long time. Just for grins I popped the Vista DVD in a spare computer and confirmed it. Why is it telling me the license key is invalid?

So here comes the educated guess. I modified the Task Sequence to not use a Product Key…just left that field blank. Hmmm…the install works perfectly fine. That led me to search on something different and find this thread. Basic gist is that if you are using a Task Sequence to install an OS using an Operating System Install Package, you should NOT specify a product key. Perhaps that is documented somewhere, but I haven’t seen it. It is however doggone frustrating to have wasted as much time as I have on this problem.

February 27, 2008 Posted by | ConfigMgr | , , , | 16 Comments