Can GroupWise work without NDS 3

[Buzzard7]

I am trying to convert from Novell to Windows 2003 Server. I would like to keep GroupWise. Can I run GroupWise with Windows 2003 Server? If so, can I move my email from GroupWise over to Windows?

 

[Buzzard7]

When I try to manually create users I receive this message when tring to link NDS user to GroupWise user.

Does NDS object correspond to GroupWise object?

Then I click yes. Then I recieve this error:

javax.naming.ConfigurationException

 

[Buzzard7]

Can I export the NDS of the Netware server while the test server is on a different network?

If not, then when exporting on the same network, will the NDS stay the same on the Netware server, or will it be moved to the test server? If I do export the NDS, do I need to take the test server off the network as soon as the export is done?

The main thing is I don't want to crash my Netware server.

 

[Buzzard7]

I put eDirectory on another Windows server, and tryed to export the NDS. I recieved this errors:

Record 1: LBURP operation failed: 64(Naming violation), dn:
Record 2: LBURP operation failed: 50(Insufficient access), dn: o=Group
Record 3: LBURP operation failed: 32(No such object), dn: cn=TestServer-NDS,o=Group
Record 4: LBURP operation failed: 32(No such object), dn: cn=Admin,o=Group
Record 5: LBURP operation failed: 32(No such object), dn: cn=TestServer-NDS-PS,o=Group
Record 6: LBURP operation failed: 32(No such object), dn: cn=LDAP Server - TestServer-NDS,o=Group
Record 7: LBURP operation failed: 32(No such object), dn: cn=LDAP Group - TestServer-NDS,o=Group
Record 8: LBURP operation failed: 32(No such object), dn: cn=Http Server - TestServer-NDS,o=Group
Record 9: LBURP operation failed: 32(No such object), dn: cn=SAS Service - TestServer-NDS,o=Group
Record 10: LBURP operation failed: 32(No such object), dn: cn=SSL CertificateIP - TestServer-NDS,o=Group
Record 11: LBURP operation failed: 32(No such object), dn: cn=SSL CertificateDNS - TestServer-NDS,o=Group
Record 12: LBURP operation failed: 32(No such object), dn: cn=SNMP Group - TestServer-NDS,o=Group
Record 13: LBURP operation failed: 32(No such object), dn: ou=Users,o=Group
Record 14: LBURP operation failed: 32(No such object), dn: cn=Test,ou=Users,o=Group
Record 15: LBURP operation failed: 32(No such object), dn: cn=Test,ou=Users,o=Group
Record 16: LBURP operation failed: 32(No such object), dn: ou=TN,o=Group
Record 17: LBURP operation failed: 32(No such object), dn: cn=Unionville,ou=TN,o=Group
Record 18: LBURP operation failed: 19(Constraint violation), dn: cn=Security
Record 19: LBURP operation failed: 50(Insufficient access), dn: cn=KAP,cn=Security
Record 20: LBURP operation failed: 50(Insufficient access), dn: cn=W0,cn=KAP,cn=Security
Record 21: LBURP operation failed: 19(Constraint violation), dn: cn=Test Organizational CA,cn=Security
Record 22: LBURP operation failed: 50(Insufficient access), dn: cn=Authorized Login Methods,cn=Security
Record 23: LBURP operation failed: 50(Insufficient access), dn: cn=NDS,cn=Authorized Login Methods,cn=Security
Record 24: LBURP operation failed: 50(Insufficient access), dn: cn=CertMutual,cn=Authorized Login Methods,cn=Security
Record 25: LBURP operation failed: 50(Insufficient access), dn: cn=DIGESTMD5,cn=Authorized Login Methods,cn=Security
Record 26: LBURP operation failed: 50(Insufficient access), dn: cn=Simple Password,cn=Authorized Login Methods,cn=Security


Total entries processed: 26
Total number of errors: 26
End time: Friday, June 27, 2003
Total Time: 0:00:16.843
Time per entry: 00:00.647

 

[Buzzard7]

I found this information on Novell's web site, and I thought the "Prepare for Hardware Upgrade" might be the way I need to go.
How do you use "Prepare for Hardware Upgrade"? Is it an executable?


How to Duplicate An Existing Tree

Question: MW wrote: Short of using DSDUMP to restore a DIBset, what would be a good way to set up an exact duplicate of an existing tree in a lab? Can something like DSDesigner do this?



Answer: Depending on what you want to duplicate you may be able to DirXML eDirectory to eDirectory, or if you simply want Users, Groups, Containers etc. then you can use ICE to move everything but the user passwords across. ICE can do Server-to-Server LDAP so there is not a middle step of exporting to a file and then importing the file. DSDesigner will simply represent the Tree in a GUI; it will not create it for you.

To duplicate the same NDS tree you could do a "Prepare for Hardware Upgrade" on a server holding all partitions of the tree. Copy the file to a lab server where you removed the temporary NDS. Then do a "Restore after Hardware Update" and you will have the same NDS information on a lab tree. Make sure the servers are on their own environment to prevent a duplicate tree.

Another method could be using cpqfm.nlm and to copy the complete sys:_netware directory to the lab server. Again, make sure the servers are on their own environment to prevent a duplicate tree.

Yet another approach is to use TID 10050607 "Can I split my NDS tree?". With this one you do have to be extremely careful that the duplicate tree cannot contact the production tree, even for a second, until it is renamed and any duplicate server names and IDs are changed. After that you're cool to go.

Or, if the DSMaster server has mirroring for its drives, rip one out and use it for the lab and stick in a new one in the DSMaster to rebuild. From a liability standpoint we only indirectly hint at this, but the result is the purest duplication of a production environment you can imagine. Except for the negligible risk, no real downside. Otherwise use LDIF, it's the least likely to do something bad to the production environment.

 

[Provogeek]

Good job on the research, your getting closer to the answer.

No, "Prepare for Hardware Upgrade" is not exactly an executable, it is a part of NWDeploy.exe found on the NetWare 6 NOS CD.

The information you found on ICE is the right track you should be following if you want to duplicate your tree. The TID you found went down paths you really don't need, keep searching on Novell's knowledge base.


Here is a link to the AppNote: Using the Novell Import Convert Export Utility; Posted 01 Oct 2000.

http://developer.novell.com/research/appnotes/2000/october/02/a001002.htm

 

[gchilders]

I have just done this (move GroupWise system to Windows 2003 server) in the lab, and plan to do it on the production server next week. I'm in the process of documenting the steps right now.

 

[Buzzard7]

gchilders, when you get the steps documented, will you post them or send me an email?

Thanks

 

[gchilders]

GroupWise Migration Procedures to Migrate from GroupWise 5.5 on NetWare to GroupWise 6.5 on Windows 2003:

Source Server: existing NetWare 5.1 SP5 with GroupWise 5.5 SP4 installed
Destination Server: Install Windows 2003 Server and latest NOS updates

Install eDirectory 8.7 to Windows 2003 server:
Select NDS, SLP, ConsoleOne
NW Client Install / eDirectory 8.7 License Install (requires license file) / NICI 2.4.1 Install / Reboot
eDirectory 8.7 Install: C:\Novell\NDS, Create new NDS tree (give Tree name, context, Admin password), Create Certificate Authority (defaults)
ConsoleOne Install (defaults) / SLPDA Install (defaults)


Migrate users from source to destination NDS tree:

ConsoleOne on PC connected to source NetWare server:
Wizards > NDS Import/Export, select Export LDIF file
Enter NetWare Server IP Address and port (636), browse to RootCert.der file in SYS:\PUBLIC
Select Authenticated Login, Enter cn=admin,o=<context> (remember - comma separator) and password , NEXT
Enter Base DN (o=<context>) and scope (one level)
On Filter tab, enter objectclass=user
On Attributes tab, select Attributes, List
Add attributes: < dn, givenName, fullName, sn, cn, objectClass>, Close, NEXT
Select (create) LDIF file, NEXT, FINISH
View export results. Restart, change parameters, and retry if necessary, or CLOSE

Edit LDIF file with Notepad:
Remove entries for the Admin and Guest users, if exist (to avoid generating import errors)
For each user entry, you should have:
dn: <distinguished name>
changetype: add
givenName: <given name>
fullName: <full name>
sn: <surname>
cn: <common name>
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
You may have to change the context in the Distinguished Name fields, if the contexts differ from your source and destination NDS trees
(Hint: use Edit > Replace in Notepad or Wordpad to change multiple entries)
Copy LDIF file to the Windows 2003 server with eDirectory 8.7 installed

ConsoleOne on destination (Windows 2003) server with eDirectory 8.7:
Export Trusted Root Certificate: browse to SSL Certificate IP object, Properties
On Certificates > Trusted Root Certificate tab, Export
Select No to export the private key, NEXT
Select binary .DER format, browse to C:\Novell\NDS folder
Name file RootCert.der, SAVE, NEXT, FINISH

ConsoleOne on destination (Windows 2003) server with eDirectory 8.7:
Wizards > NDS Import/Export, select Import LDIF file, NEXT
Select Source LDIF file, NEXT
Enter Windows Server IP Address and port (636), browse to RootCert.der file in C:\Novell\NDS
Select Authenticated Login, Enter cn=admin,o=<context> (remember - comma separator) and password, NEXT
Finish to begin LDIF import
View import results. Restart, change parameters, and retry if necessary, or CLOSE
View NDS tree to verify that imported users are visible

Close ConsoleOne on Windows 2003 server


Install and Migrate GroupWise System to the new Windows 2003 server:

1. Install GroupWise 6.5 to the new Windows 2003 server (insert GW65 CD, select Create or Update GroupWise System from the Install browser)
At Administrative Options, uncheck Create or upgrade new system, leave all other options checked
Extend NDS Schema / Install Administration Files / Copy files to software distribution Directory, FINISH.
2. Copy the entire post office and domain directories you want to move to the new server to the new file location on that server.
3. Launch ConsoleOne: Close or Cancel on all GroupWise errors given while launching. Highlight GroupWise System in the left pane.
4. Select Tools | GroupWise System Operations | System Connection, then browse to the copied domain directory | OK.
(This will prompt you to log into the old tree. Just cancel out and all System Operations except System Connections will grey out.)
5. Select the container (Context) that you want the Domain Object to reside in.
6. Select Tools | GroupWise Utilities | GW eDirectory Association | Graft GroupWise Objects
7. Follow the steps in the Graft Wizard to graft the domain and post offices in to the new NDS Tree.
8. At the end the Wizard will ask if you want to graft more GroupWise Objects. If you are ready, and the user objects have all been created, select Yes.
9. Follow the Graft Wizard to graft users in to the tree.
(This is actually a matching process in which the Wizard will ask for the user`s context, then scan to match NDS User Objects with GroupWise users)
10. At the end the Wizard will ask if you want to graft more GroupWise Objects. Select No.
11. From the GroupWise Install browser, Install Products | GrouWise Agents | Install GroupWise Agents
12. Select Windows NT/2000, select installation path, select install as Services | Add the Domain and Post Office paths and names
13. Select Use System Account, Allow service to interact with Desktop, and Automatic startup type, NEXT | INSTALL
14. Uncheck Launch Agents now, FINISH
15. ConsoleOne: Access properties of the Domain object, and change the UNC path to point to the Domain directory. Change Network Type to Lan Manager.
16. Access properties of the Post Office, and change the UNC path to point to the Post Office path. Change Network Type to Lan Manager.
17. Access properties of the POA and MTA, change the Platform to Windows, and change the Network (IP) address if it changed.
18. Start the GroupWise Agents from Start | Programs | Administrative Tools | Services. Find and start the <Domain> MTA and <PostOffice> POA services.
19. If you selected Allow services to interact with Desktop, you will see windows open for the MTA and POA, similar to their NetWare screens.

You should test open a few accounts just to make sure the users can access their mail. Depending on the number of users you may want to check them all.
Note: all GroupWise clients should access the post office via Client/Server (IP) access.
Once again view the properties of the Domain and Post Office objects in ConsoleOne -- notice the database version should (eventually) change from 5.5 to 6.5

20. ConsoleOne: Change the Software Distribution directory UNC path in Tools | GroupWise Utilities | Software Distribution Directory Management.

After validating the local mail system, you can run the Internet Agent and WebAcess Agent installations (if desired).

 

[Buzzard7]

After doing this, will this have an effect on the Netware server? I want to keep my Netware server up and going.

 

[gchilders]

I have now implemented these steps on the production system, a dry run migration prior to final implementation. I am running the two (identical, except for IP addresses) GroupWise systems side-by-side on the production LAN for pilot testing, with no effect on the production GroupWise system. Essentially, the two GW systems are unaware of each other.

The key is to carefully check all the property pages for the migrated system prior to bringing up the agents on the Windows server, to ensure that none of them point back, via IP address or via UNC path, to the old system. If you intend to keep the same IP address on the migrated system (due to MX record), then you'd better keep the migrated system on a separate, isolated LAN for pilot testing, until you are confident enough for final implementation.

Since DNS was implemented in-house for the Windows 2003 implementation, I was able to add the &quot;A&quot; records for ngwnameserver and ngwnameserver2, pointing to the current (NetWare) GroupWise system. I changed all the existing GW5.5 clients (via batch file in login script) to point to the /ipa-ngwnameserver, instead of the previous hard-coded IP address. That way, when I perform the cut-over to the new GW system (tonight), all I have to do is change the DNS record to point to the new server, and all the clients will automatically go there. I will also have to change the firewall to redirect SMTP to the new IP address.

During this pilot testing, I can manually point the clients to the migrated server to verify that they can send/receive mail. I can even test outgoing (but not incoming) Internet mail (after installing GWIA). Pretty cool, eh? By the way, it's a good idea to perform the (gwcheck) database maintenance, and even expire/reduce, on the existing GW system prior to migration, if possible, to avoid having to migrate all the trash over with the mail. Also, you have to install GWIA on Windows to run as an application (not a Service)-- it's a known bug.

 

[edcard]

Hey GChilders,
Nice info that you give there, listen I'm trying to do the same installation but unfortunately I’m not very proficient with Novell and I came up with this problem.
Following your steps, when I hit finish to star the Export LDIF Wizard I get the following message:
ldap_simple_bind failed: 81(Can't contact LDAP server), dn: cn=admin,o=PF
I have done a little bit of research and the closest answer that I found from Novell site was this: &quot;Either the IP address/port combination is incorrect or the LDAP server is not running. Verify the IP address and LDAP port, make sure the server is running, and try again.&quot;

I'm definitely sure that I have the correct IP and Port numbers and my Novell server is up.
Any suggestions on how should I start troubleshooting this issue?

I'm running Netware 5.1 and GW5.5 but trying the LAB on W2k and GW 6.5 also I installed eDirectory with the free Evaluation License that Novell gives out, do you think that would have anything to do?

Any comments would be much appreciated, thanks.