Glad it was helpful.

[quote=“ssx4life, post: 10651, member: 268”]This might sound a bit silly, but do we really want to support windows 8? (I’m 1/2 kidding here)[/quote]

Really? If Win 8 support is the hold up, then I say release without it. Then work on support in the next release. BTW, those of you that don’t like Windows 8, just install Classic Shell ([url]http://classicshell.net/[/url]).

What is the status of the project? It has been a while since I’ve done anything. Do we need more specific testing at this point?

Cheers,
astrouga

Thanks for the feedback. I might be getting some of the sff and the usff 7010s. I’m hoping one image will manage for both. I’m glad you mentioned the ssd issue – something to consider. Perhaps I’ll just order one and test it out before I commit.

Cheers, astrouga

Thinking of getting some of the 7010 systems too. Anyone having luck or problems with the Ultra small form factor variety? Kevin, can you chime in since you’ve had success?

They are just different kernels built on different linux kernel versions. They have different drivers built into the kernel.

You can get them from here:
[url]http://sourceforge.net/projects/freeghost/files/Kernels/[/url]
Here is a link that show how to switch between them:
[url]http://community.spiceworks.com/how_to/show/2338-setting-up-fog-to-use-different-kernels-for-different-computers[/url]
Here is list of kernels that work well for various computer models:
[url]http://www.fogproject.org/wiki/index.php/WorkingDevices[/url]

OK, here it is:
[url]http://fogproject.org/forum/threads/extend-your-disk-partition-to-max.3640/[/url]
astrouga

Since I use “one image to rule them all”, I have to remember to shrink my partition down below the smallest disk in inventory before I sysprep it. Otherwise the image will fail on some systems. I have some disks that are 80GB and some that are 500GB. So I usually manually shrink my disk down below 80GB before I sysprep it. Then after imaging a system with larger disks, I have to extend the partition to the max size. I got tired of doing this manually, so I wrote a vbscript to do this for me. I’m sharing it in hopes that it helps others, but also to see if anyone has a better way.

I actually use this snippet of code in a larger vbscript that does other things (local account creation, firewall exceptions, registry changes, printer installs, etc), but I’ve pulled out necessary the code below. Should be complete. Note it is actually two files. One is the vbscript that just runs diskpart, the other is a text file that contains the options to pass to diskpart.

[B][U]extend_max.vbs[/U][/B]:
[CODE]’ ########## Extend Disk Partition (MAX) ##########
LogFilename = “C:\Windows\Setup\InstallLog.txt”
LogFile.writeline “-------------------------------”
LogFile.writeline “Extending partition to max size:”
LogFile.writeline “-------------------------------” & VbCrlf

diskpartScript = “C:\Windows\Setup\Scripts\extend_max.txt”

Set oShell = CreateObject(“Wscript.Shell”)
Set oShellExec = oShell.Exec("cmd /c diskpart -s " & diskpartScript)
set oStdOutputText = oShellExec.StdOut

Do While Not oStdOutputText.AtEndOfStream
diskpartOutput = oStdOutputText.ReadLine
LogFile.writeline diskpartOutput
Loop[/CODE]

[B][U]extend_max.txt[/U][/B]:
[CODE]select disk 0
detail disk
list disk
select volume c
extend disk 0
list disk
exit[/CODE]

I call this script by adding a line to my SetupComplete.vbs script. Something like:

REG ADD %KEY%\005 /VE /D “Extending disk partition size to max” /f
REG ADD %KEY%\005 /V 1 /D “%systemroot%\Setup\Scripts\extend_max.vbs” /f

astrouga

[quote=“dvlsg, post: 8532, member: 1186”]Well, I was unaware that vbscript was even able to do that. It’ll look fancy to me no matter what, haha.[/quote]
That is because I just use vbscript as a wrapper to run a diskpart via the cmd line. Not so fancy any more, huh?

astrouga

RE: partition extending script.

Sure, I’ll dig it up later and post it to a new thread. I’ll post the thread link here when I do that. It is nothing fancy. Perhaps someone else will have a cleaner method.

astrouga

My snapin method probably needs polishing. I have a samba share on my FOG server that I use to store all of the installers. All of my snapins are vbscripts that are 90% the same code. Really all I do is map a drive to the samba share on the server, copy the installer, run the installer, write to a log file, and disconnect the mapped drive. The vbscript is a little lengthy because of the logging, but it always works for me.

Regarding Adobe, I’d just apply for a distribution license from Adobe so you can get access to their versions of shockwave, flash and reader for distribution. The provide several versions of each, one is an msi file. I’ve never been turned down. I think it lasts for a year.

[url]http://www.adobe.com/products/reader/distribution.html[/url]

Lee, can you give some more info on the custumization tool? Not sure where to find it.

–astrouga