<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi,</div></div></div><div><blockquote type="cite" class=""><div class="">On 12 Mar 2018, at 16:17, Waite, Dick (External) <<a href="mailto:Dick.Waite@softwareag.com" class="">Dick.Waite@softwareag.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Many Thanks for the update Hernan,<br class=""><br class="">We do update our "mother" SLES's machine each month with "security" patches could we do that if they are not registered, do you allow "security" patch update with out being registered ? There are quite a number of "mothers”. </div></div></blockquote><div><br class=""></div><div>The only official and supported ways to retrieve our patches and updates are</div><div>directly thought SCC, via SMT/RMT or a SUSE Manager. So you need to register</div><div>your server to SCC, SMT or SUSE Manager.</div></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">We do run systemctl mask packagekit.service on the mothers to stop automatic updates. If the clone is not registered does this stop "zypper in some-need-function" running ?<br class=""></div></div></blockquote><div><br class=""></div>if not register to SCC/SMT/SUMA, well not have SUSE Channels available.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">Could you point me at a good Docu to read and understand what a SLES12 and SLES15 machine can do if it's not registered. Many of the clones only live a week or two... If we do registere them I can see the SCC filling up 'cos the good people are used to just deleting the clone when it's done it's task.<br class=""></div></div></blockquote><br class=""><div><div>Well I guess, you have all sort of processes to create and destroy clones and I</div><div>think registration and de-registration should fit perfectly into your processes. </div></div></div><div><div><br class=""></div><div>Regards,</div>--<br class="">Vincent Moutoussamy<br class="">SUSE Beta Program and SDK Project Manager</div></body></html>