Symantec Ghost cann't join Samba-PDC domain
linux at fenix.uam.mx
Mon Sep 24 12:04:45 GMT 2001
I'm using Ghost to mirror an image from a samba server over 14 computers,
but when I do it in parallel with all machines, it takes up to 7seven
hours. I have read that using Ghost in some particular mode (broadcast, I
guess) this could be faster, What do I need to do this?
Thank you in advance.
On Mon, 24 Sep 2001, Mark Haney wrote:
> Here's my suggestion from someone who has done close to a thousand of these
> types of installs using ghost: Do not have the machine in the domain when
> you ghost it. Add it later. This way you guarantee that it works.
> -----Original Message-----
> From: samba-ntdom-admin at lists.samba.org
> [mailto:samba-ntdom-admin at lists.samba.org]On Behalf Of Matt Lessem
> Sent: Monday, September 24, 2001 3:47 AM
> To: samba-ntdom at lists.samba.org
> Subject: Symantec Ghost cann't join Samba-PDC domain
> I've got a Redhat 7.1 server running samba-2.2.1a serving as a PDC for
> about 100 machines in teaching labs at a university.
> In general, the server works well. It is very stable and has no problem
> supporting 400+ users. As an added bonus, it also serves as a firewall
> and a dhcp server and provides the students with ssh/scp access to their
> home directories.
> The one major problem I'm having involves using Symantec Ghost 7
> Enterprise edition to image the Windows 2000 clients in the labs. I
> won't spend too much time explaining how this works, as only those
> familiar with Ghost will likely have any suggestions or care to read on.
> What happens is: when Ghost 7 Console re-images a client machine, it
> attempts to re-add it to the domain using a name and password given to
> Ghost when it is installed. This user exist on the Samba-PDC server, and
> has permission to create domain accounts.
> When the freshly imaged client machine comes back up, with the correct
> name and thinking it is in the correct domain, it gives an error of,
> roughly, "Failed to join domain. Bad parameter". I hit "ok" and the
> machine reboots. When the client comes up again, it still thinks it is
> in the domain. If I attempt to login to the domain, it says roughly,
> "Unable to logon to domain. Computer account is nonexistant or password
> is wrong". Of course, all of these machines already have accounts on the
> Samba-PDC server.
> The solution, up to this point, has been to remove each machine from the
> domain, reboot, put each machine back into the domain, providing a name
> and password for the samba-pdc that can do that, and reboot again. You
> can see how this could get old with 100 clients.
> I have seen Ghost 7 successfully put machines back into a domian that is
> run by a Win2K server, so it is not purely a matter of Ghost being
> Questions you might be able to help me with:
> 1. How is Ghost attempting to re-add these machines to the domain? If it
> is attempting to use user manager for domain style commands, I know that
> Samba-PDC does not support that. If it is doing something else, what is
> 2. Is Samba logging the attempts by Ghost to rejoin these machines to
> the domain? If so, where?
> 3. Is anyone doing this successfully? In other words, is it just me/my
> 4. Does anyone have any solutions/work-arounds for getting Ghost 7 and a
> Samba-PDC to play nice -- besides moving to a Win2K Server and just
> using the Samba machine as a file server?
> Any help or thoughts are much appreciated.
> Matt Lessem
Ing. Romy Perez Moreno
e-mail: romy at fenix.uam.mx, romy at correo.azc.uam.mx
tel: 5318 9067 / 5382-7157
More information about the samba-ntdom