Introduction When you use the Configuration Manager tenant attach scenario, you can deploy endpoint security policies from Intune to devices you manage with Configuration Manager. Prerequisites Tenant attach CMG (only if you need it to apply policies to internet based devices) Configuration Manager current branch version 2006 or later, with
Introduction Microsoft just introduced an updated kit for IT pros to plan, test and validate deployment and management of desktops running Windows 10 Enterprise and Microsoft 365 Apps for enterprise. This was earlier known as “Windows insider lab for Enterprise” or “Olympia”. The lab will cover technologies: Microsoft Endpoint
Now that we have tenant attach available let’s have a closer look. Microsoft is now bringing Configuration Manager and Intune closer together in a the console Microsoft Endpoint Manager admin center (https://endpoint.microsoft.com/). Starting in Configuration Manager version 2002, we can upload Configuration Manager devices to the admin center and start
When running the prerequisite check before upgrading SCCM to the newest releases you might see the following warning (this is taken from 1812): Warning details: SQL Server Native Client version [Completed with warning]:Verifies that the version of Microsoft SQL Server Native Client installed on the site server meets the minimum
You might see that your WSUS server will crash after KB3159706 is installed. The event log will report event ID 507 Update Services failed its initialization and stopped. In the support article you will se that manual intervention is required, but since the update is pushed from Windows Update and
Microsoft has released a new update for the SCCM cmdlet Library 5.0.8373.1189 Release History: 6/6/2016 – Update Release, version 5.0.8373.1189. Contains bug fixes5/16/2016 – Update Release, version 5.0.8373.1182. Contains bug fixes and support for Configuration Manager (current branch – version 1602)1/25/2016 – Update Release, version 5.0.8328.1155. Contains bug fixes and
You might se this error when deploying Windows from a SCCM 1511 task Sequence: Task Sequence: xxx has failed with the error code (0x80070002) If we take a closer look at the smsts.log file, you will in this specific case find the message No credential information in environment. The reason
If you choose to do an in place upgrade of SQL 2012 to SQL 2014 on your SCCM server, you might see this error when trying to run a report: Failed to load expression host assembly. Details: Could not load file or assembly ‘SrsResources, Culture=neutral’ or one of its dependencies.
If you choose to do an in place upgrade of SQL 2012 to SQL 2014, you might see this error when trying to access the report server: The version of the report server database is either in a format that is not valid, or it cannot be read. The found
When using a custom Windows 10 1511 image captured with a SCCM 1511 client you might see that the step Setup Windows and Configuration manager will hang with the status Initializing the System Center Configuration manager client. I you take a closer look at smsts.log you will see the message
Cumulative Update 3 for System Center Configuration Manager 2012 R2 SP1 has been released https://support.microsoft.com/en-us/kb/3135680, and if not already on System Center Configuration Manager (Current Branch) lets take a closer look at how to determine the installation status of this cumulative update: Remember that you will only see the prompt
You might se this error when deploying Windows from a SCCM 2012 R2 task Sequence: Task Sequence: xxx has failed with the error code (0x80070002) The error is raised during Apply operating System: If we take a closer look at the smsts.log file, you will in this case find the
Microsoft has released an updated version of System Center 2012 R2 Configuration Manager Toolkit. The Microsoft System Center 2012 R2 Configuration Manager Toolkit contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager. System Center 2012 R2 Configuration Manager Toolkit The new version
Microsoft has released an update for WSUS on Windows 2012 and 2012 R2 server. This update is required to support deployment of the Windows 10 1511 upgrade by WSUS or the upcoming Configuration Manager (vNext). Update to enable WSUS support for Windows 10 feature upgrades Before installing this hotfix on
Cumulative Update 2 for System Center Configuration Manager 2012 R2 SP1 has been released https://support.microsoft.com/en-us/kb/3100144 So once again it’s time to take a closer look at how to determine the installation status of this cumulative update, this time for SP1 CU2. Remember that you will only see the prompt about
You might see this error when deploying Windows with SCCM 2012 R2 SP1, Task Sequence has failed with the error code (0x80004005) When you look at the Installation Progress you will notice the the task sequence is installing updates and last status is Detecting Updates: In smsts.log you will see
When testing, doing Build and Capture or simply low on local space, you might skip copying the WIM to a local folder before applying, just to save some time. By default SCCM will first copy the WIM to a local folder and the apply the WIM. The WIM file is
When installing SCCM 2012 R2 you are able to install it in evaluation mode: How do we identify if SCCM has been installed in evaluation mode? Very hard to overlook, when starting System Center 2012 R2 Configuration Manager console, it will be shown clearly in the top: OK but lets
I know this is old news, but I have seen the problem on various sites so now it’s time to write a short post about the issue. You may find that the SQL Server Reporting Services (SSRS) log database ReportServer_log.ldf file is using almost all diskspace. The reason for this
When we include Office 2013 in our Build & Capture Task Sequences and use KMS (Key Management Service) we must always remember to rearm Office. If Office is not rearmed then 25 days after deployment your users will get a notification dialog right after deployment of their new Windows. This
Today I will take a look on how we detect if our SCCM installation is running on a SQL 2012 evaluation version. The first thing we will have to do is to start SQL Server Management Studio: Connect to the server. Right click on the SQL server name and select
Cumulative Update 1 for System Center Configuration Manager 2012 R2 SP1 has been released https://support.microsoft.com/da-dk/kb/3074857 So once again it’s time to take a closer look at how to determine the installation status of this cumulative update, this time for SP1 CU1. After upgrading to System Center Configuration Manager 2012 R2
Ok we are booting into Windows PE but how do we determine / identify the version. First of all we need command support in the WIM file (F8), then in the command prompt we can use the command ver From Windows 10 PE (10): From Windows 8.1 PE (5.0): But
Update 05-08-2015 Unfortunately Cumulative Update 1 still have this problem: Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2 Original Post I have written before about the problem with software updates that require multiple restarts:
I saw a new problem today with a driver for a Fujitsu Esprimo E700. The driver in question had a size of 215 MB before importing to SCCM. First thing to notice is that Validate Driver Information takes very long time: And there are lots of INF files in this
Infrastructure architect with focus on Windows Client management & security.
Cloud & security specialist with focus on Microsoft backend products and cloud technologies.
Infrastructure architect with focus on design, implementation, migration and consolidation.
Infrastructure consultant with focus on cloud solutions in Office365 and Azure.
