Microsoft endpoint configuration manager. error "Failed verifying schema version property in wmi sequence"

Question

question

MarioAlves-1105 asked Dec 17, '20 MayerRene-4644 commented Jan 15, '21

Microsoft endpoint configuration manager. error "Failed verifying schema version property in wmi sequence"

Hello,
I don't know if i am at the good place, sorry about it,
We have some problems editing our Task sequence on Microsoft Endpoint Configuration manager (1910),

At this moment we have 12 Task Sequence, on 2 of them, we keep having a lot of errors when we try to edit it :
Prod Windows 10 build 1909 (total Steps 976) and xdev Windows 10 build 1909 (same as prod, but we do some test on it before applying the changes)

Starting 2-3 months ago, we started having this error message when editing, if we add some new steps this problem comes more and more until we can't add anymore a a new step or edit the task sequence.

Log file (SMSProv.log) :

The only way to edit the task sequence is to restart the WMI service, then for 2-3 minutes it work and then the error come back again.

If we try to re apply again the task sequence, on my computer there is this error, on the main server the CCM console crash and I need to start the Configuration manager again :

If we remove some steps the task sequence seems to be stable again, but if you add some new steps, then the error come back again, there is what I tried until now without any success :

Replace almost all the WMI query with Task sequence Variable (on the dev version)
Edit all the last WMI to be more specific (2 WMI query "Elitebook", "Zbook" => replaced by 1 query "book")
Also tried this article, on the main server and SQL server : https://techcommunity.microsoft.com/t5/configuration-manager-archive/task-sequence-editor-8220-too-many-steps-8221-issue-and-solution/ba-p/272870
Also this one (Main server Only) : https://social.technet.microsoft.com/Forums/en-US/852110c4-4d6c-42ea-b50c-0ecfe199b19c/the-task-sequence-can-not-be-created-an-error-occurred-when-storing-the-task-sequence?forum=configmgrgeneral
Check the TS .xml size, the limitation is up to 4Mb, the TS doesn't even do 1 MB :

Does somebody have an idea how to solve this error ? It's really annoying and I would avoid to recreate a full new task sequence from 0... all the others Task sequence are working correctly, they all have 400 - 700 steps and when we edit them there is no error with them.

Thank you in advance for your help and the time you take to read all the message.

msc-operations-manager mem-cm-osd

error-ccm-console2.png (10.8 KiB)

2020-12-17-090502.jpg (116.3 KiB)

error-ccm-console3.png (3.3 KiB)

tssize.jpg (32.6 KiB)

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AlexZhu-MSFT · Dec 18, 2020 at 01:11 AM

add mem-cm-osd tag since this is MECM OSD question.

1 ·

Answer 1 · 2020-12-18T08:12:34.577Z

SimonRenMSFT-3639 answered Dec 18, '20

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

As the TS editor does not save the task sequence to the site database directly; instead, it initiates a WMI call to the SMS Provider , which will then write the data to the site database. For a very large and complex task sequence, the WMI call can cause the WMI process hosting the TaskSequenceProvider to exceed its memory quota. So we can try the following actions:

1.Increase the available number of WMI memory buffers.
2.Adjusting the Site Server's WMI Provider handles and Memory allocations.

For more detailed steps, please refer to this similar thread:
Task Sequence Error

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2020-12-18T08:23:59.977Z

MarioAlves-1105 answered Dec 18, '20 SimonRenMSFT-3639 commented Dec 24, '20

Hello,
Thank you a lot for your feedback, as mention on my first reply I already tried this solution on the Site Server without any success.

The registry settings :

The WMI settings :

Does i also need to apply them on the main SQL server ?

Regards

wmi-memory.jpg (178.2 KiB)

wmisettings.jpg (92.2 KiB)

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SimonRenMSFT-3639 · Dec 21, 2020 at 10:08 AM

Hi,

Thanks for your reply. This is a complex issue. I will do more research, if there is any update, I will let you know. Thanks for your understanding. It's also recommended to submit a case with Microsoft to get better support:
https://support.microsoft.com/en-us/help/28808/microsoft-store-contact-supportmicrosoft-store-contact-support

Best regards,
Simon

0 ·

MarioAlves-1105 SimonRenMSFT-3639 · Dec 21, 2020 at 10:56 AM

Hello,
Thank you i will do that.
Have a nice day

0 ·

SimonRenMSFT-3639 MarioAlves-1105 · Dec 24, 2020 at 01:50 AM

Hi,

Thanks for your reply. I'll keep an eye on this issue.

Best regards,
Simon

0 ·

Answer 3 · 2021-01-14T09:47:06.947Z

MayerRene-4644 answered Jan 14, '21

Any news on this topic? We are facing this issue too.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 4 · 2021-01-14T11:53:42.2Z

MarioAlves-1105 answered Jan 14, '21 MayerRene-4644 commented Jan 15, '21

Hello,
From my side, I have no news, unfortunately, I need to see if we have the contract with Microsoft to open a ticket with the support,

For the moment the only work around I have is to restart the WMI then for 1-2 minutes I can edit the Task sequence, I tried to reduce the amount of steps on the Task sequence it seems to help, I have a copy of the same task sequence with only 500 steps and I have no issue with this one, the other with the problem have 780-820 steps.

I was thinking about our anti virus, we are using Cybereason and with Windows 1909 we had some issues with the Powershell and WMI related to the anti-virus who blocks the process and makes it unusable.

Maybe it's also the Antivirus who does something on the server when there is a lot of data, we have a new version we are testing, if it's simply that I will tell you, I don't know if you are using the same software.

Have a nice day.

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MayerRene-4644 · Jan 14, 2021 at 12:30 PM

Thank you for your quick response.

Do you have MDT integrated Task Sequences? I assume this could be an issue to in this case too.

We do not use Cybereason yet, but there's a project in the pipe. Would be nice to have some basic feedback from you on this AV product. But there's no way to do some direct messaging here, isn't it?

May it's on me to do some troubleshooting with MS in a call. I will consider that. Let's see who's first ;)

0 ·

MarioAlves-1105 MayerRene-4644 · Jan 15, 2021 at 07:36 AM

Hello,
Yes, we have the MDT integrated in the Task Sequence.
About Cybereason, it works pretty well, too much sometimes, if you use some *. Exe files from the Technet for example, the manager can receive some alert because some of them are considered as a malware.

The main problem we had with it, is with the Windows 10 Build 1909, it blocks almost all the Powershell WMI requests from Configuration Manager, so you don't receive any more any Windows updates/Software Updates/Inventory updates/etc.... so we had to remove it from our computers with the build 1909.

It took almost 1 year to cybereason to understand the problem and make the changes, we had the first issues in April last year and we opened a case with them, and the new version with the corrections is only available now.

Maybe we are not big enough to be so urgent to them, I don't know :D.

Regards

0 ·

MayerRene-4644 MarioAlves-1105 · Jan 15, 2021 at 08:16 AM

We have MDT integrated Task Sequences too.. but the problem does not rely on this circumstance only. I think a MS Call is inevitable. I will let you know as soon I have news in this case.

Just one more off topic question regarding Cybereason. How do you deal with the fact, that it does not register as Anti Virus Provider in Windows?

0 ·

Show more comments

question