Changes in the Site Structure

Caution When Changing the Site Structure if Clients are Already Productive

When making changes to the site structure or a site definition, ensure that clients which are already productive can always assign themselves to any site, otherwise the client will be “lost” from the site definition. This will mean that it can then no longer automatically update the new configuration from a NetInstall server.

If a client is “lost” from the site definition, the following command must be executed on the client to update the new configuration from the NetInstall server - e.g. by changing the login script:

\\<Server>\<Share>\niagnt32 /install

Possible Solution: Setting Up a Catch-All Site

To prevent clients being “lost” from the site definition from the outset, you can set up what is known as a “catch-all site” to which all clients which do not (or no longer) fit into a “productive” site can be automatically assigned.

Set up the “catch-all site” with the following features:

  • Site context: Immediately below the ORG
  • Name: ZZZZ or similar. It is important to ensure that this site is displayed as the last site in the site structure. This ensures that it is always checked as the last site in the client-site assignment.
  • Use a site definition that applies for all clients, e.g. IP name from * to *
  • Ensure that no productive projects are “visible” or available in this site (you can ensure this through e.g. permissions by excluding site ZZZZ from the database level).
  • In the “catch-all site”, you can instead provide e.g. a project that sends a message to the adminstrator if a client is assigned to this site.

If a client is assigned to the catch-all site, you can ensure that it once again fits into a productive site by (depending on the particular feature the site definition of your productive site is based on):

  • Either changing the site definition(s) of the productive site(s).
  • Or performing a change on the client. For example: If you define the site via a client registry value, change the registry value accordingly.