Now that you understand the technical details and intricacies of the various MetaFrame XP and NDS integration options, you need to figure out which ones will work best in your environment. To do this, you will need to answer the following questions:
- Do all of your users need to access the same data on NetWare servers, or do they each need to access their own data?
- Do users need to use applications where they are authenticated as NDS users, or do they just need access to their data?
- Do users need their own unique desktop environment, or can they use a common MetaFrame XP environment?
- Do you have Feature Release 1 or newer?
- Is NDS going to be in your environment long-term, or are you migrating to Active Directory?
- Do your NetWare users also have Windows domain or Active Directory accounts?
- Do your users need to access NetWare resources from all MetaFrame XP servers in the farm, or just certain servers?
If all of your users need to access the same data, then you can use one of the options where all users login to NetWare with the same credentials, such as a NetWare auto-login or a NetWare gateway. If users each need to access different components in the NetWare environment, then they will need to login to NetWare with their own unique accounts.
User Access to NDS
If users need to access an NDS application, then they will need to authenticate to the tree. If they just need to access data that is stored on NDS volumes, then the NetWare gateway should work.
If your users do not need their own unique Windows desktop environment, they can share a Windows account which can be configured to auto-logon. This means that each user would only need a NetWare account, saving you from having to create or migrate too many Windows accounts. However, if users need their own unique desktops, they will need their own Windows accounts or you will need to use the ZENworks for Desktops to create Dynamic Local User accounts.
Feature Release Level
Obviously, if you don't have or are not planning on using Feature Release 1 or 2 then you cannot use any of MetaFrame's native NDS integration options.
Future User Account Platforms
If you have users with NDS accounts that you're planning on migrating to Windows or Active Directory accounts, it might be worth migrating them now for use with MetaFrame XP. However, if you're planning on NDS as your primary directory, then creating Windows accounts for your users would be counterproductive. In this case, your best solution would be to use the NDS integration features of Feature Release 1 or 2, or use the Dynamic Local User functionality of ZENworks.
User Account Types
If your NetWare users already have Microsoft accounts that they use on a daily basis, they are familiar with the account integration and synchronization issues. In this case, you can probably just install Novell's NDS Client software or Microsoft's Client Services for NetWare, and your users will already know what to do when they see the NetWare login screen. If your users do not currently have both types of accounts, then you will need to plan on educating them when you roll out MetaFrame XP.
MetaFrame XP Servers that will Access NetWare Resources
If you have MetaFrame XP servers that you dedicate to NDS users, you will be able to use the Feature Release 1 or 2 NDS integration features of MetaFrame XP. However, if you will need to have some servers that support users authenticating via NDS and Microsoft methods, you will need to choose an alternative method of integration.
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.