Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 13 subscribers
  • Views 11366 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Gold image methods clarification

pat-sc8383

I appreciate this has already effectively been asked in the following post.

 set up gold image to be deployed 

The case I'm looking to use this on is for a VMware template, so having the server template VM with the goldimage option. When new VMs are deployed from this template and get sysprep etc. with a rename as part of that (expected to happen within the timeout period). Then my understanding is that when they register in Sophos Central they will be seen as NEW devices with no link back to that original templated device in Central. Is that correct? So they would be the same as if someone had just created a new server VM and installed Sophos Central from scratch? For this use case I'm not doing any VDI, or non-persistent related work, it is for simple server VM deployment use (that will be live for many years).

Please can someone confirm that after a successful rename and new identity, that the server then doesn't do any "check for identity" timeout? That this is limited to just the template "goldimage" device?

Or given the above use case, would I be better using the older scripted method, rather than the "--goldimage" option method?

Also I see in the post above, the statement "The older content remains for reference purposes should customers have a need for it." - it would be useful if KB's and pages on docs.sophos.com could have both the last modified date AND the created date. This way it is easy to see whether you are looking at an old method that has recently had an update/modification to the content, or just newer content in general. Thanks.



This thread was automatically locked due to age.
Parents
  • 0

    Been doing some testing - I think I've answered some of my own questions.  It does look like they do get a new identity OK with no link back.

    For the "after a successful rename and new identity, that the server then doesn't do any "check for identity" timeout" question - in the log it shows as "Endpoint cloned from gold image named SERVERNAME" and that is the last time it references it.

    However I have now noticed that the way tamper protection is dealt with (at least for me) needs more specific guidance.  It is this that has caused me most trouble - with the "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer." message in the majority of cases, as tamper protection has ended up being back on during those initial boots.  Still doing some more testing and will post back later.

Reply
  • 0

    Been doing some testing - I think I've answered some of my own questions.  It does look like they do get a new identity OK with no link back.

    For the "after a successful rename and new identity, that the server then doesn't do any "check for identity" timeout" question - in the log it shows as "Endpoint cloned from gold image named SERVERNAME" and that is the last time it references it.

    However I have now noticed that the way tamper protection is dealt with (at least for me) needs more specific guidance.  It is this that has caused me most trouble - with the "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer." message in the majority of cases, as tamper protection has ended up being back on during those initial boots.  Still doing some more testing and will post back later.

Children
No Data
Unfiltered HTML