Re: Strange FBReseal Behavior?
From: Desi Richards (richardsd_at_tycoelectronics.com)
Date: 10/13/04
- Next message: Andy Allred [MS]: "Re: SP2 tech preview"
- Previous message: Mario: "Stop Error 7b at change from Standard PC to ACPI"
- In reply to: Doug Hoeffel: "Re: Strange FBReseal Behavior?"
- Next in thread: Doug Hoeffel: "Re: Strange FBReseal Behavior?"
- Reply: Doug Hoeffel: "Re: Strange FBReseal Behavior?"
- Messages sorted by: [ date ] [ thread ]
Date: 13 Oct 2004 08:49:38 -0700
Doug - I am now using QFE 810144 and the -keepall switch, but I still
have an issue:
When the cloned image is booted on an identical system (I even put the
master CF module back into the original hardware set), the MSDTC
service is "Marked for deletion". This causes a number of services to
fail, notably MSMQ.
It appears that the "fbreseal -keepall" is still stepping on something
that causes the MSDTC service to fail on the next boot. Could this be
a bug in fbreseal?
To resolve it, I have to do the following:
1. Using the Services applet (Control Panel -> Administrative Tools
-> Services), shut down the "Distributed Transaction Coordinator"
service if it is running.
2. Close the Services applet and run "C:\WINDOWS\System32\msdtc
-install".
3. Reopen the Services applet and change the startup type to
"Automatic"
4. Reboot the machine.
When I do all of this on the target, MSDTC and MSMQ now start and run
as expected!
~Desi
"Doug Hoeffel" <doug.hoeffelNo@SpAmMcamtronics.com> wrote in message news:<eCzeADvpEHA.3896@TK2MSFTNGP15.phx.gbl>...
> Desi:
>
> Are you building your image with QFE 810144? If not I would add it. Also,
> you might want to look into the -keepall switch.
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;810144&Product=WinXP
>
> HTH
> ... Doug
> "Desi Richards" <richardsd@tycoelectronics.com> wrote in message
> news:1bc49301.0409300510.63feaead@posting.google.com...
> > I set the reseal phase to 0 in Target Designer System Cloning Tool
> > component's advanced properties, so that I can tweak the image prior
> > to cloning it.
> >
> > FBA ran successfully, and I tweaked the image to my liking.
> >
> > When all was complete, I had:
> > - Video drivers installed & working
> > - resolution set to 1024x768x32bpp
> > - MSMQ components installed and running
> > - Various other settings modified
> >
> > I ran fbreseal from a command prompt, and the system stated that it
> > had been resealed and then rebooted. When it shut down, I made two
> > Ghost clones of the master compact flash module. One copy was
> > installed into each of two target machines, and they were rebooted.
> > The master compact flash module was put in a desk drawer for
> > safekeeping.
> >
> > One of the machines was the one that the master image was created on.
> > This machine booted quickly, had the correct video resolution and
> > driver, and behaved as though it had never been resealed.
> >
> > The other machine booted much more slowly, paused for long times with
> > just a blank desktop and at the "Windows Settings" dialog boxes, and
> > looked as though it was generating unique SIDs, etc.
> >
> > This second machine, however, came up in 640x480 mode, and the "Add
> > New Hardware" wizard popped up, asking for the video drivers. I
> > browsed for the drivers, but they had been removed from the system! I
> > had to reload the driver from an external disk just to get the video
> > drivers to run.
> >
> > On both targets, the MSMQ service was not running, either.
> >
> > Most of my other changes were in place, so I know that the image was
> > the correct one. But some of these things puzzled me - Are they
> > supposed to occur?
> >
> > Desi Richards
- Next message: Andy Allred [MS]: "Re: SP2 tech preview"
- Previous message: Mario: "Stop Error 7b at change from Standard PC to ACPI"
- In reply to: Doug Hoeffel: "Re: Strange FBReseal Behavior?"
- Next in thread: Doug Hoeffel: "Re: Strange FBReseal Behavior?"
- Reply: Doug Hoeffel: "Re: Strange FBReseal Behavior?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
