Hi, all -- I'm working on adding an LDAP Client configuration section to my autobuild scripts for SuSE Pro 9.2, and I'm having a funny little issue with disappearing values. Specifically, after the machine is built, LDAP authentication doesn't work. An LDAP user attempting to log in gets the message that his/her account doesn't exist. If I pull up YaST and look at the LDAP Client configuration section (under Network Services), the following values are selected: Use LDAP (this is correct) LDAP base DN: dc=example,dc=com (this is wrong) LDAP Server: 127.0.0.1 (this is wrong) LDAP TLS/SSL (this is wrong) Everything in the Advanced Configuration section is configured correctly. Wondering if anyone else has experienced this... The LDAP section of my rules is: <ldap> <base_config_dn>ou=ldapconfig,dc=subdomain,dc=studentuniverse,dc=com</ba se_config_dn> <bind_dn>cn=AnAdmin,dc=subdomain,dc=studentuniverse,dc=com</bind_dn> <create_ldap config:type="boolean">false</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>dc=subdomain,dc=studentuniverse,dc=com</ldap_domain> <ldap_server>10.0.0.2, 10.0.0.3</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <member_attribute>member</member_attribute> <nss_base_group></nss_base_group> <nss_base_passwd></nss_base_passwd> <nss_base_shadow></nss_base_shadow> <pam_password></pam_password> <start_ldap config:type="boolean">true</start_ldap> </ldap> Thanks, Ian