Hello,

We have just update a FOG 0.32 to version 1.2.
Local default storage works fine but the old system administrator added a 2nd storage manually.
I mean that he made a directory called “images” on a linux server (it’s a backuppc server in fact), add line for NFS on “exports” and create a local fog user.
I have check SSH login with fog account using the password write for this storage on GUI and it works fine.
FTP is running and works fine too. I have check connection from the FOG server.
We read fine this storage “Hardware Information”.

Is there need package to read image size ?

Thank you.

Also checked on an other fog install so this is not an error that we both had on our configuration.
Yet, i don’t have problem of size as you so i don’t think this will change something.

If i have any other idea, i’ll reply but i think my knowledge of fog is too limited.

Not sure of this but there is check disk thing in options -> general settings -> FOG_DISABLE_CHKDSK
It looks disabled for me because it’s ticked.
Maybe translation isn’t good ?

Directly checking deploy problem ?
Maybe image isn’t saved the right way on the server and already has a fixed drive size after upload ?

There is 2 different FOG account on FOG in my case.

• storage account AND TFTP/FTP account that is the local fog account
• GUI account that is an sql account

The first one can be seen in storage and in options “TFTP Server” at FOG_TFTP_FTP_PASSWORD.
I can be used on server TTY, for ssh connexion and FTP.

I don’t use ExpandOSPartition on my sysprep so this shouldn’t be needed i think.
Have you only one partition on the drive (other than the small one for system created by Windows) ?

[quote=“Tom Elliott, post: 37198, member: 7271”]Your stuff should be perfectly fine now.[/quote]

Not exactly.
I will explain somewhere else that on this topic.

Are you sure that your image type is on resizable single partition on FOG web page ?

Is it normal that it display current blocks and total blocks for a resizable upload ?
I don’t remember having this (maybe i just don’t take time to look during download and upload).
This let me think about RAW format.

Why i feel that Tom is thinking of me when we speak of 100% partition problem ?

Hello again,

we all wonder about compatibility when we update FOG to the last version and we don’t all have the time to search the forum for our brand or just inform people on forum of our solutions.

Could it be possible to add a “send anonymous data” that would bring back usage of tftp files and boot exit type with which computers brands and series of the FOG users ?
This could be store to a database that would give us a list of what tftp file choose and what boot exit type ?

Thank you.

Tom is a wonderful contributor to the project (with Junkhacker from what i saw), a great support technician and very professional worker.
I have nearly the same daily work as him (i’m work in 3 college with around 500 computers in total, maybe more) and i couldn’t spend the tenth of his time on FOG (testing, debugging, improving, solving, etc.).

Everybody should understand that FOG is free and so, people working on the project doesn’t earn money for the time spend on it.
They only earn, other than the last added “Donate” advances task, is thankfulness from us (computer user, technician, administrator and company owner) and a bit of our time for testing, and bring them back the few bugs we could see.

Again, Tom, thank you.

Hello,
could you display the list of deployed computers on the main page graph when we go over the dot ?
We could easily see what we have deployed the past few weeks without going to the report management.
Thank you.

I don’t activate Windows when the image will work for different brand of computer unless i would have buy an amount of licence but i will keep note of the amount used at the same time in this case.
I use OEM key from the brand of the computer after deploying this “multi system” image.
I only backup keys when image will stay on the same computer brand and serie.

For me, using brand installed OS then remove ALL unwanted and useless software and configuration or install Windows from the DVD and use the same OEM key, end at the same things.
The 1st way can create unstable OS, unused files and unused reg key and will ask you to spend days to clean it.
The 2nd way reach the minimal size possible.

The question is if the OEM licence is for Windows itself or for Windows with the brand software layer.

[quote=“Tom Elliott, post: 36441, member: 7271”]What is this?[/quote]
A drunk user ? haha
I don’t think there is link with the topic.

.pxe and .kkkpxe does exist on fog 1.x ?
In the updates, i only remember that it was write kpxe and kkpxe.

I see that services were not running when you run the stop command.
Does it change something after you started them manually ?

When i have strange things, i run install.sh and fog takes it as an update (no db drop or image deleted).
In fact, i do it for each new svn version.
Maybe this could fix something ?

This depend of your hardware, how you work and what you want to do.
My image were not working and i had to deploy some before this was fix by Tom so i had no choice than build a second server and keep the old one ready to deploy.

I’m under 1.2 and log should be somewhere else.
Try to find it with this command :

[CODE]
locate fogreplicator.log
[/CODE]

Hello,
i had to change “undionly.kpxe” to “undionly.kkpxe” to be able to boot on pxe with my laptop.
What are the difference between them ?
Would it be possible to see computer boot fine with the “undionly.kpxe” then not work with the “undionly.kkpxe” ?
Thank you.