This shows it joined. maybe deleting the object in the OU and rebooting(PC) might get it to work.

20/01/2012 14:35 FOG::HostnameChanger Attempting to connect to fog server…
20/01/2012 14:35 FOG::HostnameChanger Module is active…
20/01/2012 14:35 FOG::HostnameChanger AD mode requested, confirming settings.
20/01/2012 14:35 FOG::HostnameChanger Hostname is up to date
20/01/2012 14:35 FOG::HostnameChanger Attempting to join domain if not already a member…
[COLOR=#ff0000] 20/01/2012 14:35 FOG::HostnameChanger Domain Replied: (‘SetupAlreadyJoined’ Code: 2691)[/COLOR]

Update1: Well I deleted the third partition, Extended the OS partition, syspreped, uploaded a new image, and deployed to another machine and now I get a ‘A disk read error occurred Press Ctrl+Alt+Del to restart’. Basically a no go. I am going to try pop in gparted and see if i can get the machine to boot.

Update2: Gparted wouldn’t boot in the machine. I have been working on this for to long so I am giving up on Fog. Only because I have to image these machines by Friday and can’t waste anymore time. But thank you for your help.

Yeah I understand that you haven’t changed anything but the OU. From what you put OU=Workstations,DC=ourdomain,DC=gov,DC=uk that looks okay. So i’m not exactly sure what could be the issue other than making sure some of the little nuances of using Hostname changer are checked. I already mentioned log files to see if you could get any info and you said there is nothing relating to it in there.

So what I would try is:

make sure you put: [FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_USER: [/COLOR][/FONT]‘DOMAIN\USER’ (Other wise it would t work for me)
try adding a machine to AD manually with the exact same credentials your using in fog

Other than that im all out ideas.

[quote=“BryceZ, post: 650, member: 2”]Is this a standard installation of Windows 7 from the DVD or a preinstalled OEM installation? Single Partition is the preferred image type for standard Windows installations as it allows you to deploy to HDDs with different geometries. With deploying a non-resizable image to a different model of HDD can potentially cause problems.

The problem you’re describing sounds like a “corrupt” MBR that doesn’t match the disk geometry.[/quote]

Hey,

Yes this is a OEM pre-installed installation. The computers have three partitions which stoped me from using the re-sizable option.

They are…

1. 100MB Windows System Partition
2. 250GB OS Parition
3. 10GB Lenovo System Restore Partition

------------------------------TO DO:
From what you are saying I think I should delete the third partition and make the image again using the re-sizable option. And if that doesn’t work re-install the OS from a DVD of Windows 7 x64 and make a new image.

Thanks for the help I will report back on the success of this in a few hours for others encase they run into he same problem.

Thats weird your not seeing anything in the logs have you tried checking to see if the hostname changer setting is set to on.
Other Information -> Fog Settings -> Fog-Service Hostname Changer -> Value = ‘1’.

and under

Host Management -> (Find your PC) -> Service Settings (on the left) -> In the list under ‘Hostname changer enabled?’ make sure that it is checked.

Hey,

I have an issue with a blinking cursor on boot after deploying an Windows 7 x64 image made from a Lenovo E525 Laptop.

The image deploy works with original laptop used to make the master image. But doesn’t work with any of the subsequent laptops of the same make and model.

So what I have done to get machine ready to upload an image was…

1. Use a ‘Multiple Partition Image - Single Disk (Not Resizable)’
2. Run Sysprep with an unattended.xml
3. Shutdown PC
4. Run image task

Has anyone had any issues with a blinking cursor and the machine not booting after a deploy? IF so what was the steps you took to fix the issue?

Server setup…
FOG 0.32
Ubuntu 10.04.3

Hey,

I have been testing this feature for the last few days. Make sure you got the right OU structure. So if I have a computer in the computer OU it should look like this.

[FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_DOMAINNAME: fogproject.org[/COLOR][/FONT]
[FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_OU: OU=Computers,DC=[/COLOR][/FONT][FONT=Ubuntu][COLOR=#333333]fogproject[/COLOR][/FONT][FONT=Ubuntu][COLOR=#333333],DC=org[/COLOR][/FONT]
[FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_USER: [/COLOR][/FONT][FONT=Ubuntu][COLOR=#333333]fogproject.org[/COLOR][/FONT][FONT=Ubuntu][COLOR=#333333]\fogproject[/COLOR][/FONT]
[FONT=Ubuntu][COLOR=#333333]FOG_AD_DEFAULT_PASSWORD: 3red339dsa23kjdo9[/COLOR][/FONT]
[FONT=Ubuntu][COLOR=#333333][/COLOR][/FONT]

Also check the fog.log in the C:\ drive for errors it was really helpful for troubleshooting.

Brilliant thanks! Man this a awesome project. Can’t wait to figure it all out.

Hey all,

When I am entering a hostname into FOG when creating a host it says hostname not found I am assuming its not able to find the computer. Now the host name is TESTPC.mydomain.net. FOG wont let me enter in a full domain name so I just enter in TESTPC and finds nothing. I ping TESTPC from the server and it works but comes back as TESTPC.mydomain.net because the PC is apart of a AD domain environment.

My question is how can I get FOG to recognize a desktops hostname in a AD Domain environment?

I have the FOG server network interface set to DHCP and the remote DHCP Server(Win 2003 with options 66 and 67 set) has an IP reservation for that machine. Is this okay? Or is there another reason we use a static IP address with FOG?