At a recent client engagement we discovered that Microsoft SQL Server Enterprise edition was installed on the ConfigMgr Primary Site Server. Technically this is not a problem, but it is only needed if you expect to have more than 150,000
Ok, so that’s a bit misleading. The actual issue is that ConfigMgr’s detection routine for some virtual machines is broken. This apparently started around May 2014 but I noticed it for the first time on a new ConfigMgr v1511 installation.
When the ConfigMgr Admin Console version 2012 SP2 (or 2012 R2 SP1) is installed and the ConfigMgr client is not updated on the same computer you could see an error like the one below. StatView is the utility that displays
In a new ConfigMgr 2012 R2 SP1 environment the Reporting Services point was proving a bit challenging to install. After setting all of the required permission it was finally happy. Required Permissions On the SQL Server Reporting Services server, an
When preparing a new Windows Server 2012 R2 system for a new ConfigMgr 2012 R2 site, I ran into an error installing the Windows ADK. In this case it is version 10; however, I believe the same scenario would apply
If you’ve ever wanted to report on ConfigMgr client IPAddress you know it can be a challenge. ConfigMgr stores IP Address information in the v_GS_NETWORK_ADAPTER_CONFIGURAITON SQL view (and other places) but it is actually an array of both IPv4 and
I’ve been installing a few lab and production ConfigMgr environments recently and found a little quirk with the versioning to go along with the service pack madness / confusion of the 2012 SP2 / 2012 R2 SP1 release. Here’s the
When attempting to install the ConfigMgr / SCCM client on a few remote computers, the installation failed (more like stalled out) when ccmsetup.exe tried to download the full client binary files. The download couldn’t complete and the following error was