Hi all, One of my customer is planning to deploy 1200 MC3100 WIFI in 802.11A. He is using Wavelink Avalanche to deploy and manage all the PDAs. the Regkey (obtained via RemCapture) to allow to activate 802.11A is very long and according to support encrypted. This key deployement is not supported by Wavelink. How can I, from start change the fusion default (702.11B/G active 802.11A disabled) to 802.11A activated 802.11B/G inactive via an other way that this long Regkey. Thank you for your help. Regards. Philippe
Fusion: I want to use 802.11A by default// Expert user has replied. |
5 Replies
Can you deploy the actual registry file rather than just a registry key? If you deploy the file and it gets merged on the first cold/clean boot, that would be the best recommended method. This key represents everything found in the Options menu by Fusion. -Dave
Hi Philippe, Wavelink offers an AVA pacakge builder that allows you to build your own Avalanche packages (much like Airbeam package builder allows you to build Airbeam packages). You could create a Fusion REG key to do what you want, then build that REG key into an AVA package and use Avalanche to deliver it to your Mobile units. Please note however that the Wavelink package builder is supported by Wavelink and not Motorola Support. Thanks, Mario
Hello Philippe You can export the fusion profiles and options to a .REG file - can you not create a master reg file and deploy that? Failing that you will need to change via the Fusion API's. There are script commands that will allow you to to this.
Hi Paul I have captured the RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Symbol Technologies, Inc.\FUSION\WCSOptions] "OptionsInformation0" = hex:\ 02,00,00,00,44,00,34,00,32,00,45,00,43,00,44,00,38,00,33,00,2d,00,31,00,30,\ 00,44,00,41,00,2d,00,34,00,30,00,31,00,34,00,2d,00,38,00,33,00,43,00,35,00,\ 2d,00,35,00,45,00,42,00,33,00,45,00,41,00,43,00,30,00,36,00,43,00,33,00,30,\ 00,41,00,42,00,43,00,44,00,7d,15,3d,a8,7c,83,a7,45,17,62,90,f0,de,6b,eb,65,\ 7d,f7,6b,0c,1a,b8,99,b3,3e,42,f0,47,b9,1b,54,6f,7d,f7,6b,0c,1a,b8,99,b3,3e,\ 42,f0,47,b9,1b,54,6f,7d,f7,6b,0c,1a,b8,99,b3,3e,42,f0,47,b9,1b,54,6f,7d,f7,\ 6b,0c,1a,b8,99,b3,3e,42,f0,47,b9,1b,54,6f,7d,f7,6b,0c,1a,b8,99,b3,3e,42,f0,\ 47,b9,1b,54,6f,7d,f7,6b,0c,1a,b8,99,b3,3e,42,f0,47,b9,1b,54,6f,7d,f7,6b,0c,\ 1a,b8,99,b3,3e,42,f0,47,b9,1b,54,6f,7d,f7,6b,0c,1a,b8,99,b3,3e,42,f0,47,b9,\ 1b,54,6f,52,79,8e,35,d8,f9,ac,7c,2d,98,cd,fc,bc,4a,e6,ef,ce,1f,72,8d,9a,11,\ fd,e8,18,75,26,24,e5,57,98,e7 This key is too long to be deployed via Avalanche. I am therefore trying to find a "smart way" to change the defaults, to have 802.11a active by default. Is there a small undocumented Regkey??? Thank you all for your support Philippe
Hello Phillppe, I am not aware of a reg key that will do what you require. Could you not have all combinations on the terminal and switch between? i.e. store in \application\MyRegKeys\ and then use a copy file or WaveLink to copy the correct one (with generic name) into \application\ for merging in on next warm boot (use the Skip reg setting to force a reg merge).