Deployment Solution

 View Only
  • 1.  Package Servers?

    Posted Dec 22, 2008 06:09 AM
    Is there a way to set something that acts like a package server for a deployment server? I have a stand alone DS but have remote sites, I would like to have the packages deploy locally at those sites.
    Thanks!


  • 2.  RE: Package Servers?

    Posted Dec 22, 2008 08:37 AM
    Hi Blanca,
    I would start here: https://kb.altiris.com/article.asp?article=22688&p=1. I personally don't use the DS library\DS Solution for NS (and don't recommend it either, usually), so the DS library portion may not apply. Basically you can do the following: map a drive in the Deployment Server configuration to the alternate location, map the same letter to the PXE\boot file you use, and for ease of job creation, map the same drive in Windows on the DS itself. Be sure to check the box for disabling the image validation in the deploy image job though.
    Anyway, I use this method quite successfully. Also, you can (and should) setup PXE servers (if you are using PXE) on the remote servers as well.

    Hope that helps, and I'm happy for anyone else to provide corrections.

    Jim


  • 3.  RE: Package Servers?

    Posted Dec 22, 2008 08:43 AM
    Thanks Jim! I'll give that a shot. With our DS in Canada and sites in UK and Arizona, I'd like to have local repositories. Particularly as it seems we'll be using the DS quite a bit for jobs and packages.


  • 4.  RE: Package Servers?

    Posted Jan 21, 2009 02:49 AM
    Sorry for the late response.

    Jim has mentioned some good solutions. Also, one that we have implemented is in our packages, we list the path to the installation source as, "\\%SITE%\RemoteShare\Apps\app1.exe".

    Then, in the properties of the client there is an area which allows you to define a Site for the machine. In that Site field, we enter the name of the server at the local branch. i.e. (Serv1W2K3)

    When the job is run against the client the token is replaced with the value in the "Site" field. So the final installation path would be, "\\Serv1W2K3\RemoteShare\Apps\app1.exe".

    In the Advanced options for the package, make sure you select either "Copy files directly from the source the execute" or "Run directly from file source"

    There is a SQL query that can be found in the Altiris KB that makes setting the Site field on all existing clients a lot easier. With your clients seperated into different groups based on geographical location, you enter the server name into the Site field for one client in each group. The query then copies that value to all other clients within the same group.

    This may not work for you but I thought I'd trow it out there as an option.