Re: Error 1721, weak password

The issue is still occurring after applying SP2 for Server 2008.

"Doug Neal [MSFT]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> This was actually an issue with Windows. The well-documented API calls
> didn't function correctly until Service Pack 2 of Windows Vista and Windows
> Server 2008. If you still have this issue after upgrading to SP2, please
> let me know.
>
> Otherwise, this is unfortunately an expected issue since Windows isn't
> responding correctly to MBSA's request.
>
> --
> --
>
> Doug Neal [MSFT]
> dugn@online.microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> If newsgroup discussion with experts and MVPs is unable to solve a problem
> to your satisfaction, feel free to contact PSS for support on the Microsoft
> Baseline Security Analyzer (MBSA). Information is available at the following
> link:
>
>
> This e-mail address does not receive e-mail, but is used for newsgroup
> postings only.
>
> "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
> news:ecY$GYhCKHA.4608@TK2MSFTNGP02.phx.gbl...<!--coloro:green--><span style="color:green <!--/coloro-->
> > [[Forwarded to MBSA- and Windows Server-specific newsgroups via
> > crosspost.]]
> >
> > Shawn Martin wrote:<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> >> I keep getting Error 1721 for local accounts I have on 2008 server
> >> (64-bit).
> >> I'm running the MBSA under a domain account that is an administrator of
> >> the
> >> server.
> >>
> >> The local account that keeps getting flagged by MBSA has a password of
> >> Wh$v9Jx^=b
> >>
> >> so I have no clue as to why it thinks that is a weak password. Any
> >> suggestions?<!--colorc--><!--/colorc-->
> > <!--colorc--><!--/colorc-->
> <!--colorc--><!--/colorc-->

 

I have a Windows 2008 Server x64 running Service Pack 2 and i am facing the
same error.
How shall i resolve this?


"Shawn Martin" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> The issue is still occurring after applying SP2 for Server 2008.
>
> "Doug Neal [MSFT]" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > This was actually an issue with Windows. The well-documented API calls
> > didn't function correctly until Service Pack 2 of Windows Vista and Windows
> > Server 2008. If you still have this issue after upgrading to SP2, please
> > let me know.
> >
> > Otherwise, this is unfortunately an expected issue since Windows isn't
> > responding correctly to MBSA's request.
> >
> > --
> > --
> >
> > Doug Neal [MSFT]
> > dugn@online.microsoft.com
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > If newsgroup discussion with experts and MVPs is unable to solve a problem
> > to your satisfaction, feel free to contact PSS for support on the Microsoft
> > Baseline Security Analyzer (MBSA). Information is available at the following
> > link:
> >
> >
> > This e-mail address does not receive e-mail, but is used for newsgroup
> > postings only.
> >
> > "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
> > news:ecY$GYhCKHA.4608@TK2MSFTNGP02.phx.gbl...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > [[Forwarded to MBSA- and Windows Server-specific newsgroups via
> > > crosspost.]]
> > >
> > > Shawn Martin wrote:
> > >> I keep getting Error 1721 for local accounts I have on 2008 server
> > >> (64-bit).
> > >> I'm running the MBSA under a domain account that is an administrator of
> > >> the
> > >> server.
> > >>
> > >> The local account that keeps getting flagged by MBSA has a password of
> > >> Wh$v9Jx^=b
> > >>
> > >> so I have no clue as to why it thinks that is a weak password. Any
> > >> suggestions?
> > > <!--colorc--><!--/colorc-->
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Joe wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> I have a Windows 2008 Server x64 running Service Pack 2 and i am facing the
> same error.
> How shall i resolve this?
>
>
> "Shawn Martin" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>> The issue is still occurring after applying SP2 for Server 2008.
>>
>> "Doug Neal [MSFT]" wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> This was actually an issue with Windows. The well-documented API calls
>>> didn't function correctly until Service Pack 2 of Windows Vista and Windows
>>> Server 2008. If you still have this issue after upgrading to SP2, please
>>> let me know.
>>>
>>> Otherwise, this is unfortunately an expected issue since Windows isn't
>>> responding correctly to MBSA's request.
>>>
>>> --
>>> --
>>>
>>> Doug Neal [MSFT]
>>> dugn@online.microsoft.com<!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

Hello Joe:

I suggest you contact Doug Neal with your trouble.

--
1PW

 

This is a known issue and has not been corrected

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Joe" <Joe@discussions.microsoft.com> wrote in message
news:AA493448-6895-4A13-991A-4B3835A9BC7D@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
>I have a Windows 2008 Server x64 running Service Pack 2 and i am facing the
> same error.
> How shall i resolve this?
>
>
> "Shawn Martin" wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>> The issue is still occurring after applying SP2 for Server 2008.
>>
>> "Doug Neal [MSFT]" wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>> > This was actually an issue with Windows. The well-documented API calls
>> > didn't function correctly until Service Pack 2 of Windows Vista and Windows
>> > Server 2008. If you still have this issue after upgrading to SP2, please
>> > let me know.
>> >
>> > Otherwise, this is unfortunately an expected issue since Windows isn't
>> > responding correctly to MBSA's request.
>> >
>> > --
>> > --
>> >
>> > Doug Neal [MSFT]
>> > dugn@online.microsoft.com
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no rights.
>> >
>> > If newsgroup discussion with experts and MVPs is unable to solve a problem
>> > to your satisfaction, feel free to contact PSS for support on the Microsoft
>> > Baseline Security Analyzer (MBSA). Information is available at the following
>> > link:
>> >
>> >
>> > This e-mail address does not receive e-mail, but is used for newsgroup
>> > postings only.
>> >
>> > "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
>> > news:ecY$GYhCKHA.4608@TK2MSFTNGP02.phx.gbl...
>> > > [[Forwarded to MBSA- and Windows Server-specific newsgroups via
>> > > crosspost.]]
>> > >
>> > > Shawn Martin wrote:
>> > >> I keep getting Error 1721 for local accounts I have on 2008 server
>> > >> (64-bit).
>> > >> I'm running the MBSA under a domain account that is an administrator of
>> > >> the
>> > >> server.
>> > >>
>> > >> The local account that keeps getting flagged by MBSA has a password of
>> > >> Wh$v9Jx^=b
>> > >>
>> > >> so I have no clue as to why it thinks that is a weak password. Any
>> > >> suggestions?
>> > >
>> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->