Clear Encrypted Data When Moved to New Switch Port

[Psycholiquid]

This is what I am getting for the hostname changer part:

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 6/29/2015 11:24 AM Client-Info Version: 0.8.4
 6/29/2015 11:24 AM HostnameChanger Running...
 6/29/2015 11:24 AM Middleware::Communication URL: http://10.20.60.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=F8:B1:56:B5:EE:31|&newService=1
 6/29/2015 11:24 AM Middleware::Communication Response: Success
 6/29/2015 11:24 AM Middleware::Communication URL: http://10.20.60.14/fog/service/hostname.php?moduleid=hostnamechanger&mac=F8:B1:56:B5:EE:31|&newService=1
 6/29/2015 11:24 AM Middleware::Communication Response: Invalid host certificate
 6/29/2015 11:24 AM Middleware::Communication URL: http://10.20.60.14/fog/management/other/ssl/srvpublic.crt
 6/29/2015 11:24 AM Data::RSA CA cert found
 6/29/2015 11:24 AM Middleware::Authentication Cert OK
 6/29/2015 11:24 AM Middleware::Communication POST URL: http://10.20.60.14/fog/management/index.php?sub=authorize
 6/29/2015 11:24 AM Middleware::Communication Response: Invalid security token```

[Psycholiquid]

Trying to gather as much info as possible. This seems to be happening over night also. Re-imaged a machine more than 10 times yesterday without issue. Come in the morning and try to reimage it and the hostname problem is there again. I have attached the FOG client log for troubleshooting

fog.log

[Psycholiquid]

Screenshot of the Service Settings in Fog Configuration also

[Psycholiquid]

When creating the image I am installing the client to the windows 7 machine then running sysprep set to shutdown, then uploading to FOG. Not sure if that is relevant or not.

[Wayne Workman]

This post is deleted!

[Psycholiquid]

Would it be possible to turn this feature off. MY FOG is only internal and I don’t really have a need for the encryption. Unless I am way off-base and feel free to correct me if I am.

[Wayne Workman]

@Psycholiquid Are your FOG Service settings still the same as in the picture below?

You need the “FOG_New_Client” setting enabled to use the new client at all.

[Psycholiquid]

Yes setting have not been changed. I have now checked that and will be running a few tests. I’ll give an update after i reimage a few times and move ports around to see if I can break it.

[Joe Schmitt]

The encryption is not optional. Making it so would open up quite a few security holes.

[Psycholiquid]

@Jbob OK good to know. I will run these tests and see what happens.

[Psycholiquid]

Seems I can get 5 re-images out of it before the encryption data has to be reset. I have been able to move it from one port to another within that 5 and it not cause me to have to clear the Encryption data. But after 5 re-images it forces me to clear it to rename the host and join the domain.

Also as soon as I hit the clear button the computer renames and joins the domain without issue.

[Psycholiquid]

I can officially say it is every 5th image that is breaking it. I am not sure why but that happens on image 5 every time. Any ideas. I will try to upgrade to the latest SVN tomorrow to see if that helps but I am not sure that the server is the issue.

[Wayne Workman]

@Psycholiquid notifying @Jbob about it… this is his realm till the official release.

[Joe Schmitt]

Thanks for the notification Wayne. @Psycholiquid I will attempt to reproduce this issue in my vms. Is there anything special you are doing to the image? E.G. sysprepping?

[Psycholiquid]

If you need any information from me let me know I will post it.

[Joe Schmitt]

Can you give me the log files from each of the 5 re-images (that is log file from post-image #1, #2, …)?

[Joe Schmitt]

I just finished talking with Tom and we may have found a fringe case that would cause the issue you are seeing. As for why it happens ever 5 re-images we have no idea, but we are hoping its caused by this fringe case. Tom will push out a patch when he has time.

[Psycholiquid]

Starting imaging now. I will post the logs as soon as it is complete.

[Tom Elliott]

SVN 3700, hopefully, should only reset the token data on imaging task checkin now, rather than when a task is created. Hopefully this helps.

[Psycholiquid]

Should I just go ahead and update the SVN version I am running or do you need the logs for verification?