Fix for incorrectly named devices enrolled using Autopilot through Azure Automation

Thanks for this!

You'll actually notice that the correct profile does make it to the device. I put in a ticket. Microsoft Support says there's a 3 minute hard-coded timeout. If the work (in that 3 minutes, including PC rename) isn't completed in time, it moves on, leaving a generic name. It's apparently not going to be an easy one to fix on MS side.