Quantcast
Channel: SSRS - System Center Dudes
Viewing all 31 articles
Browse latest View live

SSRS : SMS_SRS_Reporting_Point failing with 7405 error message

$
0
0

I was configuring the reporting services on a dedicated server when I received a SMS_SRS_Reporting_Point failing with 7405 on the component status failure message.

SMS_SRS_Reporting_Point failing with 7405

The error logs from reporting services is :

ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item ‘/ConfigMgr_CAS’ cannot be found.;

Cause: The datasource was not in the good directory.

Resolution: Move the datasource on the SSRS website to the same place of the component configuration in SCCM 2012.

SMS_SRS_Reporting_Point failing with 7405

 

The post SSRS : SMS_SRS_Reporting_Point failing with 7405 error message appeared first on System Center Dudes.


SCCM Query to identify who imported OSD Computers

$
0
0

This query might be helpful to know who imported a specific computer.

You can view this information in the Status Message Queries and search for MessageID #30213. But this query will target only the information you need.

You can use this query to create a report or directly in SQL MS.

select
CASE smsgs.Severity
WHEN -1073741824 THEN ‘Error’
WHEN 1073741824 THEN ‘Informational’
WHEN -2147483648 THEN ‘Warning’
ELSE ‘Unknown’
END As ‘SeverityName’,
smsgs.MessageID, smsgs.Time, smwis.InsString1 as Username, smwis.InsString4 as ComputerName, smwis.InsString5 as MAC
from v_StatusMessage smsgs
join v_StatMsgWithInsStrings smwis on smsgs.RecordID = smwis.RecordID
join v_StatMsgModuleNames modNames on smsgs.ModuleName = modNames.ModuleName
where smsgs.MessageID = 30213
Order by smsgs.Time DESC

Results

sccm query computer name

 

SCCM Query Computer Name for OSD

The post SCCM Query to identify who imported OSD Computers appeared first on System Center Dudes.

Report subscription in SSRS does not list Email in drop down menu

$
0
0

What can you do when your report subscription in SSRS does not list email in drop down menu?

Symptoms

When you first try to create an email subscription in SCCM 2012, you only have the Windows Share choice in the drop down menu. Email is missing from the list.

report subscription in ssrs

Cause

The principal cause of this issue is that your SSRS is not configured properly to send emails.

report subscription in ssrs

Resolution

  • Log to your SSRS server
  • Open Reporting Service Configuration Manager
  • Click on the Email Settings tab
  • Enter the settings of your sender address and SMTP server
  • Click Apply

report subscription in ssrs report subscription in ssrs

Verification

Once completed, go back in SCCM and create a new subscription. The “Email” option will now show in the drop down menu.

report subscription in ssrs

report subscription ssrs

The post Report subscription in SSRS does not list Email in drop down menu appeared first on System Center Dudes.

Reporting Point Error after R2 Upgrade

$
0
0

This post explain how to fix Reporting Point Error after R2 Upgrade.

Problem :

After upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2.

You get the following error when running reports :

An error has occurred during report processing. (rsProcessingAborted)
Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
Conversion failed when converting the nvarchar value ‘S-1-5-21-1010946700-728571707-39459515-134623’ to data type int.

Removing and adding the “Reporting Service Role” did not fix the issue.

SRSRP.log has Invalid Class errors :

Invalid class SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)
Could not retrieve the reporting service name for instance ‘RPSERVER’ SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)
Invalid class SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)
Could not stop the reporting service ” SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)
Next security configuration at [07/7/2014 1:52:12 PM] SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)

Resolution:
The problem is due to the required SQL management provider not getting properly registered in WMI. As a result, The reporting point upgrade is not able to complete successfully and reports fails to be redeployed to the RSP.

To re-register the SQL Management provider class you need to compile the MOF file that is available in SQL.

  • Log to your SSRS Server
  • Open a command prompt and launch this command : (Modify the path to fit your environment)
  • mofcomp “C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”

Once completed, review the SRSRP.log. You will see that the SSRS Service gets properly detected, stopped and started.

After a few minutes, the upgrade process will completes. Run a report and confirm that the error is gone.

The post Reporting Point Error after R2 Upgrade appeared first on System Center Dudes.

Install SCCM 2012 Reporting Services Point

$
0
0

Download and own part 1 to 18 of the SCCM 2012 R2 Installation Guide in a single PDF file. Use our products page or use the download button below. This blog post won’t be updated, only the document will be.

 

This post describe how to install a SCCM 2012 reporting services point.

It describe how to install the reporting services point on a primary site server.

This role can be installed on a remote machine, the process is the same but the logs location is different.

Requirements

Before you can install the reporting services point role you must configure SQL correctly.

We’ll be using SQL 2012 on this post. We are assuming that SQL is already installed and that your SCCM site is up and healthy.

During the initial SQL installation, you must select Reporting Services.

If you have installed SQL Server, but have not installed Reporting Services follow the following steps. If Reporting Services is already installed, skip to the “Configure Reporting Services” section.

  • Launch the SQL Server 2012 installation from the media.
  • Click the Installation link on the left to view the Installation options.
  • Click the top link, New SQL Server stand-alone installation or add features to an existing installation.

sccm 2012 reporting services

  • Follow the SQL Server Setup wizard until you get to the Installation Type screen.
  • Select Add features to an existing instance of SQL Server 2012.
  • Click Next to move to the Feature Selection page.

sccm 2012 reporting services

  • Select Reporting Services – Native

sccm 2012 reporting services

  • At the Reporting Services Configuration page
  • Select Install Only

sccm 2012 reporting services

Continue through the wizard and reboot the computer at the end of the installation if instructed to do so.

Configure Reporting Services

Before configuring the reporting point, some configuration needs to be made on the SQL side. The virtual instance needs to be created for SCCM to connect and store its reports.

If you installed Reporting Services during the installation of the SQL Server instance, SSRS will be configured automatically for you. If you install SSRS later, then you will have to go back and configure it as a subsequent step.

To configure, Open Reporting Services Configuration Manager

  • Click Start > All Programs > Microsoft SQL Server 2012 > Configuration Tools > Reporting Services Configuration Manager

sccm 2012 reporting services

  • Click Connect to connect to the SQL instance

sccm 2012 reporting services

  • On the left-hand side of the Reporting Services Configuration Manager, click Database.
  • Click the Change Database button

sccm 2012 reporting services

  • Select Create a new report server database and click Next

sccm 2012 reporting services

This wizard creates two databases: ReportServer, used to store report definitions and security, and ReportServerTempDB which is used as scratch space when preparing reports.

  • Click the Web Service URL tab
  • Click Apply

sccm 2012 reporting services

This step sets up the SSRS web service. The web service is the program that runs in the background that communicates between the web page, which you will set up next, and the databases.

  • Select the Report Manager URL
  • Accept the default settings and click Apply.

sccm 2012 reporting services

If the Apply button was already grayed out, this means the SSRS was already configured. This step sets up the Report Manager web site where you will publish reports

Exit Reporting Service Configuration Manager.

Add role in SCCM

  • Open the SCCM console
  • Navigate to Administration/Site/Configuration/Servers and site System Roles
  • Right click on your Site Server and click Add system Roles

sccm 2012 reporting services

  • On the General tab, click Next

sccm 2012 reporting services

  • On the Proxy tab, Click Next

sccm 2012 reporting services

  • On the Site System Role, select Reporting Services Point, Click Next

sccm 2012 reporting services

  • On Reporting Services setting tab
  • Click Verify
  • At the bottom, Add an account to use for the reporting point. This account needs to have access to the SCCM DB
  • Click Next

sccm 2012 reporting services

  • Wait for the process to complete and close the wizard

Recovery Model
Using the simple recovery model improves performance and saves your server hard drive and possibly large transaction log file.

To change the Recovery Model of the ReportingDB to Simple

  • Open SQL Management Studio
  • Right click on the ReportServer database and select Properties
  • Go to the Options page
  • Under Recovery model select Simple
  • Click OK

3222 (23)

Verify

Log
Check for the following logs for reporting point installation status. Both logs are under the SCCM logs file locations.

  • Srspsetup.log
  • Srsrpmsi.log

If your reporting point is installed on a remote server look for the logs in :

Drive:\SMS\Logs\

Console

Open Monitor/Reporting/Reports node. Verify that your reports are listed

Web Browser

Open Internet Explorer, navigate to http://yourservername/Reports

If everything went well, you’ll have a folder Config_SiteCode containing your reports

sccm 2012 reporting services

SQL

If you check your SQL instance, you’ll see the 2 new database which were created by the installation.

  • Open SQL Management Studio
  • Locate ReportServer and ReportServerTempDB

sccm 2012 reporting services

Happy reporting ! :)

sccm 2012 reporting services

The post Install SCCM 2012 Reporting Services Point appeared first on System Center Dudes.

Upload RDL file to Report Server

$
0
0

There are many way to upload RDL file to report server (SSRS). This post will show how to do it with the web portal.

A RDL file is an XML application and a standard proposed by Microsoft for defining reports.

Requirements

Upload RDL file to Report Server

Upload the file

We suggest to upload your file into a Test folder before releasing the report in production. The report can be tested in pre-prod and be approved by your team.

Browse to the respective folder where you want to upload your file and click Upload File.

Upload RDL file to Report Server

Click Browse, find your file location and select the file. If you want to override an existing report, check the box Overwrite item if it exists. Click OK.

Upload RDL file to Report Server

If the upload is successful, the report will appear else you will have an error message explaining the failure. Any unhealthy RDL file will fail at this process.

Verify

There are few thing to check if you want to deploy the report and make it work perfectly on day 1.

Put the mouse over the report name, a small option menu will appear. Click on Manage.

Upload RDL file to Report Server

In the Properties tab, make sure the description does not contain typo and the content is clear enough for users. Click Apply after each changes else it won’t save last modification.

Upload RDL file to Report Server

In the Data Sources tab, select your data sources else the report will not process. You can use shared or custom data source. Click Apply.

 

To enable another data source, click on Browse and select an existing data source in the appropriate folder.

In the Security tab, add security groups or users who want to run your report. The security settings will be enforced by new parent folder security settings. Don’t be surprised if the access change after moving the report into production.

Upload RDL file to Report Server

Summary

Adding a report with the web portal isn’t the fastest way but it requires the least prerequisites. It’s pretty straight forward. Make sure your RDL file is not corrupt and the data source is well configured. Verify security settings before sending the link to users.

Good reporting!

 

Upload RDL file to Report Server

The post Upload RDL file to Report Server appeared first on System Center Dudes.

Report Builder error – The certificate chain was issued by an authority that is not trusted

$
0
0

When editing a SCCM 2012 report in Report Builder you receive the following error : A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.)

Report Builder error

Cause

This error occurs because you don’t have the required SCCM SQL certificate on the computer running Report Builder. Follow the following steps in order to resolve the issue.

Export the certificate from your SQL server

  • On the SQL Server
  • Click the Start menu, click Run, and then type mmc. Click Enter. This starts the Microsoft Management Console (MMC)
  • In the console, click the File menu and then click Add/Remove Snap-in

Report Builder error

  • On the Snap-in list, select Certificates and then click Add

Report Builder error

  • In the Certificates Snap-in window, select Computer account, and then click Next

Report Builder error

  • In the Select Computer window, select Local computer, and then click Finish. This adds the Certificates Snap-in to the list. Close the window.

Report Builder error

  • Browse to Console Root / Certificate (Local Computer) / Personal / Certificates
  • Right-click your ConfigMgr SQL certificate

Report Builder error

  • Select All Tasks and Export

Report Builder error

  • Select default choices in the Certificate Export Wizard (Next,Next,Next)
  • Export the certificate file (.CER) to the machine where you run Report Builder

Import the certificate on your machine

  • On the machine running Report Builder
  • Click the Start menu, click Run, and then type mmc. Click Enter. This starts the Microsoft Management Console (MMC)
  • In the console, click the File menu and then click Add/Remove Snap-in
  • In the Add/Remove Snap-in window, click the Add button
  • On the Snap-in list, select Certificates and then click Add
  • In the Certificates Snap-in window, select Computer account, and then click Next
  • In the Select Computer window, select Local computer, and then click Finish. This adds the Certificates Snap-in to the list. Close the window
  • Browse to Console Root / Certificate (Local Computer) / Trusted Root Certification Authorities / Certificates
  • Right-click Certificate and select All Tasks / Import

Report Builder error

  • In the Certificate Import Wizard click browse and select the exported certificate

Report Builder error

  • Ensure that the certificate is placed in the Trusted Root Certification Authorities, click Next

Report Builder error

  • Click Finish to complete the wizard

That’s it, reopen Report Builder and the error will be gone.

The post Report Builder error – The certificate chain was issued by an authority that is not trusted appeared first on System Center Dudes.

Create custom reports with Labels of Asset Intelligence

$
0
0

Usually we use information from Add Remove Programs when it’s time to make software reports. For technical reasons, it’s not always easy to have adequate results. The use of custom labels in Asset Intelligence helps standardize and gather software information.

In this post, we will explain how to use the data from custom labels in asset intelligence to create a custom reports. Before starting the reports, make sure the custom labels are set in your environment from how to maximize the use of custom views in Asset Intelligence.

Configuration Manager 2012 came with a couple of Asset Intelligence reports but nothing special based on the custom labels. The only one useful is Software 12A | Software titles with a specific custom label defined.

After this post, you will be able to do a report like this one below.

sccm 2012 custom reports

Views

First, here’s the list of SQL views used by SCCM for custom labels in Asset Intelligence :

sccm 2012 custom reports

If you want to see what they are made and also what are the relationships between them, right click on each view in SQL Server Management Studio and select top 1000 rows. You can access the database from the central site or primary.

SQL Server Management Studio is an essential tool to develop queries for reports in SCCM. Make sure your account have enough access to read the database.

For our report, we will use v_LU_SoftwareList_Editable because it contains everything we need.

Query

The report will show the total count by custom labels. Open SQL Management Studio and execute the below SQL query in your environment. You should see something like the below screenshot.

SELECT DISTINCT CategoryName AS 'Publisher', FamilyName AS 'Family', Tag1Name AS 'Type', Tag2Name AS 'Version', SUM(Count) AS Total
FROM v_LU_SoftwareList_Editable SL
WHERE Tag3ID IS NOT NULL
GROUP BY CategoryName, FamilyName, Tag1Name, Tag2Name, Tag3Name
ORDER BY Total DESC

sccm 2012 custom reports

We are now ready to create the custom report!

Custom Reports

To create a custom report, please follow those steps :

  • Open the SCCM console and go to Monitoring / Overview / Reporting
  • Right click on Reports and select Create Reports

sccm 2012 custom reports

  • On the Create Report Wizard, select type SQL-based Report
  • Enter the name of the report Asset Intelligence – Inventoried Software with Custom Labels
  • Fill the report description with This report shows inventoried software where a custom label is configured
  • Click on Browse and select the folder of the report which is the report location. In this case, we use Asset Intelligence folder
  • Click Next

sccm 2012 custom reports

  • Confirm details summary and click Next

sccm 2012 custom reports

  • If the Create Report Wizard succeed, you should have green check everywhere.
  • By clicking Close, Report Builder will automatically run

sccm 2012 custom reports

  • Click Run

sccm 2012 custom reports

Here we are, ready to create the report.

Report Builder

There’s a lot of features that you can use in Report Builder to develop nice reports. This post will explain only the minimum requirement of creating a report.

We will not use Built-in Fields, Parameters and Images in our case but they are very useful when you want to standardize your reports.

We will only cover Data Sources and Datasets since they are minimum requirement of creating report. A data source is the database configuration and dataset is the query used for the report.

sccm 2012 custom reports

Data Sources

  • Right click on Data Sources in Report Data on left panel and select Add Data Source
  • From General tab, enter the name of your data source
  • Select Use a connection embedded in my report and select Microsoft SQL Server from connection type
  • In the connection string, enter this string syntax

Data Source=ServerNameWithCMDatabase;Initial Catalog=CMDatabase

** Make sure to enter your information instead of ServerNameWithCMDatabase and CMDatabase **

sccm 2012 custom reports

  • Click Test Connection to test your configuration and Ok when you’re done

** Make sure that your account has access to the database. If not, set up another account via Credentials on the left panel. **

Datasets

  • Right click Datasets in the left panel and select Add Dataset

sccm 2012 custom reports

  • From Query tab, enter the dataset name in the Name textbox
  • Select Use a dataset embedded in my report and select the data source you created in previous step
  • In the Query field, copy paste the SQL query from the Query section at the beginning of the post
  • Click Ok

sccm 2012 custom reports

You are finally ready for the most fun part, creating the visual side of the report.

Design

  • Rename the title to Asset Intelligence – Inventoried Software with Custom Labels
  • Right click anywhere in the report, select Insert / Table
  • An empty table will appear

sccm 2012 custom reports

The idea is to take the dataset fields to the table. There’s 2 ways to import fields :

  • Expand Datasets and drag drop each field into the table

sccm 2012 custom reports

  • Click directly the Data textbox in the table, the complete list will appear and select respective field

This is what your table will look like.

sccm 2012 custom reports

We won’t cover it but by modifying text box properties, you will be able to change font color and modify style.

  • To modify properties, right click the text box and select Text Box Properties

sccm 2012 custom reports

Testing

When the design if finished, test the result in Report Builder before thinking to import the report into production.

  • Click Run button on the top left

sccm 2012 custom reports

sccm 2012 custom reports

Deploy

Happy with the results? Let’s deliver the report.

  • Click Save button on the top left.

Verification

By saving the report in Report Builder, your report will be updated in SSRS and your console. For sure, you need to install SCCM 2012 reporting services point to see it in SSRS.

SSRS

sccm 2012 custom reports

Console

  • From the console, click on Monitoring / Overview / Reporting / Reports and discover the report in the right location

sccm 2012 custom reports

This formula can be used for any situation. Only your imagination is the limit.

You are now able to create report for installed software by standardizing the custom labels. Be sure to keep an eye on the custom labels and inventoried software in Asset Intelligence. Any new versions detected by the system won’t be added automatically.

Asset Intelligence Blog Series

sccm 2012 custom reports

The post Create custom reports with Labels of Asset Intelligence appeared first on System Center Dudes.


How to install Microsoft Intune Client for MAC OSX

$
0
0

Did you ever wanted to install the Microsoft Intune client on MAC OSX? Microsoft Intune standalone supports Apple operating systems since November 2015. SCCM 1602 is required to support the Microsoft Intune client with the SCCM connector (hybrid environment). The Intune client is a lightweight version of the SCCM client. You can deploy some policies, SCEP certificates, VPN and WiFi profiles. There is also a hardware inventory scan on the devices.

In a previous post, we explained how to set up a compliance policy for MAC OSX, now that our client is ready to receive the compliance policy, we will install the Microsoft Intune client on Mac OS X devices.

Install the Intune Client Mac

There is still no way to automatically install the client.

  • Connect on the MAC OSX devices that you want to install Microsoft Intune client
  • Open Safari and go to manage.microsoft.com
  • Click on This device is either not enrolled or the Company Portal can’t identify it

intune client mac 1

  • Click on Enroll

intune client mac 2

  • This message is a warning message of the management profile requirement, click on Install

intune client mac 3

  • Now, the installation process will need to install the Management Profile, click on Install

intune client mac 4

  • You will be prompt to enter full admin credential to installation a new management profile into your MAC OSX device
  • Enter your password and click OK

intune client mac 5

  • The MDM and SCEP Enrollment will be requested, click Continue

intune client mac 6

  • Another confirmation to install the Management Profile, Click Install

intune client mac 7

  • Management Profile installation is completed when you reach this window

intune client mac 8

  • Don’t be surprised, if you see this little warning. Microsoft Intune is in the process of approving the device installation. Wait few seconds and it will disappear

intune client mac 9

  • Choose your active device and click on Select

intune client mac 10

The Intune client installation is now complete. From now on, your device will appear on the manage.microsoft.com portal and SCCM.

Verification

There’s a few ways to determine if the Microsoft Intune client is correctly installed.

  • From the SCCM console, navigate to Assets and Compliance Devices 
  • In the Devices node, search the device you recently installed
  • If your Mac does not appear, it’s a sign that the installation failed

intune client mac

Once the client is installed, you should be able to check the hardware inventory of the device. Note that the Microsoft Intune client Mac is not considered as a normal SCCM client, it’s considered like a mobile device.

  • Right-click on the device name, select Start and Resource Explorer

intune client mac

  • All information of the device appears at this place for only one device.

intune client mac

Finally, using an inventory report such as our Intune Devices, it can help identify all your company assets. All MAC OSX devices with the Intune client will be listed in this report.

HowtoinstallMACOSIntuneClient 17

The post How to install Microsoft Intune Client for MAC OSX appeared first on System Center Dudes.

List of SCCM Client Installation Error Codes

$
0
0

As an SCCM administrator, it’s important to learn the concept of troubleshooting a Configuration Manager client installation. By targeting the SCCM client installation error codes, you will have a better idea of what is happening during client installation. The error codes is not an exact science, they can defer depending on the situation. For a better understanding about error codes, read this great post from Jason Sandys.

These codes appears in ccmsetup logs, located on in C:\windows\ccmsetup\logs. During the installation process, monitor the ccmsetup.log using cmtrace.exe and locate each error codes.

SCCM Client Installation Error Codes

There are other logs, on which the SCCM client installation relates. If you don’t find enough information in the ccmsetup.log, scan all related log files in c:\windows\ccm\logsUse the command line net helpmsg, for more information about your return error code.

SCCM Console

You can also add the Last Installation Error in the SCCM console:

  • Open the SCCM console and navigate to Assets and ComplianceDevices
  • In the devices view, right click on the header and select Last Installation Error

SCCM Client Installation Error Codes

There are chances that the last error code return an empty value for a device.

SCCM Client Installation Error Codes

This post from Technet Forums (Thanks to Charlie Hawkins), has inspired us to prepare a list of all error codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.

Feel free to send us any new error codes, this list will be updated based on your comments.
IDSourceDescriptionSolution
Technet Forums Sources
2The system cannot find the file specified
This error occur when the WMI service is corrupt
Technet Resolution
WMI Repair
5Access deniedMake sure that the installation account is member of the Administrator Group
52You were not connected because a duplicate name exists on the networkCheck for duplicate name in DNS (IP)
53Unable to locate
Cannot connect to admin$
Computer Browser not started
Add File & Print sharing to Exceptions in Firewall
Turn file and print on
KB920852
58The specified server cannot perform the requested operation
64WindowsThe specified network name is no longer available
67Network name cannot be foundCheck if client has a DNS entry or invalid DNS
86Incorrect network configuration
112Not enough disk spaceFree some space on the computer
1003Cannot complete this function
1053The service did not respond to the start or control request in a timely fashion
1068The dependency service or group failed to start
1130WindowsNot enough server storage is available to process this command
1203The network path was either typed incorrectly, does not exist, or the network provider is not currently available
Please try retyping the path or contact your network administrator
1208WindowsAn extended error has occurred
1305The revision level is unknown
1396Login FailureThe target account name is incorrectCheck for duplicate name in DNS (IP)
NBTSTAT -a reverse lookup
1450WindowsInsufficient system resources exist to complete the requested service
1603CCMExec could not be stoppedReboot and install the client as administrator
1618MSIThis error is cause by a multiple client.msi installation at the same timeStop all related MSI install process
1789The trust relationship between this workstation and the primary domain failed
KB2771040
12002Failed to send HTTP RequestCheck firewall ports
8007045DMSISetup was unable to create the WMI namespace CCMDelete all SCCM folders and rebuilt wmi Repository
80041001MSISetup was unable to create the WMI namespace CCM
Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS
WMI Repair
8004103BWMIUnable to create the WMI NamespaceRebuild WMI Repository
80070070Setup failed due to unexpected circumstancesRebuild WMI Repository
2147023174The RPC server is unavailableCheck out firewall or AntiVirus
2147024891Access is denied
2147749889WMIGeneric failure
2147749890WMINot foundWMI Repair
2147749904WMIInvalid class
2147749908WMIInitialization failure
2147942405Access is DeniedMissing Firewall rules
MacAfee-HIPS
2147944122The RPC server is unavailableKB899965
Dcom is miss-configured for security
2148007941Server Execution Failed

Don’t forget to put emphasis on the prerequisites of the SCCM client, this will increase your success percentage during client installation. You can also check the list of client commands list, as an additional help for troubleshooting your SCCM clients.

Reporting

Knowing the client installation status from reports, reduces the amount of devices without SCCM client installed in your IT infrastructure. It’s also increase your effectiveness, when it’s time to tackle all unhealthy clients.

One of our System Health report is made especially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment state. This report will help you achieve the *near* 100% client installation, that project managers loves to see.

SCCM Client Installation Error Codes

 

The post List of SCCM Client Installation Error Codes appeared first on System Center Dudes.

SCCM Office 365 Inventory Report

$
0
0

This post describe how to inventory Office 365 using SCCM 1606. We will also provide a free report at the end of the post that you could use on your Reporting Point to easily display Office 365 inventory data.

SCCM 1606 introduces new hardware inventory classes for Office 365 configurations. You no longer need to edit your MOF files to gather Office 365 inventory. If you are using SCCM 1602 or below, follow Jason Sandys post which describe Office 365 inventory process using a MOF customization.

If your goal is to deploy Office 365 updates, refer to our post on how to manage Office 365 updates using SCCM.

SCCM Office 365 inventory report post summary :

  • Office 365 Inventory Data explained
  • How to enable Office 365 Inventory classes
  • Verify Office 365 Inventory data on a client
  • How to upload and use our free Office 365 report

Office 365 Inventory Data

Office 365 is using new update channels and update mechanism. Tracking versions and update channels is an important task. The good news is that it’s easy to do using SCCM 1606 but the data needs to be interpreted as it’s not straight forward (mostly for update channel).

Here’s the complete definition of the update channel and their meaning :

Update Channels

ChannelValues
Insider Preview / First Release for Current Channelhttp://officecdn.microsoft.com/pr/64256afe-f5d9-4f86-8936-8840a6a4f5be
Current Channelhttp://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60
First Release for Deferred Channelhttp://officecdn.microsoft.com/pr/b8f9b850-328d-4355-9145-c59439a0c4cf
Deferred Channelhttp://officecdn.microsoft.com/pr/7ffbc6bf-bc32-4f92-8982-f9dd17fd3114

Other data

Here’s the definition of other information gathered by the new hardware class. We haven’t found definition for all fields, unfortunately Technet documentation is not completed. If you have any information on your environment, feel free to share it using the comment section.

FieldValue Example
InstallationPathC:\Program Files (x86)\Microsoft Office
ClientInstallationFolderC:\Program Files\Common Files\Microsoft Shared\ClickToRun
VersionToReport (Version)16.0.6741.2056
ClientCulture (Language)en-us / fr-fr
CDNBaseUrl (Channel)See Channels table
UpdatesEnabledTrue / False
Platform (Architecture)x86 / x64
LastScenarioUpdate
LastScenarioResultsSuccess / Failure
CCMManagedUpdateNotify Object
AutoUpgradeTrue / False
GPOChannelSee Channels table
OfficeMgmtCOM?
SharedComputerLicensing?
UpdateURL?

How to enable Office 365 Inventory

After upgrading to SCCM 1606, your Default Client Settings should already gather the new inventory class. Here’s the step to check if it’s enabled :

  • Open the SCCM Console
  • Go to Administration / Client Settings
  • Right-Click your Default Client Setting, select Properties

SCCM Office 365 inventory report

  • Click on Hardware Inventory
  • Click on Set Classes

SCCM Office 365 inventory report

  • Ensure that Office365ProPlusConfiguration is enabled, click OK (remove unneeded field if necessary)

SCCM Office 365 inventory report

Verification

Now that our classes are enabled, trigger a Machine Policy Retrieval & Evaluation Cycle (to have the latest Client Settings) followed by an Hardware inventory Cycle on a computer that has Office installed. Once the inventory is completed, check the inventory using Resource Explorer :

  • In the SCCM Console
  • Right-Click your device, select Start / Resource Explorer
  • Confirm that you have OFFICE365PROPLUSCONFIGURATIONS listed

SCCM Office 365 inventory report

SCCM Office 365 inventory report

Now that your inventory is gathering Office 365 data, we created a report to display the results. This report is free to use.

SCCM Office 365 inventory report

To use the report :

Is this information useful ? Share your comments using the comment section.

 

The post SCCM Office 365 Inventory Report appeared first on System Center Dudes.

5 Ways to view Hardware Inventory Information of a Device with SCCM

$
0
0

 

One of the SCCM features is to inventory hardware information from devices that are managed by the SCCM client. It’s not very difficult to enable and configure the hardware inventory client settings in SCCM. Once the devices received next machine policy and hardware inventory scan, data will start to populate in your SCCM database.

The information gathered from the devices can be very useful from a system health, inventory or operation perspective. You can use this information to create collections, queries as well as reports.

However, one thing not too obvious with the hardware inventory information, is to see all the data of a device in a one pager. There’s several ways to do it, some more difficult then others, but we will show you how.

Resource Explorer

The first one is the Resource Explorer tool. It’s a tool accessible directly within the console and which don’t require any additional third party tool to be installed. It’s built-in in the console, it’s pretty easy to use and very useful during troubleshooting.

  • To open the Resource Explorer, open the SCCM console and navigate to Assets and Compliance / Devices 
  • Right click on any device and select Start then Resource Explorer

SCCM Device Hardware inventory

The Resource Explorer tool will open and by expanding each sections, you will be able to find any hardware inventory information related to a device.

SCCM Device Hardware inventory

 

The Resource Explorer works with all SCCM client platforms.

SQL Query

Are you a SQL fan? Do you understand a little bit of SQL syntax? If not, I would say don’t loose your time and go to the next section. However, if you still want to learn and you are DIY person, open the SQL Management Studio and query all v_GS_ xxxxx views in your CM database. They are the classes inventoried during the hardware inventory.

SCCM Device Hardware inventory

By joining the v_R_System or v_GS_Computer_System views to your SQL queries, you will have all the information you need to make nice queries. Take your SQL queries and transform them in great SSRS reports.

Here is a SQL query example that you can do. This is a very interesting post as well!

 

This is the option with the most difficult learning curve but a nice long term investment.

WQL Query

The WMI Query Language (WQL) is a subset of the American National Standards Institute Structured Query Language (ANSI SQL) with minor semantic changes. You can use queries to retrieve information about inventory data, status messages and many more. What is nice with WQL queries is that you can use those same queries for collection. For those that understand SQL syntax, you won’t be lost. It looks a lot like SQL queries.

  • To create WQL query, open the SCCM console and navigate to Monitoring / Queries

  • Right click on Queries and select Create Query

  • This windows will open and you will be able to configure your query. Follow this post to help you create your WQL query

There’s few websites that give examples of SQL queries as well. The difficulty of using WQL query is based on your ability of programming. If SQL is your fear, you will probably end up doing the same with WQL. But, it is worth the money since the queries will help you save time.

Built-in Reports

Microsoft has included built-in reports in SCCM and has displayed the complete list here. The reports are divided into several categories and these reports can help develop your own ones.

You can execute the built-in reports from the SCCM console or from SSRS website.

  • Open the SCCM console and navigate to Monitoring / Reporting / Reports

  • Right click on the report you want to execute and select Run

 

To edit the report with Report Builder, select Edit

SCCM Device Hardware Inventory

The final way to see the information of one device, is to use our Dashboard – DeviceDashboard – Intune Device or even all asset reports. You enter the name of any device in SCCM and you get a one pager overview of the device. This report can save lot of time to your SCCM team and minimize time in their operation task.

We also included in the report, collections, deployment and system health information.

 

Have you ever bought one of our reports? With the latest updates, this report is linked to other reports. Blue font is considerate as linked!

Summary

Finally, your choice depends on the time you want to put or invest. For a person who wants to save time, you can use our reports or builtin reports. Others, who swears by the console, the resource explorer is an excellent choice. For those who like to develop own stuff, SQL and WQL are your choices. What’s good with SQL is once you learn how to query the SCCM database, you can do your own reports.

Oh… by the way, one more thing about hardware inventory, even if the Add Remove Program information of a device is considered as software, it’s the hardware inventory scan that inventory add remove programs information. Not software inventory! 🙂

Do you use another way to scan SCCM device hardware inventory?

 

The post 5 Ways to view Hardware Inventory Information of a Device with SCCM appeared first on System Center Dudes.

Step-by-Step SCCM Report Creation using Report Builder

$
0
0

One of our favorite tasks when it comes to ConfigMgr management is SCCM Report Creation. Not only it brings value to an SCCM installation, it bring visibility on your hard work toward your management. Without SCCM reports, this huge management tools is running silently on all your devices but you’re not benefiting of all the advantages. It’s like having a sport car and discovering the Autobahn … ok maybe not.

But what makes a good SCCM report ?

  1. Data, data, data
    • This is the more important part of your reports. You need to query the right SQL views in the SCCM database. If you’re showing incorrect information, your report will be useless
    • Building an efficient SQL query is the hard part of report creation. Without any SQL skills, it will be hard to achieve what you want… but, everything can be learned. Two years ago I’ve never done a SCCM report and today we’ve build many and sells them to businesses like yours.
  2. Visually attractive
    • A report full of data is useful but if it’s presented awfully, you won’t get readers attention
    • Try to keep it clean : add pie charts and graph if possible. Microsoft proves this with their latest Software Update dashboard and Office 365 dashboard.
  3. The little details :
    • Try to add links between your report to direct your reader in the right direction
    • Add tool tips to explain the data shown

In our opinion, the default SCCM Reports are lacking many of those points. Yes, they offer valuable data but they are often not adapted to your environment and are visually… basic.

For all those reasons, we started to create our own set of reports and due to their growing popularity, we decided to help you begin your own SCCM report creation process. For this example, we will show the process that we took when designing our free Office 365 report.

Building the SQL Query

SCCM 1606 introduce a new way to inventory Office 365. A new inventory class is created on the client and this data is stored in the v_GS_OFFICE365PROPLUSCONFIGURATIONS. We found this view by browsing the v_GS_* classes in the SCCM database. These classes are usually related to hardware inventory information.

SCCM Report Creation

By using a simple query we can see all data stored in this view:

Select * v_GS_OFFICE365PROPLUSCONFIGURATIONS

SCCM Report Creation

By looking at the results, we know that this is the right view to use.

The machine name is not included in this view. We need to use a JOIN SQL command to get it from the V_R_System view which is the “main” discovery view containing your clients. An SQL JOIN clause is used to combine rows from two tables, based on a common field between them. In our case (We join V_R_System and v_GS_OFFICE365PROPLUSCONFIGURATIONS based on the same ResourceID)

SELECT * FROM v_GS_OFFICE365PROPLUSCONFIGURATIONS OFI
JOIN v_R_System SYS ON SYS.ResourceID = OFI.ResourceID

After that, we’re adding SYS.Name0 in the SELECT to add the machine name from the V_R_System view and we use a WHERE clause to exclude all NULL records.

SELECT SYS.Name0,* FROM v_GS_OFFICE365PROPLUSCONFIGURATIONS OFI
JOIN v_R_System SYS ON SYS.ResourceID = OFI.ResourceID
WHERE CDNBaseUrl0 is not null

We end up with something like this :

SCCM Report Creation

You can modify the query to exclude unwanted data. Once your query is created, we can create the report.

SCCM Report Creation

To create SCCM custom report, follow theses steps :

  • Open the SCCM console and go to Monitoring / Overview / Reporting
  • Right click on Reports and select Create Reports

SCCM Report Creation

  • On the Create Report Wizard, select type SQL-based Report
  • Enter the name of the report Office 365 Inventory
  • Enter a report Description if desired
  • Click on Browse and select the folder where the report will be saved
  • Click Next

SCCM Report Creation

  • Review the Summary and complete the wizard

SCCM Report Creation SCCM Report Creation

  • Report Builder will automatically run

sccm 2012 custom reports

  • Click Run

Report Builder

Report Builder is a simple tool to create reports. You can also use Visual Studio but you need a licence, so we’ll stick to Report Builder. We will explain the basic steps for creating a report.

Once Report Builder is launch, look at the left part of the screen, we will focus on the Report Data section.

Data Sources and Datasets folder are the most important to startThe Data Source section will be used to configure the database and Dataset will be used for the SQL query.

sccm 2012 custom reports

In our case, we won’t use Built-in Fields and Parameters but they are very useful when you want to standardize your reports. For example, if you want to scope a report to a specific collection, you will need to use the Parameters section. If you want to include your company logo in the report, you will need to import it in the Images folder.

Configure the Data Sources

We first need to connect to the SCCM database :

  • Right click on Data Sources in Report Data on left panel and select Add Data Source
  • In the General tab, enter a name for your data source
  • Select Use a shared connection or report model
  • Click on Browse

SCCM Report Creation

  • Browse to the end and select your SCCM Database GUID and click Open

SCCM Report Creation

  • Back in Data Source Properties, click Test Connection to test your configuration and OK when you’re done

SCCM Report Creation

Note
Make sure that your account has access to the database. If not, set up another account via Credentials on the left panel.

Create a Dataset

The Datasets section is where your SQL query will be created.

  • Right click Datasets in the left panel and select Add Dataset

sccm 2012 custom reports

  • Select Use a dataset embedded in my report and select the data source you just created
  • In the Query field, paste this SQL query
SELECT SYS.Name0,* FROM v_GS_OFFICE365PROPLUSCONFIGURATIONS OFI
JOIN v_R_System SYS ON SYS.ResourceID = OFI.ResourceID
WHERE CDNBaseUrl0 is not null

SCCM Report Creation

  • Click Ok
  • You can see on the right side all fields returned by your query

SCCM Report Creation

Report Design

We are now ready to create the visual side of the report. We will include the data returned by the query.

  • Double-click the title and rename it to Office 365 Inventory
  • On the top menu select Insert / Table / Table Wizard

SCCM Report Creation

  • Select the Dataset that you just created, click Next

SCCM Report Creation

  • Select desired fields to be displayed in the table and drag them to the Values box. In our example we simple just take everything.

SCCM Report Creation

  • In the Layout section, just hit Next

SCCM Report Creation

  • In the Style screen, choose Generic because we’ll modify the font and color ourselves, click Finish

SCCM Report Creation

  • You will end up having a basic report with a title and the table you just created

SCCM Report Creation

Visual Modification

  • We will now change the default font
  • Select the whole row and select the desired font and color on the top

SCCM Report Creation

  • We will now import our company logo in the report
  • Right-click Image and select Add Image

SCCM Report Creation

Once imported, drag the Image to your report, click OK on the Image Properties box

SCCM Report Creation

  • Size it and place it where you need it
  • It already look much better :

SCCM Report Creation

  • Other thing we suggest to change :
    • Column name and column size
    • Include tool tip if any field are non descriptive
    • Remove any unwanted column (Delete the column or remove it from the SQL query)

After all modifications, our final report look like this :

Testing

When we’re done with the design, we will test the result in Report Builder before saving it to our production folder.

  • Click Run button on the top left

sccm 2012 custom reports

Go back and modify if needed, when you’re satisfied with the results, click Save button on the top left. The report is automatically available on your reporting point in the folder you specified.

Verification

By saving the report in Report Builder, your report will be updated in SSRS and in the SCCM console.

SSRS

SCCM Report Creation Console

  • From the SCCM console, go to Monitoring / Reporting / Reports. Your report should be published in your folder.

SCCM Report Creation

 

Your first report might not been the best one but with perseverance, you’ll get better and develop your skills. Happy reporting !

The post Step-by-Step SCCM Report Creation using Report Builder appeared first on System Center Dudes.

New SCCM Endpoint Protection Dashboard and Reports Available

$
0
0

A few days ago we released three new Endpoint Protection reports. Together these reports give you a great insight into how well your Endpoint Protection clients are doing.

These reports are also available bundled together with Jonathan Lefebvre Endpoint Protection Management Guide at a discounted price.

SCCM Endpoint Protection Dashboard

This report shows you useful information about endpoint protection on a single page.

The boxes at the top show current status as well as a trend for the last 30 days for each of the 5 categories a client can be in (Protected-Inactive-At Risk-Unprotected-Infected) .

The two At Risk and Unprotected categories shows a breakdown of the subcategories that make up the these two states. If you bought the System Health – Endpoint Protection reports you can click on a number and it will drill-trough to a filtered sub report that will show you the troubled clients.

Note
A client can be in multiple states, it can be both Inactive and At Risk at the same time.

The Malware Detected and and Malware Activity charts gives you a good overview over what malware is detected and how many clients are infected per day.  If you bought the System Health – Endpoint Protection reports you can click on a either a specific malware or a specific day to drill-trough to a filtered sub report for more information.

SCCM Endpoint Protection Dashboard Report

System Health – Endpoint Protection

This report can be used by itself, but works great as a sub report for the Endpoint Protection Dashboard. It gives you detailed information about the endpoint protection clients in a defined collection.

SCCM Endpoint Protection Dashboard Report

 

System Health – Malware Detection

The Malware Detection report gives details about malware that’s detected in a given collection. Information like Client Name, Detection time , Threat name and category , Severity and most importantly if it was successfully cleaned. It can be used standalone or as a sub report of the Endpoint Protection Dashboard.

SCCM Endpoint Protection Dashboard Report

 

Additional details can be found on each report page accessible from our menu or directly from our main product page.

The post New SCCM Endpoint Protection Dashboard and Reports Available appeared first on System Center Dudes.

Windows 10 Compatibility Check using SCCM and Report

$
0
0

When planning for a Windows 10 migration, understanding your environment is the key. Luckily, Windows 10 setup comes with command line options which one of them is an excellent compatibility check (/Compat ScanOnly). This command can be used on a Windows 7,8 or 10 devices before a migration in order to see if those devices are Windows 10 compatible. Using SCCM, we will run this Windows 10 compatibility check, return the results in the SCCM database and use this data to build a comprehensive report. This report can be used to detect and fix migration errors before the actual Windows 10 deployment.

SCCM Windows 10 Compatibility Check Package Creation

We will start by creating a package for Windows 10 compatibility check. The source of this package must be the Windows 10 installation media. The deployment option and command line is important here. If they are not set correctly you’ll end up sending the complete installation media (including Install.wim) to the computers only for a compatibility check which is not really effective. Using our proposed methods, you’ll be using about 250mb on the client drive instead of 5gb.

  • In the SCCM Console, go to Software Library / Application Management / Packages
  • Create a new package

SCCM Windows 10 Compatibility Check

  • Name your package and specify your Windows 10 installation media as the source file. Be aware that setup.exe is language specific. If you have EN-US machine, you must provide EN-US media

SCCM Windows 10 Compatibility Check

  • Create a Standard Program

SCCM Windows 10 Compatibility Check

  • Command Line : SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Enable /Compat ScanOnly
    • /DynamicUpdate: Enabling it causes setup to download the latest compatibility information from Windows Update
    • /CopyLogs parameter can also be added at the end. Use it to copy setup logs to a shared network drive. The problem with that switch is that the logs are not classified using computer names, it will be a nightmare finding the right logs after hundreds of deployments. This is why I’m not using it for this blog post.

SCCM Windows 10 Compatibility Check

  • In the Requirements page, select your operating systems

SCCM Windows 10 Compatibility Check

  • Complete the wizard

SCCM Windows 10 Compatibility Check

  • Right-click your package and distribute it to your distribution points

SCCM Windows 10 Compatibility Check

Deploy Windows 10 compatibility check on a test computer

We will now deploy the Windows 10 compatibility check program on a computer that runs Windows 10 1607. In our test, we want to evaluate if this computer can upgrades from Windows 10 1607 to 1709. Create a test collection and deploy the newly created program to a test device.

  • Right-Click your package and select Deploy
  • On the General tab, select your collection

SCCM Windows 10 Compatibility Check

  • On the Content tab, ensure that your content is distributed to your distribution point

SCCM Windows 10 Compatibility Check

  • Select your deployment purpose – Available or Required

SCCM Windows 10 Compatibility Check

  • On the Scheduling pane, select your schedule

SCCM Windows 10 Compatibility Check

  • On the User Experience pane, select the desired options

SCCM Windows 10 Compatibility Check

  • On the Distribution Points pane, select Run program from distribution point

SCCM Windows 10 Compatibility Check

  • Review your choice and complete the wizard

SCCM Windows 10 Compatibility Check

Running the Compatibility Check

On a targeted computer, run the program manually in the Software Center (Available) or wait for the schedule to trigger your deployment (Required).

The installation will starts. It will take about 5 minutes to complete… and it will fail. This is normal as the error code returned by the compatibility check will always be an error. (No problem will be 0xC1900210 -1047526896).

SCCM Windows 10 Compatibility Check

If you need more information about the error, look at Setupacr.log or Setuperr.log generated by Setup.exe. They are located in C:\$WINDOWS.~BT\Sources\Panther folder. (Or in the specified path if you use the /CopyLogs parameter in your command line. We cover the topic on how to troubleshoot Windows 10 error in this blog post

Once we tested on a couple of test machine and are happy with results, we can expand our deployment to all computers.

From there, what’s the easy way to check your compatibility results? You could go in the Monitoring / Deployment section in the console… or you build a custom report.

Windows 10 Compatibility Check Report

Luckily for you, we created a report which will give you a quick overview of your compatibility success or failure. We also included basic hardware inventory information for you to refer if a computer is not compliant because of hardware limitation. The only thing you need to do is to select your Compatibility package and run the report !

SCCM Windows 10 Compatibility Check

You can download this free report by visiting our product page. The Asset – Compatibility Check report is available in the Report / Asset Section.

Good to know : How to import an RDL file

Let us know what you think of it.

Share this Post

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 4 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

The post Windows 10 Compatibility Check using SCCM and Report appeared first on System Center Dudes.


Identify Office Products with its architecture using SCCM report

$
0
0

I did blog post year ago on Microsoft office product versions with its architecture type and count. But lately, my blog readers have requested to add Office 365 ProPlus product into the report.

The Original Office Product report was created to include all Microsoft Office products from Office 2007 to Office 2016 but it doesn’t have any click-to-run (C2R) products which are Office 365. So we started looking around and developed the report for you.

This free report will have all Microsoft Office products information with its architecture type (x86 or x64) and the count. The report can be run on a specific collection which is useful to scope specific group of machines.

This can be used as all-in-one SCCM report for Microsoft Office product versions with architecture type.

This report comes with a drill-down feature to see the list of all devices with the selected product. You’ll need our Asset –  Installed Software report for the drill-down feature.

sccm report office product
  • Click on the number of installations to see the list of machines. (Available if the Asset – Installed Software is on your server)
sccm report office product

Why does it show more entries than the first report?

The multiple entries are caused because of of the language pack installed on the machine.  1 PC has English, japan and Korea languages installed hence it shows 3 entries.

The 3 entries show also in programs and features as well in resource explorer for the device in SCCM.

You can download this free SCCM Office product report by visiting our product page. The Asset– Office Products report is available in the Report / Asset Section.

For drill-down report, you also need to download Asset – Installed Software report

Upload both the reports into the same folder, change the data source and run the report.

We hope this SCCM report will help you easily identify all your Office products.

Note: There is a rating embedded within this post, please visit this post to rate it.

Share this Post

The post Identify Office Products with its architecture using SCCM report appeared first on System Center Dudes.

How to install Microsoft Intune Client for MAC OSX

$
0
0

Did you ever wanted to install the Microsoft Intune client on MAC OSX? Microsoft Intune standalone supports Apple operating systems since November 2015. SCCM 1602 is required to support the Microsoft Intune client with the SCCM connector (hybrid environment). The Intune client is a lightweight version of the SCCM client. You can deploy some policies, SCEP certificates, VPN and WiFi profiles. There is also a hardware inventory scan on the devices.

In a previous post, we explained how to set up a compliance policy for MAC OSX, now that our client is ready to receive the compliance policy, we will install the Microsoft Intune client on Mac OS X devices.

Install the Intune Client Mac

There is still no way to automatically install the client.

  • Connect on the MAC OSX devices that you want to install Microsoft Intune client
  • Open Safari and go to portal.manage.microsoft.com
  • Click on This device is either not enrolled or the Company Portal can’t identify it

intune client mac 1

  • Click on Enroll

intune client mac 2

  • This message is a warning message of the management profile requirement, click on Install

intune client mac 3

  • Now, the installation process will need to install the Management Profile, click on Install

intune client mac 4

  • You will be prompt to enter full admin credential to installation a new management profile into your MAC OSX device
  • Enter your password and click OK

intune client mac 5

  • The MDM and SCEP Enrollment will be requested, click Continue

intune client mac 6

  • Another confirmation to install the Management Profile, Click Install

intune client mac 7

  • Management Profile installation is completed when you reach this window

intune client mac 8

  • Don’t be surprised, if you see this little warning. Microsoft Intune is in the process of approving the device installation. Wait few seconds and it will disappear

intune client mac 9

  • Choose your active device and click on Select

intune client mac 10

The Intune client installation is now complete. From now on, your device will appear on the manage.microsoft.com portal and SCCM.

Verification

There’s a few ways to determine if the Microsoft Intune client is correctly installed.

  • From the SCCM console, navigate to Assets and Compliance Devices 
  • In the Devices node, search the device you recently installed
  • If your Mac does not appear, it’s a sign that the installation failed

intune client mac

Once the client is installed, you should be able to check the hardware inventory of the device. Note that the Microsoft Intune client Mac is not considered as a normal SCCM client, it’s considered like a mobile device.

  • Right-click on the device name, select Start and Resource Explorer

intune client mac

  • All information of the device appears at this place for only one device.

intune client mac

Finally, using an inventory report such as our Intune Devices, it can help identify all your company assets. All MAC OSX devices with the Intune client will be listed in this report.

HowtoinstallMACOSIntuneClient 17

The post How to install Microsoft Intune Client for MAC OSX appeared first on System Center Dudes.

List of SCCM Client Installation Error Codes

$
0
0
Consulting Services
Need help with your SCCM infrastructure ? Consult our fixed price consulting plans to see our rates or contact us for a custom quote.

As an SCCM administrator, it’s important to learn the concept of troubleshooting a Configuration Manager client installation. By targeting the SCCM client installation error codes, you will have a better idea of what is happening during client installation. The error codes is not an exact science, they can defer depending on the situation. For a better understanding about error codes, read this great post from Jason Sandys.

These codes appear in ccmsetup logs, located on in C:\windows\ccmsetup\logs. During the installation process, monitor the ccmsetup.log using cmtrace.exe and locate each error codes.

SCCM Client Installation Error Codes

There are other logs, on which the SCCM client installation relates. If you don’t find enough information in the ccmsetup.log, scan all related log files in c:\windows\ccm\logsUse the command line net helpmsg, for more information about your return error code.

SCCM Console

You can also add the Last Installation Error in the SCCM console:

  • Open the SCCM console and navigate to Assets and ComplianceDevices
  • In the devices view, right-click on the header and select Last Installation Error
SCCM Client Installation Error Codes

There are chances that the last error code returns an empty value for a device.

SCCM Client Installation Error Codes

This post from Technet Forums (Thanks to Charlie Hawkins), has inspired us to prepare a list of all error codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.

[su_note note_color=”#53C127″ radius=”8″]Feel free to send us any new error codes, this list will be updated based on your comments.[/su_note]
IDSourceDescriptionSolution
2The system cannot find the file specified
This error occur when the WMI service is corrupt
Technet Resolution
WMI Repair
5Access deniedMake sure that the installation account is member of the Administrator Group
7Reboot Required
8Setup Already Running
9Prerequisite evaluation failure
10Setup manifest hash validation failure
52You were not connected because a duplicate name exists on the networkCheck for duplicate name in DNS (IP)
52You were not connected because a duplicate name exists on the networkCheck for duplicate name in DNS (IP)
53Unable to locate
Cannot connect to admin$
Computer Browser not started
Add File & Print sharing to Exceptions in Firewall
Turn file and print on
KB920852
58The specified server cannot perform the requested operation
64WindowsThe specified network name is no longer available
67Network name cannot be foundCheck if client has a DNS entry or invalid DNS
86Incorrect network configuration
112Not enough disk spaceFree some space on the computer
1003Cannot complete this function
1053The service did not respond to the start or control request in a timely fashion
1068The dependency service or group failed to start
1130WindowsNot enough server storage is available to process this command
1203The network path was either typed incorrectly, does not exist, or the network provider is not currently available
Please try retyping the path or contact your network administrator
1208WindowsAn extended error has occurred
1305The revision level is unknown
1396Login FailureThe target account name is incorrectCheck for duplicate name in DNS (IP)
NBTSTAT -a reverse lookup
1450WindowsInsufficient system resources exist to complete the requested service
1603CCMExec could not be stoppedReboot and install the client as administrator
1618MSIThis error is cause by a multiple client.msi installation at the same timeStop all related MSI install process
1789The trust relationship between this workstation and the primary domain failed
KB2771040
12002Failed to send HTTP RequestCheck firewall ports
8007045DMSISetup was unable to create the WMI namespace CCMDelete all SCCM folders and rebuilt wmi Repository
800706BAWMIUnable to connect to WMI on remote machinePrajwal Desai post
80041001MSISetup was unable to create the WMI namespace CCM
Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS
WMI Repair
8004103BWMIUnable to create the WMI NamespaceRebuild WMI Repository
80070070Setup failed due to unexpected circumstancesRebuild WMI Repository
87D0029EWMICCMSetup FailedPrajwal Desai post
2147023174The RPC server is unavailableCheck out firewall or AntiVirus
2147024891Access is denied
2147749889WMIGeneric failure
2147749890WMINot foundWMI Repair
2147749904WMIInvalid class
2147749908WMIInitialization failure
2147942405Access is DeniedMissing Firewall rules
MacAfee-HIPS
2147944122The RPC server is unavailableKB899965
Dcom is miss-configured for security
2148007941Server Execution Failed
Technet Forums Sources

Don’t forget to put emphasis on the prerequisites of the SCCM client, this will increase your success percentage during client installation. You can also check the list of client commands list, as an additional help for troubleshooting your SCCM clients.

Reporting

Knowing the client installation status from reports, reduces the number of devices without SCCM client installed in your IT infrastructure. It also increases your effectiveness, when it’s time to tackle all unhealthy clients.

One of our System Health reports is made especially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment state. This report will help you achieve the *near* 100% client installation, that project manager loves to see.

SCCM Client Installation Error Codes

The post List of SCCM Client Installation Error Codes appeared first on System Center Dudes.

5 Ways to view Hardware Inventory Information of a Device with SCCM

$
0
0

One of the SCCM features is to inventory hardware information from devices that are managed by the SCCM client. It’s not very difficult to enable and configure the hardware inventory client settings in SCCM. Once the devices received next machine policy and hardware inventory scan, data will start to populate in your SCCM database.

The information gathered from the devices can be very useful from a system health, inventory or operation perspective. You can use this information to create collections, queries as well as reports.

However, one thing not too obvious with the hardware inventory information is to see all the data of a device in a one pager. There’s several ways to do it, some more difficult than others, but we will show you how.

SCCM Hardware Inventory – Resource Explorer

The first one is the Resource Explorer tool. It’s a tool accessible directly within the console and which don’t require any additional third party tool to be installed. It’s built-in in the console, it’s pretty easy to use and very useful during troubleshooting.

  • To open the Resource Explorer, open the SCCM console and navigate to Assets and Compliance / Devices 
  • Right click on any device and select Start then Resource Explorer

SCCM Device Hardware inventory

The Resource Explorer tool will open and by expanding each sections, you will be able to find any hardware inventory information related to a device.

SCCM Device Hardware inventory

The Resource Explorer works with all SCCM client platforms.

SQL Query

Are you a SQL fan? Do you understand a little bit of SQL syntax? If not, I would say don’t loose your time and go to the next section. However, if you still want to learn and you are DIY person, open the SQL Management Studio and query all v_GS_ xxxxx views in your CM database. They are the classes inventoried during the hardware inventory.

SCCM Device Hardware inventory

By joining the v_R_System or v_GS_Computer_System views to your SQL queries, you will have all the information you need to make nice queries. Take your SQL queries and transform them in great SSRS reports.

Here is a SQL query example that you can do. This is a very interesting post as well!

WQL Query

The WMI Query Language (WQL) is a subset of the American National Standards Institute Structured Query Language (ANSI SQL) with minor semantic changes. You can use queries to retrieve information about inventory data, status messages and many more. What is nice with WQL queries is that you can use those same queries for collection. For those that understand SQL syntax, you won’t be lost. It looks a lot like SQL queries.

  • To create WQL query, open the SCCM console and navigate to Monitoring / Queries

  • Right click on Queries and select Create Query

  • This windows will open and you will be able to configure your query. Follow this post to help you create your WQL query

There’s few websites that give examples of SQL queries as well. The difficulty of using WQL query is based on your ability of programming. If SQL is your fear, you will probably end up doing the same with WQL. But, it is worth the money since the queries will help you save time.

Built-in Reports

Microsoft has included built-in reports in SCCM and has displayed the complete list here. The reports are divided into several categories and these reports can help develop your own ones.

You can execute the built-in reports from the SCCM console or from SSRS website.

  • Open the SCCM console and navigate to Monitoring / Reporting / Reports

  • Right click on the report you want to execute and select Run

To edit the report with Report Builder, select Edit

SCCM Device Hardware Inventory

The final way to see the information of one device, is to use our Dashboard – DeviceDashboard – Intune Device or even all asset reports. You enter the name of any device in SCCM and you get a one pager overview of the device. This report can save lot of time to your SCCM team and minimize time in their operation task.

We also included in the report, collections, deployment and system health information.

Have you ever bought one of our reports? With the latest updates, this report is linked to other reports. Blue font is considerate as linked!

Summary

Finally, your choice depends on the time you want to put or invest. For a person who wants to save time, you can use our reports or builtin reports. Others, who swears by the console, the resource explorer is an excellent choice. For those who like to develop own stuff, SQL and WQL are your choices. What’s good with SQL is once you learn how to query the SCCM database, you can do your own reports.

Oh… by the way, one more thing about hardware inventory, even if the Add Remove Program information of a device is considered as software, it’s the hardware inventory scan that inventory add remove programs information. Not software inventory! 🙂

Do you use another way to scan SCCM device hardware inventory?

[ratings]

The post 5 Ways to view Hardware Inventory Information of a Device with SCCM appeared first on System Center Dudes.

Step-by-Step SCCM Report Creation using Report Builder

$
0
0

One of our favorite tasks when it comes to ConfigMgr management is SCCM Report Creation. Not only it brings value to an SCCM installation, it bring visibility on your hard work toward your management. Without SCCM reports, this huge management tools is running silently on all your devices but you’re not benefiting of all the advantages. It’s like having a sport car and discovering the Autobahn … ok maybe not.

But what makes a good SCCM report ?

  1. Data, data, data
    • This is the more important part of your reports. You need to query the right SQL views in the SCCM database. If you’re showing incorrect information, your report will be useless
    • Building an efficient SQL query is the hard part of report creation. Without any SQL skills, it will be hard to achieve what you want… but, everything can be learned. Two years ago I’ve never done a SCCM report and today we’ve build many and sells them to businesses like yours.
  2. Visually attractive
    • A report full of data is useful but if it’s presented awfully, you won’t get readers attention
    • Try to keep it clean : add pie charts and graph if possible. Microsoft proves this with their latest Software Update dashboard and Office 365 dashboard.
  3. The little details :
    • Try to add links between your report to direct your reader in the right direction
    • Add tool tips to explain the data shown

In our opinion, the default SCCM Reports are lacking many of those points. Yes, they offer valuable data but they are often not adapted to your environment and are visually… basic.

For all those reasons, we started to create our own set of reports and due to their growing popularity, we decided to help you begin your own SCCM report creation process. For this example, we will show the process that we took when designing our free Office 365 report.

Building the SQL Query

SCCM 1606 introduce a new way to inventory Office 365. A new inventory class is created on the client and this data is stored in the v_GS_OFFICE365PROPLUSCONFIGURATIONS. We found this view by browsing the v_GS_* classes in the SCCM database. These classes are usually related to hardware inventory information.

SCCM Report Creation

By using a simple query we can see all data stored in this view:

Select * v_GS_OFFICE365PROPLUSCONFIGURATIONS

SCCM Report Creation

By looking at the results, we know that this is the right view to use.

The machine name is not included in this view. We need to use a JOIN SQL command to get it from the V_R_System view which is the “main” discovery view containing your clients. An SQL JOIN clause is used to combine rows from two tables, based on a common field between them. In our case (We join V_R_System and v_GS_OFFICE365PROPLUSCONFIGURATIONS based on the same ResourceID)

SELECT * FROM v_GS_OFFICE365PROPLUSCONFIGURATIONS OFI
JOIN v_R_System SYS ON SYS.ResourceID = OFI.ResourceID

After that, we’re adding SYS.Name0 in the SELECT to add the machine name from the V_R_System view and we use a WHERE clause to exclude all NULL records.

SELECT SYS.Name0,* FROM v_GS_OFFICE365PROPLUSCONFIGURATIONS OFI
JOIN v_R_System SYS ON SYS.ResourceID = OFI.ResourceID
WHERE CDNBaseUrl0 is not null

We end up with something like this :

SCCM Report Creation

You can modify the query to exclude unwanted data. Once your query is created, we can create the report.

SCCM Report Creation

To create SCCM custom report, follow theses steps :

  • Open the SCCM console and go to Monitoring / Overview / Reporting
  • Right click on Reports and select Create Reports

SCCM Report Creation

  • On the Create Report Wizard, select type SQL-based Report
  • Enter the name of the report Office 365 Inventory
  • Enter a report Description if desired
  • Click on Browse and select the folder where the report will be saved
  • Click Next

SCCM Report Creation

  • Review the Summary and complete the wizard

SCCM Report Creation SCCM Report Creation

  • Report Builder will automatically run

sccm 2012 custom reports

  • Click Run

Report Builder

Report Builder is a simple tool to create reports. You can also use Visual Studio but you need a licence, so we’ll stick to Report Builder. We will explain the basic steps for creating a report.

Once Report Builder is launch, look at the left part of the screen, we will focus on the Report Data section.

Data Sources and Datasets folder are the most important to startThe Data Source section will be used to configure the database and Dataset will be used for the SQL query.

sccm 2012 custom reports

In our case, we won’t use Built-in Fields and Parameters but they are very useful when you want to standardize your reports. For example, if you want to scope a report to a specific collection, you will need to use the Parameters section. If you want to include your company logo in the report, you will need to import it in the Images folder.

Configure the Data Sources

We first need to connect to the SCCM database :

  • Right click on Data Sources in Report Data on left panel and select Add Data Source
  • In the General tab, enter a name for your data source
  • Select Use a shared connection or report model
  • Click on Browse

SCCM Report Creation

  • Browse to the end and select your SCCM Database GUID and click Open

SCCM Report Creation

  • Back in Data Source Properties, click Test Connection to test your configuration and OK when you’re done

SCCM Report Creation

[su_box title=”Note” style=”glass” box_color=”#000000″ title_color=”#F0F0F0″]Make sure that your account has access to the database. If not, set up another account via Credentials on the left panel.[/su_box]

Create a Dataset

The Datasets section is where your SQL query will be created.

  • Right click Datasets in the left panel and select Add Dataset

sccm 2012 custom reports

  • Select Use a dataset embedded in my report and select the data source you just created
  • In the Query field, paste this SQL query
SELECT SYS.Name0,* FROM v_GS_OFFICE365PROPLUSCONFIGURATIONS OFI
JOIN v_R_System SYS ON SYS.ResourceID = OFI.ResourceID
WHERE CDNBaseUrl0 is not null

SCCM Report Creation

  • Click Ok
  • You can see on the right side all fields returned by your query

SCCM Report Creation

Report Design

We are now ready to create the visual side of the report. We will include the data returned by the query.

  • Double-click the title and rename it to Office 365 Inventory
  • On the top menu select Insert / Table / Table Wizard

SCCM Report Creation

  • Select the Dataset that you just created, click Next

SCCM Report Creation

  • Select desired fields to be displayed in the table and drag them to the Values box. In our example we simple just take everything.

SCCM Report Creation

  • In the Layout section, just hit Next

SCCM Report Creation

  • In the Style screen, choose Generic because we’ll modify the font and color ourselves, click Finish

SCCM Report Creation

  • You will end up having a basic report with a title and the table you just created

SCCM Report Creation

Visual Modification

  • We will now change the default font
  • Select the whole row and select the desired font and color on the top

SCCM Report Creation

  • We will now import our company logo in the report
  • Right-click Image and select Add Image

SCCM Report Creation

Once imported, drag the Image to your report, click OK on the Image Properties box

SCCM Report Creation

  • Size it and place it where you need it
  • It already look much better :

SCCM Report Creation

  • Other thing we suggest to change :
    • Column name and column size
    • Include tool tip if any field are non descriptive
    • Remove any unwanted column (Delete the column or remove it from the SQL query)

After all modifications, our final report look like this :

Testing

When we’re done with the design, we will test the result in Report Builder before saving it to our production folder.

  • Click Run button on the top left

sccm 2012 custom reports

Go back and modify if needed, when you’re satisfied with the results, click Save button on the top left. The report is automatically available on your reporting point in the folder you specified.

Verification

By saving the report in Report Builder, your report will be updated in SSRS and in the SCCM console.

SSRS

SCCM Report Creation Console

  • From the SCCM console, go to Monitoring / Reporting / Reports. Your report should be published in your folder.

SCCM Report Creation

 

Your first report might not been the best one but with perseverance, you’ll get better and develop your skills. Happy reporting !

 

Share this Post

The post Step-by-Step SCCM Report Creation using Report Builder appeared first on System Center Dudes.

Viewing all 31 articles
Browse latest View live