SCCM 2012 Beta 2: UNC Paths when Creating an Application
Posted by Trevor Sullivan on 2011/05/05
In System Center Configuration Manager 2007, and prior versions, you would define an application package’s source files using a local package source path on the site server, or a UNC path to another network location.
Naturally, as you might be accustomed to by now, you probably copy / paste the path to the root folder of the content you’re deploying, when creating a new package. In SCCM 2012 Beta 2, when you go to create a new software package, you’ll probably want to automatically paste this path into the first text box you see. This has changed, however, as SCCM 2012 first presents you with an option to “automatically detect this information using existing content.” In this first dialog box, you will actually need to specify the path to an individual file, such as a MSI file, an App-V manifest (has an OSD extension, I believe), a CAB file, or a JAR file.
If you paste your folder path, rather than a path to an individual file, you’ll be presented with a message saying “Specify a valid UNC path.”
Here’s the right way to do it:
Since we’re on this topic, there are four options to automatically detect package deployment information:
- Windows Installer (Native) – These are also commonly referenced as “MSI packages”
- Microsoft Application Virtualization – App-V virtual app packages (OSD, XML, and SFT files)
- Windows Mobile Cabinet – These are CAB files used to deploy applications to Windows Mobile devices
- Nokia SIS/JAR – I’m not personally familiar with these, but I presume it’s some sort of Java applet in a file with a .JAR extension