I know, but my new instance is already installed… Only hosts interested me is why I did not update.
Another reason is the transition from Debian 7 to 8 .
![](/assets/uploads/profile/uid-106/106-profileavatar.png)
Posts made by aruhuno
-
RE: DB : convert FOG 1.2.0 to 1.3.0
-
DB : convert FOG 1.2.0 to 1.3.0
Hello,
It’s possible to have a tool to convert FOG 1.2.0 database to 1.3.0 (git 7142) ?
When I’m going to 1.3.0, I’m using a new server and 1.2.0 won’t export data with UI.Thanks for the response.
-
RE: FOGClient 0.9.11: Could not get security token after sysprep
@Sebastian-Roth
DC synchronize time only with computers added in AD but FOGClient can’t add computer in AD…
I found a solution by synchronizing time just before the sysprep command.edit: I finally installs the client after deploying the post via a script called by unattended file.
-
RE: FOGClient 0.9.11: Could not get security token after sysprep
@Jbob
Ok, but after deploy, it’s impossible to synchronize time with a DC (computer added in AD with FOGClient) and computer doesn’t have access to WAN (proxy parameters pushed by GPO and the proxy to require an AD auth).How to do?
-
FOGClient 0.9.11: Could not get security token after sysprep
Hello!
With FOGClient 0.9.11, I’ve problem after deploy syspreped Windows 10 image:
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 08/03/2016 16:13 Client-Info Version: 0.9.11 08/03/2016 16:13 Middleware::Communication URL: http://fog.domain.local//management/other/ssl/srvpublic.crt 08/03/2016 16:13 Middleware::Authentication ERROR: Could not get security token 08/03/2016 16:13 Middleware::Authentication ERROR: Le fichier 'C:\Windows\system32\token.dat' est introuvable. 08/03/2016 16:13 Data::RSA FOG Server CA cert found 08/03/2016 16:13 Data::RSA ERROR: Certificate validation failed 08/03/2016 16:13 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Un certificat requis n’est pas dans sa période de validité selon la vérification par rapport à l’horloge système en cours ou le tampon daté dans le fichier signé. (NotTimeValid) 08/03/2016 16:13 Middleware::Authentication ERROR: Could not authenticate 08/03/2016 16:13 Middleware::Authentication ERROR: Certificate is not from FOG CA 08/03/2016 16:13 Service Sleeping for 120 seconds
Thanks in advance for the help
-
RE: Strange registration messages
Following a discussion with @Sebastian-Roth, we finally found it!
The problem is the speed negotiation with the switch . I’ll update the firmware of the switches and make feedback. -
RE: Attempting to register host…Invalid MAC Address!
Thank you to all, effectively with the 6663 release, it works!
-
Attempting to register host…Invalid MAC Address!
Hello!
New problem with my ThinckCentre E73:
Yet in the hosts table:
But not in hostMAC.
-
RE: Strange registration messages
@Wayne-Workman
This is disabled since Tom to me suggested in a previous post.@Sebastian-Roth
Unfortunately, as I said yesterday , Spanning Tree is active on all switch ports:
-
RE: Strange registration messages
With the help of @Sebastian-Roth, it works!
I had actually tried other switch but had not returned to the original swith (the one I was at the opening of this topic).
Solved by mini-switch and the new init script, thanks all!
-
RE: Strange registration messages
@george1421
Perhaps, but as @Sebastian-Roth points out , last week I could go up the interface with theudhcpc
command.@Sebastian-Roth
I’ve already tested and impossible to reproduce, something has change (script? kernel?). -
RE: Strange registration messages
I have done several tests:
- use of another cable
- use another switch
- use another cable to another switch
-
RE: Strange registration messages
@george1421
Sorry for the wait. This morning, I’ve updated FOG (now in 6651) and problem persist:
@Wayne-Workman
I hope so.Even if it’s not finished, thanks everybody for the help!
-
RE: Strange registration messages
@Sebastian-Roth
I’ve updated FOG this morning:
@Sebastian-Roth said:
Edit: Found an interesting parameter for the udhcpc. Tom added it to the inits. You might want to upgrade and run the installer again to get the latest inits. This might possibly fix things for you…
So, I’m making init with updated script
@Wayne-Workman said:
@aruhuno Just an FYI, the E73 is in our working hardware list: https://wiki.fogproject.org/wiki/index.php?title=WorkingDevices
On FOG 1.2.0, yes, but not on 1.3.0 and I need it to deploy Windows 10 with FOG Client.
-
RE: Strange registration messages
@george1421
Hum, just a question in your script: line 18, it’s writtenif not wait up to 10 seconds
but where is thesleep
command ? It’s possible to edit this file directly in my FOG installation?@Tom-Elliott:
It’s not blank for me -
RE: Windows install ISO FOG server 1.3
I’m using that with FOG 1.2.0:
:WS2012R2 sanboot --no-describe --drive 0x81 ${boot_url}discimg/WS2012R2.iso goto MENU
-
RE: Strange registration messages
@Quazz said:
@aruhuno The last time I had this issue I switched ethernet cables and it worked fine. Your mileage may vary of course.
I already tried:
- another cable
- another switch
- another cable on another switch
As many say it’s certainly the card.
-
RE: Strange registration messages
@Sebastian-Roth
Ok, but, see my cold boot:- Power On: no LED (link down)
- PXE found: LED (link up)
- PXE boot: LED (link up)
Starting eth0
message: no LED (link down)Computer will reboot in 1 minute
message: no LED (link down)- few seconds after: LED (link up)
But when link is up, script wait for reboot computer… too quickly boot or?
In the script, comment line 18, it’s written
wait 10 seconds
but where is thewait
/sleep
? -
RE: Strange registration messages
@Tom-Elliott
I don’t know if my switch supports 802.11az but I do not think.
I change option in firmware from Windows but has no impact