Your SlideShare is downloading. ×
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply



Published on

Novell Brainshare 2010 Amsterdam

Novell Brainshare 2010 Amsterdam

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Unique nameing SDIDIAG Imanger Plugin PKI
  • Bonding (Laver 2) vs. Netware Teaming (Layer 3) Be aware of spanning tree algorithms
  • After about 1 hour !!
  • LUM Config: - Convert lower -> Converts users to lower case for Linux box if in Edir some ore upper and some are lower - persistent search disable - user cache only if eg. Backup software does not query into edir for the owner of files - preferred servers
  • /dnsnames for iPrint to convert used IP addresses of printers do dns names -> Problem after migration to OES2 the workstations still want to print to the ipp:// address !! - disable quota in nss /noquota... for the migration (100MB quota on directory -> but 10GB already in there -> so you can't migrate due to the quota limit if parameter not used)
  • Transcript

    • 1. Migrating Novell ® Open Enterprise Server from NetWare ® to Linux Chris Beckett and Volkmar Ruzicka Technical Consultant / Technical Consultant NDS8 / NetAgents [email_address] / [email_address]
    • 2. Hot Lab Agenda <ul><li>About Your Presenters
    • 3. Lab Scenario / Migration Options
    • 4. Tenets of a Successful Consolidation
    • 5. Pre-Migration Checklist / Pre-Flight Checks
    • 6. Building The Target Server / NetWare ® vs Open Enterprise Server Linux
    • 7. Services Ported To Linux / Managing Your Open Enterprise Server
    • 8. Linux User Management – When/Why?
    • 9. Using The Migration Tool
    • 10. Configure New Services on Open Enterprise Server 2
    • 11. Wrap Up / Question and Answer </li></ul>
    • 12. About Your Presenters
    • 13. About Your Presenters <ul><li>Chris Beckett </li><ul><li>Technical Consultant at NDS8, Novell Platinum Partner
    • 14. Over 14 years Novell ® products experience
    • 15. Specialised in Open Enterprise Server, NetWare ® , GroupWise ® , ZENworks ® </li></ul><li>Volkmar Ruzicka </li><ul><li>Technical Consultant
    • 16. Over 22 years Novell products experience
    • 17. Specialised in GroupWise, NOESL Clustering BlackBerry Enterprise Server </li></ul></ul>
    • 18. Lab Scenario / Migration Options
    • 19. Lab Scenario <ul><li>OH-LABS Tree </li><ul><li>Single NetWare ® 6.5 SP8 server </li><ul><li>Master replica holder for the tree
    • 20. Tree Certificate Authority
    • 21. SYS and DATA NSS volumes
    • 22. Several Novell ® products running on this server </li><ul><li>FTP
    • 23. iPrint
    • 24. NetStorage
    • 25. QuickFinder
    • 26. DNS/DHCP
    • 27. Novell Storage Services ™ and eDirectory ™ (of course!) </li></ul></ul></ul></ul>
    • 28. Lab Scenario FS1 NetWare ® 6.5 SP8 eDirectory ™ 8.7 FS2 Open Enterprise Server 2 SP2 eDirectory 8.8
    • 29. Migration Options
    • 30. Migration Options <ul><li>Migration Tool </li><ul><li>Transfer ID process – one to one server “swap”
    • 31. Consolidation – many to one server
    • 32. GUI console with step by step guide
    • 33. Installed with Open Enterprise Server 2 SP2, no separate download required
    • 34. Step by step process, with rollback possible in case of failure </li></ul><li>Other tools ? </li><ul><li>Command line tools, JRBUtils, scripted installations
    • 35. SCMT only supports NetWare ® /NT/2000/2003 to NetWare </li></ul></ul>
    • 36. Migration Options <ul><li>Migration Tool </li><ul><li>This lab concentrates on the lab tool, using the “Transfer ID” process
    • 37. GUI makes the process easy to follow, with options to re-do steps, should they fail
    • 38. Tool is run from the target (Open Enterprise Server 2) server console </li></ul><li>Lab assumptions </li><ul><li>Familiarity with Novell ® core Open Enterprise Server product stack (iPrint, Novell Storage Services ™ etc)
    • 39. Basic knowledge of Linux (GNOME desktop) </li><ul><li>Directory structure (/var /opt /etc)
    • 40. Familiarity with the Open Enterprise Server 2 installation process </li></ul></ul></ul>
    • 41. Tenets of a Successful Consolidation
    • 42. Tenets of a Successful Consolidation <ul><li>Step 1: Prepare Your Environment
    • 43. Step 2: Plan Your Migrations
    • 44. Step 3: Create a Server Build Process
    • 45. Step 4: The First Server
    • 46. Step 5: All Other Servers
    • 47. Step 6: Cleanup and Decommission </li></ul>
    • 48. Step 1: Prepare Your Environment <ul><li>All servers should be running a supported OS </li><ul><li>NetWare ® 5.1 sp8, or NetWare 6.5 sp7/8, or Open Enterprise Server Linux 1 sp1 </li></ul><li>Novell ® eDirectory ™ should be or 8.8+ on ALL servers
    • 49. Verify all software in use is compatible with eDirectory 8.8 </li><ul><li>Novell ZENworks ® 2.x, Identity Manager 3.x, no IPX, etc. </li></ul><li>Perform a complete eDirectory health check
    • 50. Review your Time Synchronisation, check all Servers
    • 51. Are all Network Printers at least NDPS or iPrint connected
    • 52. Clean up stale login scripts
    • 53. Delete stale data
    • 54. Test your Backup Software on the target platform </li><ul><li>To be able to restore after the migration </li></ul></ul>
    • 55. Step 2: Plan Your Migrations <ul><li>Setup a consolidation plan </li><ul><li>Map source Servers / Services to Target (4:1 average consolidation)
    • 56. Consolidate SLP, LDAP, and replica servers </li></ul><li>Create a sequence for servers and services </li><ul><li>Certificate authority and LDAP should be first to move
    • 57. Start with utility servers that have redundancy (replica, ldap, etc.)
    • 58. Move smaller work group server next as a pilot
    • 59. SLP DA services should be last to move
    • 60. Finish with critical file and print servers </li></ul></ul>
    • 61. Step 2: Plan Your Migrations (continued) <ul><li>End User – Changes on the Client Side </li><ul><li>Login scripts </li><ul><li>Server names likely changed if consolidating
    • 62. Volume names and paths likely changed if consolidating
    • 63. Export all current login scripts to text files for review
    • 64. Change of Home-Dir
    • 65. Be aware or UNC in scripts, MS Office Hyperlinks, ... </li></ul><li>Novell Client ™ upgrades and changes </li><ul><li>Should be version 4.91 sp5
    • 66. Now is the time for the scripted install with auto-update for future
    • 67. Change SLP and LDAP to DNS entries pointing to existing servers </li></ul><li>iPrint agent and printer deployments if necessary (using DNS) if NDPS is still used </li></ul></ul>
    • 68. Step 3: Create a Server Build Process <ul><li>Use a network source for installation files </li><ul><li>It's faster than DVD and will ensure all servers are the same
    • 69. update all servers to same patchlevel (eg. ZENworks ® Linux Management) </li></ul><li>Use proxy user account for each service or single proxy user </li><ul><li>e.g. cn=proxy_ifolder,ou=service,o=oh
    • 70. Password never expires, account never gets deleted </li></ul><li>Create a standard server installation document or scripted install (autoyast)
    • 71. Prepare a Linux User Management (LUM) design
    • 72. Pre-populate DNS with entries for servers and services </li><ul><li>iPrint managers, LDAP servers, SLP DA, time source, etc. eg., <treename> </li></ul></ul>
    • 73. Step 4: The First Server <ul><li>Install according to your server standard setup or autoyast
    • 74. Configure Linux User Management (LUM)
    • 75. Patch the server to your standard patch level (eg. ZENworks ® Linux Management)
    • 76. Use it for your LDAP server during subsequent server installs (using DNS for LDAP service)
    • 77. Move your Certificate Authority to this server </li><ul><ul><li>Follow TID 3618399 How do I move the Organizational CA to another server? </li></ul></ul><li>Use this server as default iManager with all needed plug-ins
    • 78. Get used to your backup/restore software on the new platform </li></ul>
    • 79. Step 5: All Other Servers <ul><li>Install according to your server standard setup or autoyast
    • 80. Configure Linux User Management (LUM)
    • 81. Patch the server to your standard patch level (eg. ZENworks ® Linux Management)
    • 82. Install all desired services including tape backup, anti-virus, monitoring, etc
    • 83. Test all services before users are moved and affected
    • 84. Did you backup just before migration starts?
    • 85. Execute the migration with your checklist for each action
    • 86. Have a subset of users from the business available for post migration tests
    • 87. Disable access to the migrated services and data </li></ul>
    • 88. Step 6: Cleanup and Decommission <ul><li>Let the new servers run for some time before old one get deleted and switched off
    • 89. Make a plan to retire the old servers </li><ul><li>Get replicas off
    • 90. Verify that ALL services are not used (ntp, dns, dhcp, slp, rsync, ...) by other servers or any client
    • 91. Remove eDirectory from servers </li></ul><li>Cleanup old server and services objects in tree </li><ul><li>Retired DNS, DHCP objects (DHCP_<retired-server> .ou.o)
    • 92. Retired NDPS, iFolder2.x, ... </li></ul></ul>
    • 93. Pre-migration Checklist
    • 94. Pre-Migration Checklist <ul><li>Backups </li><ul><li>#1 priority! Though data is copied from the source rather than moved
    • 95. Trustee backups on the source server
    • 96. Identify tree CA requirements
    • 97. License codes from Customer Center?
    • 98. Backup of source server eDirectory ™ DIB </li></ul><li>List of which Open Enterprise Server services need to be migrated: </li><ul><li>iPrint, Novell Storage Services ™ , DNS/DHCP, FTP, iFolder*, eDirectory ™
    • 99. These services need to be installed when we install Open Enterprise Server 2 </li><ul><li>Pre-requisite of the migration tool </li></ul></ul></ul>
    • 100. Lab 1 : Pre-flight Checks <ul><li>Please consult your lab guide for this exercise </li></ul>
    • 101. Building the Target Server
    • 102. Building The Target Server <ul><li>Software requirements </li><ul><li>SUSE ® Linux Enterprise Server (SLES) 10 SP3
    • 103. Open Enterprise Server (OES) SP2 </li></ul><li>Version numbers must be matched, so </li><ul><li>SLES10 SP4 + OES2 SP3 (when available)
    • 104. SLES10 SP2 + OES2 SP1
    • 105. SLES10 SP1 + OES2 FCS and so on.. </li></ul><li>Open Enterprise Server is now an add-on product that installs on top of SLES10 </li><ul><li>Unlike OES1, which was merged into the main SLES9 install
    • 106. Slightly different installation than OES1, but more intuitive </li></ul></ul>
    • 107. Building The Target Server <ul><li>Partitioning scheme </li><ul><li>By default, SUSE ® Linux Enterprise Server will give you a swap partition and a root (/) partition, formatted with ReiserFS
    • 108. For test/practice, feel free to play around with this </li></ul><li>Consider the role of the server and partition accordingly </li><ul><li>High file I/O? EXT3, XFS
    • 109. Novell ® file share? Novell Storage Services ™
    • 110. Consider partitioning /boot, /var, /tmp, /swap, / as a minimum
    • 111. Use LVM Logical Volume Manager to be flexible
    • 112. If it is a ZENworks ® Configuration Management Primary server, /var partition is a must
    • 113. If partitions will rapidly grow in size, isolate them from other parts of the disk to avoid problems later </li></ul></ul>
    • 114. Building The Target Server <ul><li>Open Enterprise Server 2 SP2 server will be built in the same container as existing NetWare ® server FS1
    • 115. To ensure we have all the packages we need, we must have :-) </li><ul><li>All services to be migrated (iPrint, Novell Storage Services ™ etc.)
    • 116. Pre-migration server pattern installed (mandatory)
    • 117. gcc and kernel-sources packages for VMware Tools
    • 118. Print server pattern unchecked if we are installing iPrint </li><ul><li>CUPS will fight with iPrint if we install both!
    • 119. Easier to remove at the start than later in the process when dependency chains make this difficult </li></ul></ul></ul>
    • 120. Building The Target Server <ul><li>In order to use Novell Storage Services ™ (NSS) without EVMS, we need to use two separate virtual disks </li><ul><li>OS and application files on disk 0
    • 121. NSS volumes on disk 1 </li></ul></ul>Disk 0 SYS DATA Disk 0 Disk 1 / DATA
    • 122. Building The Target Server <ul><li>Refer to lab guide for this exercise. </li></ul>
    • 123. NetWare ® vs. Open Enterprise Server Linux
    • 124. NetWare ® vs. Open Enterprise Server Linux <ul><li>NetWare is a 32 bit operating system </li><ul><li>Maximum 4GB of addressable memory </li></ul><li>Entered Extended Support phase in March 2010 </li><ul><li>Required current maintenance contract
    • 125. Extended Support ends March 2012 </li></ul><li>What is Extended Support? </li><ul><li>Installation and configuration support
    • 126. Critical security updates only
    • 127. Knowledgebase / forums / documentation / existing patches
    • 128. Transitionary step only ! </li></ul></ul>
    • 129. NetWare ® vs. Open Enterprise Server Linux <ul><li>Linux scales further than NetWare </li><ul><li>64 bit support allows for much more physical RAM than 32 bit (though this is hardware dependent for a definitive figure)
    • 130. Most code executes in protected memory, not all NLMs will allow this, but those that do must be configured appropriately
    • 131. Technically, NLMs run with full server privileges
    • 132. Linux daemons are similar to NLMs, but can be set to run as a specific (or “service user”) user to limit damage in case of hacking/software issue
    • 133. Many more applications certified for Linux than for NetWare </li><ul><li>Oracle
    • 134. ZENworks ® Configuration Management </li></ul></ul></ul>
    • 135. NetWare ® vs. Open Enterprise Server Linux <ul><li>Executing programs/applications </li><ul><li>NetWare generally uses NLMs and </li><ul><li>NCFs (batch files) these are called shell scripts on Linux </li></ul><li>Linux does not take file extensions into account as Windows </li><ul><li>.exe = Windows Executable
    • 136. .exe = Could be executable on Linux, could be spreadsheet for all we know!
    • 137. Linux permissions define whether or not code is executable and for whom (to make executable use: chmod +x <program_name>) </li></ul><li>NetWare is not case sensitive, Linux is </li><ul><li>MyExpenses.xls is not the same as myexpenses.xls </li></ul><li>Permissions are different between Novell Storage Services ™ and POSIX file systems </li><ul><li>RWCEMFA for NSS
    • 138. RWX for POSIX (R=Read, W=Write, X=eXecutable) </li></ul></ul></ul>
    • 139. NetWare ® vs. Open Enterprise Server Linux <ul><li>NetWare offers only Novell Storage Services ™ file system, Linux offers a la carte selection for most appropriate use </li><ul><li>ReiserFS </li><ul><li>Good for many small files, journalling file system with metadata. Good all purpose file systems and can be used in most scenarios
    • 140. Default file system in SUSE ® Linux Enterprise Server 10
    • 141. Data recovery tools liable to failure and data loss </li></ul><li>EXT3 </li><ul><li>Quick, stable and mature Linux file system
    • 142. Good for small files, journalling file system and good all purpose file system for use in most scenarios
    • 143. Default file system in SUSE ® Linux Enterprise Server 11
    • 144. Scalability issues with many files in a directory (>5000, without htree) </li></ul></ul></ul>
    • 145. NetWare ® vs. Open Enterprise Server Linux <ul><li>Novell Storage Services ™ is also available on Open Enterprise Server 2 Linux </li><ul><li>Shipped with Open EnterpriseServer 1 in 2005, so mature implementation of a proven technology
    • 146. Rich feature set, including data shredding, snapshot, compression, quotas, salvage etc.
    • 147. Works in the same way as it does on NetWare </li><ul><li>Managed in the same way, iManager etc.
    • 148. Slighter learning curve coming from NetWare </li></ul><li>Good, multi purpose file system for most scenarios, though it should be tuned appropriately for use </li><ul><li>Salvage, compression, flush files immediately turned off for GroupWise ®
    • 149. Consider noatime and nodiratime mount commands to improve throughput
    • 150. Turn off functionality you don't explicitly need! </li></ul></ul></ul>
    • 151. Services Ported to Linux
    • 152. Services Ported To Linux Novell Storage Services ™ NetStorage QuickFinder IManager and ConsoleOne ® DNS / DHCP Novell Client ™ NCP ™ Access eDirectory ™ AFP iPrint Apache Web Server Backup / Restore (SMS) CIFS / DFS iFolder* Novell Cluster Services ™
    • 153. Services Ported To Linux <ul><li>What do we lose? </li><ul><li>Virtual Office is not part of Open Enterprise Server (OES) 2 and is deprecated
    • 154. Replace Virtual Office with Novell ® Teaming, if required </li><ul><li>Can install Teaming on OES2 Linux, if required
    • 155. Free 20 user starter pack for Novell Teaming is available for download
    • 156. Or use the open source Kablink ® version, much the same product </li></ul><li>eGuide is no longer available in OES2 </li><ul><li>Possibly replace this function with the Identity Manager User Application
    • 157. CoolSolution for using OES1 Linux eGuide in OES2 </li><ul><li>Article is now dated, no guarantees this will work and unsupported by Novell </li></ul></ul><li>iFolder 2.x has been re-engineered and replaced by iFolder 3.x </li><ul><li>Architecture and functionality is different, but migration tools exist </li></ul></ul></ul>
    • 158. Managing Your Open Enterprise Server
    • 159. Managing Your Open Enterprise Server (OES) <ul><li>ConsoleOne ® can be used to manage OES2 </li><ul><li>Free download from
    • 160. Standard snapins include users and storage
    • 161. Non OES2 product snapins include Groupwise ®
    • 162. Can be run from the server's GUI console or Windows WKS </li></ul><li>iManager </li><ul><li>Can be installed to run from the server, like NetWare ®
    • 163. Reduces learning curve for NetWare administrators
    • 164. Functionally equivalent to NetWare, with same plug-ins
    • 165. Can also use iManager Workstation against OES2 server </li></ul><li>DNS/DHCP Console </li><ul><li>Installs with DNS/DHCP server pattern, same as NetWare </li></ul></ul>
    • 166. Managing Your Open Enterprise Server (OES) <ul><li>NetWare ® services could be managed from the server console </li><ul><li>Create/edit startup files (NCFs etc.)
    • 167. Load/unload NLMs
    • 168. Stop/start/restart services (GroupWise ® MTA F6, for example)
    • 169. Mount/dismount/check/repair/create volumes
    • 170. Remote connection via RConJ or AdRem etc. </li></ul><li>OES 2 Linux can also be managed at the console </li><ul><li>Terminal window in GNOME/KDE
    • 171. SSH connection via putty.exe (freeware) </li><ul><li>Like Telnet, but secure channel, not clear text
    • 172. Same functionality as above </li></ul></ul></ul>
    • 173. Managing Your Open Enterprise Server (OES) <ul><li>OES2 Linux has NSSMU to manage storage
    • 174. Stopping/starting/restarting services </li><ul><li>Unload/load NLM ™ on NetWare ® </li><ul><li>Unload GWMTA.NLM
    • 175. Load GWMTA.NLM </li></ul><li>/etc/init.d/service stop|start|restart|status on Linux </li><ul><li>/etc/init.d/ndsd stop
    • 176. /etc/init.d/ndsd start
    • 177. /etc/init.d/ndsd status
    • 178. On Linux, we can also query the status of a service
    • 179. Sometimes we can also omit the path and use “rc”, so :- </li><ul><li>rcndsd restart
    • 180. rcgrpwise stop </li></ul></ul></ul></ul>
    • 181. Managing Your Open Enterprise Server (OES) <ul><li>How to navigate the Linux file system? </li><ul><li>/opt used for Novell ® application binaries (/opt/novell/groupwise)
    • 182. /var used for variable length files, generally log files, but other data may also be pathed here, such as the ZENworks ® Configuration Management Content Repository
    • 183. /tmp used for temporary files
    • 184. /home used for Linux user home areas ( not eDirectory ™ users)
    • 185. /bin and /sbin used for binary executables
    • 186. /media used as a temporary mount point for DVD/USB etc
    • 187. /etc used for configuration files for server and services
    • 188. /srv used for services such as WWW, FTP, Tomcat
    • 189. /proc used for server processes </li></ul></ul>
    • 190. Managing Your Open Enterprise Server (OES) <ul><li>How to navigate the Linux file system? </li><ul><li>/root is the root user's home area
    • 191. /boot is used for boot files
    • 192. /lib is used for shared libraries
    • 193. /mnt is used for temporary mount points
    • 194. / is generally referred to as “root” </li></ul><li>Mount points </li><ul><li>More or less anything can become a mount point </li><ul><li>Removable storage (USB disk, flash drive etc.)
    • 195. NFS storage on another server on the network
    • 196. ISO file on a server (handy for installing software!) </li></ul></ul></ul>
    • 197. Managing Your Open Enterprise Server (OES) <ul><li>Using Linux runlevels </li><ul><li>Runlevels runs from 0 to 6, inclusive </li><ul><li>Init 0 – shutdown
    • 198. Init 1 – single user only, no network or services (aka “safe mode”)
    • 199. Init 2 – multiuser access, no network or services
    • 200. Init 3 – multiuser access, networking, services, no GUI
    • 201. Init 4 – unused/user definable
    • 202. Init 5 – multiuser access, networking, services, GUI, default SLES runlevel
    • 203. Init 6 – reboot </li></ul></ul><li>Services can be set to start at certain runlevels but not others, and have dependencies (a benefit on Linux) </li><ul><li>For example, don't start iPrint and eDirectory unless networking has been started </li></ul></ul>
    • 204. Managing Your Open Enterprise Server (OES) <ul><li>What gets logged and where does it go? </li><ul><li>Pretty much everything is logged, this is a major benefit over NetWare ™ , whose logs are generally minimal unless configured otherwise </li><ul><li>eDirectory ™
    • 205. NCP ™
    • 206. iPrint
    • 207. Novell Cluster Services ™
    • 208. AFP/CIFS/NFS
    • 209. GroupWise ® agents, Novell ® Identity Manager, ZENworks ® Configuration Management etc. </li></ul><li>The main system log is /var/log/messages </li><ul><li>If your service/ daemon does not have it's own log file check here </li></ul><li>Log files invariably get scattered across /var </li></ul></ul>
    • 210. Managing Your Open Enterprise Server (OES) <ul><li>What OES services log files are there? </li><ul><li>/var/opt/novell/eDirectory/log/ndsd.log
    • 211. /var/opt/novell/log/ncpserv.log
    • 212. /var/opt/novell/log/ncpcon.log
    • 213. /var/opt/novell/log/iprint/ipsmd.log
    • 214. /var/opt/novell/log/iprint/idsd.log
    • 215. /var/log/boot.msg </li></ul><li>Check documentation for other products </li><ul><li>/var/log/novell/groupwise/*
    • 216. /var/opt/novell/log/zenworks (ZCM) </li></ul></ul>
    • 217. Managing Your Open Enterprise Server (OES) <ul><li>How do we create Novell Storage Services ™ (NSS) pools and volumes? </li><ul><li>Same way as we do on NetWare ® now!
    • 218. NSSMU at the server console (must be root)
    • 219. iManager on the server, or use the workstation version </li></ul><li>Differences between NCP ™ and NSS volumes </li><ul><li>NSS volumes are disk pieces, carved up and formatted with the NSS file system
    • 220. NSS volumes provide compression, quotas and all the good stuff you get on NetWare currently
    • 221. NCP volumes are chunks of the Linux file system presented as “Novell ® ” volumes </li><ul><li>They look the same on a Windows client device
    • 222. SYS volume on an OES2 Linux server is an NCP volume </li></ul></ul></ul>
    • 223. Managing Your Open Enterprise Server (OES) <ul><li>When to use an Novell Storage Services ™ volume? </li><ul><li>When you want “regular” Novell ® file services
    • 224. When you want compression, quotas, salvage etc.
    • 225. When you want rich permission sets
    • 226. Physical disk should be separate from OS disk, so we don't have to configure EVMS
    • 227. When creating volumes for migration from NetWare ® </li></ul><li>When to use an NCP ™ POSIX volume? </li><ul><li>No general use, aside from the install provided SYS volume
    • 228. Can be useful to expose part of the Linux file system to Novell Clients
    • 229. For example, an installation point (GroupWise ® SDD) </li></ul></ul>
    • 230. Linux User Management - When/Why?
    • 231. Linux User Management – When/Why? <ul><li>What is Linux User Management? </li><ul><li>Called LUM for short
    • 232. Linux has it's own local database of users, much like Windows in some respects
    • 233. Linux native services such as FTP, rlogin, SSH etc assume the presence of a local user, or configured authentication source such as LDAP, NIS etc.
    • 234. LUM allows eDirectory ™ users to access Linux servers using their current eDirectory username and login credentials
    • 235. Some Open Enterprise Server 2 services also require LUM to be present </li><ul><li>Novell Storage Services ™ (NSS)
    • 236. iPrint, Samba
    • 237. Defaults generally work quite well </li></ul></ul></ul>
    • 238. Using The Migration Tool
    • 239. Using The Migration Tool <ul><li>The tool is a core part of the Open Enteprise Server 2 installation and does not need to be downloaded separately
    • 240. Can be accessed via YaST menu or by running miggui from a command prompt/terminal window
    • 241. Tool provides two main features: </li><ul><li>Transfer ID
    • 242. Server Consolidation </li></ul><li>We are going to use the Transfer ID migration </li><ul><li>Easiest and quickest way of demonstrating the tool's capabilities
    • 243. Many migration scenarios involve a one to one migration of data and services away from NetWare ® </li></ul></ul>
    • 244. Using The Migration Tool <ul><li>The tool essentially has two parts </li><ul><li>Copy data and configs from the source NetWare ® server
    • 245. Perform the ID transfer, so eDirectory ™ , replicas, IP addresses etc. move to Linux from NetWare </li></ul><li>Build your Open Enterprise Server 2 Linux target in the same container if possible </li><ul><li>Makes life a little easier as we go </li></ul><li>Some backout procedures exist, in case of failure </li><ul><li>Each step can be re-tried, for example if there are comms issues </li></ul><li>O nce iPrint is migrated, you cannot go back
    • 246. Remember, data is copied , so you lose nothing! </li></ul>
    • 247. Lab 3 : Running the Migration Utility <ul><li>Refer to lab guide for this exercise. </li></ul>
    • 248. Configure New Services In Open Enterprise Server 2
    • 249. Configure New Services in Open Enterprise Server (OES) 2 <ul><li>OES2 brings two new services we're interested in </li><ul><li>iFolder 3.8
    • 250. Dynamic Storage Technology </li></ul><li>iFolder 3.8 is slightly different than iFolder 2.x </li><ul><li>Concept of shared folders
    • 251. iFolder 2.x had one to one relationship with user and server
    • 252. iFolder 3.x allows folders to be shared with other iFolder users
    • 253. Re-written in Mono ® , so Linux only
    • 254. Clients for Mac, Linux and Windows XP/Vista/7
    • 255. iFolder data store migration utility available in YaST
    • 256. Can be clustered, if required </li></ul></ul>
    • 257. Configure New Services in Open Enterprise Server (OES) 2 <ul><li>What is Dynamic Storage Technology? </li><ul><li>Put simply, it allows administrators to manage file storage in a policy based way
    • 258. Server volumes have shadow volumes defined
    • 259. Depending in the policy, files can be transparently moved from the “main” volume to the shadow volume
    • 260. For example, policy states MP3's are to be stored on the shadow volume, along with files not accessed since 2008
    • 261. Free in OES, perhaps on of the best app in the whole suite Saves a lot of money!
    • 262. Allows backup times to be reduced to keeping stale data away from the live data
    • 263. Prevents old/non-mission critical data from clogging up expensive storage </li></ul></ul>
    • 264. Configure New Services in Open Enterprise Server (OES) 2 <ul><li>How do I configure Dynamic Storage Technology? </li><ul><li>Policies are configured in Novell ® RM
    • 265. Can apply policies to both Novell Storage Services ™ (NSS) and NCP ™ volumes
    • 266. Decide on how you want to manage your data before you think about how you want to configure DST policies
    • 267. Use the inventory functionality available to you to find out what is on your NSS volumes before you decide on your DST policies
    • 268. Don't forget a Novell Client™ is installed on the OES2 Linux server, so don't be afraid to use that to check if your policies are working, you don't need a Windows client as such </li></ul></ul>
    • 269. Wrap Up / Question and Answer
    • 270. Wrap Up / Question and Answer <ul><li>If you're new to Linux: </li><ul><li>Take some Novell ® curriculum courses (classroom, online etc.)
    • 271. Build, test, break, rinse, repeat
    • 272. Use virtual machine snapshots in your lab to speed things up </li></ul><li>In your production environment: </li><ul><li>Consider login scripts, server migration/consolidation issues
    • 273. Remember to catalogue all of your apps, including GroupWise ® , ZENworks ® , Novell Identity Manager etc. Will they run on Linux? Third party products, GWAVA, anti-virus etc.
    • 274. Service Location Protocol </li><ul><li>Not quite the same on Linux, OpenSLP is not Novell's SLP
    • 275. Windows 7 clients look for OpenSLP Directory Agents
    • 276. Consider DNS names in login scripts for faster script processing </li></ul></ul></ul>
    • 277. Wrap Up / Question and Answer <ul><li>TOP Open Enterprise Server (OES) 2 Upgrade TIDs </li><ul><ul><li>TID 7002862 - Troubleshooting data migration issues with miggui
    • 278. TID 7000901 - Troubleshooting OES2 Novell ® iPrint Migration Tool
    • 279. TID 7004455 - iPrint Migration Best Practices
    • 280. TID 3150078 - Updates Catalog Missing after Registration of OES2
    • 281. TID 3503915 - LUM Enabling Pure-ftpd
    • 282. TID 7004574 - OpenSLP vs. NetWare ® SLP
    • 283. TID 7001449 - eDirectory ™ not registering with SLP
    • 284. TID 7001767 - Troubleshooting data migrations with migfiles from Netware 6.5 to OES Linux
    • 285. TID 3884721 OES2 Novell DNS Install Error: Failed to configure DNS server
    • 286. TID 10085156 DNS Administration fails after Migration </li></ul></ul></ul>
    • 287. Wrap Up / Question and Answer <ul><li>If you have a question you're saving.. </li><ul><li>We'll be around all week, including IT Tech Talk night tonight
    • 288. If you see us in the hallway, to come and say Hello!
    • 289. Connect with us </li><ul><li> or by Email [email_address] </li></ul></ul><li>Join your local Open Horizons chapter and partipate! </li><ul><li>Attend local summits, meetings
    • 290. Don't forget the EMEA Summit in Vienna in November, even more hands on labs with the Open Horizons experts!
    • 291. Have a look on for your knowledge upgrade
    • 292. for further information </li></ul></ul>
    • 293.  
    • 294. Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.