Rename fails but adds client to domain.


  • Testers

    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.


  • Testers

    @Wayne-Workman

    It was my compression I get around 1 gig now once I turned it down a bit


  • Testers

    OK fully updated and the SetupComplete.cmd in place working like a champ now.

    I would like to know why I have to add those lines maybe something that should be put in a FAQ somewhere.

    But all in all working like a champ and the business loves it.

    Thank you all for helping on this . I’m sure I’ll be back with something else soon.


  • Moderator

    @Psycholiquid said:

    On a side note anyone able to get their upload to the FOG server to be any faster than 500MB a min. Painfully slowing the process down. Imaging is super fast getting 8GB a min.

    Hi, 500-700/min is my average speed on my network (FastEthernet).


  • Moderator

    @Psycholiquid said:

    Anyone able to get their upload to the FOG server to be any faster than 500MB a min. Painfully slowing the process down. Imaging is super fast getting 8GB a min.

    Holy wow lol. My uploads move at anywhere from 1.5GB/min to 3GB/min. What are your compression settings? Are you running over a 100 meg link? Maybe you have a bad patch cable? A bad switch port?


  • Testers

    OK this morning with SVN still being down (Thanks Sourceforge) I decided to try installing the 0.9.4 client and use it with teh SVN3702 server. So far I am now able to image and rename acomputer and add it to the domain, I am attempting a dual image now to see if both rename and add to the domain without issue. If all goes well then I will just wit for SVN to come back up and update to the latest trunk and retest.

    On a side note anyone able to get their upload to the FOG server to be any faster than 500MB a min. Painfully slowing the process down. Imaging is super fast getting 8GB a min.


  • Testers

    Ok using SVN 3702 with Client 0.9.0 I am getting the following happening:

    I create the image in Audit mode
    Install all software and updates Install FOG Service software 0.9.0

    In the SetupComplete.bat I have the following commands

    sc config FOGService start= auto
    net start FOGService

    Set windows to OOBE and reboot uploading image to FOG server.

    Once complete I push the image out to one of the hosts I have setup in FOG right now. IT runs through the whole image setup and completes to the Desktop.

    From there is joins the domain without trying to rename the computer at all. This create a problem as there will be multiple computers all trying to join the domain under the same name causing a trust issue in the process.

    Here is the log from the computer I just did. Keep in mind this one is constantly rebooting due to it trying to change the name after it has already joined the domain:

    fog.log


  • Testers

    @Tom Elliot I will give that a try and see what happens. I’ll report back with results.


  • Senior Developer

    I disable the FOG Service before sysprep, and my setupcomplete.cmd finishes by re-enabling the fog service. I don’t have any issues doing this.


  • Testers

    @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.


  • Moderator

    @Psycholiquid

    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.


  • Testers

    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.


  • Testers

    Also missing what version it is now on the cloud, not sure if this helps with what is going on?

    upload-3156692d-fb0f-4c4f-850a-d10f254d06ff


  • Testers

    @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.


  • Testers

    @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.


  • Senior Developer


  • Testers

    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.


  • Senior Developer

    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.


  • Testers

    @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.


  • Senior Developer

    @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.


Log in to reply
 

830
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.