4,608 questions
TS is not signaled by MTC to start. eState: 1 | Task sequence launcher deployment failed!. Code 0x80070480
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 63%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Boopathi S
3,816
Reputation points
Hello,
Installation started at 3/14/2023 7:21:21 PM and still continue still now saying "Waiting for job status notification... InstallSoftware 3/15/2023 3:34:36 AM 2432 (0x0980)"
Below is from smsts.log
TSAgent.log says below
TSLauncher initialized environment for task sequence: deployment ID = '00053279', package ID = '00001112', Name = 'TestTaskSeqeuncet' TSAgent 3/14/2023 12:22:25 PM 8236 (0x202C)
Successfully initialized Task Sequence environment. TSAgent 3/14/2023 12:22:25 PM 8236 (0x202C)
C:_SMSTaskSequence does not exist TSAgent 3/14/2023 12:22:25 PM 8236 (0x202C)
Updated security on object C:_SMSTaskSequence. TSAgent 3/14/2023 12:22:25 PM 8236 (0x202C)
Starting Task Sequence Manager Service. TSAgent 3/14/2023 12:22:25 PM 8236 (0x202C)
Task Sequencing Manager Service successfully started. TSAgent 3/14/2023 12:22:25 PM 8236 (0x202C)
Initializing the Task Sequence... TSAgent 3/14/2023 7:16:07 PM 6052 (0x17A4)
Please help to fix why the task sequence is like "Waiting for Installation" message
Microsoft Security | Intune | Configuration Manager | Other
{count} votes
-
Rahul Jindal 10,911 Reputation points2023-03-15T08:00:55.25+00:00 Which step of the TS is in question? Appears to be related to installation of some sort application\package.
-
Boopathi S 3,816 Reputation points
2023-03-15T10:40:27.8+00:00 -
Rahul Jindal 10,911 Reputation points
2023-03-15T13:39:46.5966667+00:00 Thanks. Can you check for the following?
- Disable application installation steps and test against packages.
- Ensure OEM specific driver packs\drivers are added in the Task sequence.
- Ensure latest source bits are being used for the installation of the ConfigMgr agent.
-
Boopathi S 3,816 Reputation points
2023-03-16T15:14:00.96+00:00 Thanks for your answers.
- Disable application installation steps and test against packages. Same applicaiton works using different task sequence
- Ensure OEM specific driver packs\drivers are added in the Task sequence. Driver packages are added
- Ensure latest source bits are being used for the installation of the ConfigMgr agent. SCCM client version is 2211
Refer the below screenshots between working and not working applicaiton. [This is means package]
Not working software screenshot
Different between working and not working applicaitons is Handle.IT says failed to register active handle.
Plesae help what should be the problem and how to solve it.
-
Rahul Jindal 10,911 Reputation points
2023-03-16T19:53:07.6166667+00:00 “Same applicaiton works using different task sequence” - which other task sequence? Are these imaging Task sequences or otherwise?
-
Boopathi S 3,816 Reputation points
2023-03-17T05:57:00.5466667+00:00 I mean to say that same task sequence with same applicaiton works at another office locations.
Hierarchy is 1 CAS and 6 Primaries. There are no secondary sites.
-
Rahul Jindal 10,911 Reputation points
2023-03-17T06:33:23.2766667+00:00 And same model?
-
Boopathi S 3,816 Reputation points
2023-03-17T13:11:20.11+00:00 @Rahul Jindal Yes. Different Model
-
Rahul Jindal 10,911 Reputation points
2023-03-17T17:09:40.7333333+00:00 If it’s a difficult model then I am going to put my money on network drivers. Try running the TS as is with driver pack disabled. Let default Windows OS driver stack load.
Sign in to comment
Sign in to answer