Password Policy

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

i think i have created my DC and an AD on Server 2k3.
I am trying to create a new user and i typed in

password

for the password for the user, however, the computer is telling me that it does not meet the password policy requirements... Fair enough if i knew the requirements, i would change it, but where am i to find the requirements?? Anybody know???

 

i saw that and it still dont work...

pass history - 24 rem
pas max age - 42 days
pas min age - 1 day
pas min lenght - 3


and the username is

adminuser

and the password is

password1

where have i gone wrong for it not to enable this
?

 

You've probably still got the 'password must meet complexity requirements' GPO set - this will mean at least one non-alphanumeric character, at least one upper case letter and at least one other character must be used

 

think it was the complexity option and the fact that i was not waiting for it to store into the registry....

ummm, whats OU? in OU GPO?

 

Server 2003

In Active Directory users and computers, i created

user:

Admin1

added the computer

win2kvmc

I then went into 2K machine, and under Network Identification Wizard, i typed in the user name, the computer name and also the domain (domain.test.vmc), and get the error message saying...

Was this caused by the fact the when i was originally trying to create a DC it could not find domain.test.vmc, it looked like it was looking for it on the net and was showing some message about DNS aswell....

 

Instead of typing in domain.test.vmc try it with only domain.

I have seen times in the past when windows DNS does not like the full path when trying to add computers, however this was with windows 2000, I don't know if it was resolved with 2003.




EDIT:Is the user Admin1 also a member of the domain admins group?

 

OU stands for organizational unit, ppl usually make organizational unit in a doman and then add users to it, it makes configuring and managing users withing this unit much easier as u would have to apply settings to the organizational unit and each member within that OU will have that setting

 

I named the domain domain.test.vmc, i tried changing the Win2k machine to connect to domain and domain.test.vmc, and still doesn't work...

and yep, Admin1 is an Adminifrustrator

 

from the win2k machine can you ping the DC?

have you set up DNS and DHCP, these are required for AD to function.

 

Nelix, im sure i have done that, but will double check soon...

 

Erm <cough> DNS is a requirement but DHCP is *optional*, AD can live without DHCP though it is recommended for clients not servers.

 

Bear in mind that since windows 2000 local name resolution relies heavily on local DNS. Hence when you promote (DCPROMO) a server to a domain controller you *must* have a local DNS server running or the wizard will create one that has the necessary records which point to the new domain controller. These are special DNS entries known as SRV records.

So, your clients need to be able to know which IP address on your network belongs to a domain controller that they can communicate with. Your clients need to have your local DNS server set as their primary DNS server in their TCP/IP properties.

This will enable them to find the domain controller but will break their ability to resolve external Internet domain names. So, you are probably thinking hmmm but how do I get my clients to be able to resolve external DNS names like www.google.com from my own humble DNS server.. Well one way is to set up forwarders in your DNS server properties. Then when your clients ask your DNS server to resolve a name which is not local, it will pass the query onto the forwarders (typically your ISP DNS servers) and they will do the work and return the query back to your DNS server which will then inform the client.

 

DNS was not enabled nor was DHCP... am doing it now, so any problems, you'll soon hear about them...

btw: cheers for the help chaps

 

I cant do it

its asking for dnsprov.mof

i download the zip file from MS and in the instructions is says

but i have not folder called wbem

btw: What OS do you guys use for doing something like this..

 

TCM are you sure that you haven't got a dns server running on your domain controller? As I said before, the DCPROMO process will install and configure DNS for you. Check to see if there is a DNS utility in Start > Administration Tools > DNS