Domain issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hi,
My XPe machine participate in a domian . It has the EWF,enabled.
After thirty days ,It just display the following error message
" The system cannot log on now because the domain MYDOMAIN is not available"
.. here MYDOMAIN is my test domain.

how can i avoid this error. I want to avoid this type of domain entry
proplem.Can anyone help me.

Thanks & Regards,
KSMH
 
Thanks Sean,

I am using the XPe SP2 image. So is there any other way to get that.

Thanks and Regards,

KSMH
 
Thanks KM,

I checked that with FP7 registry filter. Its working fine.

I want to find out the EWF SP2 - Q871225 patch.I need the solution

for the SP2 image. did the patch released officialy

Thanks & regards,

KSMH
 
Not sure if there was a question in your post but just in case. As I noted, you may want to get access to the new ECE website (folow
the link I posted earlie to read more about that website) and search there for that QFE.
 
thanks,

Is there any option in server side to disable the domain secret key changes or

To change the time between the domain secret key changes.

Thanks and regards,

KSMH
 
KSMH,

I must admit I am not a domain administrator and don't know the details.

You can change the password age:
[HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters],"MaximumPasswordAge"=dword:<days> (default 30 days)

Or you can try this to disable the password change completely:
[HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters],"DisablePasswordChange"=dword:1

Corresponding policies are:
Domain Member: Disable machine account password changes (DisablePasswordChange)
Domain Member: Maximum machine account password age (MaximumPasswordAge)
Domain Controller: Refuse machine account password changes (RefusePasswordChange)

You can see them if you launch gpedit.msc (Group Policy Editor), under Local Computer Policy-->Computer Configuration-->Windows
Settings-->Security Settings-->Local Policies-->Security Options.

I think in domain environment those policies are getting pushed to clients from domain controller. So admin can always change those
on the server side before turing on multiple clients.
 
Back
Top