sysocmgr.exe be used to add components to a pre-existed build.

[black_13]

I have the situation there i need to added WMI MSDTC and COM+ to XPe
machines in the field.
These machines are sealed units that have no keyboard or mouse and
have FTP access running
the DUA (Device update agent) could I use sysocmgr.exe and the
appropriate files to added the above components? has anyone attempted
this with success?
thanks.
black_13

 

[Sean Liming \(eMVP\)]

How about patching the systems by creating an upgrade patch with IDIFF?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

 

[black_13]

How about patching the systems by creating an upgrade patch with IDIFF?

Regards,

Sean Limingwww.sjjmicro.com/www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit






- Show quoted text -

I have been sooo disapointed with idiff. the xml output file seems to
capture a great amount of extraneous of data that you
dont need. (especially in the registry.)
maybe i dont understand the nuances of idiff as well as you do.
black_13

 

[Sean Liming \(MVP\)]

Sounds like the documentation needs to be updated. iDIFF.xml comes with
certain registry keys and files that typically would be carried forward from
the old image to the new image. You just have to add your own files and
registry keys that you know are in the old image to carry forward.

Other than that, any thing new in in the new image will be applied in the
patch.


--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit

How about patching the systems by creating an upgrade patch with IDIFF?

Regards,

Sean Limingwww.sjjmicro.com/www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit






- Show quoted text -

I have been sooo disapointed with idiff. the xml output file seems to
capture a great amount of extraneous of data that you
dont need. (especially in the registry.)
maybe i dont understand the nuances of idiff as well as you do.
black_13

 

[black_13]

Sounds like the documentation needs to be updated. iDIFF.xml comes with
certain registry keys and files that typically would be carried forward from
the old image to the new image. You just have to add your own files and
registry keys that you know are in the old image to carry forward.

Other than that, any thing new in in the new image will be applied in the
patch.

--
Regards,

Sean Limingwww.sjjmicro.com/www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit






I have been sooo disapointed with idiff. the xml output file seems to
capture a great amount of extraneous of data that you
dont need. (especially in the registry.)
maybe i dont understand the nuances of idiff as well as you do.
black_13

i have been able to use idiff and ida to create update the existing
image/firmware
to have pass my wmi test programs however. the update destroys the
machines
tcpip devices and possibly other devices. what registry keys could be
filtered out in idiff.xml to prevent this?
thanks
black_13

 

[Rawbster]

I have a similar regarding imagediff/ida and tcp/ip settings here:

http://forums.microsoft.com/EmbeddedWindows/ShowPost.aspx?PostID=3054068&SiteID=47

Maybe we can all collectively figure out this issue..