WNT Migration to VMS

[Dave Barr_1]

All,
I have an Alphaserver running WNT which I can no longer get patched for the latest WNT security problems (unless someone here knows differently). My intention is to convert it to VMS and run Advanced Server on it. My problem is not technical, I just can't find any references to the offers that were made to allow the OS coversion from a licensing standpoint. Any info gratefully received.

Dave

[Antoniov.]

Hi Dave,
to help you we would answer allbodies!
I'm trying ...
I'm thinking you have not any NT application to run in VMS, because don't work, so I think you use AXP only as File Server.
You have migrate:
a) Domain controller
b) User list, user right, etc.
c) Shared folder
d) Shared printer queue;
e) Win NT registry entry of application installed in network;
f) Check the license on server and over network (compatibility problem may born).
I can't think any other and perhaps this is a first bill.
Tomorrow I'll try post another info.
Bye
Antoniov

[Martin P.J. Zinser]

I think the problem here is not a technical one (like switching the console FW).

At the time Compaq announced that support for WNT on Alpha would go away, there were a number of offers to ease the transition for customers (like a free "Upgrade" to a "comparable" Intel server...).
There might have been migration paths to Tru64 and OpenVMS too, although I am not particularly aware of them. Given the fact that all this happened a long time ago (at least 5-6 years IIRC) I seriously doubt there is still any general standing offer from hp out there. If you are good at negotiations you still might be able to get a discount from your sales person...

[Antoniov.]

Hi Dave,
I've forgotten in my prior check list the backup and restore data.

Hi Martin,
it's true migration from WinNT to VMS it's hard and there isn't support to do this.
But I think we can write a check list that help Dave to evaluate the cost (of money and time); I read HP has a project called Windows affinity so it would be interesting discover what this means. At least, OpenVMS is more robust of WinNT or 2K or XP.

I own will try to draw the bill.
Bye
Antoniov

[Art Wiens]

Not that I don't "love" Alpha architecture and the VMS o/s, but wouldn't it be much simpler (and cheaper!) to just buy an Intel box and move it over? No licensing issues, no technical issues (not many anyways), you can upgrade to 2K or 2K3 and "keep on patching".

I've asked before about switching "white box" Alpha's to VMS...HP said it "wasn't possible". Whether that's true or not, it's definately not supported.

Is this a hobbyist project or a "real-world" environment?

I'm sure I have to do some sort of penance now for suggesting such a thing! ;-)

Cheers,
Art

[Willem Grooters]

Dave,
Antonio is right that you have to move a lot of things, and it's not simply just a 'copy'
I run Advanced Server on my machine (plainly setup and populated) and I found there are quite a few issues to take in account. Be aware that AS is Windows NT4, not W2K or even XP. It _can_ do some things of W2K, but (for instance):
- as a Domain controller in a pure W2K environment is can only be a member, never the master. For NT is can be both PDC as PDC.
- W9x clients have trouble connecting into the domain (at elast, at my location it is, but ASAIK this is an NT problem).
And you need licences for VMS, AS as well.
There'se another possibility: Use samba in stead of Advanced server. It's available on VMS as well. Beware of the right version, though, I know 2.2.8 (for VMS!) is Ok and works with W2K. Saves you AS licenses (not VMS)