Oh sweet flaming zobmie Jeebuch!
Sep. 27th, 2007 08:53 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
grayhawkfhThe date: 27 September 2007
The time: 2053 hrs.
The place: work.
Oh yeah, you read that right. I'm the bleeding f**k at work. Got here just around 0915 hrs.
Why am I still here at work? Well, I solved one of my problems earlier. Now I just had to do the final prep stages, run SysPrep (a M$ utility that helps automate Windows deployments), load the image to the servers and test the image.
What came up: An error has been encountered that prevents setup from continuing. Windows is unable to start because the registry could not be updated.
What that means (for my non-technical readers - long form): The registry is a set of instructions and values which basically tells Windows what to do and when to do it. If it can't be accessed/updated, Windows doesn't run.
What that means (for my non-technical readers - short form): I'm f**ked.
So I went back to my restore point and tried again. No futzing with the registry this time, just rebuilt everything. Ran SysPrep, uploaded the image, tested the image.
Same message.
I have a few ideas of why this is happening. My Google-Fu appears to be strong. What really sucks is that this has to be done tonight. And since it takes ~45 minutes to upload or download an image from the servers, and about 20 minutes to run SysPrep...I'm looking at about 2-3 more hours minimum.
So much for watching CSI tonight with![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
mousecat0
Still, I think I've got the answer. I'll have to wait and see to be certain.
"Don't say a prayer for me now. Save it til the morning after
No don't say a prayer for me now. Save it til the morning after" - Duran Duran
Updates as events warrant.
The time: 2053 hrs.
The place: work.
Oh yeah, you read that right. I'm the bleeding f**k at work. Got here just around 0915 hrs.
Why am I still here at work? Well, I solved one of my problems earlier. Now I just had to do the final prep stages, run SysPrep (a M$ utility that helps automate Windows deployments), load the image to the servers and test the image.
What came up: An error has been encountered that prevents setup from continuing. Windows is unable to start because the registry could not be updated.
What that means (for my non-technical readers - long form): The registry is a set of instructions and values which basically tells Windows what to do and when to do it. If it can't be accessed/updated, Windows doesn't run.
What that means (for my non-technical readers - short form): I'm f**ked.
So I went back to my restore point and tried again. No futzing with the registry this time, just rebuilt everything. Ran SysPrep, uploaded the image, tested the image.
Same message.
I have a few ideas of why this is happening. My Google-Fu appears to be strong. What really sucks is that this has to be done tonight. And since it takes ~45 minutes to upload or download an image from the servers, and about 20 minutes to run SysPrep...I'm looking at about 2-3 more hours minimum.
So much for watching CSI tonight with
mousecat0Still, I think I've got the answer. I'll have to wait and see to be certain.
"Don't say a prayer for me now. Save it til the morning after
No don't say a prayer for me now. Save it til the morning after" - Duran Duran
Updates as events warrant.
