We do extensive OTN application deployments with our Kix-based SWDIST package. The one thing that I believe makes it so successful is that we map a drive to the root of the install folder, connect to the drive, and then CD to the folder that contains the installer and all required files and execute it from there. When we referenced drives or UNC paths, we had no end of issues with consistency and reliability.

SWDIST is 90% rules and 10% code:
  • Every application product has a single folder with no version or other descriptive text (eg: "Acrobat", not "Acrobat 10")
  • Every product folder has a subfolder called "Current" where the currently deployed version resides. This is where the installation is run from.
  • Every installation folder has an "INST.BAT" file that contains the command(s) to perform a silent install. It may accept arguments to alter the default install method, but must run with reasonable defaults without any args.
  • An "Archive" folder may exist, with version-specific subfolders. Each subfolder is named after a specific version, and is configured exactly like the "Current" folder.
  • A "BIN" folder in the root of SWDIST contains the KiXtart scripting engine used for deployments, KixForms.DLL, and any other tools needed by the installers.
  • All references to the utilities in the Bin folder are relative (\bin\folder\utility.exe) and will not specify any drive letters.
There's a script in the root of the SWDIST folder called "install" that parses the arguments, does a CD to the product\Current folder, and invokes INST.BAT with any needed args. Since every product folder is configured exactly the same, it's easy to automate. If I need to install an older version, I specify the archive option and version, and the script runs INST.BAT from that folder instead.

Using this method, its easy to install apps with minimal effort:
Install the current version of Acrobat: Install Acrobat
Install an archived version of Acrobat: Install Acrobat -a:9.1

When this was deployed at the Fed, we achieved a 94% delivery and installation success rate with thousands of deployments. This compared quite favorably to the Tivoli Software Distribution (barely 61% success) and Microsoft SMS (around 78%), mostly because of the consistency of the deployment structure. I've also deployed this to large organizations with hundreds of sites and configured deployments for all kinds of applications, updates, and even MS service packs and hotfixes.

So - instead of running "S:\Lync\...", map the drive, CD to the folder on that drive, and then run the installer. You can verify that the file exists before execution
 Code:
If Exist('setup.exe')
  $Cmd = 'setup.exe ' + $Args
  'Running ' + $Cmd + @CRLF
  Shell $Cmd
  @SERROR + @CRLF
Else
  'Error - setup.exe was not present!' + @CRLF
EndIf
Glenn
_________________________
Actually I am a Rocket Scientist! \:D