Release Management vNext deployment succeeds without deploying the DSC to the target.

Question

All of a sudden, a couple of weeks ago, our vNext releases stopped working.
The log in the release management client says that the release has been deployed successfully, but nothing has actually happened on the target server. The log looks like this (which is bad)...
Copying recursively from \\xxxxx.co.nz\Public\Share\Development\Builds\DispatchService_MAIN\DispatchService_MAIN_1.1.7.0\DispatchService\_PublishedWebsites\DispatchService to C:\Windows\DtlDownloads\DispatchService Component succeeded.
That's all it says. No error, no nothing.
It used to look like this (which was good)...
Copying recursively from \\xxx.co.nz\Public\Share\Development\Builds\SosService_MAIN\SosService_MAIN_1.1.32.0\SOSWindowsService to C:\Windows\DtlDownloads\SosServices succeeded.
Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
An LCM method call arrived from computer BDWEB10 with user sid S-1-5-21-3667390900-813461161-666584507-16981.
[BDWEB10]: LCM: [ Start Set ]
[BDWEB10]: LCM: [ Start Resource ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ Start Test ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ End Test ] [[bStopService]StopTheService] in 0.0000 seconds.
[BDWEB10]: LCM: [ Start Set ] [[bStopService]StopTheService]
[BDWEB10]: [[bStopService]StopTheService] Stopping service SosServiceDevReviewPci
[BDWEB10]: LCM: [ End Set ] [[bStopService]StopTheService] in 0.1400 seconds.
[BDWEB10]: LCM: [ End Resource ] [[bStopService]StopTheService]
[BDWEB10]: LCM: [ Start Resource ] [[File]CopyDeploymentBits]
[BDWEB10]: LCM: [ Start Test ] [[File]CopyDeploymentBits]
etc etc
I have tried many things, and have discovered some clues, but have filed to find a solution.
It seems that it is successfully creating the .mof file on the "Deploy using PS/DSC Server" but then it deletes the .mof file and does not try to do a Start-DscConfiguration with the .mof file.
This is very frustrating, as we have sunk an awful lot of time and money into Microsoft Release Manager.
Does anyone have any ideas?

Answer 1

Hi Leighton,  
Thanks for your post.
You’re using TFS 2013 Update 4 and Release Management 2013 Update 4?
Do you mean that the files be copied to C:\Windows\DtlDownloads\DispatchServices folder on target machine as expect, but no file be executed to perform the deploy?
You said the release template works fine a  couple of weeks ago, do you know which changes happened on this release template after that week? 
Only this current one release template cannot works? Or if you create a new release template to run DSC deploy, it will receive the same result too?
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.