# SUSE Manager 4 - register system itself ? // Updates ?

**URL:** <https://forums.suse.com/t/suse-manager-4-register-system-itself-updates/34446>\
**Category:** SUSE Multi Linux Manager\
**Created:** [October 8, 2019, 4:40pm UTC](https://forums.suse.com/t/suse-manager-4-register-system-itself-updates/34446 "2019-10-08T16:40:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![raymondjt2](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/raymondjt2/32/10432_2.png) [@raymondjt2](https://forums.suse.com/u/raymondjt2)\
**Post date:** [October 8, 2019, 4:40pm UTC](https://forums.suse.com/t/suse-manager-4-register-system-itself-updates/34446/1 "2019-10-08T16:40:38Z")

</div>

Hi,  
new installation of suse manager 4.0.2 and trying so setup a training / lab environment.

If we try to register the manager system itself, we get an error message.

Dr. Goolge told me about:

zypper ref && zypper update && zypper update

Ok. Some packages are updated that way.

What we are looking for, why or how can the SUSE manager 4 system be registered as a system and included into a patching / salt solution?

THX  
Raymond

---

<div class="post-metadata">

**Author:** ![strahil-nikolov-dxc](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@strahil-nikolov-dxc](https://forums.suse.com/u/strahil-nikolov-dxc)\
**Post date:** [October 10, 2019, 6:09am UTC](https://forums.suse.com/t/suse-manager-4-register-system-itself-updates/34446/2 "2019-10-10T06:09:41Z")

</div>

If you have read the bootstrap scripts, there is a check if the registered system is the SuSE Manager itself and bootstrap fails to register to itself.That is intentional and I don’t see why would you register it to itself.  
Use direct SCC subscription instead!