Clear Encrypted Data When Moved to New Switch Port
-
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
-
Screenshot of the Service Settings in Fog Configuration also
-
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.
-
This post is deleted! -
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.
-
@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.
-
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.
-
The encryption is not optional. Making it so would open up quite a few security holes.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
-
@Jbob OK good to know. I will run these tests and see what happens.
-
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.
-
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.
-
@Psycholiquid notifying @Jbob about it… this is his realm till the official release.
-
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?
-
If you need any information from me let me know I will post it.
-
Can you give me the log files from each of the 5 re-images (that is log file from post-image #1, #2, …)?
-
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.
-
Starting imaging now. I will post the logs as soon as it is complete.
-
SVN 3700, hopefully, should only reset the token data on imaging task checkin now, rather than when a task is created. Hopefully this helps.
-
Should I just go ahead and update the SVN version I am running or do you need the logs for verification?
-
I’d say yeah, go ahead and update. I can’t fix what I don’t know about.
