1. How Does NetWare® User-Based Licensing Affect Me?
Derek B. Dobson
Product Manager
Novell, Inc.

2. Vision…one Net Mission
A world where networks of all types—corporate and public, intranets, extranets, and the Internet—work together as one Net and securely connect employees, customers, suppliers, and partners across organizational boundaries
Mission
To solve complex business and technical challenges with Net business solutions that enable people, processes, and systems to work together and our customers to profit from the opportunities of a networked world

4. The Role of Novell NetWare®
NetWare is the keystone to the one Net vision
NetWare is the Net services platform that enables resources to work together as one Net across all types of networks, corporate and public

5. Session Outline
Background on how licenses are consumed in 3.x / 4.x / 5.x environments
NetWare 6—new licensing model
Different types of licensing programs
Comparison to Microsoft licensing
How many licenses will I consume in upgrading to NetWare 6?
What are my options for upgrading?
Suggestions for license design
What is the future?
Links that you need to know
Questions and answers

6. Important Definitions
“License”—The right to use
Digital Certificate—The server software that verifies that you are authorized to access services
User License—Consumption of a “license unit” that is authorized by the Digital Certificate

8. 2.x and 3.x Environments Bindery-based Integrated into SERVER.EXE
Upgrading required new SERVER.EXE file from Novell
Not additive; server must be downed
Log in to each server required
Licenses per consumer/server, not service

9. 4.x Environments Directory-based
Licenses stored on SYS Vol in individual server
Log in once to tree, but licenses consumed/server
Up to eight licenses per server
Consuming licenses/server

10. 5.x Environments Directory-based SCON licenses Log in once to the tree
Licenses installed into DS in the directory tree
In either O or OU
Consuming a “service” consumes a license
Connection licenses “released” as soon as user logs out
Up to eight licenses per server
Evals weren’t additive
Consuming licenses/server

11. The Evolution of NetWare Licenses
NW 2.X
NW 3.X
NW 4.X
NW 5.X
NW 6
Bindery / Directory
Bindery
Directory
SCON / UAL
SCON
UAL
Certificate Location
SERVER.EXE
Server Sys Vol
Additive No
Yes

13. NetWare 6—New Licensing
Called User Access Licensing (UAL)
How does it work?
One user can consume “unlimited” NetWare resources on the network within the same tree for only one license
Each person accessing network resources needs a license
Each user holds the license for 90 days from last access
Why did we change?
You requested it
Easier administration
Novell moving to one licensing model for all products

14. UAL: Pros and Cons Pros Cons
You can use unlimited servers in your environment
Customer can use multiple devices
Customer can use multiple servers
No longer charged by # servers
Companies can have an employee cost model
Licensing Metering Tools
Cons
Users can’t share user objects
Multiple directory trees multiply the number of per-user licenses
Let’s take a look at some of the pros & cons of Per User licensing. By knowing what your customer is likely to see as an advantage and a disadvantage of Per User licensing, you can more easily suggest which way to count the licenses for your sale. You can also know for certain whether Per User licensing is right for your customer.
Pros
With Per User licensing, your customer is not charged based on number of devices they use (PDAs, PCs at home, multiple PCs at work). Users can use as many devices as they like and the customer will not be charged for that use--they’ll only be charged on the number of users.
Customer is not charged for servers. Users can be connected to any number of servers and your customer is still charged only for the user license itself. This makes it easy for customers to add employees to servers they need access to. It also increases deployment flexibility.
Companies who deploy a single NDS tree with a single ID per employee have employee cost model--which is especially easy to count and track!
Cons
The customer pays for each user--even if those users share a workstation or other devices
If the company deploys more than one NDS tree and has the same users replicated in more than one tree, they pay for those replicated users--unless they use a synch technology like Novell’s DirXML to synch those user IDs. If they also purchase DirXML and use it to synchronize those user objects, they can once again use the employee model--counting only the individual person associated with those duplicate user objects in those separate, but synchronized, trees.
Now let’s take a quick look at some of the other models and the pros and cons of using them.

15. How Many Licenses Will I Consume? A Comparison
NetWare 5.x
= 3 Licenses
NetWare 6
= 1 License

16. “Per-User” Software Licensing: Graphic Example
Five licenses are required for the five user objects that accesses the software service by the five different employees
Here we have five users. Each one has a unique ID. Each one is accessing the software service (like ZENworks or GroupWise). As you can see, it’s the user that is licensed for access to the software--not for their concurrent connection to the software. This example also clearly illustrates that whether users share a device or have more than one device, it doesn’t matter: you still count only the user and not the device used.
Whether they’re using concurrent connections or sharing devices, your customer pays only ONCE per user on each directory tree.
Simple, huh? Isn’t it nice to know that when someone says it’s a “user license,” they mean it’s a license FOR A USER? Refreshing, isn’t it? Wouldn’t you like everyone to do it this way?
Let’s see how this works when a user is replicated on more than one directory.

17. New Kinds of Licenses Server licenses are free
Must be unique
Link:
Three-user reviewer’s license (never times out)
90-day eval (500 users)

18. Upgrading Options
Kevin can we make this another “section title”

19. Upgrading to NetWare 6 Upgrading to NetWare 6
Red Box—purchase upgrade licenses
VLA—Upgrade protection
CLA—Upgrade protection
MLA—Maintenance
Additional info:

20. Comparison with Microsoft
Microsoft would have you believe that 80% of their customers will see no change or will have a cost decrease
“Microsoft says they're simplifying software contracts,' said Gartner analyst Neal MacDonald. 'We believe they're confusing simplifying with removing options.” CNET News May 10, 2001 “New Microsoft licenses may increase costs”
Companies upgrading every three years would pay 22—47% more, with the increase jumping to 40—68% for four-year upgrades
—Guernsey Research
More info:

21. What Is the Future?

22. Today and Tomorrow Today you can do licensing metering on NetWare 6
iPrint
NetWare
Tomorrow: Push a button, find out how many Novell licenses you’re using (a single point of information)
System administrator can do “Self-Compliance Audits” before Novell auditing group comes in
NetWare in the old world was an Operating System, with some services sitting on top of the OS. It was positioned as an OS, and sold as on OS.

23. Links You Need to Have NetWare server download page
Digital Airlines demo kit
NetWare 6 FAQs
Customer response center

24. Suggestions for License Design
White Board Discussion

25. Some Things to Remember
Don’t span the WAN: Install Certificates locally
Install users at or below License Certificates: NLS searches up the tree
License Install Methodology: Easy Maintenance vs. Availability
User License type is determined by the Server Certificate consumed:
I.e., Demo consumes NetWare 6 Demo User certificates
Red Box—consumes NetWare 6 User certificates
MLA—has no user licenses
Determining “Active” license type
NetWare 6 – PM STATS, NetWare 6 SP1 - VERSION
Changing certificate types
Unassign “old certificates”
Clear cache: unload polimgr, unload nlslsp, load polimgr
NW6 UAL Licenses must be inserted into tree “post” install
Persistent vs Concurrent license consumption

26. Other Recommended Sessions
IO 101 – NetWare Future Roadmap - Mon 12:45 / Wed 12:45
IO 102 – Six Reasons to get NW6 – Tues 4:30 / Thurs 4:30 / Fri 3:15
IO 105 – iPrint, Present and Future - Mon 11:15 / Wed 2:15
IO 204 – How Does NW6 Licensing Affect Me? - Wed 12:45/ Fri 12:15
TUT 101 – Consulting’s Best Practices for NW Migrations - Tues 9:30 / Thurs 3:00
TUT 104 – How to consolidate NetWare Servers – Wed 3:45 / Thurs 4:30
TUT 201 – Rapid and Remote NW6 Deployments - Tues 4:30 pm / Friday 12:15
TUT 202 – Consulting’s Best Practices for NW Upgrades – Tues 12:00 / Fri 12:15
TUT 203 – Upgrading NW 5 Clusters to NW 6 - Tues 12:00 / Thurs 12:00
TUT Integrating NW6 and Windows Mon 2:15 / Thurs 3:00 / Fri 12:15
TUT 208 – Customizing iPrint with the Map Designer – Tues 4:30 / Fri 1:45
TUT 209 – How to Size Compaq servers on NW – Mon 3:45 / Wed 3:45
TUT 265 – iPrint Deployment Strategies – Mon 2:15 / Wed 3:45 / Fri 3:15
TUT 301 – Technical Analysis of NW and it competition – Wed 12:45 / Thurs 1:30
TUT 303 – Integrating NW and Linux – Mon 3:45 / Thurs 3:00
TUT 305 – Understanding SLP v2 – Mon 2:15 / Thurs 4:30
DL 101 – Developing on Apache Tomcat for NetWare – Wed 11:15 / Fri 12:15
DL 201 – Application Development to NW6 and Modesto – Tues 4:30 / Thurs 4:30
DL 205 – Developing to J2EE on NetWare – Tues 12:00 / Thurs 1:30