# SM3 client installation via GUI or command-line **URL:** \ **Category:** SUSE Multi Linux Manager\ **Created:** [March 31, 2017, 8:01pm UTC](https://forums.suse.com/t/sm3-client-installation-via-gui-or-command-line/29625 "2017-03-31T20:01:35Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![lychina](https://avatars.discourse-cdn.com/v4/letter/l/97f17d/32.png) [@lychina](https://forums.suse.com/u/lychina)\ **Post date:** [March 31, 2017, 8:01pm UTC](https://forums.suse.com/t/sm3-client-installation-via-gui-or-command-line/29625/1 "2017-03-31T20:01:35Z")
Hi. Any preference for installing clients under SM3 via the GUI (Salt-\>Bootstrapping) or via the command-line (zypper ar ; zypper in salt-minion; edit /etc/salt/minion; systemctl start salt-minion)? I have decided to install clients via the command-line because it is easy to build into the clone process under VMware and, by simply running “systemctl enable salt-minion” in the VM template, cloned systems will magically appear in Salt-\>Onboarding when they boot for the first time. However, by using the GUI, you are able to assign activation keys to systems. Is there a way to do this after you install via the command-line as documented in section 5.5 of the “Getting Started Guide”? ---
**Author:** ![lychina](https://avatars.discourse-cdn.com/v4/letter/l/97f17d/32.png) [@lychina](https://forums.suse.com/u/lychina)\ **Post date:** [March 31, 2017, 9:18pm UTC](https://forums.suse.com/t/sm3-client-installation-via-gui-or-command-line/29625/2 "2017-03-31T21:18:15Z")
Looking at /etc/salt/minion.d/susemanager.conf, I found the answer. Rather than modifying /etc/salt/minion with the correct master: entry, the GUI installation method creates /etc/salt/minion.d/susemanager.conf with the following: [CODE]master: grains: susemanager: activation\_key: [/CODE] I will do the same for manual installation.