Hi, is it possible to organize the autoinstall file in a more modular way ? Can I include configuration files with only a subset of configuration information ? In this way I would have only one main file and include several configuration files according to my hardware and software selections and I could setup a simple construction kit for different hosts with different installation specifications. If yes, can I partially automatize this behavior ? For example : I define several classes of the different types of network interfaces in my workstation pool. Then I assign every host to one of these special classes. Due to this information I can make my installation decisions in my main autoinstall file for many hosts without to create an own autoinstall file for each host. What would be if I want to install some software packages only to a subset of hosts. I would define a corrsponding class and make my decisions in my main autoinstall file to install this software only to the hosts defined in this class -> If host member of class then install software ... Using the CMS it is possible to define classes, but I don't know how to use them. Exists there some reference manual which explains this in detailed or can anyone give me an Howto ? Or must I create for each host its own autoinstall file ? Tanks in advance Regards Werner Hack Universitaet Ulm