Win2K Term Service inop after migrating to new HW

Microsoft Windows
SQL Server
I have been migrating some Win2K servers from one HW platform to another using Ghost and doing an upgrade install. Everything works afterwords but Terminal Services. All of TS in these systems are in application mode. No errors logged in the Event logs. The Remote Desktop client just says it cannot connect. Anyone have an idea? Thanks, Steve

Answer Wiki

Thanks. We'll let you know when a new response is added.

I am thinking you have a licensing issue. I have run into issues with swapping out PC’s, but the server counting both by mac address. A call to Microsoft reset the licensing. Try going into the Licensing part of the server and see if perhaps that is an issue.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Joco1141
    is the service staring ? if so them you should still be able to connect and just get a refusal for logging on if not have you installed tthe the service packs on the machine? then again the license could be the issue but i don't see how it has nothing to do with the hardware in the machine like xp does win2k only needs the cals
    0 pointsBadges:
  • DNSconsulting
    I'd look at a few things. The ability to replicate a server's drive and its contents has two variables that come to mind with your specific issue. One is that you may have a attribute that doesn't allow it to be copied and the other is that the PWL files may not be be able to be copied in the first place, depending on how you originally configured the 2000 servers. Terminal Server configs and their attributes are linked for access, network mapping and user / passwords - but that depends on how you had your servers mapped. I don't know what version of Norton Ghost you're using, but do a search on their website for this. If memory serves me (and often it doesn't...) there's a bulletin on this. Cheers, Doug
    0 pointsBadges:
  • Jcan123
    Just another thought that might or might not be the issue here: A common issue when "imaging" win2000 and forward is that you have to sysprep the images maybee using -pnp option to detect new hardware. If you create images without sysprep then windows 2000 will "remember" the old hardware including NIC's and you'll have to edit registry manually to get rid of old IP-addresses and NIC's in order to get bindings right etc. You will not be able to see the old Interfaces in the GUI.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: