title: Generating MOFS for Partial Configurations using Configuration Names
body: <p>I currently have nodes set up to pull their configurations from a http pull server (lab environment). The LCMs of these nodes are using configuration names to find their mofs. If I manually modify a mof to be the same name as the configuration name and change the mof data to apply to all computers, they work. What I can not find is an easy  way to generate mofs like this from the cmdlets.</p>
  
  <p>Generated mof: servername.mof</p>
  
  <pre><code>@TargetNode='servername'...
  </code></pre>
  
  <p>Modified mof: configurationname.mof</p>
  
  <pre><code>@TargetNode='*'...
  </code></pre>
  
  <p>If I try to generate a mof without specifying a node name and having <code>Node * {...}</code> in the configuration script I just get the following error:</p>
  
  <blockquote>
    <p>out-file : Cannot perform operation because the wildcard path .\configurationname/*.mof did not resolve to a file.</p>
  </blockquote>
  
  <p>If I create that directory and put exactly one mof in it, the cmdlet will overwrite it and change <code>@TargetNode</code> to a wildcard. Multiple mofs in the directory will result in a different error.</p>