Re: FYI...ActiveX Error Resolved
From: Andre (nomade1999_at_hotmail.com)
Date: 10/18/04
- Next message: whl: "Re: Companyweb prompting for password"
- Previous message: Roger Crawford: "Re: STILL having Migration problems with ADMT"
- In reply to: Marcia: "FYI...ActiveX Error Resolved"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 19 Oct 2004 08:38:51 +1000
Thanks for your post, you put me on the right track to solve a very similar
problem.
Can I ask you a big favor and send me the output of your gpresult/v after
your problems fix? And maybe if you have time to point out which policies
you had to change/fix in order to fix your problem.
I see some places where the problem might be but not sure.
Then if I manage to fix my problem I can post back to the newsgroup the
relevant place on the GP where I had to fix. That could certainly help more
peoples with similar problems.
Thanks
Andre Couture
"Marcia" <Marcia@hotmail.com> wrote in message
news:Oh$6VNStEHA.3200@TK2MSFTNGP14.phx.gbl...
> Hi all,
>
> I posted a few times over the last few months about an ActiveX error
> that read "Your current security settings prohibit running ActiveX
> controls
> on this page." The error was discovered after installing Trend's CSM
> Suite.
> Also, Windows Update didn't function properly after that. The resolution
> was quite involved and actually involved 3 different MS Support personnel.
> We actually discovered three issues that were occuring behind the scenes.
> IIS was messed up, the cryptographic services were corrupted, and the
> ActiveX error was the little cut that was shown behind a bleeding problem.
> I'll never know if IIS and the cryptographic functionality was screwed up
> before installing Trend, but...
>
> There was some corrections to be made in IIS as Trend's home page was
> displayed for the CompanyWeb, DefaultWeb, and SharePoint webs. After
> fixing
> that, the error still persisted. This was discovered using a Filemon tool
> fo track down permissions on folders in IIS and Microsoft.net folders.
>
> The ActiveX problem was still there, but the permissions error that were
> behind the scenes were solved. I logged onto my computer locally, not
> using
> the domain, and I was able to access Windows Update and Trend's home page
> from a workstation. Saving my local policy solved it for my workstation
> and
> verified that the problem was a Group Policy problem. Disjoining all the
> workstations wasn't acceptable and the SBS box, being a domain controller,
> can't be disjoined anyway--so we still had to figure out a work around.
>
> Using gpresult /v for both the server and client showed that the default
> domain policy was in there twice, how we'll never know. MS removed the
> link
> to the SBS Client Computers GPO, removed the link to SBS Server Auding
> GPO.
> Also in the Local Security policy on the server, IE Maintenance policy was
> set to enabled, Software installation policy processing to enabled and
> disabled security policy processing on the Local Security policy on the
> server.
>
> I didn't know there was a tool that showed permissions like Filemon did
> nor
> was I aware that GPresult could be so helpful. MS took all the necessary
> information from a client computer and the server. If this happens to
> anyone else, a workaround/KB article will be created. I agree with Les,
> contacting MS is very wise and well worth the money--once your company
> agrees to spend it. I learned a lot and now I'm moving forward--very
> behind
> on updates.
>
> I hope this information helps someone...and again, I thank this newsgroup
> for all the information that the MVP's share.
>
> Marcia
>
>
- Next message: whl: "Re: Companyweb prompting for password"
- Previous message: Roger Crawford: "Re: STILL having Migration problems with ADMT"
- In reply to: Marcia: "FYI...ActiveX Error Resolved"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
