SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Sidebar

Sponsor:

Would you like to sponsor this site?
Or buy me a beer?:


Recently Changed Pages:

View All Pages
View All Q Pages


View All Tags


Sign up for Q to post comments.





WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.


Terms And Conditions for Q users


Pages with comments

PageDateDiscussionTags
2019/06/22 10:36 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments

oes2registration

OES2 Registration

Introduction

This article is actually not written, it's mostly my bash history and some output. Thing is, after I installed Open Enterprise Server 2, I registered it. Well, at least, that's what I thought. I got an update source, applied all patches, rebooted (kernel update) and checked my eDirectory edition. It was still eDirectory 8.8 SP2 as it comes with the installation media. That's weird, because I knew there should be an eDirectory FTF 2 update, which cannot be applied manually, only through the channel. So something was wrong, and as it turned out, the graphical registration does not work so smoothly. Fortunately it appears to have happened more than once because there was a TID about it.

Current Situation

So this is the current situation:

OES3:~ # /usr/lib/zmd/query-pool products
 |product|SUSE_SLES_SP1|10.1-0|i686
 |product|OPEN_ENTERPRISE_SERVER|2|i686
i|product|SUSE_SLES_SP1|10.1-0|i686
i|product|OPEN_ENTERPRISE_SERVER|2|i686
 |product|SUSE-Linux-Enterprise-Server-SP2-migration|10-24|i386

My Open Enterprise Server and Suse Linux Enterprise Server are both installed. Which is good.

OES3:~ # rug sl

# | Status | Type | Name                  | URI
--+--------+------+-----------------------+----------------------
1 | Active | NU   | https://nu.novell.com | https://nu.novell.com

I have an update source called Novell. Which is good.

OES3:~ # rug ca

Sub'd? | Name                        | Service
-------+-----------------------------+----------------------
Yes    | SLES10-SP1-Updates          | https://nu.novell.com
       | SLE10-SP1-Debuginfo-Updates | https://nu.novell.com

I only have a update catalog for Suse Linux Enterprise Server, and not for Open Enterprise Server. Which is bad.

Fixing

As said before, it turns out that the GUI NCC registering procedure isn't always working properly. I had to re-register using the commandline: First remove some old data:

OES3:~ # rczmd stop
Shutting down ZENworks Management Daemon                              done

OES3:~ # rm /etc/zmd/secret /etc/zmd/deviceid

OES3:~ # rczmd start
Starting ZENworks Management Daemon                                   done

OES3:~ # rm /var/cache/SuseRegister/lastzmdconfig.cache

And re-register with Novell:

OES3:~ # suse_register -a regcode-sles=************** regcode-oes=************** -a email="emailaddress"

Note that the sles and oes code, and the email address as well should be known with Novell and there should already be a customer center entry. You can login with your novell account to obtain the codes. Alternatively you could evaluate Open Enterprise Server, in which case you also need these codes but you don't have to pay for them (yet).

New Situation

So now we've registered the right way there should be some updates waiting. But let's check first:

OES3:~ # rug sl
Waking up ZMD...Done

# | Status | Type | Name                  | URI
--+--------+------+-----------------------+----------------------
1 | Active | NU   | https://nu.novell.com | https://nu.novell.com

I still have an update source called Novell. Which is good.

OES3:~ # rug ca

Sub'd? | Name                        | Service
-------+-----------------------------+----------------------
Yes    | SLES10-SP1-Updates          | https://nu.novell.com
       | SLE10-SP1-Debuginfo-Updates | https://nu.novell.com
Yes    | OES2-Updates                | https://nu.novell.com

I now have a update catalog for Suse Linux Enterprise Server, and one for Open Enterprise Server. Which is good.

Now when I go to Yast → Software → Installation Sources I also see the new update source. And when I go to Yast → Software → Online Update I also see the new eDirectory edition patch:

OES3:~ # ndsstat
[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: OES3.****
Tree Name: TREE
Server Name: .CN=OES3.OU=****.
Binary Version: 20216.55
Root Most Entry Depth: 4
Product Version: eDirectory for Linux v8.8 SP2 [DS]

OES3:~ # /etc/init.d/ndsd stop
Executing customized settings before stopping the Novell eDirectory server...
Stopping Novell eDirectory server...
..............................                                        done
Executing customized settings after stopping the Novell eDirectory Server...
OES3:~ # /etc/init.d/ndsd start
Executing customized settings before starting the Novell eDirectory server...
Starting Novell eDirectory server...
                                                                      done
Executing customized settings after starting the Novell eDirectory server...
Novell eDirectory LDAP Server is listening on the TCP port.
Novell eDirectory LDAP Server is listening on the TLS port.

OES3:~ # ndsstat
[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf: OES3.****
Tree Name: TREE
Server Name: .CN=OES3.OU=****.
Binary Version: 20216.63
Root Most Entry Depth: 4
Product Version: eDirectory for Linux v8.8 SP2 [DS]

Resources

To read more about the registering procedure check the Novell documentation

You could leave a comment if you were logged in.
oes2registration.txt · Last modified: 2013/05/14 20:45 by sjoerd