Tuesday, July 26, 2016

Part 26 - How To Deploy Bginfo Using SCCM 2012 R2

We a using a powershell script to install and config Bginfo from Sysinternals.

Download the script from here:
Download Bginfo from here:
Extract the files both zip files and pick these for the deployment application:
  • Bginfo.exe - the application
  • Eula.txt - End-user license agreement for Bginfo
  • psBGinfo_sccm.ps1 - the powershell deployment script.
  • default.bgi - a bginfo template
  • restore.bgi - a restore template for restoration 


Go to Software Library > Overview > Application Management > Applications

Right click on Applications and select Create Application

Select Manually specify the application information. Next

Fill out the application information. Next



Review your settings and click Next.


The application is now created. click Close.

Now we create a deployment type for the application. Right click on the newly created application and select Create Deployment Type.

From the Type drop down menu select Script Installer. Next.

Give the deployment type a name. Next.

Specify these: 
  • Content location: \\sccm.traininglab.local\source$\software\psBGinfo\
  • Installation program: powershell.exe -executionpolicy bypass -file ".\psBGinfo_sccm.ps1"
  • Uninstall program: powershell.exe -executionpolicy bypass -file ".\psBGinfo_sccm.ps1" -DeploymentType Uninstall


Now we provide a way for SCCM to detect that our installation went well. Click on Add Cause

  • Setting Type: File System
  • Type: File
  • Path: C:\Program Files (x86)\BGInfo
  • File or folder name: BGinfo.exe


  • Setting Type: File System
  • Type: File
  • Path: C:\Program Files (x86)\BGInfo
  • File or folder name: default.bgi

  • Setting Type: Registry
  • Hive: HKEY_LOCAL_MACHINE
  • Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Run
  • Value: BGinfo

With these detection we make sure that the program is there (bginfo.exe) - the template that used also there (default.bgi) and last the registry that make the program run at every login. Next.

Installation behavior: Install for system
Logon requirement: Whether or not a user is logged on
Installation program visibility: Normal
Next.

Next.

Next.

Review your settings and click Next.


Deployment got created click Close

In SCCM we cant directly deploy a application to a machine. 
Go to Assets and Compliance > Overview > Device Collection
Right click on Device Collections and select Create Device Collection

Give the device collection a name. Software for TESTING
Next

Next.

OK.

Next.

Device Collection got created. Click Close.

Now find the device you want to deploy to under Assets and Compliance > Overview > Device
Right click on the device and select Add Selected Items > Add Selected Items to Existing Device Collection

Select the collection Software for TESTING
OK.

Now we will deploy the application to the collection.
Select the application and click on Deploy

Browser to the collection Software for TESTING
Next.

I have already distributed the content. If you haven't then select a DP by clicking on Add.
Next.

Here we can control how the software is deployed.
Under Purpose we select Available 
Next.

Next.

Next.

Next.

Review your settings. Next.

The Deploy Software Wizard completed. Next.

Logon the device that got add to the Software for TESTING collection and press Start
Find Microsoft System Center folder and expand it. Expand Configuration Manager too.
Click on Software Center.

Here we see our application that got deployed to the Software for TESTiNG collection which we added our device to. 
Select the application and click on the INSTALL button.

Status: Installing

Status: Installed

And the result is weird but after a reboot we got our wallpaper back :D


Task Sequence

I find this application quite useful so i added it to my OSD task sequence


Monday, July 25, 2016

Part 25 - Operating System Deployment - Deployment New Computers

Computer Name

We use a collection variable to give the computer a name when we deploy the OS.

Right click Unknown Computers and choose Properties. Open Collection Variables Tab.
Click on the yellow star to add a new variable. Type OSDComputerName. OK.

Turn on a new blank VM mashine and press F12 for network boot.


You can follow what happen in the SMSPXE.log file with Cmtrace viewer.

Enter your PXE password. Next

Choose your task sequence. Next

Double click on OSDComputerName and enter a computer name. OK

Next to continue.

Drive is getting formated.

Image file is downloaded.

Image file is applied to the formatted drive

Install done. Press CTRL + ALT + DELETE to login.


Part 26 - How To Deploy Bginfo Using SCCM 2012 R2

We a using a powershell script to install and config Bginfo from Sysinternals . Download the script from here: psBginfo - For simpl...