Posts

Showing posts from May, 2017

Universal Task Sequence Import - SCCM Task Sequence with a GUI

Image
Previously I put together a how to on building a SCCM Task Sequence that allows you to choose what image file and software is applied to a computer and perform a few other tasks. Its good to know how to do the process from scratch but with how long the process of building your own Universal Task Sequence is I decided to export the TS to that you can import it into your own environment and customize it as you need to. You can download the TS from HERE, it can take some time to download its about 8gb. So start it off and go get some coffee.

Once the file is downloaded unzip the file and copy the content to the where you keep your SCCM content files (Should be a UniversalTaskSequence_x64_files folder and a UniversalTaskSequence_x64.zip file) .

Open your SCCM Console and navigate to Software Library > Operating Systems > Task Sequence and along the top ribbon you will see Import Task Sequence from there browse to where you put UniversalTaskSequence_x64.zip.



Once the TS is imported it…

SCCM Task Sequence with GUI - How to install more then one image with a single Task Sequence

Image
Update to the process 


A few weeks ago, I put out a guide on how to create a Task Sequence for windows 10. This post will build off of that that and will show you how to build a TS that will display a GUI that will allow your technicians to set the computer name, enter a description to be updated to AD, choose what operating system image to install and choose from a list of applications to install. You should try to understand this process but I do have a post on how you can just import my own TS that you can customize HERE.




The first thing you will need to do is download a copy the TS example files, you can get them from HERE. In the zip files, you should have a few folders InstallUpdates, SetADDescription, TSGUI_x64 and Windows10Config copy each of the folders where you keep your SCCM content files.
1. Create a package for the GUI, give the package a name like TS_GUI, for the version type x64, check the box "This package contains source files" and brose for the TSGUI_x6…

Get-SCCMDeviceInfo - V 1.0.0.2

Image
This tool works much like my Add Computer to SCCM Collection Script but gathers select information about a device from SCCM

I have rereleased my Get-SCCMDeviceInfo script for some minor bug fixes
1. Fixed and issue that would duplicate the device status and resource Id of the device had more then 
    one primary user.
2. Fixed an issue that could result in an error if the user did not specify both a Site Code and Site Server



<#.SYNOPSISThe script will allow you to gather inforamtion about a device from SCCM.DESCRIPTIONThis script will gather Activation status, Resorce ID, OS, Managment Point,Primary User, Last log in time, Hardware scan,Software scan and Policy request time..EXAMPLEIf you do not want to use the Site form specify yoru site code and site server in the paramiters.\Get-SCCMDeviceDeviceInfo.ps1 -SiteServer SCCMSiteServer -SiteCode CC1.EXAMPLEif you want to load the PowerShell Module from the local install path use .\Get-SCCMDeviceInfo.ps1 -LoadLocal True.NOTESCreated By: K…

Test an Application Install localy

Image
If an Application deployment keeps failing it can be helpful to try running the install directly on the local device. This can tell you weather or not you have the syntax correct for they Application since the base content is not always the same and many application venders have proprietary switches for there installers.

For this example I will be using the installer for Blue Beam PDF Editor.

1. I need to find where SCCM has put the install files. I can do that by reviewing the AppEnforce.log* file with cmtrace.exe*, The AppEnforce.log file can be found at C:\Windows\ccm\logs on the device you are having problems with.

2. When looking though the log I want to find where the log references my software by finding the below line.







Take note of the text to the right of Prepared command line: since that is what you will want to run on the local system.

3. Now that I know I'm looking at right section in the log file I want to find the directory that the software was downloaded to by findi…