Early on we had problems with the security model in Win2K (different registry rights model, different PW check model, the permissions/rights stuff was quite a bit different etc...) so we had a lot of calls on that type of thing because we had bugs on our side that needed to be ironed out.
The LDAP port issue on Win2K trips a lot of people up as well, but that's not such a critial issue and is easy to work around. You do get the occasional site trying to cram the ADC on there and get it flying which is not supported, of course.
On the other hand the NT stuff is tougher to install since folks miss parts (or all) of the option pack items and the like and running that down is a real trick. Having to install the updated database files from MS catches a lot of folks as well. The Win2K install is pretty straight forward from our side and everything we need is there, so that's nice.
Since the release of 2.4.5, most of the Win2K issues have been worked out. I don't see either OS version having significant advantages (from a support perspective) over the other.
I personally do most of my initial testing on NT since that's the OS we ship by default but the lab testing has switched over to a majority of Win2K machines so your testing coverage is definitely starting to lean in that direction.
go with your personal preference... whatever you're more comfortable with should be what you go with for now. If it were me an I were installing new systems, I'd probably reach for the Win2K and save myself the headaches of upgrades later.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.