Posts made by danilopinotti

@Joe-Schmitt said in Hostname is correct:

Just try disabling it, and re-imaging.

Works !

@danilopinotti Solved.
The problem was in mapping of WINS server in the image.

@Wayne-Workman said in The parameter is incorrect, code = 87:

The image was not on the domain already when you captured it, correct? Can the domain’s DNS name be pinged? Leave the OU field blank for testing until you have it working.

The machine in question is the image itself. Already we tried various combinations, with and without the OU. DNS works and can be pinged

@Wayne-Workman I tried all combinations of possible configurations

The machine not join in domain.
The parameter is incorrect, code = 87

The following link have all images link broken.
https://forums.fogproject.org/topic/3846/domain-join-not-working-since-moving-to-v1-2-0-error-87/4

FOG 1.3 RC7

@Joe-Schmitt I’ll try

@Joe-Schmitt disable and enable again ?

Windows 7

The fog log says that the hostname is correct, but it is not and is not updated.
I updated the client and the server but the problem persists.
Was not used sysprep.

Fog client logs.

10/08/2016 10:39 Client-Info Client Version: 0.11.5
10/08/2016 10:39 Client-Info Client OS:      Windows
10/08/2016 10:39 Client-Info Server Version: 1.3.0-RC-7
10/08/2016 10:39 Middleware::Response Success
10/08/2016 10:39 HostnameChanger Checking Hostname
10/08/2016 10:39 HostnameChanger Hostname is correct

Fog server: Ubuntu 14.04

Hi there,
can i use a mounted partition via CIFS to store images of FOG?
When I tried to do, the following error appeared: Could not mount images folder (/bin/fog.upload)

PS: The VM that FOG is installed has 15GB of storage.

@Tom-Elliott I’m really surprised the way you think at the time of development and updates. Congratulations

@Tom-Elliott After i reinstall FOG Service it works. But is not possible reinstall in all machines

@Tom-Elliott The service is still not working

@Tom-Elliott I tried to restart the computer two times. It remains the same message

@Tom-Elliott

Well, now it shows another log

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 31/03/2016 09:36 Client-Info Version: 0.9.10
 31/03/2016 09:36 ClientUpdater Running...
 31/03/2016 09:36 Middleware::Communication URL: http://acad.fog.gp.utfpr.edu.br/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=90:2B:34:F3:C2:39||00:00:00:00:00:00:00:E0&newService=1
 31/03/2016 09:36 Middleware::Communication Response: Success
 31/03/2016 09:36 Middleware::Communication URL: http://acad.fog.gp.utfpr.edu.br/fog/service/getversion.php?client&newService=1
 31/03/2016 09:36 Middleware::Communication URL: http://acad.fog.gp.utfpr.edu.br/fog/client/FOGService.msi
 31/03/2016 09:36 Data::RSA FOG Project cert found
 31/03/2016 09:36 ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 31/03/2016 09:36 Bus {
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 31/03/2016 09:36 Bus Emmiting message on channel: Update
 31/03/2016 09:36 Service-Update Spawning update helper
 31/03/2016 09:36 Bus Registering ParseBus in channel Power
 31/03/2016 09:36 Update Helper Shutting down service...
 31/03/2016 09:36 Service Stop requested
 31/03/2016 09:36 Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 31/03/2016 09:36 Bus Emmiting message on channel: Status
 31/03/2016 09:36 Update Helper Killing remaining FOG processes...
 31/03/2016 09:36 Update Helper Applying MSI...
 31/03/2016 09:36 Update Helper --> msiexec /i "C:\Program Files (x86)\FOG\tmp\FOGService.msi" /quiet USETRAY="" HTTPS="0" WEBADDRESS="acad.fog.gp.utfpr.edu.br" WEBROOT="/fog" ROOTLOG="1"
 31/03/2016 09:36 Data::RSA FOG Server CA cert found
 31/03/2016 09:36 Update Helper Starting service...
 31/03/2016 09:36 Bus Became bus server
 31/03/2016 09:36 Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 31/03/2016 09:36 Bus Emmiting message on channel: Status

After install the fog with old certs (https://forums.fogproject.org/topic/6975/change-server-but-not-change-certificate/17) this error on fog service log appears:

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 30/03/2016 12:19 Client-Info Version: 0.9.10
 30/03/2016 12:19 Middleware::Communication URL: http://acad.fog.gp.utfpr.edu.br/fog/management/other/ssl/srvpublic.crt
 30/03/2016 12:19 Middleware::Authentication ERROR: Could not get security token
 30/03/2016 12:19 Middleware::Authentication ERROR: Não foi possível localizar o arquivo 'C:\Windows\system32\token.dat'.
 30/03/2016 12:19 Data::RSA FOG Server CA cert found
 30/03/2016 12:19 Middleware::Authentication Cert OK
 30/03/2016 12:19 Middleware::Communication POST URL: http://acad.fog.gp.utfpr.edu.br/fog/management/index.php?sub=authorize
 30/03/2016 12:19 Middleware::Communication Response: Invalid security token
 30/03/2016 12:19 Service Sleeping for 120 seconds

Any idea ?

@Tom-Elliott
So I will not have to redo the settings in clients?

@Tom-Elliott said:

It will use the old CA to generate a new Private key.

In that case I’ll have to reinstall the client on all computers again?

@Jbob said:

If you copied over the root CA keys (it sounds like you did), run ./installfog.sh --recreate-keys

With this argument it will take advantage of the old scripts or create new keys?

@Tom-Elliott said:

So your main server is also having issues?

My old server works perfectly.