PENDING WMI for Task Sequence

[dba55]

Does anyone know if there is a way to NOT run a task sequence if the Built in Administrator account is logged in. But only if another user is logged in?

 

[Garth]

Just to be clear it does NOT run as built in administrator. It runs as Local system account. There is a HUGE different.

What are you trying to do?

 

[dba55]

I want it to run when anybody but the built in administrator is logged on. This is LAPS install and it will disrupt the build process if it changes the password during the build. So I want it to run after the build is completed and a user logs in. So I was wondering if using a WMI query could be the answer to this.

 

[Garth]

Again CM does not use the local administrator account it uses the local system. You can't change the pw on it, per se.
Have you seen this. https://www.prajwaldesai.com/how-to-deploy-microsoft-laps-using-sccm/

 

[dba55]

MDT is using the Local Administrator account to build machines. During the build process if the Local Administrator password gets changed, then the build fails. I want to install LAPS after the build process is complete using a task sequence at logon. So I would like to see if I can create a WMI query that would look at the logged on user and NOT run the LAPS install if the logged on user is the local Administrator. Then when a user (anyone but the local Administrator) logs on, then the LAPS install will run. I hope this is a clearer explanation.

 

[abnrangerx67]

I want it to run when anybody but the built in administrator is logged on. This is LAPS install and it will disrupt the build process if it changes the password during the build. So I want it to run after the build is completed and a user logs in. So I was wondering if using a WMI query could be the answer to this.

What is your environment, domain or workgroup? If the former, why not use a different account like a domain join account? Also, something does not seem to add up when you say MDT is using the local account to build machines, please elaborate. Where is MDT pulling these creds from? When you say local admin account, in my mind, I am thinking an account local to the computer. Also, if these are new computers being built, then by design there is no "previous" account to reference that MDT should be using to throw a password error. Forgive me, just trying to wrap my head around your process. However, as already pointed out, the local system account does everything, it is only if there is domain join step that specific creds are needed. If a workgroup, then based on either a step in the TS or the customsettingings.ini, local accounts will get created as defined