Re: More fbreseal strange behavior
From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 01/28/05
- Next message: Slobodan Brcin \(eMVP\): "Re: PROCESS1_INITILIZATION_FAILED"
- Previous message: Jonson: "Re: About tow IP Helper Functions"
- In reply to: Desi: "Re: More fbreseal strange behavior"
- Next in thread: Robert: "Re: More fbreseal strange behavior"
- Reply: Robert: "Re: More fbreseal strange behavior"
- Reply: Desi: "Re: More fbreseal strange behavior"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 28 Jan 2005 15:24:51 +0100
Hi Desi,
Since you got new user account created that explains why all your user related settings were gone.
Perhaps if before image duplication you copy your configured account over Default User account you will make some ugly workaround.
(At least newly created account will be configured)
Regarding wmp.inf do you have it? I don't know why Windows Media Player is complaining :-(
Do you have purged setupapi.log so we can see what hardware is found by PnP?
Regards,
Slobodan
"Desi" <richardsd@tycoelectronics.com> wrote in message news:1106919161.964388.136640@c13g2000cwb.googlegroups.com...
> Well, I have more information to report.
>
> I recreated the image with the following set to FALSE:
> cmiRemoveAutoLogon, cmiUnjoinDomain, cmiRemoveNetSettings,
> cmiRemoveUserSettings, and cmiRemoveMountedDevices. Booted through FBA,
> all seemed well there. I tweaked and installed some software that we
> require (Enterprise Instrumentation Framework, Web Services
> Enhancements SP2), and changed a bunch of little UI items. I changed
> the password for the "Admiistrator" user. Then I ghosted the box so I
> don't have to go through that again.
>
> Finally, I ran fbreseal.exe -keepall from a command prompt. It came
> back with a dialog that "Machine is sealed" and I clicked OK to
> restart.
>
> On the next start, I PXE booted to a RAM drive image and ghosted the
> drives again. When finished, I restarted.
>
> The target took a long time to start up, as though it were changing the
> SIDs. When it finished, I was presented with a logon screen. The
> "Administrator" user, and the password I changed it to worked. But
> after logon, another delay for 3-4 minutes with nothing but a blank
> screen. An error box appeared telling me that "Windows could not find
> the file: C:\WINDOWS\wmp.inf". Then, shortly after that, another dialog
> that said "Windows has finished installing your new hardware and must
> be restarted to finish the installation".
>
> Keep in mind that this is THE hardware that the image was created on.
> Not just similar hardware, but the exact box.
>
> When the desktop was finally started, all kinds of things were
> immediately noticeable: Here's a quick list:
>
> - The system had created a second account: Administrator.NSXXYYZZ,
> under Documents and Settings. This is what was used for the logon.
> (NSXXYYZZ is the hostname)
>
> - None of the UI changes were present, no "My Computer" on the desktop,
> etc.
>
> - In Explorer, "Network Connections" under the Control Panel was a
> default icon. Clicking on it did not show any network connections (The
> unit has two that were configured and working prior to resealing).
>
> - Drive letters are rearranged. Drives C & D are swapped.
>
> - My Network Places -> Add Network Place does not do anything when
> clicked, and icon is default "Unassociated" icon.
>
> - MMC cannot start at all. Event viewer cannot start.
>
> - UI colors for menus, etc. have a dark gray background instead of the
> normal light gray.
>
> - Trying to view security settings for folders results in a "Security
> Settings dialog could not be found" error.
>
> - Finally, as Mark Vallevand has also seen, fbreseal.exe in the
> system32 folder is not deleted.
>
> What would cause a new account to be created? Before resealing, I had
> the network up and running, and was in a workgroup. I had mapped
> network drives, etc. so the network did not suddenly appear... Would a
> failure to load the network cause it to create a local account
> "Administrator.NSXXYYZZ"?
>
- Next message: Slobodan Brcin \(eMVP\): "Re: PROCESS1_INITILIZATION_FAILED"
- Previous message: Jonson: "Re: About tow IP Helper Functions"
- In reply to: Desi: "Re: More fbreseal strange behavior"
- Next in thread: Robert: "Re: More fbreseal strange behavior"
- Reply: Robert: "Re: More fbreseal strange behavior"
- Reply: Desi: "Re: More fbreseal strange behavior"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|