well,
i tried another way and solved it.
installed grab4dos on the hard drive and set up a menu that will grab and boot thinstation.iso.
captured it as a linux image, and deployed with no problems!
Best posts made by nivbehar
-
RE: boot error after deplying linux image
Latest posts made by nivbehar
-
Create New Host Bug
Server
- FOG Version: 1.3.5-RC-2
- OS: centos-7
Description
Manually creating new host in the Host management, directing me to an unknown page.
I didnt see a fix mentioning about this in the newer versions, so I didnt try to update to last git. -
Capturing images stuck on the client
Server
- FOG Version: 1.3.0-RC-10
- OS: CentOS 7
Client
- Service Version: not relevant
- OS: Linux/Windows
I noticed that since updating to 1.3.0-RC-10, I cant capture any machine.
The progress is stuck on the client, like this:
im trying to capture an image i already captured, just for testing, I left it all night and it didnt continued…
I also updated to the latest kernel: 4.7.3.
Im sure about the settings i set for the new image, since its the same as the image settings that already deployed to the machine.any help?
Niv. -
RE: Failed to add snapin, unable to locate snapin directory.
@Wayne-Workman
Thank you Wayne and Tom for your replies.
I guess i didnt understand the idea of snapins, anyway, now I do.
Eventually, I solved the problem with creating a new path to the sanpins.Regardless of this problem, I have another one now.
I just noticed that since updating to 1.3.0-RC-10, I cant capture any machine.
The progress is stuck on the client, like this:
im trying to capture an image i already captured, just for testing, I left it all night and it didnt continued…
Im sure about the settings i set for the new image, since its the same as the image settings that already deployed to the machine.Should I post a new topic about this or wait here for help?
Niv.
-
RE: Failed to add snapin, unable to locate snapin directory.
@Tom-Elliott
Hey Tom!do u mean the Storage node?
i have only the default, and it look ok:regards
Niv. -
RE: Failed to add snapin, unable to locate snapin directory.
do you mean “who” is the owner of the folder?
this is how it looks like through winscp: -
RE: Failed to add snapin, unable to locate snapin directory.
do u mean setting permission in /opt/fog/snapins to 777 ?
i did that too…didnt work -
Failed to add snapin, unable to locate snapin directory.
Hey,
First of all, thank you very much for this project!
finally a cloning solution that works, and really easy to manage. YOU ROCK!Well, Im trying to add snap-in (just a test snap-in for now) of a batch file.
This snap-in will just open google chrome on the target workstations and nothing else.
When Im trying to add the snap-in i get an error “Failed to add snapin, unable to locate snapin directory.”
I searched to that online, and saw some comments says to update fog.
I just updated fog to 1.3-RC10 - didnt fixed it.I saw about checking all the ftp credentials - did that, and still the same. (According to this link - https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#Credentials_.2F_Passwords).
I havent seen anything else online, so Im asking here for help.
tnx again,
Niv. -
RE: 1.3-RC10 - capture faild to update database
i looked for /opt/fog/.fogsettings and changed the password the for fog user to the password i set before the update.
After that, re-runed the installer - seems to fix the problem.tnx
Niv -
1.3-RC10 - capture faild to update database
hey guys,
since i have update fog server to 1.3-RC10 im getting an error while capturing.
the task is looking fine but after finished it returnes this errors:Updating Database…Failed
could not complete tasking (/bin/fog.upload)I can see the image under a folder called /images/dev with the computer mac address, but not in the actual folder is supposed to be.
SVN Revision: 5955
tnx for helping
niv -
RE: boot error after deplying linux image
well,
i tried another way and solved it.
installed grab4dos on the hard drive and set up a menu that will grab and boot thinstation.iso.
captured it as a linux image, and deployed with no problems!