@Tom-Elliott I didn’t realise it was as easy as that - will give it a whirl next time we get a new batch of computers.

Thanks

Hi,
This one probably isnt too high on anyones agenda as they most likely delete them from FOG, but for those of us that have to retain audit trails, its helpful.

It would be useful to have the option of marking a computer as disposed of/recycled.
Make their entry read-only.

Save date/time they were archived - also allow this to be specified when archiving as some may have kept their old information in fog but have already disposed of the equipment.

Archive them so that their PC name can be reused and they don’t appear in the searches/reports unless ‘search archive’ is ticked or something similar.

Would help to retain a log of previously owned PCs without it cluttering up the FOG GUI/reports.

Thanks

Hi,
It would be great if we could have something like this for new PCs:

1. Full host registration
2. Boot and input all details image/pc name/etc as normal
3. At the end when it asks if you would like to image it, give the option to create a temporary multicast session using the image specified previously.
4. Reboot and join as the 1st PC in that session automatically
5. Provide the option for the 2nd/3rd/Nth PC to join this multicast group automatically at the end of their host registration
6. Allow the last newly registered PC to ‘finish’ the group so that when it reboots and joins the session it automatically starts.

Maybe keep that temporary multicast group with the same members until you specify at point 3 to start a fresh one (empty the group) so that you can re-use the group in case of errors/problems.

Currently we have to do this instead:
Boot all PCs to new host registration.
Input all details, deny imaging and reboot.
Catch all the PCs at their reboot cycle before they boot into the OEM sysprep’d image where you have to remove the battery/power off at wall to get out of it.
Create a new temporary group, add all PCs to it.
Deploy multicast image to group with WOL.

Thanks

Hi Tom,
I realise the web page already has a limit, but that limit is 16.

From the Microsoft support documentation “Note The 16th character is reserved to identify the functionality that is installed on the registered network device.”

The limit needs to be 15 for the hostname.

The reason for having the image/os first on registration, is so that the script can then limit the hostname entry to 15 when a windows image/OS is selected.

I’ve no idea if linux/other OS’s have the same restrictions or not, but you could then apply each OS’s hostname restriction after choosing the relevant image/OS.

Hi,
I know some people have had problems with this in the past and have written their own fixes/hacks but would be nice to have the following in 0.33.

On full host registration, ask for OS selection before the hostname.
When windows based host is selected, truncate/limit the hostname to 15 characters as per windows naming convention.

When windows is selected for a host, limit the hostname box on the web interface to 15 characters.

[url]http://support.microsoft.com/kb/909264[/url]
Maybe warn about unsupported characters?

Thanks

EDIT:
Just looking at this post:
[url]http://fogproject.org/forum/threads/host-os-should-be-linked-to-the-image-and-not-the-host-computer.4452/[/url]
Perhaps my suggestion should be changed slightly.
Ask for the Image first on Full host registration first and then limit the following hostname box accordingly.

Having the same problem with the same netbook, NB510.
Tried Eric’s kernel, still same problem.

Any help appreciated, need to get these imaged asap!

EDIT: Also tried the core 3.3.3 kernel.
Ran the ‘fog compatability’ test from ‘Client information’ on the pxe menu which said network drivers failed.
Building custom 3.6.1 now with extra drivers now to test that.

Didnt work with 3.6.1 however I think I have found the driver needed to make this work, but im unsure of how to add/patch the driver to the source code before building bzImage.
[url]http://www.linuxfoundation.org/collaborate/workgroups/networking/alx[/url]
Can anyone help?

As this is down to the network module not being loaded can someone move this thread to Hardware?

FIXED:
[url]http://fogproject.org/forum/threads/dell-2330-all-in-one-network-issue.1054/#post-9005[/url] Someone compiled ALX drivers into the kernel last week

Hi All,
Ive run through the following steps while preparing/rolling out a Windows 7 Enterprise image 32-bit.

1. Install Win 7 on VM workstation (2 partitions, system reserved and drive)
2. Enter Audit Mode
3. Install updates + applications
4. Configure administrator profile ready for sysprep/default user
5. Sysprep with xml
6. Boot to winpe + use dism to add drivers
7. Upload image to fog
8. Deploy to workstation.

At step 8, the physical workstation wont boot up and gives the error winload.exe missing or corrupt. The VM workstation boots up as normal, runs through the setup process and gets back to the login screen.

Ive tried all manner of settings and combinations on Fog 0.32.
Single partition resizable / Multiple Partitions single disk with expand OS partition specificed in sysprep xml
Used with fogprep and without before sysprepping
Removing the “??” entries under MountedDevices in the registry before sysprepping
Tried with and without the BCDEDIT options
All as specified here:
[url]http://www.fogproject.org/wiki/index.php?title=Create_a_windows_7_image_for_many_different_hardware[/url]
[url]http://www.fogproject.org/wiki/index.php?title=What_do_I_have_to_do_to_an_image_before_uploading%3F[/url]

I cannot for the life of me figure out what is causing the problem - I realise its re-assigning the system reserved partition to and actual windows contents to upon booting the imaged PC but how can I stop it doing this and mount them correctly? (system reserved should have no drive letter and should become )

Has anyone gone through this process with 2 partitions, had this problem and then resolved it? Am I doing something in the wrong order? Does DISM need to be ran before sysprep?

Help!
Thanks