Sounds like you're using Per-Server licensing, switch to Per User licensing and the system will just keep track of how many licenses you should be purchasing, rather than strictly enforcing it. That won't work for him as he would need additional CALs for that. He is using 25 users "at a time" licensing right now. Not names users which, based on the tone of the post, is a bit higher. CALs, in theory, should still be available either directly or as CALs with downgrade rights, if I am not mistaken.
Have you called your Volume License consultant yet? They should have the exact answer for you, plus pricing, right at hand. How can I confirm that our server is using per-server licensing mode?? Is it possible or not?
It only shows a pop up message, ' To add more licenses use the Licensing wizard from I'll give our IT resellers a call soon, but there is no record of from where the previous 20 CALs were purchased. I don't understand why all in a sudden sbs realized that it has exceeded the maximum licenses limit. No new users have been added this week. A new Foundation server was installed to replace it, but for some reason this was incomplete, which is where I came in.
I have built a new domain using the foundation server and joined the desktops and file server as a member server to this new domain. I am not on the site at the moment, but the error is an on screen dialogue that comes up on the nmachine stating that it is unable to communicate with the DC to verify license compliance and will shut down in x hours, days, minutes, whatever. AFAIK there is no error code. I just want to clear this error. I believe that this may be related to the licensing conditions of the previous SBS domain the server was joined to, a domain which was not properly shut down and the machine not properly removed from.
I cannot find any licensing on the machine to uninstall, so I am geuessiong this may require some registry or other tweaking to remove it. This is now more of an issue as the server has now started to periodically shut down, any info on how to remove this from the machine would be a lifesaver.
Was it ever dcpromod out? You will probably have to use the ntdsutil to clear it. Since we don't know exactly what happened do a search on "how to remove orphaned DC from domain" and see if any of the results are helpful. My first thought is to drop its DC role from the current domain with dcpromo, and from a member try to clean it up. You may have to disjoin from the domain altogether.
Before starting down any of the above, can you verify that the Foundation Server does no have events in the event viewer that replication is not taking place?
Search on "event id ad replication" and see if any of the listed events are present. Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit. The machine was not and isn't now a DC, it has always been a member server. This is why I am stumped. With the old domain lost the machine would have to be disjoined ie: converted to workgroup and rebooted and then rejoined to the new domain.
Was this done? That compliance message BTW: posting the exact message may help sounds like something a Foundation Server would spit out - you sure the box isn't a foundation version or that the message isn't originating from the box? What do the event logs on each server show?
I have got to the site and had a look, it is a Foundation server. My understanding is that this can run as a member server, it had done previously with no problem. Could this be as simple as disjoining and rejoining the domain? Having spoken more to people here, this message used to come up in the old setup when the SBS server was shut down.
Honestly I think the mean crashed! The displayed message is 'failed to complete license compliance check, will restart in 2 days 23 hours, etc I think your problem is you have two foundation servers and both want to be domain controllers as per their licensing. Now it does seem MS allowed to be a domain-joined member server but in they no longer allow this.
Not sure which applies in your case as you have a mix. I wondered this and read the info for which states that the server can be a member server, which it has always been before, the only difference being that before the DC was an SBS machine.
WHat are peoples thoughts about making the machine a DC too? Windows Server Foundation Edition must be alone on the Domain. Thanks for the reply, but I'm not totally convinved this is the case, ncan be a member server in another domain at, as far as I can tell from the MS specs, the top of the forest. This is the case here. Other logs suggest that there may be a DNS error I think, as there are errors relating to being unable to find the DC.
The network has DNS and Wins running. I even tried setting the LMHosts file on the server with the DC details, but this hasn't solved the immediate problem as far as I know. I think what I need is to completely erase and reconfigure the DNS, is there a guide to this that ensures all old data is fully removed?
I am prepared and happy to be contradicte4d if there is someone who can offer me a reasonable solution,. I wouldn't go as far as blowing away DNS at this point. We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need. Who are the certified experts?
How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk. We're a community of IT professionals committed to sharing knowledge. Our experts volunteer their time to help other people in the technology industry learn and succeed.
Plans and Pricing. Contact Us. Certified Expert Program. Credly Partnership.
0コメント