Hey everyone, I had a quick question about a situation that I think would cause AD and/or SCCM issues but couldn't really find much to back it up or prove otherwise.
I work for a school division and we occasionally have the odd computer hardware issue. We then take the hd and place it in a working machine and put the new computer back in the classroom to get them back up and running faster while we work on the defective machine. My question is, does a simple remove from domain/re-add to domain completely resolve any AD issues? Or does the machine have to be re-imaged through SCCM to make sure everything is fine?
I'm also curious if SCCM would have any issues with this machine now as the hardware ID/MAC is now different.
Any answers or direction would be appreciated, thanks!
*edit* We are using WinXP w/ SP3 on clients, Win 2003 on servers, and forest/domain level is 2003.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hey everyone, I had a quick question about a situation that I think would cause AD and/or SCCM issues but couldn't really find much to back it up or prove otherwise.
I work for a school division and we occasionally have the odd computer hardware issue. We then take the hd and place it in a working machine and put the new computer back in the classroom to get them back up and running faster while we work on the defective machine. My question is, does a simple remove from domain/re-add to domain completely resolve any AD issues? Or does the machine have to be re-imaged through SCCM to make sure everything is fine?
I'm also curious if SCCM would have any issues with this machine now as the hardware ID/MAC is now different.
Any answers or direction would be appreciated, thanks!
*edit* We are using WinXP w/ SP3 on clients, Win 2003 on servers, and forest/domain level is 2003.
Share this post
Link to post
Share on other sites