Hi, At our campus we have ~40 machines. If a new program is needed we install it on a single machine and replicate this one to the others. The whole process is automated: (Wake-On-LAN) (with pxe) booting a kernel via grub. booting a minimal ram based linux and doing: netcat server port > /dev/hda If we send a WOL packet the restore process starts. The problem is that we have to rejoin each machine after. So my question is: where WinXP stores this information? Now I know the way howto mount NTFS RW (with captive: http://www.jankratochvil.net/project/captive/ ) And howto manipulate the registry: http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html The only question: where windows stores this information? In the registry or in a file? I want to backup that information at the start of the backup and write back after the restore completes. Any help would be appreciated. -- cstamas
On Sat, Mar 13, 2004 at 12:17:01AM +0100, Csillag Tamas wrote:> Hi, > > At our campus we have ~40 machines. If a new program is needed we > install it on a single machine and replicate this one to the others. > > The whole process is automated: > (Wake-On-LAN) (with pxe) booting a kernel via grub. > booting a minimal ram based linux and doing: netcat server port > /dev/hda > If we send a WOL packet the restore process starts. > > The problem is that we have to rejoin each machine after. > > So my question is: where WinXP stores this information? > Now I know the way howto mount NTFS RW (with captive: > http://www.jankratochvil.net/project/captive/ ) > And howto manipulate the registry: > http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html > > The only question: where windows stores this information? > In the registry or in a file? > I want to backup that information at the start of the backup and write > back after the restore completes. > > Any help would be appreciated.If you are ghosting your machines like that, you have bigger problems. Like what each machines' name is, what it's sid is and the like. however, if it is a Samba DC, you can just restore the 'old' password to the DC at the same time. Andrew Bartlett
On 03/15, Clint Sharp wrote:> On Mon, 15 Mar 2004, Csillag [iso-8859-2] Tam?s wrote: >[...]> > The machine's sid only changes if you run a program to change it, > otherwise it will inherit the SID of the ghosted machine. We use NewSID > from Sysinternals (http://www.sysinternals.com/), but GhostWalker which > comes from ghost or several other packages exist to do the same thing. > Having multiple machines with the same SID on your domain will cause very > unusual problems :).Can you give me some examples? I am really interested. I use ldap as a backend, here is a machine account. I do not undestand how can it work in the domain if the machines sid does not changes accordingly (on a particular machine). dn: uid=sucker$,ou=machines,dc=itk,dc=ppke uid: sucker$ sambaSID: S-1-5-21-1628963623-43893491-1455040052-181004 sambaPrimaryGroupSID: S-1-5-21-1628963623-43893491-1455040052-181005 displayName: sucker sambaPwdCanChange: 1063609369 sambaPwdMustChange: 2147483647 sambaLMPassword: 6B77AF665E0B4665A9A5F808568734A4 sambaNTPassword: 6B77AF665E0B4665A9A5F808568734A4 sambaPwdLastSet: 1063609369 sambaAcctFlags: [W ] objectClass: sambaSamAccount objectClass: account structuralObjectClass: account entryUUID: c251de74-6c14-1027-8621-f081c87e167e creatorsName: cn=admin,dc=itk,dc=ppke createTimestamp: 20030826132718Z entryCSN: 2003091507:02:27Z#0x0001#0#0000 modifiersName: cn=admin,dc=itk,dc=ppke modifyTimestamp: 20030915070227Z (This is a fake entry) Any ideas? -- cstamas