I just started thinking more about the question. If the drive is going to replace another drive in the same box then, clonning would be the best option, I've done it múltiple times without issues, even AD account was fine. No sysprep though. But if there are other drives in the same system, I think you would encounter acl issues. Even if you were to switch the cloned drive to another h/w and precure the old one will work On Dec 6, 2013 5:16 PM, "elsalvoz" <[email protected]> wrote:
> I would use a climbing tool versus a file base tool which imagex and dism > are. There are some free clonning tools you can use, ghost would do the > tick but is pay tool. > On Dec 6, 2013 11:55 AM, "Art DeKneef" <[email protected]> wrote: > >> Working on this stuff right now creating a new base image of Windows 8.1 >> Pro >> and Office 2013 Home & Business. >> >> (1) It's been a long time but I seem to remember that the one time the >> OOBE >> was interrupted, when it started again it started from the beginning. But >> this was with XP. I haven't had that happen with Windows 7 or 8 yet. I >> think >> it might depend on where the OOBE got interrupted whether the new SID is >> created. Completing the OOBE should generate a new SID. >> >> (2) To keep the same SID I wouldn't run Sysprep. Plus what switches you >> use >> matter here also. Here I think we have to define what needs to be >> accomplished. Is it a backup image of the PC, a recovery image for the PC >> or >> a base image for a brand new computer. >> >> (3) Define damaged. ImageX makes a copy of what's on the disc. >> >> As a side note I wouldn't use ImageX anymore as Microsoft has deprecated >> it >> in favor of DISM. Get and use the new Windows 8.1 Assessment and >> Deployment >> Kit for the latest version of Windows PE and DISM. >> >> Art >> >> -----Original Message----- >> From: [email protected] [mailto: >> [email protected]] >> On Behalf Of Ben Scott >> Sent: Friday, December 6, 2013 10:06 AM >> To: [email protected] >> Subject: Re: [NTSysADM] RE: Migrating a Windows 7 wkst to another hard >> drive >> >> On Fri, Dec 6, 2013 at 8:32 AM, Michael B. Smith <[email protected]> >> wrote: >> > If you don't go through the full OOBE, then you'll get a new SID and >> > the new SID won't be in any of the old ACLs. Instant horkage. >> >> OK... I understand how the PC getting assigned a new SID (leaving the >> old >> SID owning everything in the filesystem) would hork effective permissions. >> >> But, can you please clarify: >> >> (1) To confirm: If one does *NOT* complete the full >> Out-Of-Box-Experience >> process, then a new SID will be generated? But if one *DOES* complete the >> full Out-Of-Box-Experience process, a new SID will *NOT* be generated? >> That >> seems backwards to me. >> >> (2) Thus, to *keep* the same SID, one should run SYSPREP before creating >> the image, and then allow OOBE to complete upon applying the image? >> >> (3) As a corollary, if the existing installation is damaged somehow, >> preventing one from running SYSPREP, ImageX cannot be used to accurately >> preserve the system before attempting repairs? >> >> -- Ben >> >> >> >> >>
