[Fog] Fog and windows 7

[marlwoodadmin]

You dont need netdom anymore just have the newest fog client on the PC .32. You will need to update the hostnamechanger.dll. C# needs to be .net2 then you create it.

[saadi]

Thanks mate didn't know that. Been using netdom for no reason then. Is this the same with XP? Only I have had issues with XP and the latest version of FOG. Basically FOG hasn't been adding the machines to the domain and in some cases it doesn't even rename the machines. But the same machines join the domain if I use a windows 7 image.

[marlwoodadmin]

You need netdom if you are using XP (i think). Could it be that the username format to join the domain is different? On the web console Win7 works like domain\username but xp was just username. Again i think this i correct as now it is set up i rarely have to change anything.

We are using mulitiple FOG clients for various bit of the setup. the FOG server is installed as .31; the init.gz is .29; the client on the PC is .32. FOG doesnt seem to care if all these are mismatched.

Reason:
FOG server .31 was used because it was the newest one when we set it up
init.gz .29 was used because the uploads and deployments are quicker than any other version we have tried
Client .32 was used to get the PCs to join the domain even if there was a computer account in AD with the same name

[mats]

Hi again Chris,

Well I've been trying this and I just can't get it to work. Keep getting:

'Windows Failed to start. A Recent hardware or software change might be the
cause. To fix the problem:

1: Insert your Windows disc ...blah blah
2: blah
3:blah

If you do not have this disc, contact your system administrator or computer
manufacturer for assistance.

Status: 0xc000000e

Info: The boot selection failed because a required device is
inaccessible.'

Which I believe is the reason I gave up trying to use FOG for our deployment. Any ideas?

There is another topic open, and unsolved here;
Fog windows 7 and ntfs resizable

Thank you

Grey Fox

In case somebody in the future finds this (hello!), I think that error is caused by the image type being set to single image. Try specifying a multiple partition image (win7 likes a separate boot partition at the start of this disc. Forget it and it doesn't want to boot).

[marlwoodadmin]

You CAN use single resizable image. But you MUST sysprep the image with the shutdown switch and then upload the the image. works hunky dory then!

[kv102t]

i wrote a manual for this. FOG .29 & .32 My Windows 7 Guide (32/64 Bit) DocV1 | blog.ibuddy.info

[marlwoodadmin]

That looks a lot like documentation to me...