Posts made by jc35

@george1421
OK,
How to do mark this post as solved ?

@Tom-Elliott said in problem with hostname.php when i migrate 1.3.4 => 1.3.5.:

#!ng = Not enabled globally.

Is the value enabled in Services->Hostname Changer?

Hello,
thank you very much.
It’s work fine.

what is better wget or curl ?

what is better hostname.php or hostinfo.php ?

@Tom-Elliott

@Tom-Elliott said in problem with hostname.php when i migrate 1.3.4 => 1.3.5.:

@jc35 So the problem is likely authentication with the other database?

the authentication is it different that web interface ?

@Tom-Elliott I don’t know, I have just the message “#!ng” since 1.3.5.
The web web interface it work fine.

@george1421 I install fog with a local database, after I change the config.class.php for use with a database on another server.

@george1421 It’s work with the database is local, but it doesn’t work with the database is on another server.

@Tom-Elliott Hello, I try this, with 1.4.0-RC3, I have the same problem, I think we have a problem with database, but I don’t know how to find this problem.

@george1421
Okay, I’ll look at that.

@george1421
We have return to 1.3.4 and it’s works. We try to duplicate database and with the dev server we try to connect with 1.3.5 to connect to find what’s th problem with database and fog 1.3.5.
our dev server is on 1.3.5

sorry for very bad english.
Thanks for your answer.

@george1421 said in problem with hostname.php when i migrate 1.3.4 => 1.3.5.:

@jc35 Now that I’m aware of what you are trying to do, then this post will give you the background: https://forums.fogproject.org/topic/6463/expose-fog-host-and-image-properties-to-post-install-scripts/10

In your fog post install script you need to add this code

  . /usr/share/fog/lib/funcs.sh;
  wget -q -U '' -O /tmp/hinfo.txt "http://<fog_server_IP>/fog/service/hostinfo.php?mac=$mac"
  . /tmp/hinfo.txt
  rm -f /tmp/hinfo.txt

Once you stat the hinfo.txt file ( . /tmp/hinfo.txt) the following variables will be added to your postinstall bash shell.

$hostname == name of the host (should overwrite existing $hostname)
$hostdesc == Description of host
$imageosid == Operating System ID (should be the same as $osid)
$imagepath == The root path of the image(should also be the image name)
$hostusead == 1 or 0 to add host to AD
$hostaddomain == host domain name
$hostadou == host target ou
$hostproductkey == host product key
$primaryuser == Value from Primary User field
$othertag == Value from OtherTag field
$othertag1 == Value from OtherTag1 field
$location == Location Name from location plugin
$sysman == System Manufacturer from smbios
$sysproduct == System Product Name from smbios (from full registration)
$sysserial == System Serial Number from smbios (from full registration)
$mbman == Motherboard Manufacturer from smbios (from full registration)
$mbserial == Motherboard Serial Number from smbios (from full registration)
$mbasset == Motherboard Asset tag from smbios (from full registration)
$mbproductname == Motherboard Product Name from smbios (from full registration)
$caseman == Case Manufacturer from smbios (from full registration)
$caseserial == Case Serial Number from smbios (from full registration)
$caseasset == Case Asset tag from smbios (from full registration)

From there once you have these bash variables you can use them in your post install script. This document shows you what could be done with a post install script: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

more precisely you can use the variables with sed to replace settings in your unattend.xml file. Such as changing the computer name to what was collected from the hostinfo.php page.

sed -i -e "s#<ComputerName>\([^<][^<]*\)</ComputerName>#<ComputerName>$hostname</ComputerName>#gi" $unatendfile 

I have try this, it doesn’t work.
I think the problem is database.
We return to 1.3.4.
Thanks you very much for your answer, we try to go to 1.3.5 later.

@Wayne-Workman
On my test server on local base is work fine on local base,. When I try to use our base on another server I have same problem, I think the is a problem with our database on other database, i don’t understand why.
Can I do a schema updater ?

@george1421 said in problem with hostname.php when i migrate 1.3.4 => 1.3.5.:

The hostinfo.php is setup so that postinstall scripts can pick up details about the current deployment. This script outputs the data in a form that can be easily used by a bash shell.
That is why I asked what are you trying to accomplish.
Yes you can not view that data with a browser, that is a security attempt to only allow certain devices (FOS Engine) to access the data. But there is a hack to get around that too.

I want get some host information as hostname, adou, for modify the sysprep file in postinstall.
I read to get this information with hostinfo.php, but i don’t understand how to use it.

I try with :
wget -q -O /tmp/hinfo.txt “http://${web}service/hostinfo.php?mac=$mac”
. /tmp/hinfo.txt

The content of /tmp/hinfo.txt is “Cannot view from browser”.

@jc35 I don’t understand what happen, because I test on a test server (1.3.5) and it’s work.

Hello,

@Wayne-Workman said in problem with hostname.php when i migrate 1.3.4 => 1.3.5.:

The query looks wrong. This works for me on 1.3.5:
http://10.0.0.2/fog/service/hostname.php?mac=00:26:2d:b4:d9:25

it doesn’t work for but it work in 1.2.0,1.3.4.
I try

echo wget -q -O - "http://10.0.0.2/fog/service/hostname.php?mac=xx:xx:xx:xx:xx:xx" 2>/dev/null

Hello,
@george1421
I want to get hostname and active directory information.

Server

• FOG Version: 1.3.5
• OS: debiaqn 8

Client

• Service Version:
• OS:

Description

Hello,
To get some informtation hostname,active directory,… with this command :
hostinfo = wget -q -O - "http://${web}service/hostname.php?mac=$mac" 2>/dev/null
It’s works fine in 1.3.4.
In 1.3.5, I have #!ng
How to get information in 1.3.5 ?

@george1421 Hello, thanks for your answer, Sorry, I change the path and I foget to copy postinitscripts.

Hello,
I test in debug mode, when I launch “fgo” and I have a message “* Running post init scripts…/bin/fog: line 20: fog.postinit: No such file or directory”

Sorry for my very bad english.

@Tom-Elliott said in change color of icon "upload":

I don’t think changing the color should matter at all. If people are clicking the button, I don’t think the reasoning for the clicking is color based or not.

That said, what is the “warning” for? If you’re capturing an image, you’re capturing an image. if you don’t want user’s

Yes, It attracts user attention. I change color in red with other version, but I must do it after each update. actually we work on 1.2. It is true that with version 1.3, it is obsolete with the protected image.

to accidentally overwrite an image, why not just set the image to “protected” and/or change the files so they’re immutable?

Sorry I don’ty see this in 1.3.
We change version monday 20 febrary.