ITManLT Posted June 11, 2019 Posted June 11, 2019 Good Morning, Hoping someone can advise please. New to SCCM and we're just working on the OS Deployment task sequence. Everything seems to be working okay, I have had to make a number of tweaks for Win10 1903 such as the unattend file to fix the "just a moment..." screen, but it looks okay at first glance. My question is, how do you tell that the task sequence has been completed 100% like 15/15 steps successful? I know there are numerous log files dotted around, but is there somewhere obvious that shows 15/15 successful? I've had the task sequence fail at various points when I have added some steps in, but when it fails, the machine reboots and sits at the login screen.. Just the same as it would if it got all the way through the task sequence successfully. Thanks in advance.
strawberry Posted June 11, 2019 Posted June 11, 2019 (edited) Are you using MDT or SCCM? MDT has a monitoring option Monitoring Deployment with MDT 2013 | Askme4Tech Edited June 11, 2019 by strawberry
clareq Posted June 11, 2019 Posted June 11, 2019 I go to Monitoring - Deployments, and find the task sequence deployment. If you haven't set any step in the TS to continue on error any machines you see in the Success panel have completed. If you have set anything to continue on error, double click the machine and click on Status - you'll find the build log. There might be a better way, but I find this gives an overview quite well. 1
ITManLT Posted June 11, 2019 Author Posted June 11, 2019 Thanks for the replies both. We have had SCCM installed and configured by a 3rd party. I can see MDT is installed and looks to be configured. I enabled the monitoring and kicked off a build but nothing shows up there, so I assume it's not actually using MDT to build. Checking in SCCM Monitoring it looks like it shows up in there, so from this I will take it that we don't use MDT to build then, it's all done through SCCM. Unless I'm mistaken there.. again, new to SCCM. I've checked one of the machines in the Error section here and it shows the point where one of our builds failed. This looks like exactly what I was after, thanks very much @clareq
Driftingforlife Posted June 11, 2019 Posted June 11, 2019 (edited) Hi. I'm am learning SCCM myself for Win10. I am using the log file smsts.log for checking what is working and what isn't, its located on the client PC under C\windows\CCM\Logs. I am using CMTrace to look at it. Edited June 11, 2019 by Driftingforlife
Fazza Posted June 12, 2019 Posted June 12, 2019 we don't use MDT to build then, it's all done through SCCM. Unless I'm mistaken there.. again, new to SCCM. Correct, you/we dont use MDT at all, you/we must use SCCM. SCCM itself uses MDT and WSUS etc. but you mustnt touch either of them and just let SCCM do its stuff else you might prevent SCCM from working if you make any changes to MDT etc.
ITManLT Posted June 12, 2019 Author Posted June 12, 2019 Thanks for the clarification @Fazza, I thought that must be the case with it being installed and having a deployment share.
gaz350b Posted June 18, 2019 Posted June 18, 2019 (edited) We use this tool great for remotely monitoring deployments so you know when to go back to a room. Also gives you error messages 95% of the time, but there are some instances where it doesn’t give you feedback on the error. But that might be a limitation of other factors such as steps being ran or software etc. https://gallery.technet.microsoft.com/ConfigMgr-Task-Sequence-fefdc532 Edited June 18, 2019 by gaz350b 1
Fazza Posted June 20, 2019 Posted June 20, 2019 (edited) We use this tool great for remotely monitoring deployments so you know when to go back to a room. Also gives you error messages 95% of the time, but there are some instances where it doesn’t give you feedback on the error. But that might be a limitation of other factors such as steps being ran or software etc. https://gallery.technet.microsoft.com/ConfigMgr-Task-Sequence-fefdc532 I've downloaded this but cant get it to connect - I've put in the name of my SQL server and the database name but it just says "[ERROR] Could not connect to SQL Server database!" - is it just a case of installing this msi or is there some configuring of SCCM that needs to be done to? [EDIT] All sorted, the program says to enter the servername as SERVERNAME\INSTANCE whereas it's simply just SERVERNAME! Edited June 20, 2019 by Fazza
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now