Sysprep Create Reboot Loop

Hi Guys,

I have created a Vista Enterprise x86 image several times and tried to
sysprep it. I used the 'sysprep /oobe /generalize' command. When the
computer boots after I have syspreped it I get a black screen that says
'Setting up your computer...' or somthing similar. It then displays the
vista background and says 'Please wait while Windows continues setting
up your computer'. The machine then reboots and the green loading bar
shows for a second and reboots. The machine is then stuck in a reboot
loop. Not even safe mode or Last known good config will let the machine
boot.

Also I had several days of pain trying to get the vista to sysprep at
all. My vLite SP! slipstreamed disc didn't allow syspreping and errored
out. I had to install vista and manually install the SP1.

Thanks for any help you can give me!


--
mountnco

LOL.. bad configuring of the image hehe. After you have sysprepped it
and you run the image again (booting into it) , you will get that setup
screen as the general state will again populate the installation. If you
have created the image, why are you sysprepping again? Because you think
it's needed? Not really if you are making a single computer (specific)
image. Anyway.. let's say you want to sysprep it anyway.. sure.. but
then you should capture the image before booting it up again.
(nevermind, you don't seem to know why you are doing it and
regardless... it shouldn't go into reboot loops , unable to boot). You
definitely have screwed up some things. Either use vLite and just don't
mess around with autounattend.. NOTE!! If you remove wrong components in
vLite , you could get a pretty messed up OS.. I would recommment NOT* to
remove anything and just USE WAIK, until you get your autounattends
right.. then , first then you could go back to humping your OS in vLite.


--
lakmilis

What Sh!t are you talking?

I'm creating an image for a hundred odd machines. I built the image
from scratch and tried to sysprep it so that I can deploy it to all the
machines. Sysprep murders my image and puts it in a reboot loop!

I only used v-lite to slipstream SP1 onto the disc.

All I want to really know is if there will be any logs that will
contain information about why the system won't boot?

P.S. Vista sux hairy balls, bring on Windows 7!


--
mountnco

I'm just saying, I wouldn't want to be one of those using those
machines, nor your boss ;)

The things you describe after booting back into your generalized image
(when you know your image is good, you won't boot back into it after
generalizing it). The loop indicates a pretty unstable state no? The
thing is when you tried to boot back into your generalized image to
populate it again.. did you get time to create a user for example? or
did it reboot before you got to do anything? That could explain why it
is looping.

If you installed SP1 , then I would suggest you take your original
vista again, attend it and sysprep it into sysprep /audit mode...
install SP1 (and anything else you want), then when you are happy, you
generalize it in oobe mode.

gl


--
lakmilis

"mountnco" <guest@unknown-email.com> wrote in message
news:812313e98c073d0db441ab02a2be157e@nntp-gateway.com...
>
> Hi Guys,
>
> I have created a Vista Enterprise x86 image several times and tried to
> sysprep it. I used the 'sysprep /oobe /generalize' command. When the
> computer boots after I have syspreped it I get a black screen that
> says
> 'Setting up your computer...' or somthing similar. It then displays
> the
> vista background and says 'Please wait while Windows continues setting
> up your computer'. The machine then reboots and the green loading bar
> shows for a second and reboots. The machine is then stuck in a reboot
> loop. Not even safe mode or Last known good config will let the
> machine
> boot.
>
> Also I had several days of pain trying to get the vista to sysprep at
> all. My vLite SP! slipstreamed disc didn't allow syspreping and
> errored
> out. I had to install vista and manually install the SP1.
>
> Thanks for any help you can give me!
>
>
By default, the generalize pass forces a re-detection of installed
device drivers. I wonder if one of the drivers isn't getting
reinstalled properly (mass storage driver maybe?). Anyway, if you are
deploying to a single, standard hardware platform you can force sysprep
to preserve the installed device drivers like this:

<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep"
processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>

Hope this helps!

--
Zaphod

No matter where you go, there you are!

Zaphod Beeblebrox;958282 Wrote:
> "mountnco" <guest@xxxxxx-email.com> wrote in message
> news:812313e98c073d0db441ab02a2be157e@xxxxxx-gateway.com...> > >
> > >
> > > Hi Guys,
> > >
> > > I have created a Vista Enterprise x86 image several times and tried
> > to
> > > sysprep it. I used the 'sysprep /oobe /generalize' command. When the
> > > computer boots after I have syspreped it I get a black screen that
> > > says
> > > 'Setting up your computer...' or somthing similar. It then displays
> > > the
> > > vista background and says 'Please wait while Windows continues
> > setting
> > > up your computer'. The machine then reboots and the green loading bar
> > > shows for a second and reboots. The machine is then stuck in a reboot
> > > loop. Not even safe mode or Last known good config will let the
> > > machine
> > > boot.
> > >
> > > Also I had several days of pain trying to get the vista to sysprep at
> > > all. My vLite SP! slipstreamed disc didn't allow syspreping and
> > > errored
> > > out. I had to install vista and manually install the SP1.
> > >
> > > Thanks for any help you can give me!
> > >
> > > > >
> By default, the generalize pass forces a re-detection of installed
> device drivers. I wonder if one of the drivers isn't getting
> reinstalled properly (mass storage driver maybe?). Anyway, if you are
> deploying to a single, standard hardware platform you can force
> sysprep
> to preserve the installed device drivers like this:
>
> <settings pass="generalize">
> <component name="Microsoft-Windows-PnpSysprep"
> processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
> language="neutral" versionScope="nonSxS"
> xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
> </component>
> </settings>
>
> Hope this helps!
>
> --
> Zaphod
>
> No matter where you go, there you are!


but two headed freak.... that! has nothing and little to do with reboot
cycles :)


--
lakmilis

"lakmilis" <guest@unknown-email.com> wrote in message
news:75e9294958763fdc276147ed8d6b79d3@nntp-gateway.com...
>
> Zaphod Beeblebrox;958282 Wrote:
>> "mountnco" <guest@xxxxxx-email.com> wrote in message
>> news:812313e98c073d0db441ab02a2be157e@xxxxxx-gateway.com...> > >
>> > >
>> > > Hi Guys,
>> > >
>> > > I have created a Vista Enterprise x86 image several times and
>> > > tried
>> > to
>> > > sysprep it. I used the 'sysprep /oobe /generalize' command. When
>> > > the
>> > > computer boots after I have syspreped it I get a black screen
>> > > that
>> > > says
>> > > 'Setting up your computer...' or somthing similar. It then
>> > > displays
>> > > the
>> > > vista background and says 'Please wait while Windows continues
>> > setting
>> > > up your computer'. The machine then reboots and the green loading
>> > > bar
>> > > shows for a second and reboots. The machine is then stuck in a
>> > > reboot
>> > > loop. Not even safe mode or Last known good config will let the
>> > > machine
>> > > boot.
>> > >
>> > > Also I had several days of pain trying to get the vista to
>> > > sysprep at
>> > > all. My vLite SP! slipstreamed disc didn't allow syspreping and
>> > > errored
>> > > out. I had to install vista and manually install the SP1.
>> > >
>> > > Thanks for any help you can give me!
>> > >
>> > > > >
>> By default, the generalize pass forces a re-detection of installed
>> device drivers. I wonder if one of the drivers isn't getting
>> reinstalled properly (mass storage driver maybe?). Anyway, if you are
>> deploying to a single, standard hardware platform you can force
>> sysprep
>> to preserve the installed device drivers like this:
>>
>> <settings pass="generalize">
>> <component name="Microsoft-Windows-PnpSysprep"
>> processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
>> language="neutral" versionScope="nonSxS"
>> xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>> <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
>> </component>
>> </settings>
>>
>> Hope this helps!
>>
>> --
>> Zaphod
>>
>> No matter where you go, there you are!
>
>
> but two headed freak.... that! has nothing and little to do with
> reboot
> cycles :)
>

Personal compliments aside ;-), why not? Couldn't it be a BSOD reboot
cycle - think stop 7b errors because of a bad/missing mass storage
driver.

--
Zaphod

Arthur: All my life I've had this strange feeling that there's something
big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.

hehe.... everyone in the universe don't get 'that' .. they just have
it... we are marvins in disguise... simply we get more out of our
organic designs than the non-organic ones. so we adjust our metaphysics
accordingly.... sure.. but even if the drivers are not finding the
devices on the mass storage controllers... does it really create a
vicious cycle of reboots? (I do not think I have experienced that
phenomena in that situation.. although it's been a while it happened ...
xp on 'newer' comps)


lak


--
lakmilis

"lakmilis" <guest@unknown-email.com> wrote in message
news:c21aba62178dcc3c8104f869e42d0862@nntp-gateway.com...
>
> sure.. but even if the drivers are not finding the
> devices on the mass storage controllers... does it really create a
> vicious cycle of reboots? (I do not think I have experienced that
> phenomena in that situation.. although it's been a while it happened
> ...
> xp on 'newer' comps)
>
>
I don't know, I'm just proposing it as a possibility. Worth a try, and
can't hurt if the OP is deploying to a unified platform. Hopefully the
OP will report back...

--
Zaphod

Vell, Zaphod's just zis guy, ya know? - Gag Halfrunt

GREAT.. hit my mouse 'back' button ..msg gone..

Ok.. I was saying.. sure... I agree on that, but wouldn'y OP mention
stop erro codes if he was getting BSODs? I assume(d) it is blank screens
just rebooting.

(The personal was just to zaphod.. hero unconventional weirdo, but the
driving element in the story... one has to say he is also the persona
non grata ino in the book hehe. ,))


--
lakmilis

"lakmilis" <guest@unknown-email.com> wrote in message
news:efff2e01489ae1b520af71e50ff5dd89@nntp-gateway.com...
>
> GREAT.. hit my mouse 'back' button ..msg gone..
>
> Ok.. I was saying.. sure... I agree on that, but wouldn'y OP mention
> stop erro codes if he was getting BSODs? I assume(d) it is blank
> screens
> just rebooting.
>

One would hope that the OP would mention BSOD errors, but if (as by
default) the system is configured to reboot on stop errors, and if it
went by quickly, they might not notice, or might not understand the
significance. Although since the OP wants to distribute the image to "a
hunderd odd machines" one would also hope that the OP has the knowledge
and understanding.

--
Zaphod

Voted "Worst Dressed Sentient Being in the Known Universe" for seven
years in a row.

Ok. let's not hijack the thread...

ANyway OP.. I suddenly realized what is your problem most likely.

Did you pass the sysprep /generalize an unattend file?

sysprep ..... /unattend:/absolute path/myunattendfile.xml?

Did you get an error at one point saying ..error in parsing this
file... settings pass specialize OR oobeSystem failed?

Your symptom PRECISELY shows this. *except you didn't mention this
error?)

If so.. you will have to reinstall.. however, just reinstall wihtout
partitioning.. then enter windows.old\panther\unattendGC. In there you
will have logs which will show you even which entries in your file have
caused the ooobe to crash and burn and die.

Fix these.. and voila. reinstall , etc etc.

And seriously.. I doubt this OP will deply to 100+ odd machines... a
technician just wouldn't be so noobie in his description of the problem.
More likely a guy working on his pirate copy at home and is worried he
would sound like that and so claims to deploy many machines lol :o)

Anyway OP... can you get back to me on that.. I thinkk this is the
case so if you are still having troubles, I can maybe guide you further
*by looking at your xm; file for example* and adding what vista version
u have etc.

EG. A classic error which would lead to this is if you have
slipstreamed windows mail out of your build , yet in windowsfeature have
set a link to mail in startlist to true... or showwindowsmediacentre to
true when you are not on vista home premium or ultimate (which are
theonly versions with the centre). Any incorrect parsing of this file
in oobe will RENDER YOU SYSTEM USELESS AND REQUIRE A REINSTALL (as you
mentioned you had to do in your OP).

lak


--
lakmilis

and zaphod.. I *know* he doesn't have BSODs.. he would mention it.. even
if fast.. when you are building a comp YOU WILL NOTICE A BSOD lol ,)


--
lakmilis

PS... I forgot to say, you might also have gotten a message like..
windows could not configure a component or something like this.. please
restart windows to continue the installation or install again..
something along those lines... you don't *need* to get the message I
mentioned above.. (if you got this message.. then prolly it was your
audit pass there are problems with).


--
lakmilis