Kevin79 2 Report post Posted August 21, 2019 I've got a weird issue. I use an OSD task sequence in Config Manger to install Windows 10 on new computers. Up until recently, it was working perfectly. Now when I deploy a new computers, if I look under Assets and Clients > Devices, I can find the computer but it shows Client as No. If I search for the GUID that the Configuration Manager client uses, it shows the name as "unknown". How do I get these to sync up? Quote Share this post Link to post Share on other sites
anyweb 461 Report post Posted August 22, 2019 sounds like it's not completing the task sequence correctly, and possibly the client agent is not getting installed properly during the task sequence, i'd start by focusing on smsts*.log and see what it reveals for the Setup Windows and ConfigMgr step... Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted August 22, 2019 I don't see anything that stands out to me regarding the client. Quote Share this post Link to post Share on other sites
anyweb 461 Report post Posted August 23, 2019 attach your logs here so I can see.. Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted August 26, 2019 I zipped the 3 SMSTS files. The computer name is us-war-w0051 smsts.zip Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted August 29, 2019 Have you had a chance to look at the logs? Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted September 9, 2019 Any update? Quote Share this post Link to post Share on other sites
TrialandError 10 Report post Posted September 9, 2019 The image you are deploying in the task sequence.....is it from a capture or are you applying the OS from the WIM file? Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted September 9, 2019 It uses the unmodified WIM from W10 1809. Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted September 16, 2019 Anyone? Quote Share this post Link to post Share on other sites
anyweb 461 Report post Posted September 17, 2019 ok sorry about the delay, busy working, from first (quick) looks it looks like your logs are way too small and therefore missing details (such as the info we really need to see to diagnose this_), so you'll need to modify the ccmsetup command line to increase the log file size this will show you how to do that once done, deploy a machine again and capture the new logs, attach them here cheers niall Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted September 18, 2019 19 hours ago, anyweb said: ok sorry about the delay, busy working, from first (quick) looks it looks like your logs are way too small and therefore missing details (such as the info we really need to see to diagnose this_), so you'll need to modify the ccmsetup command line to increase the log file size How big should the log files be? I made the change and did as setup, I got 2 smsts logs that are around 5MB each. Quote Share this post Link to post Share on other sites
Kevin79 2 Report post Posted September 18, 2019 Here it is. smsts.zip Quote Share this post Link to post Share on other sites
