Rocket Man Posted March 7, 2017 Report post Posted March 7, 2017 Created ADRs for the new update servicing models, some while back now - Monthly rollup and .NET updates. ADR's created fine with no errors - for example ADR:.NetReliabilityMonthlyUpdateWin7 ADR:Windows8.1MonthlyRollUp Have just stumbled across a possible bug - maybe this is a known bug or is isolated to this CM setup. When you go into the properties of the SUG it states that I must specify a valid name for software update group? It is due to the single . in the names of the ADRs - can anyone confirm they have similar issue? Have re-edited name of SUG removing any single .'s from name and all is OK I have came across this blog that states changing the desc and name of SUGs have no bearing on the deployments and will not trigger another cycle - https://social.technet.microsoft.com/Forums/en-US/a9560993-efa6-48a8-a28a-bb0d5a472bef/sug-name-change?forum=configmanagersecurity Thanks Quote Share this post Link to post Share on other sites More sharing options...
