Jump to content

Recommended Posts

Posted

Hi folks - completely new to FOG, having a bit of a falling out at the moment.

 

Long story short is we took a disk image of a machine locally, which we HAD intended to have FOG rename for us but for various networking issues on the day it wouldn't after several restarts of the client.

 

I've used that image we took locally now on another machine, but THIS machine is now restarting constantly thanks to FOG and renaming itself to the name of the ORIGINAL machine whenever it's restarted.

 

I have access to the FOG console and had meant to get to grips with it one of these days, but was hoping it wouldn't be on unpleasant terms!

 

What do I need to change on the FOG server to stop this mischief?

 

Many thanks for reading!

Posted

Not sure why the machine should be re-naming its self as the name of the origenal machine. Anyhow, it's quite easy to disable that service, you can do it on a global or individual client level.

 

Log into the fog console, and click the 'hosts' tab and search for the correct host that you want to stop re-naming its self.

Click the Edit icon at the end of the line

Select service settings from the left hand menu

Un-tick the box that says 'hostname changer enabled' this will stop the FOG client re-naming the machine.

Save the settings.

 

The client will need a re-boot to pick up the new settings from the FOG server.

 

If you want to disable the renaming service globally, you can do that from the Services menu, select hostname changer from the left hand menu, remove the tick from the box and save the settings.

 

Mike.

  • Thanks 1
Posted (edited)

Ah that sounds like it! I'll run off and see if that does the trick.

 

Yeah I found the option to globally disable it but I'm loth to. FOG's kinda useful that way when it's working alright (from my limited experience with the thing.)

 

Thanks so much for the help!

 

EDIT - urgh. No it's still doing it. Chopping the Hostname changer. (EDIT2 - Which HAS now sorted it) I'd love to be able to use the FOG server but with the way things are here it's going to have to wait until I've got a spare afternoon to read up on. 'orrible thing.

 

Cheers again for helping me out though.

Edited by El_Nombre
  • 6 months later...
Posted

I image computers and let my students deploy them out into the classrooms. As such I want the names to stay set (all the same) because they autologon 1 time as a local admin for the AD joining. I also DO NOT want Fog to rename them at all. No problem until I recently upgraded and now it renames them to the NIC address, which breaks the autologon of the image. Worked fine until the recent upgrade.

 

I tried turning off renaming globally but that did nothing, still renames them to the NIC.

 

Thoughts? Really don't want to go backwards!

 

Brian

Posted
I image computers and let my students deploy them out into the classrooms. As such I want the names to stay set (all the same) because they autologon 1 time as a local admin for the AD joining. I also DO NOT want Fog to rename them at all. No problem until I recently upgraded and now it renames them to the NIC address, which breaks the autologon of the image. Worked fine until the recent upgrade.

 

I tried turning off renaming globally but that did nothing, still renames them to the NIC.

 

Thoughts? Really don't want to go backwards!

 

Brian

 

Fog uses the mac address to link names to hosts. Set the host name on the host management page and you'll be fine.

 

Fog can tell you the mac of a machine from the pxe boot menu if it helps.

Posted
Hi folks - completely new to FOG, having a bit of a falling out at the moment.

 

Long story short is we took a disk image of a machine locally, which we HAD intended to have FOG rename for us but for various networking issues on the day it wouldn't after several restarts of the client.

 

I've used that image we took locally now on another machine, but THIS machine is now restarting constantly thanks to FOG and renaming itself to the name of the ORIGINAL machine whenever it's restarted.

 

I have access to the FOG console and had meant to get to grips with it one of these days, but was hoping it wouldn't be on unpleasant terms!

 

What do I need to change on the FOG server to stop this mischief?

 

Many thanks for reading!

 

Is the client machines name correct against its mac address on the host management page?

  • 4 weeks later...
Posted

correctly.

 

All computers are tied to the mac address. If you reimage a host and have a different name for the machine the hostnamechanger.dll in the fog client will compare that against the database and update it for you.

 

Check the mac address of the computer against your current computers and update it to what you want.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...