Individual Computers assigned to groups

[Quazz]

@howtogravity Not that I’m aware of. If it’s always the same machines though, you can simply create another group and assign them to that one as well.

[HowToGravity]

@quazz The thing is we always have computers (laptops) coming and going that needs to be re-imaged. Some days we get just 4 laptops back and the next day we can get 10 laptops back and they are not the “same” but they are the same model laptops.

Will just having computers tasked on the fog server have any impact on the speed of the server or the speed of the imaging process?

[Quazz]

@howtogravity You can also use ‘Quick Deploy’ by booting them manually and just selecting the correct image. On light loads this seems doable to me.

You’ll want to clear out unfinished tasks for sure, but shouldn’t be a huge issue afaik.

[HowToGravity]

@quazz Where do you see “Quick Deploy”, because when I NIC boot and get to the FOG boot screen the only options i have listed from top to bottom are:
Boot form hard disk
Run Memtest86+
Update Product Key, Deploy Image
Join Multicast Session
Quick Host Deletion
Client System Information (compatibility)

The deploy image option prompts you to enter in the FOG username and password. I can’t go that route but i know there will be complaints about that as well.

[Quazz]

@howtogravity “Deploy Image” is the one

[HowToGravity]

@quazz Is there a way to disable the prompt user for username and password?

[Quazz]

@howtogravity Yes, change the fog.deployimage iPXE menu item.

Replace parameters with

set username foglogin
set password foglogin
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

Replace foglogin with login credentials and you should be good to go.

[HowToGravity]

@quazz It works, Thank you for your help. I’ll see if this will work with them.

[HowToGravity]

@quazz Is it possible for multiple images to have the same image path?

[Quazz]

@howtogravity Not that I know of. It wouldn’t really make sense, you typically wouldn’t want another host to overwrite the same image.

[HowToGravity]

@quazz Yea that was an issue that they faced. The only reason I ask is because that is how they currently have it for their production FOG server and just wanted to know if it could be done again on this version of FOG.

[Quazz]

@howtogravity I guess you could technically trick the system by creating a symlink to the target folder and use that symlink path for the pointer image. I have no clue how well this will hold up and of course you must be careful with capturing image and such.

ln -s /images/Dell_790_Master/ /images/Dell_790_Pointer

You will have to test it I suppose, I have no idea how well this will work, but it should do the job afaik.

[HowToGravity]

@quazz Tried that yesterday and i get the following error. And the image does not go on the machine.

The current version that they are on.

[Quazz]

@howtogravity That’s unfortunate. I guess it might still work if the path on the server and the client (so where FOS mounts it) is the same, but I’m not sure what the default path is atm.

[HowToGravity]

@quazz Do you know where I can find more information about the FOG version that i posted an image about? I’m curious as to why i works for that version and not the current one.

[Quazz]

@howtogravity Looks like a trunk version of 1.4.0

I’m guessing the check to make sure paths are unique was added later, likely to resolve a bug involving using the same path.

[HowToGravity]

@quazz Okay, thanks for your help. You can mark this post as solved.