I was playing around earlier in my System Center 2007 Configuration Manager lab and ran some updates since it has been a while. One of the updates I ran was to upgrade Internet explorer to version 11. After applying the updates, I decided to check everything to make sure something did not break. Sure enough reporting broke. When I went to the reporting website I noticed the following:
This can be easily resolved. Go to the settings (gear) and select Compatibility View Settings.
Add your Reporting Server to the Compatibility View list.
You will now see your reports.
In this post I will walk you through the steps of installing the Linux client, and ensuring the client is registered with Configuration Manager. Lastly I will walk through creating a custom device collection for the Linux systems.
In this example I am running Ubuntu 14.04.1. I have joined it to my domain.
Installing the Linux Client for Configuration Manager
You will need to download and extract the executables from Microsoft for the System Center 2012 R2 Configuration Manager Linux or Apple client.
Once you have downloaded and extracted the files copy over 2 files. You will need the install and the ccm-Universalx64.tar in order to install the client.
Once these files are copied over, open a terminal shell as a SU and run the following command:
./install -mp <computer> -sitecode <sitecode> <property #1> <property #2> <client installation package>
The install will take a few moments to run, and should complete successfully.
Creating a Linux Devices Collection
In this final step I am going to show you how to create a collection query for your Linux Systems. This is a simple query where the client Edition for Linux systems in this case = “13”.
The end result should show all your Linux Devices within the collection.
As of late I have started to see more and more organizations take advantage of providing an image to the organizations hardware vendor to save time in deploying the image out to their systems. The goal is to have the image already on the systems so that when the systems arrive on site at the organization, they will just continue with the task sequence.
This post will walk through the steps to .wim file that can be applied to a bare-metal system either on site or from your hardware vendor. The post will then show the continuation of the process once the system is on site.
Create the prestaged media
Browse to the Software Library and expand Operating Systems. Right click Task Sequences and select Create Task Sequence Media.
The Create Task Sequence Media Wizard window will open.
Select Prestaged media and click Next.
Select how media finds a management point. In this example I chose Dynamic media. Click Next.
Specify the information for the media file. Click Next
Select the security settings for the media. In this example my lab is running with certificates.
Browse for the task sequence. The selected task sequence will reference content.
Select the boot image to be used.
Note: This must be the same boot image as referenced in the task sequence above.
Select the image package that will be applied as part of the prestage wim.
If any applications are needed, select those.
Select content packages to add.
If you are using driver packages, select those.
Specify the distribution point(s) for the media.
Customize the task sequence media
Confirm the settings
Importing the prestaged image into Configuration Manager
Browse to Software Library expand Operating Systems and right click Operating system Images. Select Add Operating System image.
Browse to the path of the .wim file created in the previous steps. Click Next.
Provide the details and click Next.
Review the summary and click Next.
Deploy this image to your distribution points.
Creating a Task Sequence to deploy the prestaged image to a computer
Since I do not have a hardware vendor for my lab, and everything is virtualized, I am providing the steps I used to apply the In this section I am providing the steps I used to apply the wim image similar to how it would be applied to a bare-metal system.
I have created three tasks. First we need to format and partition the disk.
Next we need to apply the prestage wim file.
Lastly we want to shutdown the winPE.
Staging a system with the prestage image
Now that we have the task sequence ready, boot up the virtual machine and select the Prestage task sequence.
The Task Sequence will begin to apply the wim. When the Task Sequence has completed, the system will power off.
Continuing the image post prestage
Now that we have the prestage image applied to our system, we can power up the system. The system will load into the boot environment. Select the Task sequence for continuing the imaging process.
Note: My windows 7 x64 Enterprise Task Sequence was created using the MDT 2013 integration.
The process will continue to finish applying the needed settings.
Once it is completed, you should be at the CTRL + ALT + DELETE screen.