I build and sell PC's to small businesses.
As an OEM System Builder, you are being paid to build & support your builds.
My Computer
At a glance
ME/XP/Vista/Win7
- OS
- ME/XP/Vista/Win7
I build and sell PC's to small businesses.
One of the benefits to the way Microsoft has re-written the driver model of the OS (since Vista) and changed sysprep is so you *can* clone to dissimilar hardware. You just have to do it right (JIT driver injection, build your template machine into a VM, use Microsoft's tools to capture/distribute the OS, etc.). If you don't do it right, you can (and likely will) end up with an OS that doesn't work once re-applied to other hardware (especially older imaging/driver management tools designed around XP - these always seem to break imaging, and they're just not necessary anymore). Also, you *will* need to re-activate the OS, and provide a valid product key, no matter what type of OS it is.You cannot IMAGE/CLONE to dis-similar hardware which is a lot of the things. I am being told to do in 2-6. You JUST CANNOT. YOU MUST UNDERSTAND THIS. Please see the other post.
Anything that requires a driver to survive sysprep will require you to do things a very specific way (persistalldeviceinstalls). I don't know for sure what specifics you're trying to achieve here (if anything - again, it's still not 100% clear what you are and aren't doing, and what specifically your issues are. If I missed them in a previous post, I do apologize.I am asking for a way to install a master to dis-similar hardware. To state it another way, my question involves hardware and software. Not licenses. I will properly license my PCs.
This can be done, but it's not as simple as install, inject a gigantic driver pack, sysprep, and reboot anymore - nor should it be. If you're comfortable with XP imaging, you're in for a somewhat rude awakening (especially if you skipped Vista at all), unfortunately - things have changed (for the better, but you'll have a learning curve).The problem at this point is my question of HOW TO perform a MASTER INSTALL and then I will properly license it. I haven't even gotten to the license installation yet. My problem is dis-similar hardware and how to properly and legally install things.
Be careful with your attitude - folks are trying to help, and in reading this thread, I came to the same sorts of conclusions others did about what was and wasn't working until I read between the lines. I can help, but you need to calm down a bit. You're probably a little (or a lot) frustrated, and I can empathise, but you have to keep a level head if and when possible, especially on the internetCould someone else please step in and put this thread back on proper course?
.Good question. However, I did re-read your first post, and it's just not thick on the details. However, instead of beat you up on it, I'll just answer the questions you posed in order, and wait for your response:How did this thread get this way?
Yes, indeed. If you're doing onesie-twosie customer installs (rather than gigantic enterprise rollouts), I recommend using MDT for this.Is this possible? How?
There are software packages (like Macrium and Acronis) that do this, but they are in the mold of backup/disaster recovery imaging, rather than business rollout image maintenance. Also, given the way they work, they can sometimes have issues with imaging to dissimilar hardware from the original source, keeping the image updated, etc. Make no mistake that there's nothing wrong with either of those software packages, but they really are designed for home use or business disaster recovery (and have to be licensed as such if you do - very expensive per seat that way), rather than a more business scenario (images to put on multiple machines, keeping the image updated easily, etc). I still suggest MDT for this. It's free, uses Microsoft's tools, is supported (officially) by Microsoft, and the tool is not that difficult to use and understand once you take the time to learn it.I've seen a few references to commercial software that does this. Recommendations?
.Windows 7 creates a 100MB partition during the install process, unless you stop it from doing so. It is hidden, so you do not see it and certainly you won't have a C drive with 100MB. This partition is for the bitlocker feature.
If your original (donor) computer had Windows 7 installed and it created this partition, and you try to restore the image to a computer without the partition, you will most certainly have problems since Windows will be looking for this partition.
----------------------------------------------------------Thank you all.
I just wish MS had told me all of this
the first time I asked them.
Steve Broshears, thanks again ...