Creating a clean software package environment

In this post we are going to discuss how to create a clean software packaging environment, or package street/package factory.

 1). It is highly recommended to use a virtual machine and a good tool is VMware Workstation for PC or VMware Fusion for Mac. If you use Windows 8(or higher), then you could use Hyper-V, which is free (see my other post HERE on how to enable this)
 
2). Choose an Operating System. Preferably Windows 7 32-bit or 64-bit (depends on what environment is most used in your company, possibly both are needed).
 
3). Create a 30 GB virtual hard disk and a 10GB virtual hard disk (used for page file) and attached to your virtual machine. If you have a SSD in your host system, it is recommended to point it to that disk (to achieve best performance)
 
4). Install Windows to the freshly created virtual hard disk(the 30 GB one)
 
5). Turn Off Automatic Updates then Run Windows Updates but only Security Updates, Service Packs, and other Critical Updates. Avoid Language Packs, Windows Defender, Internet Explorer Updates, and Driver Updates. You are best off not installing any dependencies like Visual C++ or .NET Framework. In this case, if your software complains then you'll know what .NET Framework your software package needs. You can then add it as a dependency (for instance when creating the package using Adminstudio).
 
6). Turn Off System Restore
 
7). Disable Extra Features from Programs / Add or Remove Windows Features you will not need. It is necessary to create a reference computer that is as clean as possible.
 
8). Create your page file. You may need to format your 6GB Hard Drive.

Right Click Computer -> Properties -> Advanced System Settings -> Advanced Tab -> Performance Settings -> Adjust for Best Perfomance -> Advanced Tab -> Change... -> Uncheck Automatically manage paging File size for all drives -> Check Custom size -> Click your Second 6GB Drive -> Take the amount of Physical Memory in your PC and double it for both Initial size and Maximum Size EX 2048 Physical is 4096 -> Click Set -> OK -> OK -> OK -> Restart
 
9). Turn off Services you don't need. Services.msc Double click a service, Choose Disabled, Click Stop, Click Apply. 
Services I disabled were:

• Disable BITS
• Disable MpsSvc (Windows Firewall)
• Disable wuauserv (Windows Update)
• Disable WSearch (Windows Search)
• Disable WinDefend (Windows Defender)
• Disable Themes
• Disable wscsvc (Security Center)

 
10). Install VMware Tools, Parallels Tools, VirtualBox tools, Hyper-V Integration Services etcetera. Whichever hypervisor you are using. Reboot when done
 
11). Install your MSI Packaging Tool, (for instance, Admin Studio, InstallShield, AppDeploy, EMCO, Orca) I'm using AdminStudio
 
12). Add anything else you think you may need. Now you can configure your Machine how you want it. 
 
13). Shutdown the machine and create a snapshot/checkpoint. Now you can use your MSI creating tool, and create snapshots when done. You can also use this machine to create captures.

Howto: Create an application in SCCM 2012 R2

This blog describes how to create an application in SCCM 2012 R2, which you can deploy to your users and devices. 

In this example, we have created an application called 'Audacity'. Bare in mind that this is an MSI application. For an executable the steps are similar, but some extra windows in the wizard need to be overcome.
Below are the steps that need to be taken to implement the application:


First, you open your SCCM console.

Then, you browse to Software Library, rightclick Applications, and choose 'Create Application'.

 Choose the above option, and browse to the unc path (\\servername\sources$\softwarelocation)

 You can click browse, and doubleclick on the MSI to let SCCM automatically fill out the information based on what is available in the MSI file.

 Follow the wizard to complete the 'Import Information' step.

 Fill out the missing fields, and give the correct parameter in the 'Installation program' field.

 Follow the wizard by clicking next next next (etcetera).

 Once finished, lookup you package and rightclick it, select properties.

 Place the check mark for the 'Allow this application to be installed from the Install Application task sequence action without being deployed' option. It's pretty much self explanatory...

 I also tend to add the /l*v switch in the MSI property, for troubleshooting reasons.

 Also add the product code for the Windows Source management option

It's possible to change the detection method or user experience if needed. Also you can specify requirements or custom return codes, or dependencies (other applications).

Once done, you are ready to deploy your application to your user collection(s) or device collection(s)!