The OEM systems builder kit [which rocks, by the way....], reflects: [Per BOB Wired - YES, BOB lives, LOL ]
Microsoft made some changes to Microsoft Windows desktop operating system software related to the way in which Internet Explorer (IE) handles some web pages (IE Active X update, KB912945). This update to Internet Explorer technology relates to Microsoft's involvement with the Eolas Technologies and the Regents of the University of California v. Microsoft patent case (Eolas v. Microsoft).
Microsoft has made new end item part numbers for affected Windows XP, Windows Server 2003, and Small Business Server 2003 products to implement the Internet Explorer Update. Client SKUs include Starter Edition, Home Edition, Professional, Tablet PC Edition, and Media Center Edition.
View the IE Active X update description, and the MSDN article at Activating ActiveX for more information on the changes.
With the kit, builders may easily assemble and maintain their images and ensure they are
lawfully supporting the required "Out of the box experience" builders must provide. One may build images, recovery CD's and customize the OPK in about any way they wish - so any argument that builders cannot control what their systems do, or what defaults they have is pure BS. For example, a builder may slip in and set as the default, just about any default applications they wish and present an anything but MS experience if they wish - FF, Real, QT - whatever they want to do.
Builders may also function as integrators and if they are not direct to consumer shippers, they needn't deliver systems within these restrictions, so long as they ENSURE they are shipping lawfully loaded systems using genuine MS SW.
For OEM builders there is a lesser known OEM Backdoor at, http://login.live.com/login.srf?id=25126&ru=http%3a%2f%2foem.microsoft.com%2fscript%2fredirector.aspx%3f404%3bhttp%3a%2f%2foem.microsoft.com%3a80%2fBackRoom
Within the Partner Channel and using the kits which arrive with the Action Pack, one is provided with a very good and complete set of tools. Using them and with a little practice,
just about any good engineer can provide as good and professional a build as any very large OEM - even better since small OEM's can build very specific systems with more diverse hardware. With the extender to the OPX [the OPX] one may,
From some of what one may access:
The US Partner Technology Strategists and Worldwide System Builder Channel teams are pleased to announce version 1.0 of the OPK eXtender (OPX). The OPX is a powertoy that:
Adds system builder-specific features to the OEM Preinstallation Kit (OPK).
Can be used with or without the OPK.
Can be used to build fully customized PCs using the CD-based preinstallation method if you do not have the OPK installed.
Runs Most Frequently Used Tools, Manages Configuration Sets
OPX adds a management layer to the preinstallation infrastructure created with the OPK. With the graphical user interface (GUI) of OPX, you can run the most frequently used command-line OPK tools and manage the configuration sets created by the OPK.
Easier to Automate Windows PC Builds
Use OPX to manage all the software resources used to build new PCs:
Windows SKUs
Product keys
Out-of-box drivers
Windows updates
Third-party applications
Your company logos and support information
Using the OPX makes it easier to automate the process of building a Windows PC, using either the network-based or CD-based method.
It's great stuff and that is what the "b" is all about - not at all unlike the OSR "releases" seen between win 95 and 98 se
|