Novell Home

Round-up of the NDS for NT Live Discussion

Novell Cool Solutions: Feature

Digg This - Slashdot This

Posted: 8 Jul 1999
 

We hosted a Live Discussion about NDS for NT on June 29, 1999, and for all intents and purposes, we've got to say that it was a smashing success. We opened the flood gates at the designated hour, and as planned, your questions came rushing through.

Brad Anderson, the product line manager for NDS, joined us online, and while it was a little like drinking from a fire hose, he did his best to type lightning fast and post a response to each and every question you submitted.

As those of you who joined the discussion know, Brad is quite the NDS expert, and the fact that he knows a lot about the Novell Clients, NT, and ZENworks, just endears him to us more. But he wasn't born with all this knowledge. No, he started on the front lines in Novell Technical Support fielding questions. From there he worked his way up the ranks in Support and joined the World Wide Support team, the guys who come to you when you're having really big problems. After a stint there, he jumped over to product management where he's managed the Novell Clients, ZENworks, and NDS. Now, he's the product line manager for all of NDS, and he knows his stuff.

We didn't, couldn't, and just wouldn't let all that knowledge drift off into electronic oblivion, so we've gathered all of your questions and all of Brad's answers together into this article. We've added a few question summaries to make it easier find the topics that interest you, but other than that this is the uncut version. So, sit back, read this, and see what everyone is talking about. Chances are you have some of the same questions as those that were posted to the discussion.

What's on the NDS for NT Roadmap?

Brad: Let's take a minute before we get started and make sure that everyone is aware of what is currently released for NDS for NT.

NDS for NT v2.0 was released in December of 1998. This version included all the functionality in NDS for NT v1.1 with the following enhancements:
  • The ability to put an NDS replica on an NT server
  • Significant performance and scalability improvements (NDS for NT 2.0 will support up to 65,000 objects in a single domain.)
  • NT Share management
  • Guaranteed password synchronization between NDS and domains

NDS for NT v2.01 shipped in May 1999, and it includes all the functionality in 2.0 plus support for pure IP.

NDS 8 for NT will ship later this summer, and will include the following functionality:

  • Built on NDS 8 data store - ability to scale to millions of objects with great performance
  • WAN Traffic Manager
  • NDS utilities such as DSRepair (This will be an NT standalone solution.)
  • LDAP v3 support (with SSL)
  • NICI support
  • LDIF import capabilities

How do I integrate a single Citrix MetaFrame server with NDS?

Question: Novell recommends installing Citrix MetaFrame on a member server and not a BDC or PDC due to a conflict between the NDS for NT Client and MetaFrame (NetWare Client for NT later than 4.5 has no problem). This is what I have gathered from investigating all the info I could find on the Novell and Citrix web sites.

Consequently, I have a situation where we are running a mixed NetWare 4.11 and NetWare 5 network, and we have an NT Terminal Server with Citrix MetaFrame sitting all on its lonesome. How can this server be incorporated into NDS? We don't really want to have to have another NT Server installed as a PDC just for NDS for NT, but we would like to incorporate the administration of the Citrix and the NT server into NDS.

Answer: This is an excellent question. I have also been the Product Manager working on the Citrix relationship.

First of all, the conflict with the Client has been resolved in NDS for NT v2.01. NDS for NT v2.01 now installs the Novell Client v4.6 for Windows NT, which is completely MetaFrame enabled (older versions of NDS for NT installed the 4.11b Client).

For suggestions on integrating the single Citrix server, I would recommend that you use the Dynamic Local User option in ZENworks to manage access or use the domain solution that we discuss in the Novell/Citrix Integration white paper.

How do I integrate a Citrix WinFrame server with NDS?

Question: What about NDS on Citrix WinFrame?

Answer: The integration work that we have done with WinFrame requires the Novell Client v4.11b be installed. If you are going to run WinFrame in conjunction with NDS for NT, the WinFrame servers will have to be member servers and not a PDC or BDC. Once again, a great solution would be to use the domain solution we discuss in the Novell/Citrix Integration white paper.

Should I upgrade to NDS 8, and how long will it take to upgrade a 70mg database?

Question: We are converting our tree to NetWare 5. Our three root replica servers were upgraded this weekend to the 7.3 version of NDS. Do you see any problems with upgrading these servers to NDS 8? Does anyone have NDS 8 in their production tree? Any idea how long the DB upgrade would be for a 70meg NDS database?

Answer: On average for a simple system it takes about two minutes for every 1,000 objects that exist in the NDS tree. However, the time will vary depending on your hardware, number of partitions, and the complexity of the relationships between the NDS objects. I would guess that 10-15 minutes would be required to upgrade your dib set. We have upgraded hundreds of servers internally at Novell to NDS 8 without any problems.

Reader Answer: By the way, DS.NLM 5.15 is not enough for NetWare 4.10 servers when you're putting NDS 8 into your tree. You will need DS.NLM 5.17 or later to do this.

What is the future of NDS for NT?

Question: I have either used or know about the current versions of NDS for NT and they are literally "Cool Solutions". I can't say enough good things about them.

What is the future of this product with respect to Active Directory? What will the integration between NDS for NT and Active Directory be like, and how will it work?

Answer: Novell is 100% committed to integrating all aspects of your network, including Windows 2000 and Active Directory. Novell is developing a number of solutions that will integrate Active Directory into NDS and allow you to administer your entire network from a single point of administration.

NDS for NT today has two components. The first component is the actual NDS replica. The NDS replica runs on Windows 2000 today. In fact we demonstrated the NDS replica running on Windows 2000 at BrainShare 1998— almost 18 months ago.

The second component of NDS for NT is the redirector. The redirector is the component that provides the single point of administration for NDS and domain user accounts. There have been significant changes made in Windows 2000 that will require the redirector component to be updated to run on Windows 2000.

As I previously stated, Novell is working on multiple integration solutions, which we will announce shortly. These solutions will ship at the same time Active Directory ships—whenever that is. :)

What are the licensing requirements for NDS for NT?

Question: Could someone clarify the licensing requirements for NDS for NT? Here's my situation: I have three NetWare 5 servers on an MLA. I also have three NT servers that I wish to move over to NDS for NT. Each of the NT servers supports 100 users. What licenses would I need to purchase to put all of my NT on NDS for NT?

Answer: Here is an example that will help you understand NDS for NT licensing. Let's assume that you have 100 users using NetWare and NDS, and 50 users using NT. In this scenario, you'd need to purchase 50 licenses of NDS for NT. In licensing language, we'd say you have 50 managed users. Managed user refers to the number of users in the domain. (If a single user account is being used by multiple users, you need to count each user.)

If you want to place an NDS replica on the NT server there is also a server license. Novell is currently running a promotion where you get a free server license for every NetWare server you own.

Can you explain what type of licenses I need for my site?

Question: Hello. My question centers on the licensing issues of the product. For example my company is around 5000 users. Only 2500 users need access to my NT box's. They all have user licenses on the IntranetWare side. What would I be looking at for license issues? Also will this give me full management ability from ManageWise? What are the largest benefits of a move of this caliber? I run 78 Novell servers and 23 NT servers. Thank you for your enlightenment.

Answer: In your environment you would need to purchase 2,500 user licenses of NDS for NT. This would give the ability to completely manage the user/group account information on the domain via NDS. (See a previous responses for $ savings this equates to).

You could then also run solutions such as ZENworks from an NDS replica running on an NT server.

On your question about ManageWise, you should look into a product we just released named Novell BranchManager for NT. This is suite of productsdesigned0 to manage the NT server environment. The suite consists of:

NDS for NT
ZENworks
ManageWise Agent for Windows NT
BorderManager Authentication Services

You get all these products on a single CD a significant price savings - about 50%.

Will NDS for NT support Exchange?

Question: Will NDS for NT support Exchange in the future? What about other name spaces?

Answer: Chris, NDS for NT actually ships with a product today that integrates Exchange into NDS. When you install NDS for NT you have the option of installing what we call the Exchange Mailbox Manager. The Mailbox Manager extends the NDS schema to allow you to administer the Exchange specific settings via NDS and NWAdmin. We definitely have plans to extend the name spaces we are administering.

You can also purchase the product, Synchronicity, from NetVision. NetVision has solutions for administering Notes, Exchange, and the NetWare 3.x bindery from NDS.

When will NDS 8 for NT be available, and how will it change the NDS design rules?

Question: Brad, there you were talking to all those nice people at BrainShare, and who had to mind the stand? Me. You said I could have a nice black polo shirt, but what happened? I (and the Kilt) will be back.

On a more reasonable note, any rough plans on when we can get NDS 8 for NT?

And my other little question is: How you are going to revise the NDS design rules? The 1500-3000 rule has no place in NDS 8 that I can see. I would expect that WAN design is more important than ever, but what about things like an Apps container or Workstation container with ZENworks? Do the indexes solve short distance tree walking?

Answer: Tim, there are not a lot of people that walk around BrainShare with a kilt on —so I definitely remember you.

NDS 8 for NT is going into its final beta today, and we are planning on releasing NDS 8 for NT later this summer. NDS 8 for NT will have the following additions:

  • Built on NDS 8 data store—ability to scale to millions of objects with great performance
  • WAN Traffic Manager
  • NDS utilities such as DSRepair (this will be an NT standalone solution)
  • LDAP v3 support (with SSL)
  • NICI support
  • LDIF import capabilities

You're right that the old NDS design rules, such as the number of objects per container, are no longer valid. At BrainShare when we demonstrated the billion– yes that's right the billion user tree– it was made up of 10 servers with each server holding 100 million objects in a single container.

Does NDS for NT need to be installed on all of a domain's BDCs?

Question: On one of the forums, I ran across a statement that NDS for NT needed to be on a domain's BDCs for them to operate. While I agree that loading NDS for NT on the BDCs is greatly preferred (you never know when you will need to promote one), I also had the impression that the BDCs could still operate (i.e. authenticate NT logins) without the NDS for NT software. It seems to me that if NDS for NT operates by redirecting the PDC SAM requests to NDS, that it would still operate with a plain BDC and the BDC's update requests to the PDC. Maybe I'm missing something here.

Answer: The NDS for NT software must be installed on the PDC and all BDCs. This does not have to be done instantly. After NDS for NT has been installed on the PDC, the BDCs will continue to operate— they will just not receive any updates that occur to the domain at the PDC.

One of the problems that we wanted to solve with NDS for NT was the significant amount of traffic the PDC and BDCs place on the wire so we basically turn off the PDC/BDC replication when NDS for NT is installed.

Are there any known issues with NDS for NT 2.01?

Question: Have there been any reported bugs with NDS for NT 2.01? Are there plans on releasing 2.02? If so, when? I ask because we installed NDS for NT 2.01, upgrading our NT Server PDC/Exchange server from 2.0. Everything went fine, but the next day we had corruption on Exchange and had to rebuild the server.

Answer: Of course there are bugs with NDS for NT v2.01—this is software after all. :) The issues we have seen with NDS for NT v2.01 are minor. The bug count on NDS for NT is extremely low. We have not seen any corruption types of problems.

Will the NDS for NT install overwrite my newer Client 32 files?

Question: I noticed that NDS for NT replaces the Client 32 files on its install. We recently installed SP1 on our NT Server PDC. If we install NDS for NT on this machine which files are going to take precedence?

Answer: NDS for NT v2.01 will work fine with the Novell Client SP 1 installed. When you go to install NDS for NT it will not overwrite the newer files SP1 installed.

Do you like what we did with the Client Service Pack where we list all the files that have changed for the Service Pack in the network control panel?

Response question: Well, actually, I do not understand why Novell has gone to Service Packs now. ACU does not appear to work very well using Service Packs. Maybe I'm doing something wrong there. But now I have to have two application objects to update clients. Is SP1 just an interim release or is this how Novell is going to handle updates from now on? How can I get ACU to work correctly again?

Reader Answer: Actually, I think ACU works quite well with SP1, provided you first update the NT client installation files with SP1, and then install the client you patched that way.

Of course it would be very helpful if on their download page ( http://www.novell.com/download ), Novell would replace the clients with newer versions with SP1 already applied.

How do I implement NDS for NT to manage a migration from GroupWise to Exchange?

Question: My environment consists of all NetWare 4.11 servers, approximately 3000 users in 15 partitions. We are forced to migrate from GroupWise to Exchange, hence the NT. We have chosen to use NDS for NT to manage this; however what's not clear to me is how to implement NDS for NT because all users will need domain access.

Answer: When users need to authenticate to the domain they will need to talk with the NDS replicas that contain the domain object and the NDS partition that contains their user account.

You will want to place replicas of the domain object that contains the user objects as close to the users as possible. If you have a NetWare server in the same physical location, Novell recommends that you not place an NDS replica on the NT server.

I know of one customer that is using NDS for NT who was in a similar situation— where the decision was made to deploy Exchange. This customer did not have any domains deployed. They used NDS for NT to drag-and-drop the 10,000 NDS user objects into the domain, and they built their 10,000 user domain in a couple of hours. They then exported all the NDS/Domain information to BindView, and then imported that data into Exchange to populate the Exchange database. From here, they used ZENworks to deploy the Microsoft SMB Client, the Outlook Client, and Internet Explorer. The IS personnel did not have to visit a single workstation, and all 10,000 users were updated. This customer says they used NDS to completely deploy their Exchange environment.

Reader response: All I can say to that is wow. :0

Is there any way to administer NT file system rights using NWAdmin?

Question: The pure NDS for NT will ship soon, and it's becoming an interesting product for pure (and mixed) NT environments (ZENworks, domains without trusts, Exchange, and so on). However, one question always comes back from my customers: what about the management of file system rights from within NWAdmin?

And

I second this question. The ability to administer file system rights using NWAdmin and NDS for NT would be a great benefit.

Answer: NDS for NT currently has the ability to administer NT Shares from NDS. We have been researching managing the entire file system and know how to do it. We currently have the team working on the Active Directory integration and some other enhancements (such as the ability to only show an administrator using User Manager the users to which he or she has rights). Managing the file system is high on our priority list, and we will work on it after the Active Directory work is complete.

Can an NT Domain be completely substituted with NDS?

Question: First, I want congratulate Cool Solutions for giving a way to speak directly to the Novell Team. I have two questions:

  1. Can an NT Domain be completely substituted by NDS? In this scenario, all NDS resources would be native on the OS (UNIX, NT, and so on).
  2. Will NDS for NT be free?

Answer: Eduardo, the redirector component of NDS for NT moves all the domain data from the SAM database ("the secure part of the registry") into a truly scalable and secure data store, NDS. Because the data is stored in NDS, NDS for NT makes the NT server much more scalable and secure. We currently will support a domain of up to 65,000 users, and that is without running NDS 8. We are now doing the testing of NDS for NT with NDS 8 which will further increase the numbers of users we can support.

We also make NT server more secure because some password hacks, such as LOFTCRACK, no longer work because the data is stored in a true database and not the registry.

Pricing is always a difficult question with any product. The full-retail pricing of NDS for NT is $26 per managed user.

How do I keep passwords synchronized?

Question: The last company I consulted for used ZENworks for all its NT clients. The advantages were highly valued. The single sign-on was very important because there were 600+ users.

Some applications requiring an NT Domain were just beginning to be implemented, and I helped set up NDS for NT to manage them. One problem we had was maintaining password synchronization. The trade-off was this: if we allowed a workstation to join a Domain and do a Domain login, it was no longer a generic workstation, and if the workstation remained standalone, a second login to the Domain was required and the Domain password would eventually become unsynched. While this is basically a Microsoft problem resulting from the differences between Domain and Workgroup type logins, I am wondering if you have any plans that might correct this problem—such as an intelligent login by Workstation Manager?

Answer: I assume that you were using the NDS for NT v1.10 code and not 2.0 or 2.01. With NDS for NT v2.0, we added the ability to guarantee that the NDS and domain passwords were always synchronized once NDS for NT was installed.

To do this, you need to check the "Force Password Sync" option on the user accounts. (This can be selected domain-wide during the installation of NDS for NT as well.) Then install the Novell Client v4.5 for Windows NT or higher or the Novell Client v3.0 for Windows 95/98 or higher on your workstation.

Once you have these things in place, we have not found a single scenario where the passwords get out of sync, as long as a Windows-based utility is used to change the password. (There's no support for DOS utilities such as SETPASS.)

Can you give me a synopsis, for a business case, of the benefits of NetWare and NDS vs. NT?

Question: I'm developing a presentation in which I have to defend NetWare and the capabilities of NDS for NT; the push is to go NT all the way. I know some of the advantages of NDS for NT, but I don't have a clear idea on how to compare it, point for point, to what NT does. Can you give a synopsis?

Also, if we do keep NetWare, we will still be supporting a lot of NT application servers. What plans are there for NDS for NT to support Active Directory in NT 2000?

Answer: The answer to your Windows 2000 and Active Directory question is in a previous response. We have talked today about a number of things such as the enhanced scalability and security NDS for NT brings to NT server. Let's talk money $$$ now.

Neil MacDonald of the Gartner Group in his research report, "NDS for NT v.2: A Good Product Gets Better" stated the following:

?All organizations using NDS and NT domains should consider NDS for NT v.2?it is a simple, effective, low-risk and low-cost way to reduce duplicative costs. Organizations using NDS for NT will reduce administration and management costs of a mixed NDS/NT domain environment by 40 percent ($35,000 per year for a 2,500 user organization) and up to an additional 10 percent if NDS for NT v.2 is used to consolidate Exchange administration.?

Robert J. Sakakeeny of the Aberdeen Group, in his research report called "Novell Directory Services for NT Server", stated the following:

?For those organizations managing multiple NT Server domains, especially those used as application servers, NDS for NT is a life-saver.? ?For those wanting to manage their heterogeneous network environments, and for those who were awaiting the elusive Active Directory from Microsoft, it's time to consider the one directory service that will work in all those worlds.?

And finally, Laura DiDio of the Giga Information Group, in her article "New Branch on the NDS for NT Tree", stated the following:

?All of this is most-welcome news for beleaguered administrators who have grown weary and frustrated with the limitations of the NT domain directory architecture.?

?Let's not forget Windows 2000 and the Active Directory will be 1.0 products when they ship. That means lots of bugs. By contrast, NDS for NT is a mature directory that is miles ahead of Active Directory in functionality.?

The bottom line is that NDS for NT significantly improves NT Server and enables it to be used in the enterprise.

Reader Answer: As a starting point, I might recommend checking out the Aberdeen Group and Gartner Group reports that compare the two platforms.

I have found when presenting my business case that using a respected research organization helps the case a lot, rather than using information from either vendor; the vendors have a bias (and a vested interest in the outcome), but the research companies do not.

Aberdeen Group has written a few reports comparing aspects of NT 4 and Windows 2000 to NetWare 4.x and NetWare 5. I also look to Ziff-Davis publications for articles that support my objective (NDS/NetWare typically). However, these articles tend to be more biased towards Microsoft solutions, but having information to support your position from organizations that traditionally support another view is usually very persuasive.

What is the solution for mapping to NT servers?

Question: What is the solution for mapping to NT servers? Our application is a local NT server with a replica, the Novell server spans 1 WAN link (512K) and holds the master replica.

Net use commands do not work in the Novell login script.

Example: #net use h: \\nt-usa-1\user$ (the # signifying a command to execute BEFORE returning to the script)
Example: exit "finish.bat", where finish contains; net use h: \\nt-usa-1\user$.

For some reason Novell replaces nt-usa-1 with the Novell server, \\testsrv\user$. The news group novell.directoryservices.ndsfornt is just touching on this issue.

Answer: Larry, it sounds like you are using Windows 95/98 on the desktop. If you place a net use command in the login script, it will fail on a Windows 95/98 workstation because the Microsoft SMB Client has not yet loaded. The solution on Windows 95/98 is to put the net use command in a batch file, and then exit the login screen to the batch file.

On a Windows NT workstation net use works great from the login script because the Microsoft SMB Client has loaded. This is just one of the many differences between Windows 95 and NT that make NT a better workstation on the corporate network.

Reader Answer: I fixed it. :)

  1. Set the primary logon to NW Client (I'm using version 3.0.1.0 and Windows 95).
  2. Add the following to the container login script.

    SET NTVariable="%NetWare_Variable" (*This "passes" the NetWare variables to NT.)
    SET LOGIN_NAME="%LOGIN_NAME"

Logon Process:
NetWare Client login to NDS
Run Container login script
Login to Domain
Run script specified in user manager (YOUGO.bat)
Exit to OS.

YOUGO.bat file
net use f: \\nt-usa-1\sys
net use h: \\nt-usa-1\%LOGNIN_NAME%$
net use r: \\nt-usa-1\shared

Works like a charm!

Do you have any plans to add the ability to edit e-mail addresses for Exchange users from NWAdmin?

Question: Any plans to enhance the Exchange plug-ins so we can edit (add, modify) the user's e-mail address from within NWAdmn32?

Answer: Yes. We are working on that right now.

Are there any plans to improve the performance of NDS for NT?

Question: What is the plan to enhance performance for NDS for NT? All of our NT workstations experienced tremendous slowdowns when authenticating through NDS and accessing NT domains controlled by NDS. We had to remove it because it was intolerable. We did not see the same problems with 95/98 workstations accessing the same NT domains/servers.

Answer: Luis, your situation is one we would have to look into. We have done some scalability testing here in our labs where we have had 50 workstations simultaneously authenticating to a domain 20 times each. Each workstation authenticates, runs a script, then logs out 20 times. As you can imagine, the NT server utilization is pegged at 100% during this process.

We ran this test without NDS for NT installed, and then we ran it with NDS for NT installed. We were able to authenticate users at the same rate in this test that an NT server without NDS for NT did.

If you are placing an NDS replica on the NT server, I would strongly recommend that you use NDS for NT v2.01, and use only IP on the NT server running the replica. The NDS replica performs much better using IP than IPX.

Are there any known problems using NDS for NT with Arcserve?

Question: I'm using Arcserve from Computer Associates. Before I installed NDS for NT, I could restore my entire server from tape. Now when I restore, I get various problems like "bindery.dll not found", and I can't log into the server anymore. In fact, it doesn't work even when I use "workstation only" login. The only solution seems to be to remove NDS using one of your technotes.

Harold, I am not familiar with problems with Arcserve and backups on NT server. We have run into a couple of backups (documented in TIDs) that did not take the proper route and call the proper API to backup their domain—they simply backed up the registry.

I did speak with a customer in Denver a couple of weeks ago that has done away with all BDCs using NDS for NT, and he only has the PDC (do not try this at home - this is not a recommended configuration). They used Cytos to back up their NT server and domain, and then they did an FDISK on the PDC. They recreated the NT server, and the Cytos backup restored everything.

I would recommend that you open a call with Support and work through the Arcserve issue with them.

What comments can you make on the price of licenses for NDS for NT?

Question: We currently have about 10,000 users in our organization. Of these, only 3,000 are NDS users. We have a need to add the other 7,000 to our Intranet which is currently IIS. We need everyone to authenticate before accessing the Intranet. The cost to purchase both NT server and NDS for NT licenses is prohibitive. So the decision is being made to purchase only NT server licenses with several hundred users on each, less than $1,000 per server. This puts us in the position of having all of the clients in the NT database and only 25% in the Novell directory.

Answer: Liz, my recommendation to you would be to talk with your Novell Sales representative and see what can be done.

Is there any comprehensive documentation available for NDS for NT?

Question: Documentation for NDS for NT is sparse to say the least. One technical white paper and one AppNote is about all I have found.

I am reduced to reading loads of irrelevant TIDs and the Support Forum to try and piece together how this product works. I end up spending many hours in the lab having to figure it out for myself. Are there any plans to put out an authoritative work?

Answer: I will take your feedback to the documentation team.

Reader Response: I agree Don. I spoke with the Customer Response Team, Justine specifically (very, very helpful), and complained about the lack of documentation. I purchased the Novell recommended NDS for NT book that basically says what the white paper says. I've found a lot of answers on news://forums.novell.com/novell.directoryservices.ndsfornt and in this discussion.

I've never seen Novell not support their products, thus I'm not worried. It's just trying to get over this hill with our initial migration to NDS for NT.

Is there any way to merge duplicate users as you import them into NDS?

Question: If we import users when installing NDS4NT and they have a duplicate Novell account is there any way to merge the information in the accounts.

Yea, baby yea —to quote my favorite international man of mystery, Austin Powers.

When you install NDS for NT one of the options is to search the NDS tree for duplicate user accounts—then merge them as the domain user accounts are migrated into NDS.

What weaknesses do you see with Microsoft's Active Directory?

Question: What weaknesses do you see with the still unreleased Active Directory, and what advantages does NDS for NT bring to a mixed NDS/Microsoft environment?

Answer: The biggest weakness that I see with Active Directory is that it is not shipping. When it does ship, it is going to take years for them to iron out the bugs. Last time I heard there were around 30,000,000 lines of code in Windows 2000— more than 2/3 of which is new.

What performance enhancements will be added to NDS 8 for NT?

Question: It is my understanding v 2.1 of NDS for NT will be using NDS 8. What performance gains will version 2.1 have over version 2.01?

Answer: You will see a difference in scalability and performance equal to the difference between the NDS that shipped on NetWare 5 and NDS 8. NDS 8 for NT will be able to hold millions of objects, and will have the best scalable-performance for LDAP searches on an NT server.

Does NDS for NT create accounts in the Exchange namespace when you add a new domain account?

Question: If I am running Exchange server, does NDS for NT create accounts in the Exchange namespace when new domain accounts are created?

Yes! NDS for NT ships with a solution called Exchange Mailbox Manager which allows for the administration of Exchange through NDS. Most customers that have deployed NDS for NT and the Mailbox Manager use an NDS template when they create new users. The template automatically adds the users to the necessary domains (without trust relationships) and adds them to the Exchange database.

My testing of NDS for NT is going perfectly. Am I missing something?

Question: I'm looking into an NDS migration. We are a small company with two sites connected by a WAN link. At our main site we have currently a NW 3.12 server and a single NT server. At our other site we have an NT server. By the end of next month we will have 4 more NT servers at our main site and another at our second site! We (mostly I) will have at least 4 domains to manage.

I am trying to promote migrating the 3.12 server to NW 5 and incorporating NDS for NT on pure TCP/IP . I would like to migrate all the domains to NDS. We have 256k link to our other site and I would like to keep a replica on the NT server there.

So far all my testing seems to be a breeze. Am I missing something? Is this how I should proceed?

Answer: The scenario you describe is precisely the scenario for which we built NDS for NT. We spoke with numerous accounts that had NetWare at their corporate headquarters and NT servers in the branch offices—people just like you. Sounds like everything is going great.

Is there any way to install NDS for NT remotely?

Question: I have a customer with NT servers in several remote sites. I'd like to install NDS for NT on these servers without the assistance of their "support" staff. Is there any way to install this product remotely?

Answer: You could steer the installation of NDS for NT on the BDCs through a remote control solution. The BDC server will need to reboot after the installation so you will want someone at the remote office in case there are any issues with the reboot (none expected).

The migration of the users from the domain into NDS only occurs at the PDC. On the BDC the users do not have to be migrated - we simply need to install the software. We are working on a solution to remotely install.

Does Novell have any plans to support NDS for NT in a workgroup model?

Question: Does Novell have any current plans to support NDS for NT in a non-domain-architecture model (i.e., a workgroup model) or to allow for replication to non-domain-controller servers? The branch office environment I work in does not have a PDC/BDC at every branch office, but I would like to investigate moving NDS for NT into those servers. Ideally, we would create a separate domain for each branch and duplicate the accounts needed for the branch office to function. Thanks!

Answer: We are looking into this ability but do not have anything on our committed roadmap. You may want to look at Synchronicity for NT - it can be used in a workgroup model.

Reader response: Thanks for that info. I really would like to avoid synchronization problems. We have looked at Synchronicity (about a year-year and a half ago) and it didn't quite meet our needs.

On what platforms will NDS be available?

Question: What other platforms is Novell looking at providing NDS for? I am aware of Solaris (SPARC), HPUX, Linux, and NT efforts under development as well as IBM's OS/390 initiative. Are there talks about cross platform NDS for OS/400, Solaris x86 (this is a big one for me), SCO/UnixWare, SCO/OpenServer, and other popular flavors of Unix? Anything on the horizon for FreeBSD?

Answer: Novell currently delivers NDS on NetWare, NT and Solaris. We have announced and demonstrated NDS for Linux. IBM is working on NDS on their various platforms. The highest customer demand we have seen in additional to the previously mentioned platform are HPUX and Solaris (Intel) which we are working on.

Reader response: Great news—especially the Solaris x86 port - we're looking forward to that.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell