Blinking cursor no OS boot after image...partition questions
Hi all, I’m working on reimaging and updating our FOG server to the latest patch, and I’ve run into some problems imaging some of our older machines. I imaged an Optiplex 390 with Windows 7, and it worked just fine as a Single Disk-Resizeable. However, when I try to image an Optiplex 380 with the same configuration, master image comes from a 380 of course, I get a blinking cursor after imaging is complete. I tried imaging as a Multi-Partition-Non resizable, and it worked. The only problem is, the OS only sees there being 30gigs of HDD space, so this won’t work out in the long run.
I’ve tried the /fixmbr and everything, but I’m hoping someone can point me in the right direction.
Sorry for the late reply, got distracted with the weekend.
Are you deploying the same resizable image to both the 380 and 390 or are these different images?
They’re not hardware independent images, so I’ve been creating the master image on a 390 and then deploying to other 390s, and I’ve been trying to do that with the 380, but as mentioned it isn’t working.
Have you ever successfully imaged an optiplex 380 with fog before? I believe I have several optiplex 380s here at home, they all image just fine.
On our old FOG server they deployed just fine, but it seems there is some issue with this newer version of FOG or something.
I’m not at the office currently, but I believe it’s 1.5.2 or 1.5.3
Wayne Workman last edited by Wayne Workman
@loganllama Couple questions:
- Are you deploying the same resizable image to both the 380 and 390 or are these different images?
- Have you ever successfully imaged an optiplex 380 with fog before? I believe I have several optiplex 380s here at home, they all image just fine.
- FOG version?