Windows 7 RTM: Clone + Configuration Task Fails
I finished our first build of Windows 7 RTM and tried cloning an image back to a machine this morning with the same limited success as I’ve had with the RC. Of note, I didn’t have these problems with the beta. We’re using Ghost Solution Suite 2.5, updated to the latest via LiveUpdate. This particular build of Windows 7 is the 32-bit flavor of Windows 7 Enterprise. With the RC it was of course Windows 7 Ultimate, just like what everyone else was using.
With the RC I formatted the drive ahead of booting off the DVD so that the WinRE partition wasn’t created. With the RTM I went ahead and formatted the drive while booted from the DVD so that it would create the WinRE partition. In either build I customized what I needed, created an image via Ghost once without sysprep (to fall back to) and once more with sysprep (to consider as our production image).
Once the production image was created I setup a client to test against, cloned the image to the client, and the cloned succeeded. The client rebooted, went through the various sysprep configuration passes, and I had my first successful test.
I then ran a task that included both a clone step & a configuration step. The clone step succeeded, but the configuration step failed, making the entire task fail & halt. Once the task fails the client remains booted into WinPE via the virtual partition. However if I force the machine off, then power it back up, the OS boots and besides lacking the configuration it’s ok since the clone step succeeded.
It seems that by including a configuration step the task fails every time. Now if I clone the image, let the client boot, go through sysprep and finish, the task succeeds as it did the first time. Then if I run a separate task with a configuration step and optionally with or without other steps (like inventory, execute commands) it works just fine. This is the same behavior I saw with the RC.
Any ideas? Any help is greatly appreciated, thank you!
Edit: Edited Title
Comments
A slight update and
A slight update and clarification to this as well. I've tested this on a number of systems, including a Sony Vaio VGN-P598E, a Dell Optiplex 745, 755, 760, and a Latitude E6400. In cases where the system requires the proper AHCI / S-ATA drivers to be present, they're there. I don't run any of these systems in a Legacy, ATA, Compatiblity, etc. mode. All drivers required have been added to WinPE through the Ghost Boot Wizard.
The error I get in the Configuration step is:
And that's all I get. There's actually nothing after the "After lookup:" line in the error file.
Keep in mind that WinPE is able to clone & configure Vista or XP just fine using the same WinPE virtual partition.
Hi there, The same problem
Hi there,
The same problem here. Reason still unknown. Any advise will be appreciated.
Regards
Pips
Still having this problem, no
Still having this problem, no end in sight. I'd really appreciate a response since I don't know what else to do at this point besides have two separate tasks. Separate clone & configure tasks work, but it's kind of a patch job.
Is there an update for GSS 2.5.x in the works to provide better Windows 7 compatibility? I imagine more and more people will start running into this as sytem builders & customers get ahold of Windows 7. And by October the flood gates will really open.
I'm really considering jumping ship and going to MS System Center Config. Manager 2007 R2 an update for GSS doesn't come out soon. Win 7 has been available to more people since January than Vista ever was, and now it's at RTM status with 50/50 GSS 2.5.x compatibility. I'd like to stick with GSS, but I really need a solution that works!
I'm pretty sure GSS 2.5 is
I'm pretty sure GSS 2.5 is XP/Vista, i've never seen 7 support mentioned.
The thing is, Vista's kernel
The thing is, Vista's kernel is 6.0, Windows 7 is 6.1.
99% of the Vista drivers out there I've seen & tested work with 7 as well, as do applications. Obviously there's something different, I'm certainly not dismissing what you're saying, otherwise I never would have posted here in the first place!
Windows 7 support
I suspect that Symantec will not provide full windows 7 support for at least a couple of months. My personal observation is that small companies are quick to release support for new operating systems, but large companies are like snails when it comes to introducing support for a new O/S.
The RTM version is available for testing now, but the official public release of Windows 7 is not due until October 22nd.
Microsoft always have an advantage at these times, as their WAIK has been available for a long time for Windows 7 and my current client has been working on the early adopter program and has a Win7 build pretty much ready for test.
No doubt Symantec will eventually catch up with a newer version of GSS, or workarounds will be found and published. However, if you want to let the Symantec product managers know that you are considering a change, don't waste your time posting in these forums as I doubt they will ever read your intentions - track them down and tell them by email or in person.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I am having the same issues,
I am having the same issues, with the exact same error log. I would like to hear an answer as well, since we use Ghost to support around 1000 machines
Would you like to reply?
Login or Register to post your comment.