Re: Auto-Accept Agent event sink for Exchange Server 2003 help!

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Evan Dodds [MSFT] (evand_at_online.microsoft.com)
Date: 09/22/04 

Date: Wed, 22 Sep 2004 13:03:39 -0400

Rick -

That's the only thing I've run into which caused this problem (which is not
to say that it might not be caused in your case by something totally
different). It looks to me like you've got everything set properly, but it
might still be advantageous to try it from at least one or two other
workstations or servers to see if they demonstrate identical behavior with
their default IE settings. You could also do some analysis with network
monitor to see what's really getting passed between the workstation and
server. At the end of the day, however, it's really going to come down to
how much time you want to spend looking into this display problem since you
know the mailboxes are properly registered and functional. 

-- 
Evan Dodds
Microsoft Exchange Support
****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.
"Rick Newton" <rnewton@herpersgowling.com> wrote in message 
news:a3b3l01surs90rfkqg9qk691s5i6gcu67c@4ax.com...
> Evan,
>
> The system from which I'm running the script is a Windows 2000 SP4 +
> all hotfixes/patches/etc.  All client systems in my domain, 2000 & XP,
> are up to date with service packs, patches, hotfixes, security
> updates, etc., through to last week's "patch Tuesday" releases.  The
> same is true for the servers.
>
> If I look at my Windows 2000 IE intranet trust settings I've added
> entries as foliows:
>
> http://>
> https://>
> http://>
> https://>
>
> [Note: this system is SBS and as such is running both Exchange and
> OWA; so I've left out hte actual IP and system names]
>
> I have not added the following to the trust:
>
> http://>.<domain>.<domain>.local
> https://>.<domain>.<domain>.local
>
> I don't beleive this should make any difference however...
>
> How do you feel I should proceed?
>
> Thanks,
> ----
> Rick.
>
> On Wed, 22 Sep 2004 11:21:05 -0400, "Evan Dodds [MSFT]"
> <evand@online.microsoft.com> wrote:
>
>>Rick -
>>
>>Actually, this response gives even further evidence that the cause is
>>related to IE hardening. If it were seeing this server as truly within the
>>trusted sites, I wouldn't expect to get warning popups. Since we make a 
>>call
>>into DAV, it uses IE interfaces and IE security settings on the
>>workstation/server where the script is run will interfere. What operating
>>system is your local workstation where you're running the script? Have you
>>tried running the script from any other servers/workstations that do not
>>have customized IE security or the Windows 2003 / XPSP2 IE hardening
>>settings in place?
>

Relevant Pages

  • Registry settings at logon
    ... that making the settings in the ... registry of a workstation administrator and then copying ... >script is that if the user doesnt have sufficient admin ...
    (microsoft.public.windowsxp.network_web)
  • Re: Policies being applied to only some machines
    ... > creating new accounts from each workstation. ... > all machines see servers, servers see machines, everyone's happy ... > the machines take the settings. ...
    (microsoft.public.win2000.group_policy)
  • RE: Win2k log management
    ... servers to .csv files on an administrator's workstation. ... This script also ... I am currently administering over 10 serverand 20 workstation ... The management of event/security/application log has become ...
    (Focus-Microsoft)
  • RE: Propagating the Pop-Up Blocker List
    ... > changes into group policy on our Windows 2000 servers ... > being pushed down to the workstation. ... > I can see these GPO objects, ... > these settings are user specific, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Client Telnet Success
    ... I would start by looking at the Firewall settings on each PC if they are ... > occasionally we have to connect to their servers to test the development. ... > Premium running ISA) and only 3 of the workstation are able to connect to ... The software developers asked us to Telnet in from the ...
    (microsoft.public.windows.server.sbs)