I stand corrected.
This is interesting and probably was fixed in latest version as it used to bug couple of months ago if you set ConfigurationNames to more then one value. I’ve opened a github issue and a uservoice on this and got a reply its not supported or intended to hold more then one value. So I left it be, hoping it wil be fixed at later point, but never read anything about this being fixed.
Probably it bugged as it was always from a single pullserver and not from multiple. Which was my ultimate request so I didn’t have to setup multiple pull servers for four/five departments each in charge of their section.
The original blog is a good read on how he did it, indeed. Wonder what was the version of the xPSDesiredStateConfiguration module he used.
Phil, i would advise to use DependsOn on one of the partials just so you know exactly at what state the node is. Though it doesn’t matter much with two files, but with complex scripts it becomes vital.
I would also advise on using a report server to see the combined actions.Here you will need another pull server just for that, no point building one for each of the partials.
Still think they should allow partials from same pullserver URL. One can only hope Good find Greg, thanks alot for sharing, need to test more scenarios then in my lab