After users workstations have been processed by RUM, user profiles that have a wireless profile set using the Intel Proset wireless connectivity tool lose their wireless configuration.
Why is this happening and what can be done?
RUM is designed to process and repermission the file system, registry, services. etc. But some things are protected by the system to not allow other user access. Things kept in Protected Storage of Windows like IE autocomplete, certificates, Outlook Express POP3 passwords, etc. are not migrated and this is the expected behavior. Wireless profiles, as they have passwords stored, are also protected and are not migrated because of this.
Please also see KB18932 for more details on protected storage.
Quest support received some feedbacks from customers, who had Intel wireless profiles used, they reported they worked around the problem by using the Intel PROSet wireless profile Migration Tool (PSMT)
This utility was specifically designed to backup, restore and migrate wireless profiles.
Some customers decided to write a VB Script to have QMM export the profile, while they used RUM to process the workstations.
Then, when the user logged into the target AD, they created a Group based AD GPO login script, and this script imported the wireless profiles back to the workstations.
Important: support has no details, script or particular suggestions. This article was created just to share some information and to point affected customers into the right direction.