VERY WIERD

[James]

using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work on
building and deploying images of Windows Server 2003...

I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would the
same thing happen if a keyboard and mouse was physically hooked up?...
Sysprep.exe will NOT complete until I move my mouse over the iLO console
screen! I noticed this after checking up on the running job because sysprep
should have been done by this time and its not until I actually move my
mouse into the iLO console, thus moving the mouse pointer on the machine
sysprep is running on, that sysprep finishes. What the? At first I thought
it was just a coincidence that every time I when to check on it that it
happened to finish right then.. but then it happened time and time again and
I knew it was no coincidence.

I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...

1. anyone seen anything like this with sysprep? or iLO?

2. should I be concerned about the integrity of my images now? I'm using MDT
2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep finishes
and returns it's return code.. but this is wierd.

[Anthony [MVP]]

It almost sounds as though the iLO is sleeping until you move the mouse and
refresh the screen,
Anthony
http://www.airdesk.co.uk

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work
on building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would the
same thing happen if a keyboard and mouse was physically hooked up?...
Sysprep.exe will NOT complete until I move my mouse over the iLO console
screen! I noticed this after checking up on the running job because
sysprep should have been done by this time and its not until I actually
move my mouse into the iLO console, thus moving the mouse pointer on the
machine sysprep is running on, that sysprep finishes. What the? At first I
thought it was just a coincidence that every time I when to check on it
that it happened to finish right then.. but then it happened time and time
again and I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using
MDT 2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep
finishes and returns it's return code.. but this is wierd.

[James]

Hi, thanks for the reply Anthony.

I was thinking something similar (or possibly same thing you are getting
at), that the screen parts are cached, even the little loop of the hour
glass turning around and around, until it receives movement from you... but
I don't believe this could be it now because when I do give it the movement
it picks up and continues with the stuff that happens right after sysprep
finishes... in other words, you don't all the sudden see a screen that is at
a later point in time in the process, you see what you should see next, no
missing parts.

???

I will probably try to follow up with HP on this.

Post by Anthony [MVP]
It almost sounds as though the iLO is sleeping until you move the mouse
and refresh the screen,
Anthony
http://www.airdesk.co.uk

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work
on building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would
the same thing happen if a keyboard and mouse was physically hooked
up?... Sysprep.exe will NOT complete until I move my mouse over the iLO
console screen! I noticed this after checking up on the running job
because sysprep should have been done by this time and its not until I
actually move my mouse into the iLO console, thus moving the mouse
pointer on the machine sysprep is running on, that sysprep finishes. What
the? At first I thought it was just a coincidence that every time I when
to check on it that it happened to finish right then.. but then it
happened time and time again and I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using
MDT 2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep
finishes and returns it's return code.. but this is wierd.

[Julian Rodriguez]

This happens to me when I create reference images, it's happened to
me on a Dell Optiplex 490, *and* VMWare ESX.... Very weird...

Julian Rodriguez

Post by James
Hi, thanks for the reply Anthony.
I was thinking something similar (or possibly same thing you are getting
at), that the screen parts are cached, even the little loop of the hour
glass turning around and around, until it receives movement from you... but
I don't believe this could be it now because when I do give it the movement
it picks up and continues with the stuff that happens right after sysprep
finishes... in other words, you don't all the sudden see a screen that is at
a later point in time in the process, you see what you should see next, no
missing parts.
???
I will probably try to follow up with HP on this.

Post by Anthony [MVP]
It almost sounds as though the iLO is sleeping until you move the mouse
and refresh the screen,
Anthony
http://www.airdesk.co.uk

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work
on building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would
the same thing happen if a keyboard and mouse was physically hooked
up?... Sysprep.exe will NOT complete until I move my mouse over the iLO
console screen! I noticed this after checking up on the running job
because sysprep should have been done by this time and its not until I
actually move my mouse into the iLO console, thus moving the mouse
pointer on the machine sysprep is running on, that sysprep finishes. What
the? At first I thought it was just a coincidence that every time I when
to check on it that it happened to finish right then.. but then it
happened time and time again and I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using
MDT 2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep
finishes and returns it's return code.. but this is wierd.

[Julian Rodriguez]

Regarding the integrity of the image... The images seem to seal
correctly, and have been working fine over here... I just have to
remember to move the mouse in order to seal....

Julian

Post by James
Hi, thanks for the reply Anthony.
I was thinking something similar (or possibly same thing you are getting
at), that the screen parts are cached, even the little loop of the hour
glass turning around and around, until it receives movement from you... but
I don't believe this could be it now because when I do give it the movement
it picks up and continues with the stuff that happens right after sysprep
finishes... in other words, you don't all the sudden see a screen that is at
a later point in time in the process, you see what you should see next, no
missing parts.
???
I will probably try to follow up with HP on this.

Post by Anthony [MVP]
It almost sounds as though the iLO is sleeping until you move the mouse
and refresh the screen,
Anthony
http://www.airdesk.co.uk

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work
on building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would
the same thing happen if a keyboard and mouse was physically hooked
up?... Sysprep.exe will NOT complete until I move my mouse over the iLO
console screen! I noticed this after checking up on the running job
because sysprep should have been done by this time and its not until I
actually move my mouse into the iLO console, thus moving the mouse
pointer on the machine sysprep is running on, that sysprep finishes. What
the? At first I thought it was just a coincidence that every time I when
to check on it that it happened to finish right then.. but then it
happened time and time again and I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using
MDT 2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep
finishes and returns it's return code.. but this is wierd.

[James]

very weird indeed... so it must have something to do with 'virtual'
keyboard/mouse etc...

thanks for the input, I'm glad I'm not the only one, hehe. Thought I was
loosing it. :)

"Julian Rodriguez" <***@gmail.com> wrote in message news:068666d9-db82-4774-856c-***@v5g2000prm.googlegroups.com...
Regarding the integrity of the image... The images seem to seal
correctly, and have been working fine over here... I just have to
remember to move the mouse in order to seal....

Julian

Post by James
Hi, thanks for the reply Anthony.
I was thinking something similar (or possibly same thing you are getting
at), that the screen parts are cached, even the little loop of the hour
glass turning around and around, until it receives movement from you... but
I don't believe this could be it now because when I do give it the movement
it picks up and continues with the stuff that happens right after sysprep
finishes... in other words, you don't all the sudden see a screen that is at
a later point in time in the process, you see what you should see next, no
missing parts.
???
I will probably try to follow up with HP on this.

Post by Anthony [MVP]
It almost sounds as though the iLO is sleeping until you move the mouse
and refresh the screen,
Anthony
http://www.airdesk.co.uk

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work
on building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would
the same thing happen if a keyboard and mouse was physically hooked
up?... Sysprep.exe will NOT complete until I move my mouse over the iLO
console screen! I noticed this after checking up on the running job
because sysprep should have been done by this time and its not until I
actually move my mouse into the iLO console, thus moving the mouse
pointer on the machine sysprep is running on, that sysprep finishes. What
the? At first I thought it was just a coincidence that every time I when
to check on it that it happened to finish right then.. but then it
happened time and time again and I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using
MDT 2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep
finishes and returns it's return code.. but this is wierd.

[Dave Guenthner [MSFT]]

That is a bug. The issue is that it happens so infrequently, difficult to
reproduce and debug.

Dave Guenthner [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

[Adam Leinss]

Post by Dave Guenthner [MSFT]
That is a bug. The issue is that it happens so infrequently,
difficult to reproduce and debug.

I had a simliar issue back in the Windows 95 beta. OS would not boot until
I moved the mouse around. Issue cleared up by the time retail hit.

Adam

[Nick Payne]

I've seen pretty much the same problem when running an MDT image capture
through both a Dell console switch and a Dell DRAC remote console. The
sysprep dialog just sits there hour after hour with a spinning hourglass
until it is clicked on, at which point it completes and the capture
continues. Moving the mouse around the screen doesn't do anything, I have to
actually click on the dialog to get sysprep to complete.

Nick

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work on
building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would the
same thing happen if a keyboard and mouse was physically hooked up?...
Sysprep.exe will NOT complete until I move my mouse over the iLO console
screen! I noticed this after checking up on the running job because sysprep
should have been done by this time and its not until I actually move my
mouse into the iLO console, thus moving the mouse pointer on the machine
sysprep is running on, that sysprep finishes. What the? At first I thought
it was just a coincidence that every time I when to check on it that it
happened to finish right then.. but then it happened time and time again and
I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using MDT
2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep finishes
and returns it's return code.. but this is wierd.

[James]

thanks for the info Nick. So have you had any problems with the images that
were created when this happens? or is all ok?

thanks

Post by Nick Payne
I've seen pretty much the same problem when running an MDT image capture
through both a Dell console switch and a Dell DRAC remote console. The
sysprep dialog just sits there hour after hour with a spinning hourglass
until it is clicked on, at which point it completes and the capture
continues. Moving the mouse around the screen doesn't do anything, I have to
actually click on the dialog to get sysprep to complete.
Nick

Post by James
using iLO (integrated lights out) on HP servers... for those that are not
familiar its like a built-in KVM over IP. I have been using this to work on
building and deploying images of Windows Server 2003...
I have noticed, then confirmed, the following wierd behavior and am
wondering if anyone else has seen this.. is it because of iLO or would the
same thing happen if a keyboard and mouse was physically hooked up?...
Sysprep.exe will NOT complete until I move my mouse over the iLO console
screen! I noticed this after checking up on the running job because sysprep
should have been done by this time and its not until I actually move my
mouse into the iLO console, thus moving the mouse pointer on the machine
sysprep is running on, that sysprep finishes. What the? At first I thought
it was just a coincidence that every time I when to check on it that it
happened to finish right then.. but then it happened time and time again and
I knew it was no coincidence.
I have sat there waiting probably 30 - 40 minutes longer than necessary
waiting for sysprep...
1. anyone seen anything like this with sysprep? or iLO?
2. should I be concerned about the integrity of my images now? I'm using MDT
2008 so the task sequence does continue normally with no errors after
sysprep completes (by my moving my mouse)... I assume sysprep is just
sitting there doing nothing, and mdt doesn't continue until sysprep finishes
and returns it's return code.. but this is wierd.