The DHCP server on OES2 will ignore option 78 of DHCP if the DHCP is not set to be authoritative for that subnet.
To do so, you must modify the dhcp server object in iManager, under settings add Authoritative with setting value true. Then restart the DHCP server.
This will do the Trick
These are the commands you have to use to update a SLES10 OES2 sever by command line.
- First register your SLES10 by Novell
suse_register -a email=email_address -a regcode-sles=SLES_registration_code -a regcode-oes=oes2_registration_code - Confirm with the commands
rug sl
rug ca
if the registration is successful. You shoud see a link to nu.novell.com - Refresh the update list with the command
rug ref
- See what update are available
rug lu SLES10-SP1-Updates OES2-Updates - Update the server
rug up -t patch SLES10-SP1-Updates OES2-Updates - Repeat step 4 and 5 until there are no more patches available. Then reboot the server.
UPDATE
If you only see a SLES10 update channel do the following.
rczmd restart – this to make sure no wrong data is kept in cache
2. rug in -t product OPEN_ENTERPRISE_SERVER – solve the dependencies (if any) and accept.
3. rczmd restart – to make the Zenworks Management Deamon aware of the change.
4. rug products – to verify that OPEN_ENTERPRISE_SERVER is recognized as installed.
–+————————+———+———
i | SUSE_SLES_SP1 | 10.1-0 | add-on
i | OPEN_ENTERPRISE_SERVER | 2- | add-on
Run the Novell Customer Center configuration again. This time it should request a activation code for both SLES10 as OES2 and afterwards it should be possible to update both SLES10 and OES2 components.
Source: http://support.novell.com TID7000219
Last week I gave for the first time the course Implementing Novell Open Enterprise Server 2 for Linux (N3089) from Novell. Although there were only 2 students, it was a nice week.
At the end of the week, they where excited to start working with OES2.
The overall evaluation was pretty good (an 8). They found the course containing a lot of Linux beginning from scratch but I think it’s necessary to work with OES2.
Remark: It’s easier for Netware guy’s who have knowledge of Novell Services on Netware to learn Linux than for Linux guy’s to learn OES(2) Services.
When you use a different user than root to run the Groupwise agents under, some mail in the wpcout directory
still get end up there under user root and don’t get processed.
If you do a chmod root * then the mails get processed.
I disabled the user and run my agents again as root, while this is nog the situation you want.
Hope to test it on sp3 soon to see if the problem is fixed.