@george1421 Thank you for your explanation! This makes sense and I was thinking of that same scenario with having more then one of same cloned disk in the same system. I tested most of our external applications and found no issues including ones that record or reference the UUID of the disk in some way and found no conflicts. As you said, the disk is attached to the “parent” record.

@Sebastian-Roth Thanks for the code reference, this does appear to be the function performing what I am referring to and I appreciate your honesty

Thank you again to both of you on your input! Tremendously appreciated.
I’ve found this to be a great community and hopefully I’ll be able to be give back in one way or another

Hello!

As of recently, I’m implementing FOG in our organization and overall it’s going really smooth! Every hurdle I’ve been able to find an answer, either here in the forums, wiki or the docs.

During testing, in deployment I noticed the UUID for the disk and all the partitions were being cloned from the image. I understand that this is by design of FOG and possibly most other disk cloning software, however are there any possible ramifications of having identical disk UUIDs on numerous machines?

We are an MSP, imaging for different companies and currently only dealing with Windows 10/11. Each deployment does have a unique system UUID and I’m only referring to the disk and partitions.
Our soon-to-be-replaced imaging solution does not clone these so each deployment have unique UUIDs, which is what got me wondering on the purpose/requirement of this (at least for a Windows system).

From what I was able to test I’m not finding any issues with this but figured I’d reach out before putting FOG into production.

Thank you for your time and any input you may have!