I've hit a problem capturing a windows 10 image using MDT in a virtual environment (hyper-v). When I test the process by creating a reference image (using all the default settings) the .iso builds fine, syspreps and save the new capture no problems at all. As soon as I attempt to and any applications (tested using Office 2016 or Chrome) the process runs fine and creates a .wim file only doesn't pass it back to the deployment share.
I've tried several different approaches (silent installs, suspended task sequence, custom capture sequence) to no avail and i'm starting to pull my hair out over this.
From the newly created window 10 instance I have discovered that I can't browse (or cmd net use) the deployment server share (either by unc or ip) but I am able to access other shares on my network. I am able to access the deployment shares from other machines on my network.
Both Windows 10 and MDT are the latest available versions.
Hope someone can help,