Networks

Ask something
Question Locked

server

0 helpful
10 replies

by sanesh_sg

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Hai... can anybody help me.actually i tried to create a user in windows 2003 server.it accept the user name and password and all other things.but atlast it shows that some errors regarding the password and user.please help me immediatly. this is my email id - sanesh_sg@yahoo.com

10 replies

by sanesh_sg

first thanks for ur response.actually i am trying to create a user for individual systems (its not finished completely) and then i tried in server (2003) and the same error occured.The error is - [The password does not meet the password policy requirements.Check the minimum password length,password complexity and password history requirements.] after this i tried various passwords(length of 10 chars)but it shows the same error and one more i cant enable my group policy.(gpedit.msc).hope you wil reply soon.

by bart777

If full security is turned on with regard to passwords you need to have the password meet 3 of the 4 criteria.

1) Upper case letters
2) lower case letters
3) Numbers
4) Special characters

Next the password must be a certian length. Try to keep it to about 8 characters.

Here is a password that meets all of the above criteria.
Pa$$w0rd

Best of luck

by sanesh_sg

Hi...Really thanks for your reply.its very much helpful to me.very very thanks.if you dont mind whats your name and where are you from.

by sanesh_sg

hi... i need one more help that is can i change my password policy that is size of password and like tat.....

by sanesh_sg

when i tried in local machines to open gpedit.msc it shows the following error - snap in faild to initialize CLSID{8FC0B734-A0E1-11D1-A7D3-0000F87571E3} But it is working in server...

by Former member

"Snap-in failed to initialize" error message when you open Microsoft Management

SYMPTOMS
When you try to open a Microsoft Management Console snap-in that involves security policies (such as Local Security Policy, Group Policy, or Domain Security Policy), the console may not open, and you may receive an error message similar to one of the following error messages:

Error message 1
Snap-in failed to initialize.
Name: Group Policy
CLSID: {8FC0B734-A0E1-11D1-A7D3-0000F87571-E3}

Error message 2
Snap-in failed to initialize.
Name: Resultant Set of Policy
CLSID:{6DC3804B-7212-458D-ADB0-9A07E2AE1FA2}

Error message 3
Snap-in failed to initialize.
Name: Software Installation (Computers)
CLSID:{942A8E4F-A261-11D1-A760-00C04FB9603F}

Error message 4
Snap-in failed to initialize.
Name:
CLSID:{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}

CAUSE
This behavior occurs because the PATH environment variable does not include the %SystemRoot%\System32\WBEM folder.

RESOLUTION
To resolve this behavior, add the %SystemRoot%\System32\WBEM folder to your PATH environment variable. To do so, follow these steps:
1. Right-click My Computer, and then click Properties.
2. On the Advanced tab, click Environment Variables.
3. Under System Variables double-click the PATH environment variable.
4. Type:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM
Note If other system variables appear, do not remove them.
5. Click OK, and then click OK.

APPLIES TO
? Windows Vista Home Basic
? Windows Vista Home Premium
? Windows Vista Ultimate
? Windows Vista Business
? Windows Vista Enterprise
? Windows Vista Starter
? Microsoft Windows XP Professional
? Microsoft Windows Server 2003 Service Pack 1, when used with:
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows Server 2003, Web Edition

Please post back if you have more problems or questions.

This discussion is closed to new replies.