Cloned image doesn't boot

  • Thread starter Thread starter Janiek Buysrogge
  • Start date Start date
J

Janiek Buysrogge

Hello,

I created an image on HDD and ran FBA on it. When FBA finished I
booted the image and performed some post-installation steps such as
drivers, Java Runtime installation, smart-card drivers...

When I felt that it was complete I ran fbreseal from
c:\windows\system32. I used the -keepall switch.

I then copied the resealed image to the network for backup and then I
copied it to a compact flash card.

However when I boot from CF, it takes some time (ok, SID and post-FBA
stuff), and after that I get into windows but I can't logon. There is
a messagebox saying that it can't find my profile, or hasn't got the
rights to load the profile. It also says I have to check my network
connection... When I put CF into usb cardreader I can verify that
Documents and Settings\<username> exists.

Now when I press <Shift> while Windows is booting I get the logon
dialog (otherwise it would automatically log me on by design). I can
logon as a different user, say, Administrator. I get the same message
dialogs but this time I'm able to get into Windows (not a shell, just
an empty blue screen). When I launch cmd.exe from task manager I can
finally see what the culprit is... D:\Windows\System32\cmd.exe... It
seems that the drive letter changed from C: to D: ! In Disk Manager I
cannot change this to C: because it is a system volume. I think all
problems will be solved when I can change the drive, but how ?

Any help would be greatly appreciated.

Best regards,

JB
 
Janiek said:
Hello,

I created an image on HDD and ran FBA on it. When FBA finished I
booted the image and performed some post-installation steps such as
drivers, Java Runtime installation, smart-card drivers...

When I felt that it was complete I ran fbreseal from
c:\windows\system32. I used the -keepall switch.

I then copied the resealed image to the network for backup and then I
copied it to a compact flash card.

However when I boot from CF, it takes some time (ok, SID and post-FBA
stuff), and after that I get into windows but I can't logon. There is
a messagebox saying that it can't find my profile, or hasn't got the
rights to load the profile. It also says I have to check my network
connection... When I put CF into usb cardreader I can verify that
Documents and Settings\<username> exists.

Now when I press <Shift> while Windows is booting I get the logon
dialog (otherwise it would automatically log me on by design). I can
logon as a different user, say, Administrator. I get the same message
dialogs but this time I'm able to get into Windows (not a shell, just
an empty blue screen). When I launch cmd.exe from task manager I can
finally see what the culprit is... D:\Windows\System32\cmd.exe... It
seems that the drive letter changed from C: to D: ! In Disk Manager I
cannot change this to C: because it is a system volume. I think all
problems will be solved when I can change the drive, but how ?

Any help would be greatly appreciated.

Best regards,

JB
Click to expand...
When you ran FBA, was it on a second partition? Or is it a second
partition you're running on now?
 
Hi Adora,

FBA was on C: on the HDD, HDD does have an extra data partition.
Image is now running on C:, first and only partition of CF.

I think it must be the evil -keepall switch. The FBA assigns a unique
GUID for each volume, and when it doesn't find that exact volume in
target system, it creates a new drive (letter). So far, this makes
sense.

As I said, Disk Manager cannot be used to edit a boot volume. I used
to following KB article to do it anyway:

http://support.microsoft.com/kb/223188/

But this only made it worse, I can't even log in anymore. It creates
what seems like an endless loop of "Applying settings...", "Logging
off..."

Now I'm retrying with only the -keepuser switch (network, autologon
will be configured manually on target device).

Thanks for the feedback.

JB
 
Back
Top