NoReg
-
Sorry if this was already posted but I did not see it.
Before with 0.32 my organization used the noreg option a lot. We had a whole custom menu for different images which all had different software depending on where the computer was going. Our organization mainly uses FOG to image a computer then we may never see that computer again for years. Which makes keeping the host registration almost useless. A way around this was the noreg and custom PXE menus. This way it was a few clicks and a couple custom script on boot up and the computer is out the door.
Are there any plans to implement this feature back into 1.0.1?
-
i’m not familiar with noreg, do you mean capone?
-
You can use the quick image function, but in the FOG UI your quick image will need to be set to whatever image that machine needs.
Or like Junk said, you can install the capone plugin.
[url]http://fogproject.org/wiki/index.php/Capone[/url]
[url]http://fogproject.org/wiki/index.php/Plugins:_Capone[/url]
-
I was actually talking about the Bypass Host Registration. However I’ll look into Capone to see if that will work instead.
[url]http://www.fogproject.org/wiki/index.php?title=Bypass_Host_Registration[/url]
-
Thank you for tipping me off to Capone. So far I like it way better then the Bypass Host Registration. I have a quick question however.
Can Capone be used to deploy 2 separate images?
ex.
You have 2 images for the same computer. You associate both images to the same DMI key. When you Capone Deploy it prompts you asking which image you would like to use? -
[quote=“SuP3R_Ch1cKeN, post: 27963, member: 4306”]Thank you for tipping me off to Capone. So far I like it way better then the Bypass Host Registration. I have a quick question however.
Can Capone be used to deploy 2 separate images?
ex.
You have 2 images for the same computer. You associate both images to the same DMI key. When you Capone Deploy it prompts you asking which image you would like to use?[/quote]Right now that’s not supported. It assumes one DMI field per image set. So you “could” get it to maybe work but it would be rather random at deciding which one would be in use.
The idea of Capone was to use one image across multiple systems of the same make/model situation. This is ideal for work shops. You could imagine something like Best Buy where they may get 100 of the same computer. Create a single image and deploy that to all 100 systems so they know all are basically setup the same way when they leave the store.
-
From earlier testing as long as you use the same dmi field, you can associate 2 images. As an example, you set the dmi field to manufacturer, and then associate 2 different images with it. The capone server side code returns both of these to the client, and the capone client side code realises there are 2 and asks you which one you want. When I get chance I check out the latest svn and see if it is still this way.
As an alternative, you could set the dmi field to model, then associate 3 images, xp, w7, and w8.
when a client of that model images via capone it will ask which one you want.
unfortunately the dmi field is global for capone, ie you can’t have model for some and manufacturer for others. -
I’ve tested on r1717, and can confirm that you associate more than one image to a dmi criteria, and will get a message to that effect on the client, and asked to choose which one.
see attached screen shot, for info I have the dmi field set to serial number.
[ATTACH=full]828[/ATTACH]
[url=“/_imported_xf_attachments/0/828_capone_multi.png?:”]capone_multi.png[/url]
