SMS_STATE_SYSTEM Critical, loads of errors :(

[Bumbi85 1]

As far as i can see regarding the connector. The following services are installed with it:

 

SMS_DMP_Downloader

SMS_Dmp_Uploader

SMS_Cloud_Usersync

SMS_OUTGOING_CONTENT_MANAGER

[danny_gayler 0]

I logged a call with MS, STILL waiting for them to get back to me i didn't have to enable the intune connector when i upgraded though Danny, was yours connected before or not?

 

well i had both scenarios.

 

I did have it connected and then upgraded to R2 SP1 CU1 (on my home lab which is still not working)

And I didn't have it connected when on R2 CU4 (on my work live environment which is also still not working)

 

Both exhibit the same symptoms.

 

Had contact from my Intune engineer to say he's finally got round to looking at the logs. I'll hopefully hear something back today or tomorrow.

[danny_gayler 0]

Just had a call from my Intune engineer. He's just leaving for the day (lucky sod) but he has asked for a remote session first thing tomorrow morning.

 

I'm not sure what we're going to get out of that but at least it's better than me looking at the same old logs over and over again!

[CraigSCCM 1]

Just had a call from my Intune engineer. He's just leaving for the day (lucky sod) but he has asked for a remote session first thing tomorrow morning.

 

I'm not sure what we're going to get out of that but at least it's better than me looking at the same old logs over and over again!

 

I agree, I've had enough of looking at logs now lol

[Bumbi85 1]

Same.

 

Lets hope he can find a solution.

[danny_gayler 0]

So from speaking to Intune support this morning he mentioned that CU2 came out last night. Now as my current SCCM environment is R2 CU4 (not R2 SP1 CU1 as that is now knackered!) I told him that upgrading to the latest and greatest is not ideal as the current set-up can't get the extensions downloaded, so that should be the focus of the problem. He then said that there is a chance R2 CU4 is now unsupported and we have to upgrade...I asked him politely to check that before we think about upgrading.

 

I don't think MS understand this issue which is concerning but if CU2 fixes it, then i'll be a happy SCCM'er. Going to install CU2 on my home lab now and see if it works.

 

https://support.microsoft.com/en-us/kb/3100144

[Bumbi85 1]

Saw this yesterday aswell that CU2 came out, i plan to install it in our lab enviroment. But as we dont have mobile devices in that enviroment i cannot see if it helps or not, we have a intune subscription activated and a connector installed.

 

Let us know if it helps or not.

[danny_gayler 0]

Just finished upgrading my home lab from SP1 CU1 to CU2 and the compmon.log gets an execution state for all of the other components expect for...

 

Can not get the current execution state for component Windows_Intune_Service since it is not installed or completed installing

 

So basically back to square one.

 

Am I being impatient? probably but I'm not convinced CU2 is going to fix the problems with the connector component.

 

If anyone else has installed CU2 and have had any success please let me know!

[CraigSCCM 1]

Same as you guys, I'm a bit weary about installing CU2 - I can't see this having the fix we need

 

Just seen this https://support.microsoft.com/en-us/kb/3080767not sure if this will work for Primary without a CAS?

[danny_gayler 0]

I hate to say it but it looks like CU2 might fix the issues. Well it's fixed the missing extensions on my new SCCM environment anyway...however the home lab on the same CU version doesn't have any extensions still so i'm remaining skeptical and confused.

 

 

Now the next test is to enrol a device and see if the SMS_STATE_SYSTEM critical errors disappear.

 

I'll let you know how I get on.

 

 

 

[Bumbi85 1]

The message "Can not get the current execution state for component Windows_Intune_Service since it is not installed or completed installing" is probably because the service isnt running. I have that one 2 sccm enviroments with intune connector. And as i explained before i am not sure that services is even being used with intune and sccm 2012.

Correct me if i am wrong.

 

 

But let us know how it works out with sms_state_system errors

[danny_gayler 0]

You're right Bumbi85, I think those messages are nothing but...

 

 

So I'm right back where I started and where all of us have been from the very beginning. I've literally just enabled iOS9 extensions, created a configuration item, added it to a baseline and deployed the baseline to a user collection.

 

I'm not even going to both trying a Windows phone yet.

 

ho-hum. Back to Intune support I go.

[Bumbi85 1]

Well this sucks.. GG Microsoft

 

Do you have it narrowed down to it's when you deploy a configuration baseline the problem shows it self?

The weird thing is i had our baseline deployed weeks before this started.

[CraigSCCM 1]

Well this sucks.. GG Microsoft

 

Do you have it narrowed down to it's when you deploy a configuration baseline the problem shows it self?

The weird thing is i had our baseline deployed weeks before this started.

 

 

Same mate, our Baselines were configured December last year, so I can't see it being that

 

Have any of you guys tried to deploy any mobile apps recently to see if they get pulled down and can work?

[danny_gayler 0]

Morning chaps.

 

So here is what I know...

• our managed phones cannot receive configuration baselines or apps pushed through SCCM
• we can remotely retire/wipe and push down compliance policies to my Windows phone

I don't understand how a compliance policy (out of the box config so must be at least 6 characters) gets to my Windows phone within minutes yet a simple configuration baseline with the same setting doesn't?

 

The Intune engineer has been in touch this morning and we've given him a login to enrol an iPad he has. I can see it's enrolled and we get the same errors again. At least this time he can grab the logs from the device and analyse them.

 

Hopefully hear something back a little later on this morning.

[CraigSCCM 1]

That literally doesn't make sense how can a device not receive any apps or baselines, yet you can still remotely wipe the device and get compliance policies, so you've still got some administrative control on the device.... you know I hate Microsoft sometimes !!

[danny_gayler 0]

I hate Microsoft as well...but...when you speak to a Microsoft SCCM professional in the UK who resolves the problem, part of my faith becomes restored

 

So those errors in the statesys.log, ignore those. As we all first thought, Microsoft have been clever and added a type ID into Intune that is not recognized by the SCCM database (yet! I stress yet!). They've no idea who done it but it's preparing for a future extension release which is coming soon. They've not said what the extension is though.

 

If you've got any problems pushing down configuration baselines to your mobile devices, all you need to do is make sure that within 'Configuration Baseline Deployment Properties' you have "Remediate noncompliant rules when supported".

 

 

"But this is already ticked" I hear some of you cry. Indeed. I had this option ticked last week on my old SCCM environment on my only test baseline but the policy never went down to the device. So installing SCCM 2012 R2 SP1 CU2 has done something...just no idea what though!

 

In addition they've fixed the problem with adding Windows phone apps through SCCM. Before CU2 you couldn't add the app from the Windows store as the URL/GUID was invalid. Now you can find the app and click OK.

 

I hope this info helps.

 

 

 

[Bumbi85 1]

So in all Microsoft said that you can ignore those errors for now? And just live with the ammount of errors that are coming in to the system?

Do you have an official statement from them regarding this you can share?

 

And regarding the other i have remediate checked and even got allow remediation outside maintenance checked. But as far as i tested before the compliance is working for us on androind an iphone

[danny_gayler 0]

So in all Microsoft said that you can ignore those errors for now? And just live with the ammount of errors that are coming in to the system?

Do you have an official statement from them regarding this you can share?

 

And regarding the other i have remediate checked and even got allow remediation outside maintenance checked. But as far as i tested before the compliance is working for us on androind an iphone

 

yup. They said ignore them for now. Your corrupt folder within the statesys folder will fill up though so i'd clear that down every-so-often until they release CU(whatever).

 

Nothing official but i'll see if I can get that info out of the Intune engineer.

[Bumbi85 1]

Ok, please contact them and ask for an official statement / explenation. And when they plan to fix this.

[Bumbi85 1]

@CraigSCCM: have you gotten any respons from MS?

[CraigSCCM 1]

 

yup. They said ignore them for now. Your corrupt folder within the statesys folder will fill up though so i'd clear that down every-so-often until they release CU(whatever).

 

Nothing official but i'll see if I can get that info out of the Intune engineer.

 

Wow, just the response I would expect from MS *rolls eyes*

 

@CraigSCCM: have you gotten any respons from MS?

 

Nothing yet mate,...still waiting on a call back

 

I don't like red in my infrastructure i like Green, let's hope they release this asap

[Bumbi85 1]

Same here, i dont like seeing red... and at the moment we have 7 mobile devices enrolled, what will happen when the company decides to take it into produktion and we have 1000-1500 mobile devices. The ammount of errors will be staggering.....

 

Please let me know what MS says to you.

[Bumbi85 1]

Any news?

[CraigSCCM 1]

I'm now getting Critical on my app catalog point - same errors as the State System