Client policy manual update method

When dealing with an offline client that was infected, it may be necessary to change the policy being enforced on that client to disable features or settings that are locked down on the client. Apparently, there is nothing in the help function that explains how to do this and what one would think should work apparently does not.

Recently, I had to deal with this on an offline client that could not be brought online due to a viral threat. I checked the help files and did a search for "Policy Profile", "Policy", "Profile", but the only suggestion found for it was to right click and  select update policy, this is good only if the client is currently being managed by the SEPM. So, I did a search on Google and still found nothing right away. Next I logged into the SEPM, created a new policy with the settings changed that I needed and exported the policy. Burn it to disk and then try to import it  into the SEP client. It looks for an .XML file, so I select all files and try to upload to .DAT file--no indicator, no error message, nothing.

A Symantec representative informed me that I would have to create the policy, assign it to another client and then extract the policy .XML file from that client and then Import it into the other client. Where is this in the help? Why isn't it readily available information?

This is a two part request/suggestion:

(1.) Update the help information to provide this in a more readily available manner.

(2.) Allow the client to be able to manually update the policy off of the .DAT file that can be exported from the SEPM Policies tab and then imported directly into the SEP client "Help and Support" > "Troubleshooting" menu. Having to do all of those other steps is a waste of time and extra steps for no good reason that I can think of.

Creating a new policy, exporting it, transferring it to the client and importing it within the client . 
Versus,
Having to create an additional policy, pull another client out of the group (possibly reducing the security posture of that client depending on what settings have to be changed and for what purpose), making sure that client has the new policy, exporting it off the client, burning it to disk and then importing it into the new client.