We're on 1806 - which I think is 2016... I'm not part of the SCCM team so not massively familiar with the version numbers.
As I said, we don't have any widespread crashing issues across the estate and every other server uses CCM.exe. However, only our ReFS repositories have issues.
-
ejenner
- Veteran
- Posts: 636
- Liked: 100 times
- Joined: Mar 23, 2018 4:43 pm
- Full Name: EJ
- Location: London
- Contact:
-
Mike Resseler
- Product Manager
- Posts: 8045
- Liked: 1263 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Server 2016 BSOD Bugcheck
1806 is indeed SCCM 2016. I believe creating a support call is in order now. However, most likely they will not find anything or point you to MS support. But at least it is worth a shot, maybe then can see where it fails...
-
ejenner
- Veteran
- Posts: 636
- Liked: 100 times
- Joined: Mar 23, 2018 4:43 pm
- Full Name: EJ
- Location: London
- Contact:
Re: Server 2016 BSOD Bugcheck
I think Veeam have said it would go straight to Microsoft... but through Veeam so we can go through it together. Due to current workload I'll probably aim to get this going next week. It's not urgent for us though. We would like to put ccm.exe back on, but it's not urgent.
-
Mike Resseler
- Product Manager
- Posts: 8045
- Liked: 1263 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Server 2016 BSOD Bugcheck
OK. Keep us informed on the progress on this thread.
Thanks
Mike
Thanks
Mike
Who is online
Users browsing this forum: Bing [Bot] and 86 guests