<div>
<div class="content wysiwyg-content">
We recently added a windows 2003 server to an existing &nbsp;domain with a W2000 server acting as primary domain controller (PDC) and also as the license server. Another tech used the addprep tool to add it to the domain. It worked fine for a couple days, then this morning we got calls from people saying they lost a drive mapping on the new server. A tech rebooted the new W2003 server, and the drive mappings came back ok, people could now access it.<br />
<br />
Now, after examining the licensing on the W2003 server, all client licenses show up as 'Unlicensed Usage', instead of licensed.<br />
They are showing up as licensed on the W2000 server. Also, the license history we added on the W2003 license manager shows up on the W2000 license server, but not on the W2003 server.<br />
<br />
We are concerned these &quot;unlicensed&quot; users will reach a threshhold of some sort in a day or two and cause another lockout.<br />
Should we make the W2003 server the license server, (the thought being that it is easier for a W2003 server to be backward compatible than a W2000 server be &quot;forward compatible)?<br />
<br />

</div>
</div>


We recently added a windows 2003 server to an existing  domain with a W2000 server acting as primary domain controller (PDC) and also as the license server. Another tech used the addprep tool to add it to the domain. It worked fine for a couple days, then this morning we got calls from people saying they lost a drive mapping on the new server. A tech rebooted the new W2003 server, and the drive mappings came back ok, people could now access it.

Now, after examining the licensing on the W2003 server, all client licenses show up as 'Unlicensed Usage', instead of licensed.
They are showing up as licensed on the W2000 server. Also, the license history we added on the W2003 license manager shows up on the W2000 license server, but not on the W2003 server.

We are concerned these "unlicensed" users will reach a threshhold of some sort in a day or two and cause another lockout.
Should we make the W2003 server the license server, (the thought being that it is easier for a W2003 server to be backward compatible than a W2000 server be "forward compatible)?



Licensing Problems on new windows 2003 server

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).