Posts made by ch3i

@Jean-Jacques-Morda Hi, it’s not a FOG problem/feature, it’s BIOS configuration : WOL is not WOL+LAN boot auto

@Jean-Jacques-Morda Hi, you have no problem in upload task ?

@ddesabatine You are welcome

Move to Feature Request forum

Hi,

I’ve a bug on host general display in 3696 revision :

I’ve updated to 3710 and same problem. I’ve checked the function.sh file and saw that it was my “custom version” (https://forums.fogproject.org/topic/5304/3639-php5-json-failed/7).

I’ve deleted the SVN folder, checkout fog svn and now when I want to install fog I’ve that error :

  Confirming package installation.

 * Checking package: apache2...................................OK
 * Checking package: php5......................................OK
 * Checking package: php5-json.................................Failed!

Same error that Tom has fixed a week ago.

Regards,
Ch3i.

@ddesabatine sudo apt-get update; apt-get dist-upgrade --force-yes

@ddesabatine This : https://wiki.fogproject.org/wiki/index.php/SVN#Install_Subversion_2

Tested on Ubuntu 14.04.

@Andrew-Farney Just upload my HP Elitebook 820 with SSD (with trunk) and download without problem
@Wayne-Workman said:

Upgrade to trunk and you can choose your partitions.

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

@techno.clarensac You can chat with me on the forum. (Je suis souvent en ligne)

@belac Hi, I’ve the same version, but have the good version number.

@Oleg said:

it was also not possible to see the current status of downloads or uploads.
Upgraded 10 min ago to 3677 and now both problems seems to be gone.
Thanks.
If there are any bugs in the SVN, is it correct to post them here?

For SVN bug the right forum is in Developers/Bug Reports/.

@Wayne-Workman said:

@Lyendril You can use Magical Jelly Bean keyfinder to extract your key.

Also, if the key is on a sticker on each computer, you could simply just type in this key after each imaging.

If you don’t have a Windows Installation Disk, you could just download one. Enter your key into it and see if it works. If it does not, you could activate over the phone (once) and then take an image of that.

I don’t think it matters so much that each computer is using the key it’s supposed to use - as much as - you have a legal key for each computer that is running said Microsoft product.

+1
In OEM installation, manufacturers use only 1 windows key for all computers (tested on HP), you can saved it (key/certificate) by using ABR (activation backup & recovery - google it) and use it with Windows 7 Digital River download (Not provide anymore by Microsoft but you can find it by another way…).

If you want more details PM me.

@Gardinero Your /images must have 777 recursively.

@Oleg Hi, please post your apache error.log.

@sacha_marin Hi, how have you added the “new disk”, another mount point with another storage in FOG ? Please provide more details of your installation.

@kverkiss said:

@Wayne-Workman Hi Wayne,

It seems that the problem is resolved now. The problem appeared to be in the image upload with this 102 MB partition. I’ve booted a gparted iso from CD and removed this partition, then I booted a Windows 7 DVD to recover the drive as it didn’t want to boot with this 102 MB partition.

I totally agree with your remark about the vulnerabilities provided by the manufacturer’s image, but I’ve been completely striping that out.

Besides, I cannot use an OEM license key when I install Windows myself. For this reason I’m stuck with this image. I need to buy retailer CD key’s instead for about 60 machines.

Thank you very much for your help though, if others have simular problems with OEM images provided by manufacturer’s, I might be able to help them.

You can install Windows 7 from scratch with OEM licence using ISO provided by Digital River, backed Windows Key/Certificate on an OEM installation with abr (http://directedge.us/files/abr/ABR-1.0.exe) and restored it on your fresh install. Upload/Deploy/Enjoy

@Gardinero Hi, After tftp boot, the init is loaded using FOG web server >> FOG_WEB_HOST. Not sure you can modify that.

@Jason-Sauders Hi, image files are moved by FTP, use that : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

@Wayne-Workman said:

If we can specify a FTP path for storage nodes, and that path be used for all things related to FTP with that storage node, this would permanently solve all issues with using NASs with FOG.

I feel like this feature is very needed as the issue of using various brands of NAS repeatedly arise in the forums. Additionally, there is a slue of WiKi articles just on using various NAS devices with FOG that are… sometimes… poorly written and confusing and often specific to one type of setup with one type of NAS device. These articles are fairly unmanageable because everyone with WiKi access does not have access to all these devices in order to update or improve the article’s content.

Usefull feature !

@brycew said:

yes all done on same version. I have not tried to mount from a CLI. Here is my mount info.
showmount -e 10.1.0.8
Export list for 10.1.0.8:
/images/dev *
/images *

Exports and NFS service seems to be ok. Please try to mount via CLI and read/write in.