[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 648
  • Last Modified:

NFR vs. Retail vs. OEM

Good day.

I work for a VAR who has mistakenly loaded their NFR copy of NT on several customer machines. They do this because they customer's copy of NT hasn't arrived yet and they need the setup done quickly. NFRs have a 10 concurrent client connection limitation no matter what the licenses installed.

My question is how do you convert a NFR to a retail copy?

I have tried doing a retail and OEM upgrade over the NFR copy and it still comes up as NFR at the end of the upgrade. It seems that the only way to convert is to blow away the server and reinstall completely. This is unacceptable.

Thanks for any info.
0
rsletten
Asked:
rsletten
  • 2
1 Solution
 
carmineCommented:
You must perform an upgrade installation with the retail copy.

This MUST be the full version (not upgrade).

You MUST use the retail diskettes, or copy the I386 directory from the CD to hard disk and run WINNT /B from a DOS prompt (not an NT cmd prompt).

Note: If you have SP3 installed you must take special precautions. See the MS knowledge base article Q146887. (http://support.microsoft.com/support/kb/articles/q146/8/87.asp)

After the upgrade check the registry key HKLM\System\CurrentControlset\Services\LanmanServer\Parameters\Users
and make sure it is set to 0xffff
0
 
rslettenAuthor Commented:
Didn't work. Still comes up as a NFR. Does the new install/upgrade need to be in a different directory then the NFR? If it is, then it's worst-case scenario.
0
 
carmineCommented:
Ooops, I was wrong you cannot upgrade the NFR or MSDN version of Nt Server, it's only the Evaluation version that can be upgraded.
http://support.microsoft.com/support/kb/articles/q142/3/91.asp

Sorry for the duff information.

PS
Upgrades have to be to the same directory, it would be an install if you selected a different directory.

0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now