I go to the download page and get SLES12SP1 for i86_64. On the page I see
the registration code. (I am logged in to SUSE, if this is neccessary.)
After the install in a VM w/o registration (belongs to the proxy*) I try to
register with ‘yast scc’. But I get a message similar to ‘Unkown
registration code’.
How is the correct way to install SLES12-Eval including registration to get
the lastest patches?
*During the installation it is not possible to register because there is no
possibility to configure a proxy. Maybe this could be a remark during a beta
test
I go to the download page and get SLES12SP1 for i86_64. On the page I see
the registration code. (I am logged in to SUSE, if this is neccessary.)
After the install in a VM w/o registration (belongs to the proxy*) I try to
register with ‘yast scc’. But I get a message similar to ‘Unkown
registration code’.
How is the correct way to install SLES12-Eval including registration to get
the lastest patches?
*During the installation it is not possible to register because there is no
possibility to configure a proxy. Maybe this could be a remark during a beta
test
Bernd[/QUOTE]
the last time I tried (with a production key, not eval), I had to register the key at scc.suse.com before using that same key during server registration. Sorts of an pre-activation… I hadn’t have to do so with earlier installs, so things may have changed either in SCC or in SLES12.
jmozdzen wrote on Freitag, 29. April 2016 13:04 in
suse.support.server.patches-updates :
[color=blue]
Hi Bernd,
Bernd;32411 Wrote:[color=green]
Hi,
I go to the download page and get SLES12SP1 for i86_64. On the page I
see
the registration code. (I am logged in to SUSE, if this is neccessary.)
After the install in a VM w/o registration (belongs to the proxy*) I try
to
register with ‘yast scc’. But I get a message similar to ‘Unkown
registration code’.
How is the correct way to install SLES12-Eval including registration to
get
the lastest patches?
*During the installation it is not possible to register because there is
no
possibility to configure a proxy. Maybe this could be a remark during a
beta
test
Bernd[/color]
the last time I tried (with a production key, not eval), I had to
register the key at scc.suse.com before using that same key during
server registration. Sorts of an pre-activation… I hadn’t have to do
so with earlier installs, so things may have changed either in SCC or in
SLES12.
Regards,
Jens
[/color]
Now, ~2 hours later, the same RegCode (yast was not closed meantime) runs
… !!!
