Blocking Microsoft CMS Active X control.

[Jeremy B.]

How come the Beta version of this tool blocks or considers
an unknow control, the Microsoft CMS Active X control? I
didn't see a way to call an unknown or blocked control
safe?

Thanks for your help,
Jeremy B.

 

[Bill Sanderson]

It's up to the vendor of the control to make the contacts necessary to get
the control labelled in the way that they wish <G>!

It is clear to me that controls related to beta programs is not going to be
marked as known--I'm not familiar with the control you mention--is it a
production part of a supported application.

 

[Guest]

Yes, it is an essential part to Microsoft's Content
Management Server 2002 product a fully supported
production application. I have let their usergroup know
of this also: http://tinyurl.com/4dss6 .

 

[Bill Sanderson]

Have you checked for updates on that control? We've seen an instance where
what looked like a core piece of the OS was marked as unknown, and it turned
out that it was a piece of beta code that was in use beyond the expiration
of the beta (i.e. when the product went gold.)