Last active 4 months ago
Here is an update. After scanning through the form I find that trying different Kernals may correct the no nic driver problems. I tried 3.18.1 to 4.16.1 and no change. But, I will admit that I pull this "test" laptop from a vacant desk so there may be other issues here. I'll retry my test on a known working computer to see what the results are.
Details to follow....
Here is an update on installing 1803.
I created a VM and installed the OS from an ISO file. That worked fine. I then uploaded the OS to CD. No issues there. Next I deployed to a laptop (HP 3115m) and the install worked but I have no nic drivers. The wireless does work but not the nic. So as an experiment I decided to install W10 1709 but it failed with this error: Parse error: Invalid Numeric Literal At Line 1 column 5
Could not find additional distribution points. I checked the logs but didn't see anything out of the ordinary.
I've attached then to this post
Hadn't looked into using Groups but after a quick review I see that I can do that.
Thanks. Sorry for the confusion.
How about this alternate suggestion.
On the computer screen setup for group assignments. So you would check all the computer you want to assign to a group then select the group.
Maybe this would agree with every one?
Would it be possible to pick the site the computer is to be assigned during the discover process?
So when you are deploying (or uploading an image) when it asks you to give a name of the computer you are working with you could also pick the site to assign it to from a dropdown menu in the same screen you fill out the computer name.
The report I have is that the deployment of the Windows 10 Image was successful.
If other issue pop up I'll post them here.
OK I think I found out the issue. It's was my error, When I created the CD account for this tech I did not setup any ACL's rights for him.
We have started the new upload and I will report back when the deploy of the new image has been sent.
I did the update and tested using an image that worked in the past (Windows 10 but not 1709) and that worked. However, when I syspreped the 1709 image it failed right after the tech entered his login username password. I've attached a picture of what was on the screen.
Next week things should slow down and hopefully I can do the update and try the test.