When you use Group Policy management functionality in System Center Mobile Device Manager 2008 to disable a Bluetooth profile, the profile is not disabled

Article translations Article translations
Article ID: 954026 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you use Group Policy management functionality in Microsoft System Center Mobile Device Manager (MDM) 2008 to modify the Allowed Bluetooth profiles Group Policy setting, you may experience the following symptoms:
  • Some Bluetooth profiles for a managed Windows Mobile 6.1 mobile device are not deleted.
  • When you use a Group Policy setting to enable a Bluetooth profile for the first time, and then you later use the setting to disable the same Bluetooth profile, the profile is not disabled.

CAUSE

The command that is sent from the MDM server to the managed device to remove a previously enabled profile is not interpreted correctly.

WORKAROUND

Important The following workaround applies only to the English version of System Center Mobile Device Manager 2008. There are no workarounds for other language versions of the product.

Warning Serious problems might occur if you modify system files incorrectly. These problems might require you to reinstall server software or components of server software. Microsoft cannot guarantee that these problems can be solved. Modify system files at your own risk.

To work around this issue, you must modify the ADM template file that includes the Allowed Bluetooth profiles Group Policy setting. To do this, follow these steps.

Important The following workaround requires you to modify an important system file. Make sure that you back up the referenced file before you modify it. Make sure that you know how to restore the system file if a problem occurs. Do not continue with the following procedure if you do not know how to back up and restore a file. Revert to the original file if you experience any problems with the workaround.
  1. On the computer on which you have installed the MDM Administrator Tools, move to the following directory:
    %windir%\INF
  2. At a command prompt, type the following command, and then press ENTER to make a backup copy of the Mobile.adm file:
    copy mobile.adm mobile.adm.bak
  3. Open the Mobile.adm file in a text editor, such as Notepad.
  4. Locate the following lines:
    POLICY !!Policy_AllowedBluetoothProfiles
    		EXPLAIN !!Explain_AllowedBluetoothProfiles
    		PART !!Part_AllowedBluetoothProfiles LISTBOX EXPLICITVALUE
    KEYNAME "SOFTWARE\Policies\Microsoft\Windows Mobile Settings\NetworkPolicy\Bluetooth\AllowedProfiles"
    		END PART
       	        	PART !!Part_AllowedBluetoothProfilesDescr1 TEXT
               		END PART
        	END POLICY
    
  5. Use the following lines to replace the lines that you located in step 4:
    POLICY !!Policy_AllowedBluetoothProfiles
          EXPLAIN !!Explain_AllowedBluetoothProfiles
          KEYNAME "SOFTWARE\Policies\Microsoft\Windows Mobile Settings\NetworkPolicy\Bluetooth\AllowedProfiles"
    
        		PART !!PART_ProfileHandsFree CHECKBOX
               		VALUENAME "{0000111F-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
    		    PART !!PART_ProfileAdvancedAudio CHECKBOX
               		VALUENAME "{0000110A-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileAudioVideo CHECKBOX
               		VALUENAME "{0000110C-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfilePersonalAreaNetwork CHECKBOX
               		VALUENAME "{0000000F-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileOBEXObjectPush CHECKBOX
               		VALUENAME "{00001105-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileDialupNetworkingGateway CHECKBOX
               		VALUENAME "{00001103-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileDialupNetworkingTerminal CHECKBOX
               		VALUENAME "{7A5106B1-A555-446b-A8B4-7A3D582E64CE}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileActiveSync CHECKBOX
               		VALUENAME "{0350278F-3DCA-4E62-831D-A41165FF906C}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileHumanInterface CHECKBOX
               		VALUENAME "{65E8B905-1B98-484c-9748-1C7078AB3F72}"
    		   	VALUEON ""
    	    	END PART
        		PART !!PART_ProfileSerialPort CHECKBOX
               		VALUENAME "{00001101-0000-1000-8000-00805F9B34FB}"
    		   	VALUEON ""
    	    	END PART
        	END POLICY ;;!!Policy_AllowedBluetoothProfiles
    
  6. Locate the following lines in the file:
    Part_AllowedBluetoothProfiles="List of Bluetooth UUIDs:"
    Part_AllowedBluetoothProfilesDescr1="Click Show to see permitted UUIDs or to add a new one in the Value Name field."
    
  7. Use the following lines to replace the lines that you located in step 6:
    PART_ProfileHandsFree="Hands Free and Headset Audio Gateway"
    PART_ProfileAdvancedAudio="Advanced Audio Distribution Profile Source"
    PART_ProfileAudioVideo="Audio/Video Remove Control Profile Target"
    PART_ProfilePersonalAreaNetwork="Personal Area Network Profiles"
    PART_ProfileOBEXObjectPush="OBEX Object Push Profile"
    PART_ProfileDialupNetworkingGateway="Dial-up Networking Profile Gateway"
    PART_ProfileDialupNetworkingTerminal="Dial-up Networking Profile Terminal"
    PART_ProfileActiveSync="ActiveSync"
    PART_ProfileHumanInterface="Human Interface Device Host"
    PART_ProfileSerialPort="Serial Port Profile"
    
  8. Save the file, and then exit Notepad.
  9. Open the modified Mobile.adm file in the Local Group Policy Editor in MDM 2008. The Allowed Bluetooth profiles setting should now list 10 available Bluetooth profiles together with check boxes that let you enable or disable each profile. If you do not see these changes, revert to the original Mobile.adm file, and then follow steps 2 through 8 again.
  10. If the changes have been applied correctly, configure the settings as you want.
  11. To apply the new settings to managed devices, you must update the Allowed Bluetooth profiles Group Policy setting in MDM. To update the setting, run the following cmdlet in the MDM console:
    Update-MobilePolicyCalculation Device_Name
    Note Device_Name represents the managed device on which you want to update the Group Policy setting. New settings are pushed down to managed devices during the next synchronization with MDM 2008.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

In some scenarios, the settings in the Allowed Bluetooth profiles Group Policy setting are applied correctly. The following scenarios describe when the settings are not applied correctly and when the settings are applied correctly.

Scenario 1: When the settings are not applied correctly

  1. In Group Policy management in MDM 2008, set the Allowed Bluetooth profiles Group Policy setting for a managed device to enable the Hands Free and Headset Audio Gateway Bluetooth profile.
  2. Apply the setting to the managed device.
  3. Change the Allowed Bluetooth profiles setting to disable the Hands Free and Headset Audio Gateway Bluetooth profile.
  4. Apply the setting to the managed device.
In this scenario, the Hands Free and Headset Audio Gateway Bluetooth profile is not disabled on the managed device.

Scenario 2: When the settings are applied correctly

The Allowed Bluetooth profiles Group Policy setting is applied correctly on managed devices in the following scenarios:
  • You set the Group Policy setting on a managed device for the first time.
  • You update the Group Policy setting without disabling any previously-enabled Bluetooth profiles.
For example, the settings are applied correctly when you follow these steps:
  1. In Group Policy management in MDM 2008, set the Allowed Bluetooth profiles Group Policy setting for a managed device to enable the Hands Free and Headset Audio Gateway Bluetooth profile.
  2. Apply the setting to the managed device.
  3. Change the Allowed Bluetooth profiles setting to update a profile. Do not disable the Hands Free and Headset Audio Gateway Bluetooth profile.
  4. Apply the setting to the managed device.
In Scenario 2, the Hands Free and Headset Audio Gateway Bluetooth profile remains enabled on the managed device. If you disabled the Hands Free and Headset Audio Gateway Bluetooth profile in step 1, it remains disabled.

Properties

Article ID: 954026 - Last Review: June 26, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft System Center Mobile Device Manager 2008
Keywords: 
kbexpertiseadvanced kbbug kbtshoot kbprofiles kbgrppolicyprob kbpolicy KB954026

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com