Posts made by swaldow

I’m able to capture a Windows 10 image for this system but when I deploy it, the system boots to the recovery screen, error 0xc0000225. Anyone see this or have any ideas? Here are my specs:

FOG version 1.3.5 RC-10
Kernel version: 4.9.11

We have two FOG servers, one I’m able to add new kernels by downloading them and copying them to the kernel directory by using WinSCP and logging in under the ROOT user. I’m unable to do this on the second server, the credentials I use for the ROOT user on server one don’t work on server 2 and the account I am able to login gets a Permission denied error when I try to copy the file. Is there a way to change the ROOT user password so I can get in? Thank you

It looks like wiping the drive and reinstalling Windows 7 with a copy downloaded thru our MS license agreement has solved the issue. I have the image type set as single partition and the deployment takes about 10 minutes, much better. Thank you to everyone that responded.

[quote=“micah2005, post: 1971, member: 633”]Sorry for the late response. Finally checked our 6000 pro’s. They worked set to ide mode in the bios and kernel 2.6.39. Hope this helps but it sounds like it may be the windows 7 system partition.[/quote]
Thanks for checking, do you know which version of BIOS your 6000s are running? Also, you mentioned that you have it working set to multiple partition/single disk, do you know what you have selected for the Host OS for the systems? I’ve tried both Windows 7 and XP and neither have helped.

I think I may have found why Single Partition won’t boot. I rebuilt the system using the rebuild CDs that came with it, loaded GPARTED and looked at the partitions. The system partition is 2GB with 682MB used but when Fog creates this partition it’s only 100MB so the data won’t fit and therefore won’t boot.

[quote=“andyroo54, post: 1833, member: 267”]Sorry but why is your image 85 GB?? Mine is around 11 with driverpacks included?? Do you have all software already installed? Why not just use snapins?? 85GB is going to take a long time over any network![/quote]
Yes, it’s a complete system with all software installed. With the image type set to Multiple Partition/Single Disk the image starts deploying at over 4GB/min estimating that it will be finished in 20 minutes, a time I can certainly live with, but for some reason at the same completion percentage every time the transmit bandwidth flat lines and the image deployment eventually goes down to about 200MB/min. I’ve set the image type to single partition which results in a considerably smaller image size but it won’t boot and when I check the partitions with GPARTED they’re both there but it shows issues with the boot partition. Any help with this would be greatly appreciated.

[quote=“micah2005, post: 1828, member: 633”]We have some 6000 pro SFF’s that have worked just fine with unicasting win7. I know we’ve used Multiple Partition - Single Disk but I’m not sure what drive mode we are using for them. I’ll check one next week. On a side note how did you get the 3115m to image?We’re having network card issues and every kernel I’ve tried ends in various errors. Thanks and good luck.[/quote]
If you could check that I would appreciate it. I had several issues with our 3115m systems also, mostly a screen full of snow, and I’m pretty sure kernel 2.6.29.1 resolved my issue and allowed me to image it.

I reinstalled Windows using the restore CDs to get the system back to the original configuration, sysprepped, uploaded and deployed and now I just get a blinking cursor in the upper left hand corner of the screen. The only setting I would think would cause a problem would be the hard drive, I checked it and it’s set to AHCI, the only other choice is IDE. I used GPARTED to take a look at the drive after deployment, both partitions are there but GPARTED indicates that there’s a problem with the 100MB boot partition, any ideas?

I think I’ve made some progress but now I have a different problem. My original image was set to Single Disk/multiple partition, I did some research and found that setting it to single partition/resizeable would help. I uploaded a new image with this setting and then deployed the image which went extremely fast, done in about 10 minutes. The problem I’m having now is the system won’t boot and I get the error “BOOTMGR is missing”. I used GPARTED and both the boot partition and the main partition are there, I’m not sure what to do at this point.

Unfortunately I don’t know, how can I tell? I’m deploying the image the same way I’ve always done it.

I’ve been having this problem for about a week and can’t figure it out. When I deploy a Windows 7 image to our HP 6000 Pro Business Desktop it starts out fine, deploying the image at 3-4GB/min but at 25% it slows down incredibly, an 85GB image takes all day to deploy. When I check our FOG console for the transmit bandwidth it flatlines at 0 MB/s for a minute or two and then starts jumping between 0MB/s and 15MB/s yet the hard drive light on the PC is solid green. The slowdown happens at 25% every time without fail. If I deploy our XP image to it there are no issues and the upload of the Windows 7 image works fine. I’ve also deployed a Windows 7 image to an HP 3115m and ProBook 4530s without any problems so it seems to be related to the 6000. I’ve tried several different kernels and I’ve updated the 6000s BIOS, I’m at a loss, any help would be greatly appreciated, thanks.