In an earlier article, I showed you copying DSC resources and PowerShell modules to remote computers. In that article, I showed a method to authorize remote computers to access the UNC path. For the File and Package resources, this is not necessary. These two resources support the Credential attribute for authenticating to the UNC path. However, the story is different for the Archive resource. It has no Credential attribute which is not only inconsistent but also painful as this forces us to change the computer account permissions for the UNC path or use workarounds such as employing File resource to perform the local copy and then extracting the files using Archive resource. Now, why do we have to perform multiple steps for just extracting files from a simple archive?
Some of you might say that extracting over the wire isn’t recommended and it is always good to copy the files to a local system before extraction. I don’t agree. The file copy to local system has more or less the same impact on your network resources as extracting over wire.
So, if you also think that the Archive resource must have the Credential attribute, go ahead and vote for this Connect suggestion: DSC Archive resource should have the Credential attribute.