Latest FOG 0.33b
-
I found an issue with mps deploy in that it wouldn’t cycle thru the partitions. I’ve modified the code base so that, from my perspective, it seems to cycle through the partitions again, though I don’t know how well it actually works.
I’ve also added some checks/balances if using windows 8. I’m told the EFI Partition is fat32, so I added a base element to partclone.fat on the second partition if the os is windows 8. There’s a third partition that is blank, but seems to be needed, so I also added a base of code that adds partclone.dd on the third partition if the os is windows 8. Hopefully this will work, but I have no way of knowing as I don’t have windows 8.
-
if you want to try it download it from:
[url]https://mastacontrola.com/fogboot/init.gz[/url] -
r1111 released. MPS imaging (Multi-Part Single Disk) should work now. MPA always did, but MPS seemed to have issues due to ntfsfix command. It’s unneeded during deploy anyway, only really needed on upload.
While still testing, it should upload/redeploy the EFI and MSR partitions Windows 8 natively seems to generate. Hopefully we’re that much closer to true Windows 8 Support.
-
r1112 released.
Hostname Early should now work properly. I don’t know if the same keys are used for Win 8, but they are working for Win 7. Task refresh rate updated to 5 seconds instead of 10. Limit progress information to active tasks screen. Hopefully you enjoy. -
I will give it a try thanks again for your hard work. I will keep an eye out for the snapin fix for now I am just removing them and re adding them with the correct info. also Should windows verbals work? like %windir%\system32\cmd because it does not seem like they do with the run with line with the snapins.
-
r1113 released.
Snapins that already exist on the system are now able to be chosen. Better error management/visability on the coding realm as well.
-
r1114 released.
Had a mistake on checking. $_POST[‘snapin’] should always be null as it’s a file. The vars to check against are: $_POST[‘snapin’] and $_FILES[‘snapin’][‘name’].
-
Don’t worry guys, I’m already aware that hostname_early is not working…yet.
I thought it was, I tested the scripts but I just got done testing a job. It seems that I have to export the win7sys variable otherwise the changeHostname function doesn’t know how to mount the registry hive. Why this worked for windows XP, I haven’t the slightest, but I imagine exporting that variable will do the trick as well. I’m testing it right now, will be about 20 minutes or so.
-
Thanks for the capone stuff, will check it out over the next day or so.
Have just noticed a typo in installfog.sh, double equals on line 176.
I’ve changed our 0.32 install to include capone deployment in the “imaging over last 30 days” graph by:- change the source of this graph from tasks to imagingLog.
- change capone.php to insert an entry in the imaginglog
Any chance of doing something similar at 0.33?
as a further thought
3 add a field to imagingLog, to store the pc id criteria, ie for capone “system-serial-number=12345”, or a normal task “mac=<mac address>”
This would keep an imaging history for each device. (multicast may be an issue)
-
That double ='s is not a typo, it’s a comparison operator. Meaning, if the value of: “$bldhcp” is equal to “0”, then continue on. In shell scripting, you can use double == or = as comparison for if statements.
-
r1115 released,
Hostname_early appears to work properly for windows 7 systems. XP already worked, but 7 didn’t. Should be good now.
Still don’t know about the changer from FOGClient, but I’ll try to look into it tomorrow.
-
r1116 released.
Truncates hostname to 15 characters. Also added a service script that verifies that the hostname is valid/unused. This way less confusion between GUI and Fog registration scheme.
-
Aha, I understand the issue around the double equals sign now.
This is on Ubuntu 12.04 LTS, I haven’t tried on Fedora 20.
If I call “sh installfog.sh” it uses dash, which doesn’t support the “==” operator, and flags an error.
If I call ./installfog.sh it uses bash which does support “==”. -
small esthetic bug in 0.33b:
when you do ./installfog.sh
…
What is the IP address to be used by this FOG Server? [inet:192.168.0.3] [enter]
Invalid IP address!What is the IP address to be used by this FOG Server? [inet:192.168.0.3]192.168.0.3
……
On a Windows DHCP server you must set:
option 066 & 067
we can specify also that in 066 user must set the ip of fog, and in 067 “pxelinux.0”
…i edit this message today to post all bugs that i found…
-
So I’ll check the loop for the ip. Then you just want me to add the info of what the options do?
-
fabritreno,
What OS did you install this on? I’ve never seen any issues with this particular issue, as it already checks if the entry is null, but the [] part is filled out, use the [] part.
Then it tests if either the suggested IP or the entered IP is valid. If it’s not valid (extra spaces included) then it fails with that message. My guess is something is a little different on your server.
-
r1118 released.
Adds information for Option 066 and Option 067 per fabritreno’s suggestion above.
trims the last / off of the path name when deploying a multicast image.
-
[quote=“Tom Elliott, post: 21602, member: 7271”]So I’ll check the loop for the ip. Then you just want me to add the info of what the options do?[/quote]
for some reasons, instead of “xxx.xxx.xxx.xx” “inet xxx.xxx.xxx.xxx” are assumed as default. I think that is taked from /etc/network/interfaces config file.
my file:
#----------------------The loopback network interface
auto lo
iface lo inet loopbackThe primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 192.168.0.2
#---------------------- -
[quote=“Tom Elliott, post: 21604, member: 7271”]fabritreno,
What OS did you install this on? I’ve never seen any issues with this particular issue, as it already checks if the entry is null, but the [] part is filled out, use the [] part.
Then it tests if either the suggested IP or the entered IP is valid. If it’s not valid (extra spaces included) then it fails with that message. My guess is something is a little different on your server.[/quote]
is a ubuntu server edition 12.04 LTS virtualized on a win2008srv with virtualbox installed
-
[quote=“fabritrento, post: 21609, member: 21607”]for some reasons, instead of “xxx.xxx.xxx.xx” “inet xxx.xxx.xxx.xxx” are assumed as default. I think that is taked from /etc/network/interfaces config file.
my file:
#----------------------The loopback network interface
auto lo
iface lo inet loopbackThe primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 192.168.0.2
#----------------------[/quote]It’s actually taken by the command:
[code]ifconfig | grep “inet addr:” | head -n 1 | cut -d’:’ -f2 | cut -d’ ’ -f1[/code]I have a feeling, something like:
[code]ifconfig | grep “inet addr:” | head -n 1 | awk -F’:’ ‘{print $2}’|awk ‘{print $1}’[/code]Would work better as it ensure’s the whitespace is removed, where cut only removes a single space (based on the -d’ ').
