After connecting to this machine and trying to help out, I found two problems:
The first with regards to the DNS issues. This was just down to the fact that no reverse lookup zone was created. I created this and it was able to resolve the server via IP just fine.
As for non-existent domain
, I am unsure where this was seen. Typing the domain name worked fine.
As for the more serious issue of users not being able to log in, it turned out to be rather simple - I checked the event log and it turned out that as it said, the GC was malfunctioning. After some more tests, I discovered that the SysVol
folder was not being shared. I checked the basic NTFS settings, followed by sharing it and all machines now appear to be able to log in just fine.
There still seems to be a few issues that just shouldn't be there, and I think reinstall AD from scratch may just be the safest solution - but, the most important thing is that it appears to be working for now and the main errors have been dealt with.
Try an SKUUPGRADE - the eval issue can as such not be activated.
To determine the installed edition, run:
DISM /online /Get-CurrentEdition
To check the possible target editions, run:
DISM /online /Get-TargetEditions
Finally, to initiate an upgrade, run:
DISM /online /Set-Edition:<edition> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
is how it works. See whether you can change from eval to standard.
But you may be out of luck - and then you may need a reinstallation.
But if it works then you MAY be lucky - if the VLK is not requiring a totally different version.
There is a reason we normally avoid installing eval versions for production.
Note to all voters to close: This is not a LEGAL advice - the poster asks about a technical implementation issue which is ok according to the board. Technically he does not ask about LICENSING (terms etc. - legal issue and VERY complicated) but how to activate his key (technical issue), and we do handle those here. Heck, for some parts of windows there are hugh guidelines for the technical side...
Best Answer
the simplest way is to reset the administrator password.
You will find many way googling it.
This one should work (I even used it to reset a domain administrator password in a lab) :
Cleanup Steps