Latest FOG 0.33b
-
OK, Can it be changed to use the fog client again? I will also need the Active Directory Join part of that as well. Changing early might be nice but seems like it’s building a feature that FOG already has, unless there will be some other way to join AD in FOG and do all of the other nice features in the client.
If you want access I can PM you the details you need.
-
Join ad still works fine. The hostname changer was added to make imaging that little bit faster. However you can turn off the early feature within the fog configuration fog settings hostname_early bit.
-
In your test setups does the rename early work as expected?
-
Vincent,
It looks like it is imaging and changing the name as expected. Though I suspect, if you’re imaging from Registration Scripts this will not work. There was a problem, that even I didn’t know existed, until I looked deeper into the code and tried finding everything that was needed.
My next revision should address this for us all.
r1054 addresses this.
-
When I setup, I pre-stage all the host’s MAC addresses into fog. I then add them to a group and start the deploy task using the group. The only thing I do on the client machine is turn it on.
This matches how I setup my production setup where we used the DHCP leases to identify the MAC of every PC and then had one of the trainees set the PCs to PXE boot. When we buy new machines, the MAC is written on the box so I enter those as well and as soon as they are unpacked and plugged in… they run the task that I created for them.
I will nuke my Debian FOG server and remake it with r1054 and try again.
-
You don’t need to nuke to go to the latest. Just perform an update. Basically, download the latest and greatest. Then re-run the bin/installfog.sh script. It will automatically update everything for you. As I haven’t made any changes to the Schema, Database information should remain in-tact.
-
It seems that the buttons on the GUI are missing… possibly something to do with the new language stuff.
When I installed I selected not to install language packs.[ATTACH=full]464[/ATTACH]
[url=“/_imported_xf_attachments/0/464_GUIMissing.png?:”]GUIMissing.png[/url]
-
Try it again. I noticed that issue as well. Updated the files to fix the issue. You should be good to go.
r1055.
-
since your adding the internationalization… would you recommend selecting the language packs or going without?
-
Go without for now. The packs its referring to as far as I can tell is dealing with stdout not the web stuff.
-
still got the same issue downloaded about 5 minutes ago.
-
What does your error logs say?
-
Vincent,
I’m looking into this issue, and installing debian and then installing the fog server. Hopefully I’ll replicate your results and give a better answer and fix this issue for all of us.
-
I know what the problem is, and have fixed the issue. During all my “changes” I forgot to require the text.php file for menu generation, as well as the language bar generation.
Hopefully 1056 will work much more betterer.
Please forgive my single file overlook there. I’ve been modding a lot of files lately, so I think it warrants a missed file here and there.
-
you should give coding lessons
i’ll do some more tests tomorrow
-
r1057 released.
This should remove erroneous error messages, such as Illegal Offset Type, and the functions need to match. I doubt I’ve gotten all, but it should be close.
-
Something I’ve noticed… When you make a host the client settings are all off.
The Rename early still isn’t renaming my machines. and the fog service seems to be giving an error.
Could one of the changes in the database mean the client is looking in the wrong place?
[url=“/_imported_xf_attachments/0/466_HostnameChangerError.png?:”]HostnameChangerError.png[/url]
-
Are the services enabled on the FOG Server; they have to be globally enabled, and enabled on the Host as well.
Rename early works on mine, but that was testing with Windows XP. I’ll test again with both XP and 7 just to be on the safe side.
-
It is globally enabled and enabled on the host. I was thinking a change in database might be the cause due to ‘Hostname not found in the database’
I know the database from 0.33 isn’t compatible with 0.32… has this variable been moved/renamed.
My client OS is Windows 7 Enterprise 64.
-
to my knowledge, the host name field is still stored in hostName on the hosts table. However, I’m not sure if this was the case with 0.32.
I’m checking my code right now, but I’m not seeing why it would be returning with that.
