Rename fails but adds client to domain.
-
@ch3i Shoot sorry its early forgot to add that info
FOG version SVN3702
Client version 0.8.4 -
@Psycholiquid said:
@ch3i Shoot sorry its early forgot to add that info
FOG version SVN3702
Client version 0.8.4There are some new client revision since the 0.8.4, there are on latest SVNs, not sure if after the update of FOG server you have to manually install the new client.
EDIT : https://forums.fogproject.org/topic/4250/new-client-progress/90
-
@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 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
-
Forgot Unattend. unattend.xml
-
@Psycholiquid said:
@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
Why fog-testing-PC and fog-MCO-Spare have same mac address ?
-
@ch3i I am not seeing that in the logs:
Testing-PC
7/20/2015 9:58 AM Client-Info Version: 0.9.0
7/20/2015 9:58 AM HostnameChanger Running…
7/20/2015 9:58 AM Middleware::Communication URL: http://10.20.60.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=18:03:73:4A:D5:EE||00:00:00:00:00:00:00:E0&newService=1MCO-Spare
7/20/2015 8:58 AM Client-Info Version: 0.9.0
7/20/2015 8:58 AM HostnameChanger Running…
7/20/2015 8:58 AM Middleware::Communication URL: http://10.20.60.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=F8:B1:56:B5:EE:31||00:00:00:00:00:00:00:E0&newService=1 -
@Psycholiquid said:
@ch3i I am not seeing that in the logs:
Testing-PC
7/20/2015 9:58 AM Client-Info Version: 0.9.0
7/20/2015 9:58 AM HostnameChanger Running…
7/20/2015 9:58 AM Middleware::Communication URL: http://10.20.60.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=18:03:73:4A:D5:EE||00:00:00:00:00:00:00:E0&newService=1MCO-Spare
7/20/2015 8:58 AM Client-Info Version: 0.9.0
7/20/2015 8:58 AM HostnameChanger Running…
7/20/2015 8:58 AM Middleware::Communication URL: http://10.20.60.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=F8:B1:56:B5:EE:31||00:00:00:00:00:00:00:E0&newService=1I’ve checked the top of your attached log
-
@ch3i Those are the logs from before the upload of the image, so what you are seeing is the master images MAC. If you scroll through you will see it changes after timelog 8:42 this is the time of the machines coming up. So basically I have Win7 machine in Audit mode when I install the FOG service, then run sysprep and upload. That is where the beginning of the log files starts.
-
@Psycholiquid said:
ice, 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
You are running 0.9.0 but 0.9.4 is the latest.
-
@Jbob Can I just use the client and not upgrade the whole server or do I need to update both? Just trying to make sure I run like I should. I am getting so close to having this licked so I can start making use of the system.
-
You must update the server. Each server is marked with a compatible version which deployed clients will upgrade to. If you upgrade your server then all deployed clients will update themselves to the compatible version.
-
Do you have a link handy on how to switch it over to using GIT instead of Sourceforge since it look like they will be down for a bit longer than I am willing to wait LOL.
-
-
@Jbob I appreciate it I will upgrade and reinstall client and report back. Hopefully this will fix it. I have never had this many problems with FOG I am beginning to think I am cursed.
-
@Jbob , Well that made matters worse. Now it dropped my hosts out of FOG (Master Image Host) I cant add it back in for some reason, whether manually or automatically. I cant edit hosts, I get a blank screen when I try to edit or delete them like that web host is messing up or something. I add a deployment and the machine reboots but never starts the deployment. I am seeing the FOG PXE boot however. I have the server snapshotted so that isn’t a big deal I can roll back but not sure where to go from here.
Not mad or anything so please don’t read it as such. Appreciate all you guys do.
-
Also missing what version it is now on the cloud, not sure if this helps with what is going on?
-
OK tried rolling back and reinstalling the Dev-Branch. Still breaking my whole setup doing that. Is the old 0.3.2 version still stable? I never recall having all these issues in that version at all.
-
I don’t believe .32 has been touched in quite some time. You would also have to install the legacy client on your image, but you can try that with the current version of FOG you have as well.
Still strange that it only happens to the one model.
-
@cml It is now happening on all models. It is almost like there is an issue with me installing the client before sysprepping the machine. I can put my finger on what is happening. I can say once I manually rename the computer it stops rebooting, but since I changed to matching the client with teh server now no machine will rename, but will still add it to the domain which is causing big issues with having multiple machines trying to be the same machine all th time.
