Jump to content




Sign in to follow this  
anyweb

Add Trace32.exe to your boot.wim



Recommended Posts

This tip is great for incorporating Trace32.exe to your boot.wim for troubleshooting.

 

 

Create folders and populate with file(s)

 

Create a folder on your SCCM server called Extrafiles, put two blank folders in there called windows\system32

 

copy the trace32.exe file to the system32 folder you just created above (you can copy more than this if you wish, but for this tip this is sufficient)

 

trace32.jpg

 

 

 

Create a new boot image

 

In Operating System Deployment, right click on boot images, and choose create boot image using microsoft deployment.

 

create_boot_image.jpg

 

Point the Package Source to blank shared folder on your network.

 

package_source.jpg

 

Fill in the General Settings

 

details.jpg

 

 

For Image Options, use the Extrafiles folder you created above as 'extra' directories to add

 

image_options.jpg

 

click next and the boot image will be created (takes some time).

 

Note: if you get this error "Error while importing Microsoft Deployment Toolkit task sequence. Details: the ConfigMgr reported an error" then grant SYSTEM account full permissions on your network share that you are creating the boot.wim file in.

 

share.jpg

 

 

Using the new boot image

 

Dont forget to add network drivers to your boot.wim and finally dont forget to create a new Distribution Point and update it.

 

When you are troubleshooting image deployment you can switch to this debug boot.wim by right clicking on a Task Sequence and choose properties, click on the Advanced tab and change the boot image to the one you've just created.

 

add_to_TS.jpg

 

Now when you press F8 to troubleshoot you can bring Trace32 up to read the logs right there in your deployment.

 

btw, here's another cool way of adding trace32.exe to your boot images

 

http://myitforum.com/cs2/blogs/1e/archive/2010/07/17/configmgr-osd-always-including-certain-files-in-your-boot-images-think-trace32.aspx

  • Like 1

Share this post


Link to post
Share on other sites


Hey anyweb... What version of SCCM are you running? I am on R2 and I do not have the "create boot image using microsoft deployment" step for creating the boot image.

Share this post


Link to post
Share on other sites

hi Jizz

 

that option will only appear if you have install Microsoft Deployment Toolkit and integrated it with SCCM

Share this post


Link to post
Share on other sites

Hi Anyweb,

Can you tell us how you can set the pxe boot image to a keyboard layout 'belgian (period)' for example? For SCCM SP2 (WinPE 3.0)

 

I have already done this for my previous SCCM SP1 R2 (WinPE 2.0) but I can't remember how I did it :angry: :angry: :angry:

Share this post


Link to post
Share on other sites

If you are using SCCM 2007 SP1 (WinPE 2.0 images) you can use intlcfg.exe to set the keyboard layout in WinPE.

 

If you are using SCCM 2007 SP2 (WinPE 3.0 images) intlcfg.exe is deprecated and you have to use Dism.exe to set the keyboard layout in WinPE.

Share this post


Link to post
Share on other sites

I find it easier to go to

 

SCCM console>>>OSD>>> [on homepage] click on advertisement link.

All info is there!

Share this post


Link to post
Share on other sites

and now the 64 bit of the logviewer is available !

 

Trace64.exe you can get it here

 

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cd73a2c5-76c1-48b3-a366-156900bb9493

 

 

Hello, thanks for the guide, I was going to add trace64 the old "manual" way..

 

Something I'll anyway do just to manipulate DISM, international settings etc .. to be ready with the tools available or not at our customers....

(btw how many dozen years will we have to wait before these simple but important international settings are manageables by GUI...! from a plateform like SCCM, this should be the case, to me.. But en-US is big, really big :-) not fr-CH :)

 

well, thank you for all the guides etc.. I discovered your forums not long ago, would have helped me and gaining time, it seems! Thanx

 

Conrad

Share this post


Link to post
Share on other sites

and now the 64 bit of the logviewer is available !

 

Trace64.exe you can get it here

 

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cd73a2c5-76c1-48b3-a366-156900bb9493

 

Is Trace64.exe still available form Microsoft? Is it part of MDT 2010 Healthcare package?

The link from microsoft is dead, and by searching for MDT 2010 Healthcare all they offer is pdf...

 

Thanks.

Share this post


Link to post
Share on other sites

the link is being fixed according to Johan Arwidmark,

 

here it is in the meantime

 

trace64.zip

 

Rename trace64.bob to .exe

 

cheers

niall

Share this post


Link to post
Share on other sites

Hi

Is is possible to add trace32.exe to the standard boot image?

would be nice to always have trace32.exe available when something goes wrong in the task sequence.

Otherwise there is two boot images that you have to keep updated with the right drivers.

 

Best Regards

Share this post


Link to post
Share on other sites

Nope, you need to create a new Boot Image.

 

You can always use the new Boot Image as you Standard Boot Image.

 

Thanks for the reply, will try that.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  


×