Posts made by The Dealman

[quote=“Chino, post: 667, member: 276”]Funny you should ask. I did just try that and it didn’t work either and yes I’m on fog .32. I"m not sure what else can be done. I was thinking that maybe it was the image, but even if I deploy an image that isn’t for that model it will not push down. Maybe it’s a driver issue with somethinig on this machine…[/quote]

Well according to the wiki [url]http://www.fogproject.org/wiki/index.php?title=WorkingDevices[/url] you should be using the default kernel from version 0.29 for starters

[quote=“ssx4life, post: 693, member: 268”]

#3. Updating the snapin to play nicer with Windows 7.
[/quote]

Ditto on this one !

[quote=“Al@akuni, post: 622, member: 250”]Yeah I also wrestled with Optiplex 990s and FOG for quite a while.
I found that the default kernel on FOG 0.32 seemed to work (i.e it would deploy images) on Optiplex 990s. But yes, I got the same ‘fuzzy screen’ problem that you did. I found the following fix in the old forums and it seemed to work for me:

[COLOR=#555555][FONT=Arial][SIZE=2]Put [B] acpi=off nomodeset[/B] in FOG_KERNEL_ARGS. You can do for all your hosts via the Other Information Menu->Fog Settings->[/SIZE][/FONT][/COLOR]FOG_KERNEL_ARGS[COLOR=#555555][FONT=Arial][SIZE=2], or you can edit per host settings via the Host Kernel Arguments field.[/SIZE][/FONT][/COLOR]

I ignore the BIOS warnings - they don’t seem to have any effect, if you just wait for about a minute the image should start deploying regardless.

Boot Loop. Yep this is a pain. I’ve seen the chainloading workaround suggested by others, but I’m reluctant to implement it on my FOG server to fix a problem on one model of desktop. I haven’t therefor set my 990’s to default to NIC as first boot. It’s a pain because unlike old models of Optiplex the 990 doesn’t have the BIOS setting that tells the machine to boot to NIC when it receives a Wake-on-Lan package. So basically I am having to use F12 every time i want to image a 990 - even in a big lab.[/quote]

You maybe correct the default kernel for ver. 0.32 should work on those 990’s but if that kernel is used on the optiplex 780’s video will react the same

[quote=“Amanda, post: 602, member: 243”]Is anyone here trying to use FOG on the Optiplex 990 series? I just got these in and are looking to implement them into our student labs. The issues that I am having:

1. Cannot Image using DVI video on the desktop. Must use VGA, which then prompts after the POST screen that an unsupported video configuration was detected every time the machine is restarted. Is there any way to get FOG to work with DVI?

2. Optiplex 990 came with BIOS A06 installed, which when used, FOG says that it is not compatible. I have updated to A07, and the same error occurs. I have not tried A10 yet. Has anyone had any success with a BIOS version for the 990s?

3. Boot Loop. The computer is stuck in a boot loop. I have NIC as the first option, and HD as the second option. The computer will boot into the NIC to check with FOG if there are any tasks, and when there is not, the quick FOG menu appears and auto-selects “Boot from Hard Drive” and the computer restarts. When this happens, it just repeats itself and doesn’t go back into the Native OS until I choose the Hard Drive from the boot options using F12. Any suggestions on how to bypass this? I don’t want to have to select F12 for anything, including when I want to push or pull an image from the FOG server.

TIA!![/quote]

i have quite a few of these and the way i got around it was to use a different kernel, i dont remember which i choose but try updating to a different kernel

[quote=“Blackout, post: 420, member: 1”]Keep them coming guys, this is great feedback.

Sadly, snapins in FOG are very primitive and are certainly not an enterprise solution.
Right now they are there to get you out of a jam, they are not designed to deploy gigabytes of data.

I would love to revamp the system, but application packaging is a massive task. I would feel much more comfortable implementing an open source system to handle this so we dont need to worry about it. TBH, i havent looked at what is out there.

Maybe application virtualization would be a better idea?

If anyone has any ideas, please feel free to post.[/quote]

application virtualization is a good idea but costly one thing we have alot apps that could work with something like remote app but dont wanna go down that road

what’s your procedure when using it? or what was the first things you did? i read over this [url]http://fogproject.org/wiki/index.php?title=Plugins:_Capone[/url] but i was wondering how would one actually put it to work…

I changed the setting to the Single Drive / Single Partition option uploaded my image and i saw as it was going through the pre-checks it resized the partitions. i havent deployed it to a different model yet or checked to see what the partitions look like yet though but it may have worked…

I was just wondering if anyone was using the Capone plugin in fog? i did some reading up on it and it looks interesting but i havent been able to find any topics or videos about…

h
[quote=“totalimpact, post: 563, member: 217”]The developers know that Windows 7 will always have a 100mb boot partition (many people dont even see it), and then some partition of random size, so this means there is only 1 partition FOG needs to manipulate, but if you add a 3rd partition in to the mix - how will Fog make the decision as to which needs resizing?? - this is why multi partitions cant be resized - and Win7 has 2 parts, but only 1 needing resizing - this is why Win 7 works as a “resizable single partition” scenario - the term doesnt fit, but it works.[/quote]

hmmm…i may have tried that before not sure but it may have blue screened on me. i have one freshly done next to me ill give your suggestions a shot hopefully i dont lose all my effort i put into it to get it how i want it, let you guys know the outcomes. If it does work then someone needs to correct those image types descriptions:)

[quote=“totalimpact, post: 539, member: 217”]Yes - it will, not sure what instructions show that, but its mentioned all over the forum - use Single Disk/Single Partition for best performance - even on Win 7.[/quote]

Fog says that in the image types in the description and that’s why i used it.
[B]Multiple Partition - Single Disk[/B]

Multiple Partition - Single Disk will back up all the supported partitions on the first disk drive detected by FOG, but the partitions are [B]NOT[/B] resizable by FOG. This means that the image must be restored to a disk of the same or larger capacity.
[B]Overview[/B]

[LIST]
[]Single Disk Drive
[]Not Resizable
[]Supports: [B]NTFS, XFS. JFS, HPFS, FAT16, FAT32, Reiser3, EXT2, EXT3[/B]
[]Linux Support!
[/LIST]

I don’t see how you can use Single Disk/Single Partition when there are 2 partitions?

[quote=“totalimpact, post: 536, member: 217”]If it is the 2 partitions from Windows 7 (boot and C), it will still resize - its only when it gets beyond the base partitioning scheme of Win 7 (you used 3 partitions?) that resize will fail.[/quote]

It is those 2 default partitions but In the instructions i read it was suggested to use “Multiple Partition Image - Single Disk” for the image type when creating windows 7 images which doesn’t resize. Are you saying that it will ?

[quote=“rixter, post: 415, member: 168”]If it is the 2 default partitions for windows 7 (one is very small ~100 mb and the other is the rest of the disk) you can still use the NTFS Resizable option on it (fog takes into account that it is for windows 7 and allows this). Again IF you can ghost this back to the original machine and pull it again with the resizable option, I’m betting it will fix your issue.[/quote]

The only option that is resizable is the Single Partition option which doesnt work because there are 2 partitions, i tried that before and it blue screened on me

after doing some more research my windows 7 images is Multiple Partition - Single Disk non resizable. I created the image from a pc that had a drive size of 232.88 gig and i was trying to deploy to a pc that had a drive size of 232.82, since it’s not resizable the target drive needs to be the same or larger capacity. What i should have did was build the windows 7 image on the smallest drive i have…

it would be great to have a better application to make the snap-ins! the installrite seems to record reg structure which is messy and the sfx is ok but needs alot of work. I would like to see the snap-in system changed to more of a push type of method as it seems like its more of a pull type now, i think we should be able to rapidly infuse applications on to our client machines from the fog interface

[quote=“Blackout, post: 392, member: 1”]You should be chkdsk’ing before syspreping. Sysprep does not fix filesystem issues, which can cause images to fail.
This is espically true for resizable images.

This is true.

You should be chkdsk’ing and defragging before taking up any image, [B]even if you arent using FOG[/B].[/quote]

ill keep that in mind but my windows 7 image was fresh when i took it and windows xp image i dont really keep up anymore since we are deploying windows 7. The issue now is with this [SIZE=3]“can’t have partition outside the disk” error [/SIZE]
[SIZE=6][B] [/B][/SIZE]

[quote=“rixter, post: 376, member: 168”]If you can, deploy that windows 7 image on another machine, create a new image, this time make it resizable, run chkdsk /f, push it back to the server under the new image, then try it again on the machine that is having problems.

If you can’t do this, I am not sure of any other options you have. (possibly creating a partition the exact size of the one from the machine it was pulled from?)[/quote]

I have my windows 7 image that is not resizable because it has 2 partitions that it created when i installed windows 7 from scratch.

[quote=“rixter, post: 371, member: 168”]Of course it matters, the reason to run chkdsk is to fix hard drive issue (file index’s, truncated files, etc.) so running it before you upload is very important, as you don’t want corrupted data to be uploaded. ntfsresize is a tool that runs within the fog environment, and if you have disk issues it will normally let you know, but not always. Sysprep only prepares the files and registry for an image creation, it doesn’t touch the disk structure. As a matter of fact, I rarely use sysprep on xp anymore, with windows 7 though its important. Defragging before you image can reduce your image size drastically as well, when you have ‘unorganized’ data spanning across 10 gigs, but only are using 4 gigs of space, it picks the last place on the disk there is data and creates the image based on that. I have solved SEVERAL ghosting issues by using those 2 tools before I upload the image. Even issues that crop up after the deployment can be fixed by that.[/quote]

i’ll keep that in mind but the image i’m trying to deploy right now is the windows 7 image, the windows xp works on this one

[quote=“rixter, post: 366, member: 168”]My win7 images are setup for ‘Single Partiton (NTFS Only, Resizable)’ and seem to work fine (I think fog expects the extra 100mb hidden partition when you tell the image its windows 7). On your XP machine if you still have the original setup, do a defrag, then chkdsk /f, and reboot and let it scan, then reboot at least 2 more times (something I read about a few months ago) and it might fix your issue. You should always chkdsk /f before uploading a windows image.[/quote]

I know it runs a chkdsk after the image is deployed and i havent anyone metion doing it before you upload the image. But i images are sysprepped before they are uploaded so i dont think a chkdsk matters in that scenario…but as far as the windows xp image goes i have no problem deploying it to other computers it’s just every once in a while i run to it. Right now i have a desktop setting next to that i get that error on no matter what i do though

one is windows xp and that one is resizable. The other one which is a windows 7 image that is not resizable and if i understand correctly it must be deployed to a drive exactly like the one the image was taken from…

i’m running fog 0.32 on a ubuntu-10.04.3 server. on some computers when i attempt to deploy an image i get the error that says “can’t have partition outside the disk” i have tried using different partition tools to work with the partitions. I have tried blank partitions, formatted partitions and nothing seems to work.

The drives vary in size but none are under 100 gigs and 2 images i use the most are no larger than 25gigs, does anyone have a solution to this ?