On Mon, Dec 2, 2013 at 3:28 PM, Michael B. Smith <[email protected]> wrote: >> [using ImageX to clone a hard disk] > > Yes, that would be completely expected for permissions to be horked.
Can you expand on how/why this would be expected to hork the permissions, please? I've currently got my minion looking into using ImageX to copy/clone hard disks (like Ghost or partimage), for purposes including deployment, backup, and maintenance. But if that's going to result in horkage, it's not going to work for most things. -- Ben Complete thread for reference: On Mon, Dec 2, 2013 at 3:28 PM, Michael B. Smith <[email protected]> wrote: > Yes, that would be completely expected for permissions to be horked. > > (And yes, that's a common technical term I use.) > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Joseph L. Casale > Sent: Monday, December 2, 2013 3:24 PM > To: [email protected] > Subject: [NTSysADM] RE: Migrating a Windows 7 wkst to another hard drive > >> Be a bit more specific about what you did. > > I attached the SSD as the primary drive, moved the old HDD to secondary, > booted with PE and used diskpart to clean,create,set active then assign a > letter on the SDD > > I then ran: `imagex /capture d: c:\install.wim "System" /compress fast ` > where c is the SSD and d was the old disc. > > After which I applied the image, as the layout didn't change no boot changes > were needed. > > It seemed like SYSTEM took ownership of everything, office was broken for > example, lots of issues that all resolved with fixing permissions, I lost > patience and swapped the old disc back... > > Thanks! > jlc > > >
