You can also create more parent menu items (in addition to the advanced menu) and use the same concept as above. For example on the same level as the advanced menu, you can create an entry for WinOS setup pxe boot another one for disk utilities and a third for debug utilities. They don’t all have to be in one advanced menu.
You have to remember that you must be on the 1.3.0-rcX build (1.2.0 will not have the utiltiies to manage the iPXE menus from the GUI) and your paste into the parameters field must be a complete iPXE menu, so you must learn iPXE menu design (or find one you can hack up to your needs /like above/. http://ipxe.org/examples
They don’t lose storage groups going from 1.1.2 to 1.3.0 (any rc you want).
They don’t lose storage groups going from and version 1.2.0 and earlier because Storage Groups for snapins didn’t exist at all.
Trunk introduced the idea that snapins work in a similar fashion as images and because of this should be allowed to replicate and move around to different groups and nodes.
So it’s no surprise they don’t have group settings defined. This is because we don’t know (we being the FOG team) how you intend to use your snapins and think it’s safer to allow you to setup how you need it setup.
Please define your relevant storage groups and reupload the files as needed. This should fix the storage group problem for you too.