Fog-Service - hostname changer gives the name of the master computer
-
On Win81 client / fog 1.2.0, during Sysprep (audit mode) I’ve installed the FOG-Service and activated hostname-change.
After putting the image into OOBE mode, and deploy the image, the hostnames of the deployed computers have the same name as the machine where the master image was created on. If I manually try and rename the other clients, FOG-Service makes sure that the hostname is changed back to what the Master is.
So hostname changer works… but gives the wrong name.
-
[quote=“Carsten Jensen, post: 35683, member: 3876”]On Win81 client / fog 1.2.0, during Sysprep (audit mode) I’ve installed the FOG-Service and activated hostname-change.
After putting the image into OOBE mode, and deploy the image, the hostnames of the deployed computers have the same name as the machine where the master image was created on. If I manually try and rename the other clients, FOG-Service makes sure that the hostname is changed back to what the Master is.
So hostname changer works… but gives the wrong name.[/quote]
FOG Service shouldn’t be changing the name to the Master computer name. It should be changing the name to that of the value stored in the GUI for that relevant host.
I was aware of issues where the keys that get adjusted for the hostname changer weren’t correct, but I haven’t, at the moment, any Windows 8 machines to test the service with. That being said, this is kind of an aside as the FOG Team is currently working on rewriting the FOG Client (Jbob in particular). My only guess is that the relevant key’s are being updated/added where needed, but the ones that actually deal with the display of the names aren’t.
-
Would it be too much to ask for a simple thing as how the fog-service aquires the name of the master image and how it should get the name from the database… perhaps I (or my dev) can make a fix.
[this is now]
i.e. old info pulled down and stored in the registry.[Should be]
[url]http://fogserver/fog/client.php?mac_addy=1234567890ab[/url]btw as a side note while you’re making a new client… I can’t uninstall the fog-service the traditional way even in it’s Pre-Sysprepped (audit mode) state. The uninstaller runs, the program is removed from the programs list, but the physical files are still located in program files, and the service is still running. It seems the (un)installer for this version is/was broken.
-
you can download a trial version of Win81 Enterprise here:
[url]http://technet.microsoft.com/en-gb/evalcenter/hh699156.aspx?ocid=wc-tn-wctc[/url] -
[quote=“Carsten Jensen, post: 35683, member: 3876”]
So hostname changer works… but gives the wrong name.[/quote]What is the name of the client in the Host Management ?
-
is it possible that the system with this problem has a virtual network card of some sort? such as, does the imaged system have virtualbox installed?
-
@jayphizzle: the master is called udd003, and of course all the other clients have a number ranging from udd001-udd024.
@junkhacker: The host computers are all alike, same motherboard etc. There are 2 netcards but one has been disabled in the BIOS.
This was done prior image creation. The master image was created on the computer. No VM’s involved.Oh, and something to add, these computers are virgin computers
-
An update …
On Win7 computers that hasn’t been sysprepped, the renaming works.There has been no time to test if Win81 works if it hasn’t been sysprepped.
Though I’ll see if I can find some time to make more tests. -
I’m going to guess, you’re using an unattend file for your Sysprep? With that unattend, does it skip over the name PC create user functions? Is the unattend specifying the hostname during its steps?
It sounds like it’s changing the names and finding the keys that deal with the normal naming as being set, but the keys that actually display the name are being set to the master computers name.
-
Please see the attached file for full details, but answers are also below.
- Yes, it’s using an unattended file for sysprep.
- And yes it skips the create PC name / User
- No, hostname is not defined*
That sounds about right. Really weird.
I’m going to start making a sysprep machine for Win7 with some slight changes, most should look like the Win81 sysprep though. This is merely to see if the same server acts weird there or if it’s a Win81 problem.[url=“/_imported_xf_attachments/1/1370_unattended3-fog.xml.txt?:”]unattended3-fog.xml.txt[/url]