MicrosoftThanks for clarifying your concerns (and findings), christophergg, and Ian Clarke- that makes it clearer- Regarding changes in terminology or documentation, I would refer to this: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fitpro%2Fwindows-10%2Frelease-information&data=02%7C01%7Clext%40exchange.microsoft.com%7Cb0ec264f866b4333f20408d5b1cc464e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636610413273784555&sdata=ZO%2FShQsA5KiQonYJwksBEqd%2FHHfFAoMOqe5m8w9kWM0%3D&reserved=0
Meanwhile, just to emphasize that I wasn't suggesting Microsoft has dropped the terminology for SAC, it hasn't changed since https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fitpro%2Fwindows-10%2Frelease-information&data=02%7C01%7Clext%40exchange.microsoft.com%7Cb0ec264f866b4333f20408d5b1cc464e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636610413273784555&sdata=ZO%2FShQsA5KiQonYJwksBEqd%2FHHfFAoMOqe5m8w9kWM0%3D&reserved=0. SAC (targeted) is now in use (rather than SAC-T) to identify the validation ring prior to broad deployment. I just wanted to make sure the process is understood first, and it seems it is, which is great to hear! Hope that helps for now, and I'm pleased to see that in your testing (in both cases) on 1709, SAC(T/Targeted) and SAC. So the process appears to be working even if there has been confusion in the terminology.
Thanks again for the feedback and for clarifying the concerns.
