Tomasz Chmielewski wrote: > You can use the same model (Admininistrator or unprivileged user) with both unattended and wpkg. > And I'd discourage using guest access for accessing any WPKG shares anyway. > > The best approach IMO is to use an unprivileged user to access a password protected share. Why is this better? I have so far been reluctant to add another user to our LDAP database - Samba uses LDAP for authentication here. I can't see any security benefits, as either. At least not for wpkg. >> 2008-04-14 14:03:12, DEBUG : Initialized temporary local log file: C:\WINDOWS\TEMP\wpkg-logInit.log >> 2008-04-14 14:03:12, DEBUG : Initializing new log file: C:\WINDOWS\TEMP\wpkg-dell002.log >> 2008-04-14 14:03:12, DEBUG : Reboot-Cmd is standard. >> 2008-04-14 14:03:13, DEBUG : WPKG 1.0 starting... >> 2008-04-14 14:03:13, DEBUG : Base directory is '\\hq\wpkg\cur'. >> 2008-04-14 14:03:13, DEBUG : Log level is 255 >> 2008-04-14 14:03:13, DEBUG : Trying to read XML file: \\hq\wpkg\cur\profiles.xml >> 2008-04-14 14:04:20, DEBUG : Successfully loaded XML file: \\hq\wpkg\cur\profiles.xml > > It waits over 30 seconds to access the first file - looks like either: > > 1) this workstation is *very* slow > 2) your profiles.xml file is *very* large (and all other XML files) > 3) there is some problem accessing network shares (WINS, DNS resolution, other network problems etc.). > > If I'd have to bet here, I'd bet on 3). I have noticed accessing network shares on first access does take about 30 seconds, unless logged in via the domain. I haven't worked out why yet. WINS resolution seems to be working fine. I will double check. If WINS wasn't working, I wouldn't expect anything to work. However, once the share has been mapped, it should be fast. > This looks even worse: Yes. It makes no sense to me. > Definitely, it is not normal. > Does it affect every machine? So far I have only seriously investigated one computer - a Dell Latitude D610. I tried a HP Compaq nw8440 too, but it looks like the basic Windows XP SP2 installation disk won't work with this hardware :-(. Won't detect the hard disk. Brian May |