Phil, we're still SQL 2012, but good info to know.
Thanks
Rob
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Phil Schwan
Sent: Monday, September 19, 2016 11:52 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: SCCM 2012 - 1606 Upgrade - Package
What version of SQL? IIRC, there are known performance issues with SQL
2014/2016 and SCCM 1606. You'll want to set the DB compatibility level to SQL
2012 using the following (where CM_XXX is your SCCM database):
ALTER DATABASE CM_XXX
SET COMPATIBILITY_LEVEL = 110;
GO
-Phil
From:
I am currently running SCCM CB 1602 and getting a CI documents download timed
out error for some of my deployments. The deployments start out fine and slowly
go downhill. The appenforce log looks fine and these are the really the only
errors I can find. I have re deployed the
We upgraded from SCCM 2012 - 1606 this weekend and now when you go into the
packages root node its taking 3-4 minutes to return the default 1000 packages
list. When we had 2012 it took maybe 10 seconds to return them. Anyone else
see this when they upgraded?
We were planning on doing 1606
They don’t have to be straight outside. You can reverse proxy them (client
traffic is just HTTPS traffic after all) and/or put these site systems in the
DMZ – many folks do both.
As of CB, you could also host the site system in Azure IaaS (or another cloud
provider’s IaaS although that won’t
I have never had an Internet facing MP/DP and I won't get one working here
because they just won't put anything straight outside. So what are my
options to get both MP/DP/App Catalog functions going just for PC's?
6 matches
Mail list logo