|
Posted by kj [MVP SBS] on April 18, 2008, 4:40 pm
Please log in for more thread options
>
>> You are wrong!
>>
>>
http://technet2.microsoft.com/windowsserver/en/library/8af78a8c-6e66-4420-9ee7-d82dd1c9e0c61033.mspx
>>
>>
>
> With all due respect Drew I do not believe that you read the short
> sentence under
> description in page of link you referenced.
> The machine attempts to change its password with the frequence that is set
> (30 day default).
> As I had replied, that is a behavior of the joined machine. It is not a
> required change imposed
> by the domain with the domain expiring the account if it is not done
> within that time.
> Password expiration exists for user principals but as far as I have ever
> known does not
> exist for the passwords of machine join accounts.
That is my understanding as well. DC policy exists to even decline computer
password change attempts completly. However this can result in WS passwords
remaining at the intial value equal to the computername$. It can be helpfull
for a temporary measure in machine imaging though.
>
> Why are you asking?
> Have you experience something that leads you to think machine account
> password expiration is the cause ?
>
> Roger
>
>
>>>> Does anybody know the default Machine Account Password expiration in a
>>>> Windows 2003 domain in native mode? Just to clarify what I am looking
>>>> for is the machine password, not user.
>>>>
>>>> Thanks
>>>
>>> As far as I know there is no such thing for machine accounts.
>>> In policy you can control whether machines change their password, and
>>> how often,
>>> but that is a behavior of the joined machine and is not a behavior
>>> required by the
>>> domain (i.e. if the machine does not do it on time there is not anything
>>> forced onto
>>> the machine by the domain).
>>>
>>> Roger
>>>
>>
>>
>
>
| 
XML Sitemap