New Hard Drive, New SID?

[irbk]

Long story short, I've got a laptop hard drive that's on it's last legs. It still runs, so I think that I can get an image out of it (using ImageX), so that I don't have to "rebuild" it. My question is this, I've got a new hard drive. I'm going to apply the image created by ImageX from the old hard drive onto the new drive. I've used ImageX before, so this shouldn't be an issue. What I'm not sure is if this new hard drive will cause the system to create a new SID. Normally, when I use ImageX, I also use Sysprep to reseal the system and regenerate SID's (because normally, I use ImageX to create an image to be used on many systems, and they would each need there own SID) however, because I'm not creating multiple systems from this 1 image, I just want to basically clone the drive that's going bad, I'm not sure if I need to use Sysprep or not. I hope I'm making some since.
Thanks an advance.

 

[kjv1611]

There's some reference in this article regarding SIDs and cloning:

http://en.wikipedia.org/wiki/Disk_cloning

From what I'm reading, I'd say no - you shouldn't have to use sysrep or anything of the sort for a strait disk clone, assuming no other hardware changes at the same time. It sounds like that is only necessary when there are major changes, such as the motherboard, graphics card, etc. The data storage device (HDD/SSD) is not really considered a major change, as far as that type thinking goes.

Of course, I've never bothered with it at SID at all, directly, so I am only going based off of what the article stated, as well as my own experience replacing hard drives in desktop PCs and laptops.

--

"If to err is human, then I must be some kind of human!" -Me

 

[Lemon13]

no prob at all, a sid is not hardware related

http://en.wikipedia.org/wiki/Security_Identifier

so it will not change by cloning. thats the prob when you use a master image to build several pc with, then you need to change the sid

M. Knorr

MCSE, MCTS, MCSA, CCNA