Sorry this post is so long and confusing. When scheduling a task in TI9 2323, there are 2 places it asks for a user/pswd: (1) an account for accessing remote volume where image will be stored, and (2) account the task will run under on the local computer. On my computer, which is an XP Pro member of a mixed-mode domain run by W2K DCs, I normally log in as Me (a domain acct), but both places in the TI9 scheduled task I use DomAd (also a domain acct.) Q1: When I look at the TI9 script file, I see only one user/pswd pair; which one is it (the one for network access or the one for executing the task)? Q2: I tried changing the user/pswd to Me both places in a scheduled task and comparing the new script file with the old version, and there appeared to be no difference; why would this be so? Also, we experimented on this same machine with doing images from the cmd line, as described in the 16Nov05 post by MKairys. When logged in as Me, the job failed because a required privilege was lacking. When logged in as DomAd, the job worked, even though I believe Me and DomAd are members of the same groups. BUT, what really surprised me was that when I logged back in as Me and tried to check the image just created, it was not included in the TI9 list of images in that directory, even though a Windows dir listing showed it there. When I manually triggered the scheduled task from within TI9 while logged in as Me, then the file was included in the list (and the scheduled task uses acct DomAd, same as was used from the cmd line.) Q3: Is there any document from Acronis that specifies exactly what privileges are required on which machines in order to create images in various ways? Q4: Is it normal that the image file would not be listed in TI9, as described above? Q5: Does any of this bring to mind any other comments/ideas from anyone, that might help us understand all this? Thank you very much.