# Boot Parameters versus Registering with RMT **URL:** \ **Category:** SLES Install-Boot\ **Created:** [July 19, 2019, 2:38am UTC](https://forums.suse.com/t/boot-parameters-versus-registering-with-rmt/34191 "2019-07-19T02:38:04Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rich\_hanley](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rich\_hanley](https://forums.suse.com/u/rich_hanley)\ **Post date:** [July 19, 2019, 2:38am UTC](https://forums.suse.com/t/boot-parameters-versus-registering-with-rmt/34191/1 "2019-07-19T02:38:04Z")
Hi there, I’m just learning RMT and I’ve got a question. I’ve got an RMT Server running on SLES 15 SP1 (FQDN: [COLOR="#008000"][nsi-rmt.netsysint.net](http://nsi-rmt.netsysint.net)[/COLOR]). And I’m trying to install a SLES 12 SP4 server using RMT for the client’s product registration and repositories. When I specify `regurl=https://nsi-rmt.netsysint.net/` as a boot parameter when starting the installation, I see that the client obtains the certificate from nsi-rmt but then errors stating that no product repository can be found for SLES 12 SP4. However if I do the installation and don’t specify any boot parameters and select to register against a local RMT server and specify the same URL as on the regurl parameter, it works. I thought that using the “regurl=” parameter and specifying that same RMT server on the Registration installation screen were different ways to do the same thing. Am I completely off-base here - are they not used for the same purpose? Thanks Rich… ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [July 19, 2019, 3:44am UTC](https://forums.suse.com/t/boot-parameters-versus-registering-with-rmt/34191/2 "2019-07-19T03:44:13Z")
[QUOTE=rich\_hanley;58141]Hi there, I’m just learning RMT and I’ve got a question. I’ve got an RMT Server running on SLES 15 SP1 (FQDN: [COLOR="#008000"][nsi-rmt.netsysint.net](http://nsi-rmt.netsysint.net)[/COLOR]). And I’m trying to install a SLES 12 SP4 server using RMT for the client’s product registration and repositories. When I specify `regurl=https://nsi-rmt.netsysint.net/` as a boot parameter when starting the installation, I see that the client obtains the certificate from nsi-rmt but then errors stating that no product repository can be found for SLES 12 SP4. However if I do the installation and don’t specify any boot parameters and select to register against a local RMT server and specify the same URL as on the regurl parameter, it works. I thought that using the “regurl=” parameter and specifying that same RMT server on the Registration installation screen were different ways to do the same thing. Am I completely off-base here - are they not used for the same purpose? Thanks Rich…[/QUOTE] Hi According to the documentation, yes 😉 So you can browse here [https://RMT\_SERVER/](https://RMT_SERVER/) ok? Do you see the subdirectories including a ‘product’ one for SLE 12 SP4? ---
**Author:** ![rich\_hanley](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rich\_hanley](https://forums.suse.com/u/rich_hanley)\ **Post date:** [July 19, 2019, 8:48pm UTC](https://forums.suse.com/t/boot-parameters-versus-registering-with-rmt/34191/3 "2019-07-19T20:48:19Z")
Thanks for the reply Malcolm! If I browse to [COLOR="#008000"][https://nsi-rmt.netsysint.net](https://nsi-rmt.netsysint.net)[/COLOR] I get connected to [COLOR="#008000"]nsi-rmt[/COLOR]; however the page is blank. But I can browse down into [COLOR="#008000"]repo/SUSE/Products/SLE-SERVER/12-SP4/x86\_64/product[/COLOR] and see the directories for [COLOR="#008000"]noarch[/COLOR], [COLOR="#008000"]repodata[/COLOR], and[COLOR="#008000"] x86\_64[/COLOR] (which contains all the rpms). What I don’t understand is why I can go through the YaST based install (using no boot parameters) get to the registration screen and enter simply: [COLOR="#008000"][https://nsi-rmt.netsysint.net](https://nsi-rmt.netsysint.net)[/COLOR] and it works. I don’t understand how the value for the regurl boot parameter seems to be much more “literal” than what I specify at the YaST Registration Screen? Thanks, Rich… ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [July 20, 2019, 4:15am UTC](https://forums.suse.com/t/boot-parameters-versus-registering-with-rmt/34191/4 "2019-07-20T04:15:36Z")
[QUOTE=rich\_hanley;58150]Thanks for the reply Malcolm! If I browse to [COLOR="#008000"][https://nsi-rmt.netsysint.net](https://nsi-rmt.netsysint.net)[/COLOR] I get connected to [COLOR="#008000"]nsi-rmt[/COLOR]; however the page is blank. But I can browse down into [COLOR="#008000"]repo/SUSE/Products/SLE-SERVER/12-SP4/x86\_64/product[/COLOR] and see the directories for [COLOR="#008000"]noarch[/COLOR], [COLOR="#008000"]repodata[/COLOR], and[COLOR="#008000"] x86\_64[/COLOR] (which contains all the rpms). What I don’t understand is why I can go through the YaST based install (using no boot parameters) get to the registration screen and enter simply: [COLOR="#008000"][https://nsi-rmt.netsysint.net](https://nsi-rmt.netsysint.net)[/COLOR] and it works. I don’t understand how the value for the regurl boot parameter seems to be much more “literal” than what I specify at the YaST Registration Screen? Thanks, Rich…[/QUOTE] Hi I would have thought it needs the extra part of the url (repo/SUSE/Products/SLE-SERVER/12-SP4/), maybe a bug?