The tool for you is Novell's "Server Consolidation and Migration Toolkit". You can go to download.novell.com and search for 'scmt.exe' to get it. That provides a way to do a server migration from point A to point B. It's really really good. I've used it for cold P2P migrations for years before P2V became an option. It's not a next-next-next-finish P2V process, but is pretty close. The procedure is:
- Install NetWare to your VM. Name it something unique, and in its own eDir tree.
- This sets up your hardware environment.
- Launch the SCMT.
- Select "Migrate Data to New Server (hardware upgrade)"
- Select the tree of your in-production NetWare server.
- Select the tree of your server you set up in step 1.
- Then arrange your data to taste (you can even change volume names if you want, but I don't think you want to here) using the drag-n-drop interface.
- When it comes time to pull the trigger on the migration, shut down all running GroupWise agents on the source server.
- In the SCMT go to Project and select Migrate.
- Follow the prompts. It'll guide you through the process.
- You'll probably have to hand-edit autoexec.ncf to ensure the config is fully what you want.
- It's probably a wise thing to comment out the groupwise load-lines for now.
When all is done, you'll shutdown your old server and restart the VMed server. When the VMed server comes up it'll come up. Verify it looks the way it should, and manually start the GroupWise agents. If it comes up clean (and it should) de-comment the load-lines in autoexec.ncf.
This tool would also allow you to migrate to OES2-Linux if you want, which is actually a better host for GroupWise than NetWare. I'd hold off on that due to the GroupWise, since that complicates the migration process in ways that are hard to describe here.