Posts made by Psycholiquid

@ch3i No dice, with updating the client now neither computer renames but it still joins one of them to the domain. I cant tell which one though since they are both using the name from the Unattended which is only a temp name until FOG renames it. I have attached the logs from both clients, they both just reboot over and over now.

I am also attaching my unattend. Maybe someone can see something I am doing wrong in there. I have been using the same type of unattend for years now and it has never given me a problem before though.fog-Testing-PC.log fog-MCO-Spare.log

@ch3i Yes I see a considerable difference in size from the one I have installed to the one I download from the updated version of FOG server. I will give that a try and report back.

@ch3i Shoot sorry its early forgot to add that info

FOG version SVN3702
Client version 0.8.4

I have gotten FOG up and running fine. Now the only issue I am seeing is hostname changes. For one machine is seems to work like a champ (Dell OP 7010) the next machine I do, it never renames the machine but adds it to the domain and reboots over and over until I manually change the name on the PC itself.

I am wondering if this has anything to do with the way I am making the image and if there is a SID key or something of the like in the FOG client causing this issue. I install the client in the image before sysprep then run sysprep and shutdown the machine. I then upload that image to the FOG server for deployment so when imaging it starts up in OOBE mode and go through the Unattend,xml file. Everything seems to be fine until it comes to renaming machines after I do the first one.

I see nothing in the event viewer that I can discern is a problem. I also see in the FOG client where it sees the computer name is wrong and wants to rename it and sets a reboot task. This happens over and over. Any help would be appreciated. I am running through the steps this morning to have fresh event logs and FOG client logs in case I am asked for them.

OK just got done re-imaging the same machine 7 times in a row with all good results. Thank you guys so very much for helping me out with this.

Imaging now will update as soon as 5 or more work

Already did that also.

Tried that didnt help. I manually installed php5-fpm and was able to get past that part now it just sits on Updating packages as needed. Never goes any farther.

And the hits just keep on coming. I am trying to upgrade teh SVN from my current to 3701 (Came form SVN trunk download)

Upgrade hangs on php5-fpm . I have snapshotted and tried rolling back then updating Ubuntu and trying again, same result. Any ideas?

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

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

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

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.

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.

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

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.

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.

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.

Screenshot of the Service Settings in Fog Configuration also