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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can GroupWise work without NDS 3
- Thread starter Buzzard7
- Start date
-
2
- #2
No, GroupWise needs NDS to run. Even though GroupWise is not truly an NDS program, it only syncs with NDS, it still needs NDS to be administered.
GroupWise 4 was the last version of GroupWise that did not need NDS for any reason.
GroupWise 5 & 6 have Windows agents, so yes you can run GroupWise on a Windows server (and the actuall migration will be VERY easy). You will need to install eDirectory onto the Windows server. eDirectory is cross platform, and if all this server will be doing is GroupWise, then it will be the only server that MUST have eDirectory installed. To play it safe, also load a Linux or Windows box and install eDirectory onto it. This will give you a second replica of the DS database. This will also allow you to place the GWIA on a different box than the PO (recomended for security reasons). Be sure to install eDirectory onto the windows box while your current NetWare server is up and running. Get the NDS database, make the Windows box the master of ROOT, migrate mail directories over, change config files and edit NDS objects, then think about removing the NetWare server.
Remember, once you install eDirectory onto you Windows server, MS will no longer support that Windows box. Novell will, and there is a lot of info in the knowledge base when you need help (and tek-tips too).
GroupWise 4 was the last version of GroupWise that did not need NDS for any reason.
GroupWise 5 & 6 have Windows agents, so yes you can run GroupWise on a Windows server (and the actuall migration will be VERY easy). You will need to install eDirectory onto the Windows server. eDirectory is cross platform, and if all this server will be doing is GroupWise, then it will be the only server that MUST have eDirectory installed. To play it safe, also load a Linux or Windows box and install eDirectory onto it. This will give you a second replica of the DS database. This will also allow you to place the GWIA on a different box than the PO (recomended for security reasons). Be sure to install eDirectory onto the windows box while your current NetWare server is up and running. Get the NDS database, make the Windows box the master of ROOT, migrate mail directories over, change config files and edit NDS objects, then think about removing the NetWare server.
Remember, once you install eDirectory onto you Windows server, MS will no longer support that Windows box. Novell will, and there is a lot of info in the knowledge base when you need help (and tek-tips too).
- Thread starter
- #3
If I get the NDS database from the Netware server and migrate mail directories, will this effect my Netware server?
I'm just wanting to test this out for now. Is it possible to do this and still have the Netware server running, and will my groupwise on my Netware server stay functional.
I'm just wanting to test this out for now. Is it possible to do this and still have the Netware server running, and will my groupwise on my Netware server stay functional.
yes, you can copy NDS to your test server and copy your domain and po directories to a test server (don't for get the agents and config files stored in SYSTEM) with out affectiong your production server.
FYI: You don't have to use your production NDS, you can use a clean copy of NDS and still use your production groupwise directories. GroupWise will still run, but you will need to use teh groupwise view in NWAdmin to see the users.
FYI: You don't have to use your production NDS, you can use a clean copy of NDS and still use your production groupwise directories. GroupWise will still run, but you will need to use teh groupwise view in NWAdmin to see the users.
- Thread starter
- #5
Can I setup my test server with eDirectory and Groupwise and have the same settings as my Netware server. (ex. Tree; context; domain) Will this effect the Netware server?
I am just testing, I'm not sure if we will actually get rid of the Netware server, so I don't want this to have any effect on the Netware server.
I am just testing, I'm not sure if we will actually get rid of the Netware server, so I don't want this to have any effect on the Netware server.
- Thread starter
- #6
I already have give you what you need to move your mail system from one server to the other. Since this is a test enviroment you are working with, just tell me what parts with the mail system move you are having problems with. You will learn more by doing it your self and fouling things up than if I tell you step by step.
- Thread starter
- #8
I installed eDirectory to a Windows server. I'm not using the same settings as the Netware server.(ex. tree,context,server) I also have groupwise set up on the Windows server. I also have different settings than the Netware server.(ex. domain,PO) I am having a problem logging on to a test user in groupwise, online. I am trying to login online with the test servers, ip and port 1677. I can login to the admin groupwise account, online.
The main question is, can I use the same settings as my Netware server and not effect it? I would like my test server to look identical to my Netware server groupwise settings, without effecting it. I still want my Netware server up, untill I get everything ready. I am just trying to get the email straighten out first. Then I will try converting over the domain from Novell to Windows.
The main question is, can I use the same settings as my Netware server and not effect it? I would like my test server to look identical to my Netware server groupwise settings, without effecting it. I still want my Netware server up, untill I get everything ready. I am just trying to get the email straighten out first. Then I will try converting over the domain from Novell to Windows.
- Thread starter
- #10
Well yes, it will affect the server. It will not change in any way the operation of the server, but it will affect it. You are installing eDirectory onto another server, and a replica is being copied to it. The NetWare server will know about this other server and will sync DS data with it. If the servers can not communicate, you will see your DS fall out of sync unless you fix the communication problem or remove the server from DS (not exactly a stright forward thing).
If this is just a test, the use as a test. Do not attach it to your production network at all. Leave it in an isolated network with zero access in any way to your production server or your production network for that matter. Install, screw it up, try again, screw it up again, try again, and always note what you did last time so you can teach your self this stuff.
If this is just a test, the use as a test. Do not attach it to your production network at all. Leave it in an isolated network with zero access in any way to your production server or your production network for that matter. Install, screw it up, try again, screw it up again, try again, and always note what you did last time so you can teach your self this stuff.
- Thread starter
- #12
I put the test server on a different network. I reinstalled eDirectory with the same settings as the Netware server.(ex. tree,context)
When installing GroupWise, I used the Update, and used the Groupwise directories from the Netware server.
In ConsoleOne, it looks the same as the Netware server ConsoleOne. But, when I try to go to properties of the Domain or the PO, I receive this error message: An error occured converting the GroupWise object to its NDS counterpart.(ex)(Domain name here).(PO name here).Tree
Tree name here) Distinguished NamePO name here). The NDS counterpart of this object does not exist.
How can I convert the GroupWise object to its NDS counterpart? Can I just copy a directory from the Netware server? If so, which one?
When installing GroupWise, I used the Update, and used the Groupwise directories from the Netware server.
In ConsoleOne, it looks the same as the Netware server ConsoleOne. But, when I try to go to properties of the Domain or the PO, I receive this error message: An error occured converting the GroupWise object to its NDS counterpart.(ex)(Domain name here).(PO name here).Tree
Tree name here) Distinguished NamePO name here). The NDS counterpart of this object does not exist. How can I convert the GroupWise object to its NDS counterpart? Can I just copy a directory from the Netware server? If so, which one?
- Thread starter
- #15
- Thread starter
- #16
- Thread starter
- #17
Convert, no, you can't convert. What you can do is do an export of your NDS using ICE, or any other LDAP tool. Then import the info into your test tree using the LDIF file you create.
You can also create the users manually, when you create an NDS user with the same name as the GroupWise user, the system will detect a user with the same name in the groupwise database and ask you if you want to link them.
If you import them, you will need to touch each user to link the NDS id with the groupwise id.
You can also create the users manually, when you create an NDS user with the same name as the GroupWise user, the system will detect a user with the same name in the groupwise database and ask you if you want to link them.
If you import them, you will need to touch each user to link the NDS id with the groupwise id.
- Thread starter
- #19
- Status
Similar threads
- Locked
- Question
- Locked
- Question