Every new device that arrives on site is now almost fully automated with our setup routines.
There is however, one stumbling block.
We have spent hours trying to see if we can automate the static IP address allocation to the devices.
The profile settings are stored in the registry in the following location;
Unfortunately, there seems to be some form of encryption / obfuscation going on around this. (Probably because otherwise it would contain your WiFi passphrase in plain text)
The start seems to start with unicode (not sure which codepage / subset) characters;
from here onwards, the data seems entirely uneditable. Setting the static IP to another value seems to change the registry binary in 3 places, but there is no logic I could find to allow us to deploy these devices in a fully automated manner.
If anyone else knows how, the help would be greatly appreciated.
Update: Sorted! I can now automate the WLAN settings configuration.
There is however, one stumbling block.
We have spent hours trying to see if we can automate the static IP address allocation to the devices.
The profile settings are stored in the registry in the following location;
HKLM\Software\Symbol Technologies, Inc\ProfilesUnfortunately, there seems to be some form of encryption / obfuscation going on around this. (Probably because otherwise it would contain your WiFi passphrase in plain text)
The start seems to start with unicode (not sure which codepage / subset) characters;
123456789ABCDEFabcdef1234567890123456789from here onwards, the data seems entirely uneditable. Setting the static IP to another value seems to change the registry binary in 3 places, but there is no logic I could find to allow us to deploy these devices in a fully automated manner.
If anyone else knows how, the help would be greatly appreciated.
Update: Sorted! I can now automate the WLAN settings configuration.
Comments
Post a Comment