There is a bug when using a composite resource which doesn’t allow you to specify the DependsOn attribute. I posted this on the MSDN Powershell blog here
It should. What would be better is to use the DSC Diagnostics module from Microsoft to start a trace, run Start-, and then examine the trace log. That’s much more detailed.
I think the problem with having multiple node blocks is that each node block produces a MOF, and you can only have one MOF per machine. Aside from DependsOn, there isn’t much control over order-of-execution when DSC is evaluating the MOF. Obviously, the bug makes that not work… but I don’t think there’s a real workaround for that.
I know this is a long time ago now, but I believe I am hitting the same issue. After eventually managing to log in to connect with a “personal” account (really MS!!!), I got an error about it not existing or I don’t have permissions, so I can’t read whether MS fixed it or not.