Re: Can't change security policy
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 14:45:49 -0600
These might help.
823166 Overview of Exchange Server 2003 and antivirus software
http://support.microsoft.com/?id=823166
822158 Virus scanning recommendations on a Windows 2000 or on a Windows
Server
http://support.microsoft.com/?id=822158
817442 IIS 6.0: Antivirus Scanning of IIS Compression Directory May Result
in
http://support.microsoft.com/?id=817442
309422 INF: Consideration for a Virus Scanner on a Computer That Is Running
SQL
http://support.microsoft.com/?id=309422
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"rindi" <rindi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2C5656D6-0782-43B8-9EEC-28E6746B70E1@xxxxxxxxxxxxxxxx
>I rebooted many times and that didn't help. The password policy didn't
> directly have to do with the problem, but it it but it got me to narrow
> down
> the issue. I had wanted to change the policy settings for the password and
> couldn't save the changed settings, which indicated something to be wrong
> with the credentials in the sysvol folder.
>
> I'll do the exclude for the exchange folder as well, thanks for the tip.
> Maybe Avast didn't exclude the folder because I didn't use the standard
> locations for them. I don't like mixing data and static program files all
> in
> one place (C:), I prefer using partitions and then saving the volatile
> data
> in an area reserved for that.
>
> "Leonid S. Knyshov" wrote:
>
>> "rindi" <rindi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:D06728EB-5361-4E08-9DB4-0ACCC0BCDBDC@xxxxxxxxxxxxxxxx
>> >I went through the following:
>> > I hadn't known anything about that but it looks as if this was the
>> > cause
>> > for
>> > the problems. Ichecked my avast scanner and found no exclusions, so I
>> > added
>> > them, uninstalled and reinstalled AD, and now it looks OK!
>> >
>>
>> "Uninstalled/reinstalled" AD? You didn't have to. A reboot would have
>> likely
>> fixed the problem (and really just restarting netlogon and whatever is
>> responsible for ntfrs).
>>
>> Perhaps a suggestion should be made to Avast developers to exclude the
>> SYSVOL volume from their scanning if they find themselves on a Domain
>> Controller. While you are at it, please also exclude the C:\Program
>> Files\Exchsrvr\ (or whatever the localized equivalent is for you) as that
>> is
>> also going to create a lot of problems with Exchange.
>>
>> The password policy had nothing to do with your inability to login from
>> the
>> network.
>> --
>> Leonid S. Knyshov, CEO
>> Crashproof Solutions, LLC - http://www.crashproofsolutions.com
>> MCP Exchange 2003/Small Business Server 2003, CCNA, SCSA 8
>> Microsoft Small Business Specialist Partner
>>
>>
>>
.
- Follow-Ups:
- Re: Can't change security policy
- From: rindi
- Re: Can't change security policy
- References:
- Re: Can't change security policy
- From: Leonid S. Knyshov
- Re: Can't change security policy
- From: rindi
- Re: Can't change security policy
- From: Leonid S. Knyshov
- Re: Can't change security policy
- From: rindi
- Re: Can't change security policy
- From: rindi
- Re: Can't change security policy
- From: Leonid S. Knyshov
- Re: Can't change security policy
- Prev by Date: Re: Can't change security policy
- Next by Date: Re: VPN Client problems (settings client side)
- Previous by thread: Re: Can't change security policy
- Next by thread: Re: Can't change security policy
- Index(es):
Relevant Pages
|
