Hostname Changer No Reboot
-
It’s probably noteworthy to say that you should absolutely NOT take an image from computers that are bound to an Active Directory domain…
It’d probably screw up the hostname changing… and it’d definitely screw up the trust relationship between your DCs (domain controllers) and the deployed client images…
-
@Wayne-Workman We doesn’t have any image with Active Directory active, it is just normal Windows PCs
-
@Wayne-Workman Hi, I’ve done a new deploy and the hostname doesn’t change after imaging, but after it fog try to change it (* Changing hostname…Done) so it have to be something about the Windows Image that by some reason its not changing the registry.
What is the commands fog use to change it?
Can this happen because of permissions?
Thanks!! -
@Bruno-Nogueira The only thing that I can think that is not allowing the hostname to change is your image is sysprepped, but setup for OOBE mode which requires the user to create a username and hostname.
-
Maybe I found part of my solution here:
https://forums.fogproject.org/topic/3361/early-hostname-change-not-working-win7/19My image that change the hostname only have 1 partition (not counting with small windows partitions).
But the image that’s not changing the hostname have 2 partitions and maybe it is applying hostname configuration in the last partition (only data) and not on Windows partition.
I’ve tried to config my server with the steps in the link but my fog.download its a little diffrent and some commands like “xz --decompress init.xz” doesn’t work.
-
@Tom-Elliott My image is just a normal machine clone, ready to use but not OOBE (the first start is a normal windows startup with all users and everything on it).
Do you think that update to SVN fix the problem? -
I need help!
-
@Bruno-Nogueira said:
I need help!
Please look at this thread: https://forums.fogproject.org/topic/3361/early-hostname-change-not-working-win7
That person was using FOG 1.1.2 (I imagine it’s probably fairly similar to 1.2.0). They reported that the early hostname changer only tried to change the name on the last partition restored.
How many partitions does your image have?
You said you were installing “TimeFreeze” or activating it or turning it on or something. If this is “hard drive locking” software, I have some experience with this. In the case of Centurion Technologies Smart Shield and Faronics DEEP FREEZE, both of these create a “unfrozen/unlocked” partition.
If this is the case with “TimeFreeze”, then this might be why you’re experiencing these issues with the early hostname changer…
Just a guess…
-
@Wayne-Workman Time Freeze is not installed, on first boot after imaging the computer run a script to install it. When the image is deployed time freeze is not there.
I’ve already seen that topic, the problem is the file initmountdir/bin/fog.download is not exactly the same as mine.
For example, in the line 268 I haven’t “elif [ “$imgType” == “mps” ]; then” and if I search for it I have 4 or 5 lines like this.
All of them doesn’t have the same sequence:268 elif [ “$imgType” == “mps” ]; then 269 parts=fogpartinfo --list-parts $hd 2>/dev/null; 270 diskLength=expr length $hd; 271 for part in $parts; do 272 partNum=${part:$diskLength}; 273 echo " * Processing Partition: $part ($partNum)"; 274 sleep 2; 275 imgpart="$imagePath/d1p$partNum.img"; 276 if [ ! -f $imgpart ]; then 277 echo " * Partition File Missing: $imgpart"; 278 else 279 writeImageMultiCast $part 280 fi 281 changeHostname; 282 done— mod edited to use code box.
-
host_namechange_early functions by editing the registry of the computer offline
fog 1.2.0 assumed a specific partition would be used for the operating system and only tried to edit the registry there.
the latest development versions of fog attempt the edit on all ntfs partitions.
upgrading to trunk will almost certainly resolve your problem. -
Hi again!
Today I’ve installed the most recent SVN version and the problem is now solved, thanks to all!
I’m impressed with the download speed of the images… 10GB /Min vs old 4 GB /Min!!
But now I have a problem (the only problem so far). I can’t edit groups, it returns error HTTP 500. -
@Bruno-Nogueira said:
But now I have a problem (the only problem so far). I can’t edit groups, it returns error HTTP 500.
Please be more specific, exactly what were you editing with groups?
-
@Wayne-Workman In group management I have some groups with hosts inside.
Example, I have a group called “Group 1” with 10 members (hosts) and when I press edit it give error “HTTP 500”
-
Whenever you have a “Blank Page” or a 500 series error, it usually indicates an error of syntax, or some other issue. Can you go to the groups page while tailing the apache error logs and give us the output?
-
@Tom-Elliott Here is today’s output:
[Fri Jun 26 02:34:02.983126 2015] [:error] [pid 3712] [client 192.168.1.102:53150] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 608 bytes) in /var/www/fog/lib/db/MySQL.class.php on line 72, referer: http://192.168.1.253/fog/management/index.php?node=group&sub=list
[Fri Jun 26 02:45:51.502846 2015] [:error] [pid 3598] [client 192.168.1.102:53414] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 281, referer: http://192.168.1.253/fog/management/index.php?node=group&sub=add
[Fri Jun 26 02:47:03.615361 2015] [:error] [pid 21292] [client 192.168.1.102:53471] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 282, referer: http://192.168.1.253/fog/management/index.php?node=group&sub=list
[Fri Jun 26 02:49:06.558315 2015] [:error] [pid 2110] [client 192.168.1.102:53486] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 608 bytes) in /var/www/fog/lib/db/MySQL.class.php on line 72, referer: http://192.168.1.253/fog/management/index.php?node=group&sub=list
[Fri Jun 26 06:51:00.905983 2015] [mpm_prefork:notice] [pid 1990] AH00171: Graceful restart requested, doing restart
AH00558: apache2: Could not reliably determine the server’s fully qualified domain name, using 192.168.1.253. Set the ‘ServerName’ directive globally to suppress this message
[Fri Jun 26 06:51:01.109407 2015] [mpm_prefork:notice] [pid 1990] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.9 OpenSSL/1.0.1f configured – resuming normal operations
[Fri Jun 26 06:51:01.109424 2015] [core:notice] [pid 1990] AH00094: Command line: ‘/usr/sbin/apache2’
[Fri Jun 26 10:46:14.206152 2015] [:error] [pid 4622] [client 192.168.1.102:53779] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 281, referer: http://192.168.1.253/fog/management/index.php?node=group&sub=list
[Fri Jun 26 11:50:41.105491 2015] [:error] [pid 29653] [client 192.168.1.102:53964] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/fog/lib/fog/FOGController.class.php on line 281, referer: http://192.168.1.253/fog/management/index.php?node=group&sub=list -
I’m just guessing but you have a bunch of groups?
To fix the memory issue: From the fog gui goto:
FOG Configuration Page->FOG Settings->General Settings->FOG_MEMORY_LIMIT
You’ll likely find that it’s currently set to 128. Increase this a big. I normally double, as needed. (E.G. 128->256, 256->512, 512-1024)
Don’t start High though as it impacts performance of the server the more you attempt to “add”
-
@Tom-Elliott I have 14 groups and 200 hosts
Now it is working!!! Thank you very much!! But it takes a little to open…
My server have an i5 intel processor and 4GB RAM
Can this be solved by adding more RAM?
Thanks!!!
EDIT: I think it only have 276MB free -
@Bruno-Nogueira said:
@Tom-Elliott I have 14 groups and 200 hosts
Now it is working!!! Thank you very much!! But it takes a little to open…
My server have an i5 intel processor and 4GB RAM
Can this be solved by adding more RAM?
Thanks!!!
EDIT: I think it only have 276MB freeI don’t think so… this memory limit specifies how much memory a page in fog can use (I think).
4 gigs of ram is probably excessive lol. I have my virtual fog machine set to 4 gigs and it’s only using 200 ish megs of that lol…
This command will display the amount of ram free, used, and such in MB format:
free -mtotal used free shared buff/cache available Mem: 3934 262 198 2 3474 3433 Swap: 3967 11 3956 -
total used free shared buffers cached Mem: 3754 3375 379 10 84 2898 Swap: 3891 0 3891I think mine are using 3375 MB of 3754 MB
My OS is Ubuntu 14.04.1 LTS
