Choosing Distribution Points

Creating multiple distribution points to balance the load is important when you create shared applications. You can simulate your network using the SMS Site Properties Manager and the SMS Object Generator to give you an idea of how many distribution points you need and where they should be located. For more information about these tools, see Chapter 11, “Configuring and Populating Pilot Sites.”

SMS includes three methods you can use to allow clients to choose a distribution point, if several exist for a package:

Existing connections
The current list of connections is checked for matches against the shares in the CAP and distribution point lists. The first existing connection is reused. This is the default method for SMS.
Random
A distribution point is chosen randomly from the list. This method is enabled by default and is used if there are no existing connections.
Preferred
You can set up a list of preferred distribution points. Distribution points that have been assigned to the preferred list are tried first. This method is disabled by default.

You can use the Set Preferred Distribution Point and CAP tool (PrefServ.exe), included in this Resource Kit, to set up a single preferred distribution point for a client. Use the tool several times to create a list of preferred distribution points. For more information about this tool, see Chapter 13, “Using SMS 2.0 Tools — Part 1.”

If security is required for the package, use package access accounts to restrict access to the package binaries on distribution points to only those users who receive the advertisement. This should only be necessary if you think unauthorized users will try to install the application. By default, distribution point shares are hidden and Read access is granted to the Users and Guests generic package access accounts. Since sophisticated users could connect to a distribution point and execute applications not advertised to them, you should use package access accounts for any packages that require security or have limited licenses. If the package is being advertised to a collection that includes users or user groups, you can easily give them permission to the access accounts.

Procedure Bullet  To set up a package access account

  1. Navigate to Access Accounts in the SMS Administrator console.
    2. Systems Management Server   Lower levelSite Database (site code - site name)      Lower levelPackages         Lower levelpackage            Lower levelAccess Accounts
  2. Right-click Access Accounts, click New, and then click the kind of access account you want to create. You can create a Windows NT access account or an access account for NetWare bindery or NetWare NDS. In the Access Account Properties dialog box, set the user or user group account that should be allowed to access a package on the package’s distribution points.