So what functionality was added? With my patched wpkg.js you can use in hosts.xml: -group of hosts: <host name="PC1;PC2;Server" profile-id="profile" /> <host name="Server2;PC.+;192.168.1.1-10" profile-id="profile" /> -operating system of host: <host system="xp.+professional.+sp3" profile-id="profile" /> - combinations of upper attributes: <host name="192.168.1.1-100" system="vista" profile-id="some_profile" /> On LAN with MS Active Directory or OpenLDAP you can also use: -domain organizational units of computers <host ou="mydomain.local/Classrooms" profile-id="profile"/> -domain groups of computers <host group="Domain Computers;Laptops;Print Servers" profile-id="profile" /> Using of domain organizational units is GREAT ADVANTAGE. Why? I have LAN with Win2003 server and 50 Pc's. Because names and IPs are very different, I would to use 50 host definitions in hosts.xml: <host name="somename" profile-id="profile" /> <host name="anothername" profile-id="profile" /> ... ... ... <host name="lastname" profile-id="profile" /> With my patched wpkg.js I can use only 2 host definitions!: <host ou="mydomain.local/TeachersComputers" profile-id="profile" /> <host ou="mydomain.local/Classrooms" profile-id="profile" /> ANOTHER ADVANTAGE is in case of new PC coming. I need not do any changes in hosts.xml! I just add its computer account to organizational unit and WPKG profile is applied immediately. The same situation is, if I migrate computer account from one organizational unit to second organizational unit. |