In a large and distributed environment it is not practical to touch each machine you want to capture a Master Image from. According to the Snap Deploy user guide, Acronis recommends creating a Master Image using boot media which requires being at the computer to insert the CD from which to boot. Today I tried to capture an image remotely from one of our Workstations before joining it to the Domain, and I can connect to the Workstation via Remote Desktop in either configuration (Domain member or Workgroup) provided the machine is up and running. In Workgroup configuration I was not able to browse to the Network location of our image repository (which resides on a Domain member Server) where I wish to store the image. When I expand the Microsoft Windows Network node all I see is our current Workgroups, but none of our Windows Domains. I even tried using the UNC path but that did not work either. After joining the target Workstation to the Domain and again attempting to remotely image the computer I was then able to see all the Domain nodes in the browse list. Imaging the machine as a Domain member presents a problem, as any seasoned Windows professional knows, where users will not be able to log in to the Domain after the image is deployed to another machine. I suspect I may have a workaround, but in the meantime I was wondering if anyone can tell me for sure whether adding the appropriate entries for the Server name (where the image repository resides) and IP address as well as the Domain name to the lmhosts file will work Thanks for sharing your experience or any ideas regarding this issue.