Fog 0.33b Snappin deployment
-
Can you do the reinstall of FOG at 1161 (of course backing up the init.gz)
But before running the install script,
rm -rf the /var/www/fog directory (whereever it actually is.)
-
Reinstalled like you asked and I get the same thing… I dont see the hostname change anymore like i used to. I used to see it right after the image was deployed right before reboot.
-
What do you mean, “you get the same thing?”
The host name or no host name happens?
I’m about to release r1162, found the place where ntfsresize was supposed to happen in my scripts, but wasn’t happening. Why?, you ask with a slight bit of confusion. Because I forgot to add the resize part.
My guess with your issue is, the sysprepped system was trying to expand, but the way the drive was sized, it couldn’t expand any further, therefore it wouldn’t work on your system. I’m using VM’s so things can happen in the background dynamically which would be why I wasn’t seeing the same issue you where. I’m surprised others weren’t as well.
-
[quote=“Tom Elliott, post: 22172, member: 7271”]What do you mean, “you get the same thing?”
The host name or no host name happens?
I’m about to release r1162, found the place where ntfsresize was supposed to happen in my scripts, but wasn’t happening. Why?, you ask with a slight bit of confusion. Because I forgot to add the resize part.
My guess with your issue is, the sysprepped system was trying to expand, but the way the drive was sized, it couldn’t expand any further, therefore it wouldn’t work on your system. I’m using VM’s so things can happen in the background dynamically which would be why I wasn’t seeing the same issue you where. I’m surprised others weren’t as well.[/quote]
I get the same thing as before. The host name doesn’t change, nor do I see it reporting that its changing the hostname like in .32fog right before restart after imaging.
-
So the changing hostname before restart after imaging probably isn’t happening because you disabled HOSTNAME_EARLY in the FOG Settings, if I recall correctly.
What does the fog.log say in regards to the hostname changer?
-
Did r1162 fix the Hardware issue you were seeing, if you use the available init.gz (the one I packed, not the one I packaged for you specifically)?
-
[quote=“Tom Elliott, post: 22229, member: 7271”]So the changing hostname before restart after imaging probably isn’t happening because you disabled HOSTNAME_EARLY in the FOG Settings, if I recall correctly.
What does the fog.log say in regards to the hostname changer?[/quote]
I set HOSTNAME_EARLY back to 1
Here is the Log.
[CODE]1/29/2014 11:56 AM FOG::HostnameChanger Attempting to connect to fog server…
1/29/2014 11:56 AM FOG::HostnameChanger Module is active…
1/29/2014 11:56 AM FOG::HostnameChanger General Error Returned:
1/29/2014 11:56 AM FOG::HostnameChanger #!er: Join domain disabled on this host.
1/29/2014 11:56 AM FOG::HostnameChanger Host name was not found in the database.[/CODE] -
[quote=“Tom Elliott, post: 22230, member: 7271”]Did r1162 fix the Hardware issue you were seeing, if you use the available init.gz (the one I packed, not the one I packaged for you specifically)?[/quote]
I have yet to try it, today is Hectic for me, I have had circuits to our remote locations dropping all day.
I will try and see if I can test when things calm down. -
And you have the system setup to join the domain as well, don’t you?
I, again, made a mistake.
The line with the checks and balances for this is supposed to read (in plain English)
If the host is not to use AD, print er: BLAHBLAHBLAH
Otherwise continue on your merry way.I forgot the not part of it.
So it was reading:
if the host is to use ad, print er: BLAHBLAHBLAHI’m sorry I’m such an idiot.
-
“Fix issue on hostname changer where if something was true, it continued on where it shouldn’t have. Add base elements for the Loation plugin (NOT READY YET). Add openssh to init.gz, mostly for me, but could prove useful.”
r1163 releasing as we speak.
-
[quote=“Tom Elliott, post: 22237, member: 7271”]And you have the system setup to join the domain as well, don’t you?[/quote]
Yes I do.Cool, trying to get free’d up to test!
-
That’s why you knew something wasn’t working right.
It does make me wonder though, should I through exception, or just print that the system isn’t going to join the domain?
I’m guessing, based on this, a print is what’s needed. I’ll make that change and release as well.
-
This post is deleted! -
[quote=“Tom Elliott, post: 22243, member: 7271”]That’s why you knew something wasn’t working right.
It does make me wonder though, should I through exception, or just print that the system isn’t going to join the domain?
I’m guessing, based on this, a print is what’s needed. I’ll make that change and release as well.[/quote]
ok, let me know, I am ready to pull the trigger on the next release. -
r1164 released. Hopefully fixes ntfsresize for xp, specifically does ntfsresize for win7. Also changes from throw exception, to print in hostname.
-
Good news! as soon as I upgraded to R1164 the PC that was setting here already images rebooted twice. once for the hostname and once for the domain.
I am now trying to re-image it and see how that goes. -
I did however come accross another bug, If the machine does not image for some reason or another and you have snapins associated with the PC, active snapins start to pile up with no way to kill/cancel them.
[IMG]http://imagizer.imageshack.us/v2/800x600q90/191/rjum.png[/IMG]
-
There is a way to kill them, just your icon’s not showing.
-
[quote=“Tom Elliott, post: 22256, member: 7271”]There is a way to kill them, just your icon’s not showing.[/quote]
mysql
truncate activeTasks; -
ok all is good! it imaged fine, I am waiting to see if the snapin loads or not.
