Imaging Rights - Windows - Looking for clarification
-
You may be allowed to do a one to one image to a unique image for each machine. That's very possible, I'm not sure there. But reimaging from a standard image is exclusive to VL.
-
You answered your own question in the first post. I am not sure what the heck your issue it..
First the definition of imaging.
@DustinB3403 said:
Q: What are "reimaging rights"?
A: Reimaging is the copying of software onto multiple devices from one standard image.@DustinB3403 said:
OEM-Specific Information
Reimaging is the copying of software onto multiple devices from one standard image.now on to OEM
snip
All of that basically said you can use original OEM of customized OEM images to resinstall only on the same hardware that the OEM image was originally used used on. AKA a 1 to 1.
-
@DustinB3403 said:
The similarity is that the machine is back to an OEM state.
How does it matter how it go to that state.
It doesn't - how you get an OEM image back on a machine is irrelevant. but doing so has NOTHING to do with reimaging rights, because you are not reimaging, you are reinstalling the OEM stuff.
-
The whole idea of Imaging Rights is the use of VL media deployed to multiple machines. If you are still using the OEM media, you're not using imaging rights.
And as JB said, you can deploy/image/reinstall the OEM supplied software to the hardware it came with however you want.So onto your other question - why would you use FOG to deploy OEM images to a machine? This seems like a waste of time. When using FOG, you will more than likely be using VL media to deploy images.
-
The contention (at least on SW) has always been how you install said ISO to a machine. I've always said, you can deploy an OEM Image (which in my opinion means what came with the device when you bought it) to the machine without any legal issue, in any way that you want.
So I've always been correct, if you guys agree with me.
The only trouble comes in if you ever change that image, that you legally aren't able to use the OEM product key.
-
@DustinB3403 said:
The contention (at least on SW) has always been how you install said ISO to a machine. I've always said, you can deploy an OEM Image (which in my opinion means what came with the device when you bought it) to the machine without any legal issue, in any way that you want.
This may or may not be true. What is important is that it is not considered related to reimaging rights.
-
@DustinB3403 said:
The only trouble comes in if you ever change that image, that you legally aren't able to use the OEM product key.
Not sure if there is an issue there either. I know how reimaging works, I am unclear how OEM installs are allowed as I never do them (reimaging is just too valuable.)
-
I'm curious if you aren't allowed to update the image with windows security updates.
Technically, you'd be changing the image, but for security reasons.
I wonder if there are any loopholes...
-
@DustinB3403 said:
I'm curious if you aren't allowed to update the image with windows security updates.
I believe that you are. But... why? That is a lot of work for a one to one deploy.
-
@DustinB3403 said:
I'm curious if you aren't allowed to update the image with windows security updates.
Technically, you'd be changing the image, but for security reasons.
I wonder if there are any loopholes...
Let's step back and think at the goal level. What is it you are trying to accomplish?
-
Restore a computer an a workable state.
Conditions being, that I don't have to sit through 6 hours of windows updates.
-
@DustinB3403 said:
Restore a computer an a workable state.
Conditions being, that I don't have to sit through 6 hours of windows updates.
Why would you not use imaging rights for that? So cheap, would pay for itself after the third machine easily.
-
-
@scottalanmiller said:
@DustinB3403 said:
Restore a computer an a workable state.
Why not use backups?
Not sure, guess I've never thought about it in that light. But I've always just restored (imaged) a machine or purchased a license for Windows if it needed it.
How would you build a deployable image with a backup. Generally it doesn't make an ISO.
-
@DustinB3403 said:
But I've always just restored (imaged)
Stop stating it like that. If you are using the restore ISO, you are neither restoring nor imaging, you are installing. You know that imaging doesn't mean this at all, this is very confusing both to us and I think to you to try to push this word where it has no place.
-
@DustinB3403 said:
How would you build a deployable image with a backup. Generally it doesn't make an ISO.
Use a bare metal restore tool. You need to take image backups to do a bare metal restore. It's all about planning.
I'd never do this, though, SO easy to get imaging rights and do it so much better.
-
@scottalanmiller said:
@DustinB3403 said:
But I've always just restored (imaged)
Stop stating it like that. If you are using the restore ISO, you are neither restoring nor imaging, you are installing. You know that imaging doesn't mean this at all, this is very confusing both to us and I think to you to try to push this word where it has no place.
Sorry.
-
Free Bare Metal Backup and Restore for Windows:
-
@DustinB3403 said:
Generally it doesn't make an ISO.
Only because you are using the wrong tools for the job
-
My definition of Imaging is the act of restoring a computer through any automated method.
So it's difficult to let go of that mindset.
But building an image seems to be a completely separate process, albeit the act of installing it is where I've had contentions.
