Topics created by rbaldwin

@rbaldwin Sounds like you found and fixed the issue. Yes PIM (modes) is definitely a good keyword. Marking this solved now. Hope that others might stumble upon this and find it helpful as well.

@Tom-Elliott Another example:

You have a lab of 30 computers. 8 of them are Dell, 22 are Lenovo. You have an image that works on the dells, and an image that works on the Lenovos, but not an image for both yet.

You’d make three groups. ONe for the dells, one for the lenovos, and one for all 30 of them.

Use the dell group to apply the Dell image to all the dells. Use the Lenovo group to apply the Lenovo image to all the Lenovos. Use the bigger classroom group to apply Active Directory settings, Snapin Settings, Printer Settings, and whatever else.

Another example:
You have a building with 500 computers. 250 of them are Dell Optiplex 7010 models. The rest are other models. For this, you could have two or more groups. One group for all Optiplex 7010 models, and one group called “Blah-blah-Building” for every computer in the building. You’d use the building group to deploy updates for things like Chrome, and you’d use the model-specific group to do mass re-imaging when that time comes.

Already fixed in 1.3.1-RC-2 (which as also been released).

@Tom-Elliott said in dmraid and mdadm?:

@rbaldwin while we await your suggestions/ideas/etc… Anyway we could have you try the --metadata flag during auto assembly? While I will likely add the postinitload feature anyway, I’d still be interested in seeing if we can get automated detection working.

Since mdadm --examine --scan shows the metadata for the array as metadata=imsm, I used that in my attempt.

madadm --assemble --scan --metadata=imsm

Same results as before, the array isn’t found.

Found the secondary issue of the “multicast session is invalid”.

Basically I missed one point by not including a space where it needed one.

This is now (properly) fixed and patched up so people doing fresh installs will be fine, and people doing upgrades (that had the issue originally) will magically be fixed when they install the latest (when rc 20 gets pushed).