I want to be able to have Novell as the primary login using Novell 4.11 server and Win98 workstations with Client32. We also have Windows 2000 server and I am looking for a product that will keep the Win2k passwords in sync after the Novell password expires and gets changed. I know about NDS for NT but I wonder if there are any low budget options. I read about Microsoft Services for Netware5 and wondered if anyone used it or anything else?.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Novell and Win2K Passwords
- Thread starter MarkhP
- Start date
IN order to do what you are wanting, you will need to use E-Directory. That will allow both NDS and NT to keep the passwords synch'd. With E-Directory installed on the NT server, you can make a change in NWADMIN and it will automatically update the information on the NT Server. If you are working on the NT server and make a change to a users account at the server, the change is then pushed out to NDS. So its kind of nice that it works in both directions. You can also add users to groups etc within NWADMIN for the NT server (access to shares) and you don't have to worry about domains etc because NDS overrides it.
HTH
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
HTH
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
IN order to do what you are wanting, you will need to use E-Directory (NDS for NT). That will allow both NDS and NT to keep the passwords synch'd. With E-Directory installed on the NT server, you can make a change in NWADMIN and it will automatically update the information on the NT Server. If you are working on the NT server and make a change to a users account at the server, the change is then pushed out to NDS. So its kind of nice that it works in both directions. You can also add users to groups etc within NWADMIN for the NT server (access to shares) and you don't have to worry about domains etc because NDS overrides it.
To help justify the cost of NDS for NT, take into account the amount of time you spend re-setting passwords for both platforms. Then from there, you average out the cost on a monthly basis and then for a year. You then take into account the costs associated with purchasing NDS for NT, you show a ROI in that the software will pay for itself by reducing downtime to the end user, reducing your time to reset 2 passwords, and show that over the course of 3 years, the software will more than pay for itself as it would increase production etc. Tkae my advice, you can sell the solution to your mgmt if you spend a little time plugging in the numbers and developing an ROI to show that the program is not just wasting money, but saving money.
All of the abovbe items mentioned downtime for users, your time to reset passwords etc. need to have a dollar value associated with it, that way you will have a pretty accurate account of how much it costs. Here is a good example, the cost for downtime per hour is about $350.00 So if you figure you spend about 4 hours a week resetting passwords, that averages out to $1400.00 a month, that times 12 months is a lil more than $16,800.00. Pretty impressive as to how fast that adds up. Now we take into consideration that NDS for NT is going to cost about $6000.00 just rough estimate. If you took that 6000.00 and showed the initial costs to buy the software and lets assume about 5 days for testing and 2 days to install and configure, so lets add about another $3000.00 for your cost in time etc. Now the total cost of the software is $9000.00 start to finish. If you know you spend about $1600.00 a month to reset passwords, you take the $9000.00 its going to cost and apply $1600.00 of the cost to each month. So lets see, 9000 divided by 1600 is 5.625 months. So if NDS for NT is purchased, in 5.625 months it should start paying for itself. WHich means less time for you to spend resetting passwords. IN fact you can take this one step further, you can even say that with the implemntation of this you will spend maybe a couple of hours each month resetting locked accounts so you can add that into the equation. So in turn it may actually take 7 months to pay for itslef, but longterm, you are now saving hte company money because months 8, 9, 10, 11, and 12 will have very reduced costs, and the following year, you will actually increase the bottom line and again for each successive year following. So take the time, do some research and put together a good ROI and you will see that the mgmt folks may actually buy off on the investment, especailly if they know the solution will increase the bottom lin long term.
And a word of advice, don't use anything that says some sort of MS service for netware, Microsoft can't write a decent server operating system, they sure can't mimic netware emulation in any fashion, though they try.
HTH
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
To help justify the cost of NDS for NT, take into account the amount of time you spend re-setting passwords for both platforms. Then from there, you average out the cost on a monthly basis and then for a year. You then take into account the costs associated with purchasing NDS for NT, you show a ROI in that the software will pay for itself by reducing downtime to the end user, reducing your time to reset 2 passwords, and show that over the course of 3 years, the software will more than pay for itself as it would increase production etc. Tkae my advice, you can sell the solution to your mgmt if you spend a little time plugging in the numbers and developing an ROI to show that the program is not just wasting money, but saving money.
All of the abovbe items mentioned downtime for users, your time to reset passwords etc. need to have a dollar value associated with it, that way you will have a pretty accurate account of how much it costs. Here is a good example, the cost for downtime per hour is about $350.00 So if you figure you spend about 4 hours a week resetting passwords, that averages out to $1400.00 a month, that times 12 months is a lil more than $16,800.00. Pretty impressive as to how fast that adds up. Now we take into consideration that NDS for NT is going to cost about $6000.00 just rough estimate. If you took that 6000.00 and showed the initial costs to buy the software and lets assume about 5 days for testing and 2 days to install and configure, so lets add about another $3000.00 for your cost in time etc. Now the total cost of the software is $9000.00 start to finish. If you know you spend about $1600.00 a month to reset passwords, you take the $9000.00 its going to cost and apply $1600.00 of the cost to each month. So lets see, 9000 divided by 1600 is 5.625 months. So if NDS for NT is purchased, in 5.625 months it should start paying for itself. WHich means less time for you to spend resetting passwords. IN fact you can take this one step further, you can even say that with the implemntation of this you will spend maybe a couple of hours each month resetting locked accounts so you can add that into the equation. So in turn it may actually take 7 months to pay for itslef, but longterm, you are now saving hte company money because months 8, 9, 10, 11, and 12 will have very reduced costs, and the following year, you will actually increase the bottom line and again for each successive year following. So take the time, do some research and put together a good ROI and you will see that the mgmt folks may actually buy off on the investment, especailly if they know the solution will increase the bottom lin long term.
And a word of advice, don't use anything that says some sort of MS service for netware, Microsoft can't write a decent server operating system, they sure can't mimic netware emulation in any fashion, though they try.
HTH
Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com
CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.
I work with NT servers, NDS for NT as well.
- Status
Similar threads
- Locked
- Question