Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SEP RU6 disables the webcam internal microphone

Updated: 03 Oct 2010 | 17 comments
NoyanIT's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.
Hi all,

Although I created a Application and Device Control Policy about the webcam, SEP RU6 still disables the webcam internal mic but the webcam can work still !  
When using Office Communicator, webcam can be opened and  the sounds can be received but no sound can be sent at all. 
Known that the Application and Device Control may not block or enable the webcams but we all use Logitech Quickcam 3000 webcam and I had added the camera's Class Id = {4d36e96c-e325-11ce-bfc1-08002be10318} and hoped its correct.  Then I'd excluded this device in the App and Device Control Policy but the outgoing sound was still lost; incoming voices were good as needed. 

What can I do with the policy, is there any idea??

Comments

AravindKM's picture
01
Sep
2010
0 Votes 0
Login to vote

If you remove this policy

If you remove this policy whether it is working properly?

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

NoyanIT's picture
02
Sep
2010
0 Votes 0
Login to vote

Only opening the usb port at all

Only opening the usb port at all ( usb ports may not be open in our company) is solving this issue; but this one is not the right way to do.. 

Mahesh Roja's picture
02
Sep
2010
0 Votes 0
Login to vote

post the screen shot

post the screen shot of the policy which you have created

If this Info helps to resolve the issue please Mark as Solution

Thanks

NoyanIT's picture
02
Sep
2010
0 Votes 0
Login to vote

A Screenshot of Device

A Screenshot of Device Control policy is posted. 

screenshot.JPG
Mahesh Roja's picture
02
Sep
2010
0 Votes 0
Login to vote

post the screen shot

post the screen shot of the policy which you have created

If this Info helps to resolve the issue please Mark as Solution

Thanks

AravindKM's picture
02
Sep
2010
0 Votes 0
Login to vote

Go to device manager and

Go to device manager and check whether this mic is listing as a separate device or not.If it it is listing as a separate device collect the GUID/Class ID and add it in exception list...

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

NoyanIT's picture
02
Sep
2010
0 Votes 0
Login to vote

Yes its a seperate device,

Yes its a seperate device, looks like "Logitech Mic (Quickcam 3000) " but how can I collect the Class ID information of it? 

Fatih Teke's picture
02
Sep
2010
0 Votes 0
Login to vote

Device ID

Can you block it via device id please?

Best Regards.
Fatih

 Everything works better when everything works together.

NoyanIT's picture
02
Sep
2010
0 Votes 0
Login to vote

Does the Device Id seem as it

Does the Device Id seem as it shown in screenshot2? 

screenshot2.JPG
AravindKM's picture
02
Sep
2010
0 Votes 0
Login to vote

It should be.Better confirm

EDIT:

 Select device instance ID.It is better to use devviewer.Find out the class ID ,add it in hardware device,add in exclusions. 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Mahesh Roja's picture
02
Sep
2010
0 Votes 0
Login to vote

HI

What about the MIC its in build with Laptop or you have installed external manually

If this Info helps to resolve the issue please Mark as Solution

Thanks

Mahesh Roja's picture
02
Sep
2010
0 Votes 0
Login to vote

Hi

Sorry top you said its internal ..In device manager go to properties of that device and details . check wether you have the class id details

If this Info helps to resolve the issue please Mark as Solution

Thanks

Fatih Teke's picture
02
Sep
2010
0 Votes 0
Login to vote

Yes it is true, Use it and

Yes it is true,
Use it and you will see there is successfuly blocked :)

Best Regards.
Fatih

 Everything works better when everything works together.

Bekir's picture
02
Sep
2010
0 Votes 0
Login to vote

Hello Noyan, You need to

Hello Noyan,

You need to exclude the device ID or Class ID of the microphone. You may use the DevViewer.exe tool from the SEP Manager setup CD (Under Tools folder) to copy those IDs to clipboard.

However, the important point is that you'll confront with things like that in the future. If all you want to do is block all USB storage, I'd suggest you to create a new Device ID under Policy Components -> Hardware Devices with this ID: USBSTOR*

You can use wild cards like * (star) in those fields. And all usb storage device IDs start with USBSTOR tag. That way you will not need to block whole USB class which will always lead problems.

In addition, in the future you'll see that some USB hard drives do not go under USB class and do not get blocked. So you'll have to use this method anyway.

Best regards,
Bekir Burak Durmaz

NoyanIT's picture
02
Sep
2010
0 Votes 0
Login to vote

Thank you all for the nice

Thank you all for the nice replies. 
After a couple of research, I'd found out that at least 50 webcams are being used in the company and most of them have a Logitech microphone device ID starting with USB\VID_046D&PID_09A5&MI_02\... 
Then I added a new hardware device named Logitech Mic and created a Device ID looks like {USB\VID_046D&PID_09A5&MI_02\*}
Is this ok to include all the Logitech mic Device ID's to exclude the device on the policy? 

AravindKM's picture
02
Sep
2010
0 Votes 0
Login to vote

Yes it will do...

Yes it will do...

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Bekir's picture
02
Sep
2010
0 Votes 0
Login to vote

Sure, that would be an

Sure, that would be an accurate solution to this Logitech webcam problem.

Tip: VID means "Vendor ID" and PID means "Product ID" ;)

Best regards,
Bekir Burak Durmaz