Can the FOG service register clients again?

[silentsoul]

I have been using FOG for many years now, and I am still on version .28 because we like the features of this version, and the ability of the FOG service (which we use for a ton of stuff) to enable us to register a machine out of the box, image the machine with a task, then rename and add that machine to AD.

I know this ability was taken out around version .29 for the service, and I am not sure why, or what the issues were.

If there is a way for me to enable this back into the newer services for I would be glad to do it. We are getting ready to deploy a bunch of windows 7 64 bit machines, and I thought it might be good to get on the latest version.
Or does it matter, can I continue to use the version .28 service with no issues.

I know of 10 or more school districts around me that have moved to FOG after we started using it a few years ago, and they have stuck to the old version for the same reason.

Any help would be greatly appreciated.

Thanks.

[falko]

A move to 0.32 (0.33 is to be released soon I believe) is a must for Windows 7 deployment, no more fogprep and has a brand new web GUI over 0.28

I can’t comment on exactly what you want bit I have windows 7 both 32 and 64 images that I can deploy, auto renames, adds itself to the domain etc
And so far the latest kernel 3.2.4 (I think). Works on all 8 of my different desktop/laptops

[silentsoul]

[quote=“falko, post: 1481, member: 48”]A move to 0.32 (0.33 is to be released soon I believe) is a must for Windows 7 deployment, no more fogprep and has a brand new web GUI over 0.28

I can’t comment on exactly what you want bit I have windows 7 both 32 and 64 images that I can deploy, auto renames, adds itself to the domain etc
And so far the latest kernel 3.2.4 (I think). Works on all 8 of my different desktop/laptops[/quote]

Right, I do all those things you mentioned, the one thing I cannot do with anything over version .28 is have the fog host register host.

It’s not to have them automatically register with the service that I push out via GPO, so that I know in 6 months when I got to image the machine I can count on it being in the database.

I have machines spread out over 7 locations, so being able to go to in to FOG, know the machine is there, tell it to image , and it be imaged, named and added to the domain without me having to go to the location to PXE boot it because it never got registered before being rolled out to the site is a huge thing.

I’m just trying to figure out why it was removed, if it was causing issues, or if it just wasn’t requested.

Or if it’s possible if someone could help me integrate the funtion into a custom FOG service module:
[url]http://www.fogproject.org/wiki/index.php?title=Creating_Custom_FOG_Service_Modules[/url]
I Would think it would be fairly simple as taking the code from the earlier service module and adding it, but i’m not programmer.

Thanks for all the help.