Background: My first experience with the SEPM was with MR4 MP2.
I was able to successfully build a 11.0.4202 package that placed new SEP installs into the proper, separate group for my division.
Later, we then upgraded to RU5 and again I successfully built a 11.0.5002 package that placed new installs into my group.
However, after upgrading to RU6a, I am no longer able to build a 11.0.6005.562 package which will place new clients into my group.
After expanding this new single exe package, I found that the SyLink.xml file in the new RU6a package differed in that, unlike the RU5 package, the
<RegisterClient PreferredGroup= ... tag is
not specified. As a result, having done two new client installs before realizing this problem, those clients instead of course ended up in the Default Group. I of course tried exported the package two more times, making sure I was in fact specifying my group, but something has clearly changed on at least our SEPM or in RU6a itself.
This sure sounds like a bug I found in the release notes, 1418576, which was fixed back in MR4, back before I even started deploying SEP 11:
> Fix ID: 1418576
> Symptom: Location-specific communication setting does not honor the preferred group and preferred mode.
> Symantec Endpoint Protection Client reports to Default Group
> Solution: While exporting a package, preferred group information and preferred mode information is set to
> these location-specific communication settings.
Also, I have verified that the "Use Group Communication Settings" checkbox is still checked for my group (as it also chekced at the top My Company level), in case someone was going to ask me about that setting.
Anything else I should check or is this really a new manifestation of that old bug?