GCW.License

We used to have the answer files skip all but the machine naming/domain join dialog during deployment and had the rest of the standard answers in the answer file. With 2.0.3020, that no longer worked and every dialog was shown during deployment. We rebuilt the answer files with 3020 and changed all of the sections to 'skip="1" ' to match what worked before. Now most of them are skipped, but "Network Credentials" and "Naming Convention" still are not skipped. Any thoughts?

What we ended up doing was rebuilding the reference machine from scratch and installing everything with Windows in "Audit Mode". So far that has resolved the issue, but I'm still not done fully and have a lot of software yet to install. However, with Windows Updates, Microsoft Office, standardized apps, start menu, desktops, images, etc., it all looks good so far.

The agent for windows appears to communicate frequently with the SmartDeploy Server. How do we configure the agent settings to reduce this unnecessary network traffic? Our network team is concerned with the volume of apparently useless traffic being generated by all of these agents. What port, protocol, frequency, etc. does it use? What does the agent actually do that it needs constant communication to the server?

Here's the log from the last test deployment. Thanx! Deploy.log

We have been trying to resolve this for over a month now. After a deployment, the Start menu is full of broken tiles and links. This has been reported in other threads and across the Internet, but we have not been able to resolve the issue after trying everything posted elsewhere. We even went so far as to create a fresh VM, disable the NIC, install Windows 10 1703 fresh, make a fresh image, and deploy that to no avail. The broken links still show up after the machine is deployed. On a broken deployment, if we run a Windows 10 "Upgrade" Install from the Windows DVD, that will resolve the issue for that machine, but this is not a viable option when trying to deploy Windows to 100+ computers... How do we resolve this definitively at the time of deployment? What is the Windows 10 "Upgrade" doing that fixes the machine, and is there a way to run that after the image is dropped?