This is an example of embedding a GitHub repository script in WordPress using the WP-GitHub plugin (with customized prism.js to add PowerShell, Batch, SQL and AutoIt language support)
And an example of a custom plugin (not yet published) with shortcode: Read More Redirect
continue reading on CatapultSystems.com
Chad January 5, 2017
Posted In: Uncategorized
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 50,000 clients*. As this environment wasn’t anywhere close to the limit so there was no need to pay the extra licensing cost of Enterprise edition (Standard edition comes with the ConfigMgr licenses).
These steps are largely based on the Jonathan Kehayias approach as documented by Brady Upton at MSSQLTips.
select ‘Master’ as [Database], * from [master].[sys].[dm_db_persisted_sku_features]
select ‘Model’ as [Database], * from Model.[sys].[dm_db_persisted_sku_features]
select ‘msdb’ as [Database], * from msdb.[sys].[dm_db_persisted_sku_features]
select ‘tempdb’ as [Database], * from tempdb.[sys].[dm_db_persisted_sku_features]
select ‘CM_P01’ as [Database], * from CM_P01.[sys].[dm_db_persisted_sku_features]
select ‘SUSDB’ as [Database], * from SUSDB.[sys].[dm_db_persisted_sku_features]
select ‘ReportServer’ as [Database], * from ReportServer.[sys].[dm_db_persisted_sku_features]
select ‘ReportServerTempDB’ as [Database], * from ReportServerTempDB.[sys].[dm_db_persisted_sku_features]
Using this method is simple and easy, but there is one additional thing to keep in mind… SQL Trace flags (thanks Allen for pointing this out). When installing SQL, trace flags are not enabled / added by default; this is taken care of by the ConfigMgr installation. Since we are not doing a ConfigMgr installation or a site reset, etc. these options need to be added manually.
Executing DBCC TRACEON (4199,-1) and DBCC TRACEON (8295,-1) in SQL Server Management Studio will enable these flags as seen by executing DBCC TRACESTATUS (-1). However, this only affects the current session and they need to be added as startup flags.
Chad April 20, 2016
Posted In: Uncategorized
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.exe – System Error
The program can’t start because mfc12u.dll is missing from your computer. Try reinstalling the program to fix this problem.
StatView is the utility that displays ConfigMgr status messages and is typically initiated from the console by navigating to
StatView.exe requires Microsoft Visual C++ and ConfigMgr 2012 SP2 now uses VC++ 2013 which is not installed as part of the Console.
To resolve the issue, install Microsoft Visual C++ 2013 Redistributable (x86) which can be found at \client\i386\vcredist_x86.exe">\client\i386\vcredist_x86.exe">\\PrimarySiteServer\SMS_<SiteCode>\client\i386\vcredist_x86.exe. Notice that the x86 version is required even if you are running Windows x64. This is because StatView is a 32-bit application.
This will install and register mfc12u.dll and other files which should resolve the issue.
You can verify the installation in Programs and Features (Add/Remove Programs) as shown below.
Microsoft Visual C++ Redistributable (x86)…
Problem. Solved.
Chad September 24, 2015
Posted In: Uncategorized
Tags: ConfigMgr; SCCM
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.
On the SQL Server Reporting Services server, an account (in this case a domain user "functional" or "service" account) needed the following:
This ConfigMgr environment has a complex configuration with 3 different SQL servers in play.
With Server1 (ConfigMgr) and Server2 (SQL DB) configured and most functionality working (software deployment, software update deployment, OS deployment, inventory, etc.) it was time to install Reporting Services point. We created a new ConfigMgr Site Server for Server3 using a domain user account. However, when attempting to install the Reporting Services point the following error was encountered:
We knew that SSRS was installed, configured, and working as there were two other applications already using the SRS instance in a production capacity.
We verified the domain user account could actually access the SSRS website from Server1 (the ConfigMgr server) and discovered
As the screen shot shows, UAC was actually disabled already.
Once the domain user account was given rights to the root folder, the Reporting Services point role could see the Reporting Services server instance the the role installed without issue.
After the role installed, ConfigMgr reset its own permissions to give the domain user account only "ConfigMgr Report Users, ConfigMgr report Administrators" roles.
Also, the logs for the Reporting Services point are on the SSRS server (Server3 in this case), and located at C:\SMS\logs
Chad August 27, 2015
Posted In: Uncategorized
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 to 8.1 Update, 8.1, 8, etc.
The installation appears to be working, then performs a rollback with the following error:
Image path is [\??\C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimmount.sys
Could not acquire privileges; GLE=0x514
Returning status 0x514
Additionally, after installation was successful, it was not possible to mount a WIM or create boot media in ConfigMgr.
Crating ConfigMgr or MDT Task Sequence Media fails with the error:
Error: 1313 A required privilege is not held by the client. Refer to CreateTsMedia.log file to find more details.
CreateTSMedia.log file…
using CreateMedia.exe /K: boot … fails
The PowerShell cmdlet New-CMTaskSequenceMedia -BootableMedia … fails
Mounting a WIM with DISM fails
DISM.exe /Mount-Image /ImageFile: …
Error: 1313 A required privilege is not held by the client.
In my case the root cause was that a default permission was removed for the local Administrators group by a domain policy.
By default, the User Right Assignment for "Back up files and directories" and "Restore files and directories" is held by the "Administrators, Backup Operators". But in this case the "Administrators" group had been removed and replaced by the "Domain Admins".
Since my account isn’t and shouldn’t be a domain admin, I simply added it to the local "Backup Operators" group, logged off, logged back on, and presto! Success.
If the User Right Assignment isn’t you issue, another solution, or rather workaround, is to run the installation as the SYSTEM account.
Multiple other solutions were attempted before resorting to the SYSTEM account for installation including
None of these made any difference.
Several forum posts were found with a resolution pointing to a blog that has since been taken down. That solution required removing the computer from the domain. This solution was not attempted.
There are a few ways to gain SYSTEM account access; however, I took the interactive route and used PSEXEC from Sysinternals.
From an elevated Command Prompt (Run as Administrator), run ‘PSEXEC.exe -s -d -i cmd.exe‘
A new Command Prompt will be generated. run ‘whoami‘ to ensure you are running as SYSTEM, then run ‘adksetup.exe‘
Thanks to Adam for working through the issue with me.
There are a few instances of the same error documented in a few blogs and forum posts. The options basically include ensuring you are running as an administrator (and with the administrator token), running as SYSTEM (as described in my workaround), or dis-joining the computer from the domain and running as admin.
Chad August 21, 2015
Posted In: Uncategorized
Tags: ConfigMgr, OS Deployment, OSD, Windows ADK
