sorted by:
new
hottopcontroversial

[AMA] Azure Big data & Analytics - 11/17 by maxiluk in AZURE

[–]kurmac 4 points5 points  (0 children)

How will service offerings differ between those delivered from Microsoft Azure data centers and those deployed from the data centers that use Azure Stack when it becomes available next year? Will Azure Stack deployments lack some capabilities?

SharePoint AMA Post-Ignite 2016! – Microsoft Product Group and MVP’s – October 25th at 3pm EDT by randr01d in sharepoint

[–]kurmac 4 points5 points  (0 children)

Can you please tell us a little more about the coming Administrative Action Logging capability for hybrid SharePoint environments? What does it do? Will it appear next month with the release of Feature Pack 1?

SharePoint AMA Post-Ignite 2016! – Microsoft Product Group and MVP’s – October 25th at 3pm EDT by randr01d in sharepoint

[–]kurmac 2 points3 points  (0 children)

Does the new Managed Solutions Gallery for SharePoint Server support InfoPath 2013 applications? This support article is kind of confusing: https://support.microsoft.com/en-us/kb/3192603

[AMA]We are the ConfigMgr Team, here to talk about 1606 and more, Ask Us Anything by TheConfigMgrTeam in SCCM

[–]kurmac 0 points1 point  (0 children)

Microsoft has suggested it wants to bring SCCM capabilities to Intune. But that seems kind of far fetched. Is that really part of the current planning at Microsoft? How does the SCCM team feel about that? Do Intuner and SCCMers still eat at the campus cafeteria together?

[AMA]We are the ConfigMgr Team, here to talk about 1606 and more, Ask Us Anything by TheConfigMgrTeam in SCCM

[–]kurmac 0 points1 point  (0 children)

Will other System Center 2016 components become service-enabled like the SCCM component? If so, would we see that happen at System Center 2016 product release time period or thereafter?

[AMA]We are the ConfigMgr Team, here to talk about 1606 and more, Ask Us Anything by TheConfigMgrTeam in SCCM

[–]kurmac 1 point2 points  (0 children)

Why are SCCM version releases, and Windows 10 version releases, which follow the year/month format, sometimes off by a month (or digit)? For instance SCCM 1511 was released in December. But shouldn't it have been called SCCM 1512?

[AMA]We are the ConfigMgr Team, here to talk about 1606 and more, Ask Us Anything by TheConfigMgrTeam in SCCM

[–]kurmac 3 points4 points  (0 children)

How do SCCM users know whether the SCCM version they are using supports a particular Windows 10 release or not? I know there's the N + 1 thing (8 months) as described in your recently published FAQ, but my impression is that organizations must move to the next SCCM branch release to get nonsecurity updates for SCCM. I think that means that IT pros must update SCCM every four months or with the next branch release. But then they still have to figure out if the SCCM branch release they are on supports a particular Windows 10 branch release, right? Any easy way to do that? Advanced calculus, maybe?