MSFN Forum: Unattended [UpdatesToOeminfoFile] - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Unattended [UpdatesToOeminfoFile] Rate Topic: -----

#1 User is offline   Jeweliettev 

  • Group: Members
  • Posts: 5
  • Joined: 25-February 04

Posted 06 March 2004 - 09:57 PM

Can't seem to get "UpdateSystem" in Winbom file to work as required.
As documented in OPK usersGuide under "Reference\Oeminfo.ini\oemspecific" section, M$ example the following:

***********************************************************
Include this section in Winbom.ini:

[UpdateSystem]
UpdateInis = UpdatesToOeminfoFile

[UpdatesToOeminfoFile]
%WINDIR%\System32\Oeminfo.ini, OEMSpecific, , Submodel = 456A0123
%WINDIR%\System32\Oeminfo.ini, OEMSpecific, , SerialNo = 12345678
%WINDIR%\System32\Oeminfo.ini, OEMSpecific, , OEM1 = Built from image 20010630
%WINDIR%\System32\Oeminfo.ini, OEMSpecific, , OEM2 = Factory location: Redmond, Washington
When Sysprep processes this Winbom.ini file in Factory mode, it writes the following information in Oeminfo.ini:

[OEMSpecific]
SubModel = 456A0123
SerialNo = 12345678
OEM1 = Built from image 20010630
OEM2 = Factory location: Redmond, Washington
***********************************************************
While being happy with all of the rest of my fully unattended installations of XPH & XPP, I am now at the tweaking of minor details stage. I've tried the lines detailed above within the fdd winbom.ini file - this gave an error msg, tried hdd cfgset winbom.ini file - this also gave an error msg. Neither winbom.ini files changed the contents of Oeminfo.ini

The details above were copied directly from M$ OPK usersguide into my winbom.ini files, i was kinda hoping they would just need to be changed for my details once tested and working. Not so.

My cfgsets are run over a network from tech pc to newbuild. Boot with M$WinPE Disk & fdd in newbuild.

Anyone got any ideas or is the answer staring me in the face and I'm just missing it.


#2 User is offline   likuidkewl 

  • [Centos~]$
  • PipPipPipPipPip
  • Group: Members
  • Posts: 960
  • Joined: 16-September 03

Posted 06 March 2004 - 10:29 PM

Have you posted a question here :
<http://communities.microsoft.com/newsgroups/default.asp?icp=oem&newsgroup=microsoft.communities.oem.windowsxp>
They are the preinstall MS Guru's and are more than willing to help out if they can.

#3 User is offline   Jeweliettev 

  • Group: Members
  • Posts: 5
  • Joined: 25-February 04

Posted 06 March 2004 - 10:59 PM

Cheers likuidkewl
I've dropped a dupe of this post on M$ newsgroup as you suggested.

#4 User is offline   likuidkewl 

  • [Centos~]$
  • PipPipPipPipPip
  • Group: Members
  • Posts: 960
  • Joined: 16-September 03

Posted 06 March 2004 - 11:53 PM

Glad o help out they will post a response monday around 9-10 PDT.

#5 User is offline   Jeweliettev 

  • Group: Members
  • Posts: 5
  • Joined: 25-February 04

Posted 08 March 2004 - 10:59 PM

Minor update on the "UpdateSystem" in Winbom.ini if it's of any use to anyone else.
Managed to get it working with the assistance of Erik @ Microsoft OEM System Builder ThanX for the sugestion likuidkewl.

In short I was missing the header "[OEMSpecific]" within my oeminfo.ini file, when this is placed below the section "[Support Information]" then the info gets written into the file when Sysprep -Factory is run.

The only other recommended amendment was to change my "%WINDIR%" path for absolute path - so:
%WINDIR%\System32\Oeminfo.ini, OEMSpecific, , Submodel = example
C:\windows\system32\Oeminfo.ini, OEMSpecific, , Submodel = example

It has been tested and works the way I wanted it to.

Cheers :)

#6 User is offline   likuidkewl 

  • [Centos~]$
  • PipPipPipPipPip
  • Group: Members
  • Posts: 960
  • Joined: 16-September 03

Posted 09 March 2004 - 08:29 AM

Nice! Glad to see you got it working. :)

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy