Windows – ny way to add an HTTP Header to every IE request on a computer

My preferred method is to use Active Setup. What it does, is check when a user logs into a machine if they've ran a particular script or command (Such as the one you would have) and if not, execute it. So, you'll only run a particular script for a user one time on their workstation. I found this to be perfect for writing to HKCU, because you don't have to load each hive and only the accounts that people log into are modified.

Not to self promote, but I did write a blog post about doing this. The basic solution is as follows:

Add the following registry entries:

[HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\UniqueID]
"Version"=""
"Stubpath"=""
@=""

• You can choose any Unique ID you want. GUID's are often used, but you can use anything that will be unique.
• Version is whatever version number you want to use.
• Stubpath is the command that will be executed. MSI, EXE, and VBS calls all seem to be fine.
• The @ is what should be displayed when the command is running.

With this solution, the scripting language is irrelevant. You could do a VBScript, Powershell, Batch file. Whatever lets you write to HKCU as the logged in user. Using reg.exe directly works fine as well.

The other, optional final touch you could make is load and modify the default user Hive. That would set the registry value for any new users that log on for the first time to that particular system.

Set the Outlook client to not Send immediately when connected. They compose the message and hit Send as they normally would. The message sits in their Outbox. When they "actually" want to send the message, just open it up from their Outbox and click Send again, it will re-timestamp the message. Then do a Send/Receive in Outlook. No evidence of the original composition date/time can be seen in the header. Alternatively (and probably a better solution), just compose and save the message in Drafts and then Send it when you actually want to send it...

I am aware that this is not a solution like you are describing you want at the server level globally for all messages, but more of a workaround for the client. It becomes very annoying if there are a lot of these messages to do this on, but a couple a week/month won't be too bad for them. Weird requirement from the client..."Send the message, but DON'T ACTUALLY send the message until I say so..." If you don't want to send the message, DON'T hit the Send button...

Another possibility is to not even use Outlook to send the message, compose the message in notepad, saving it as an eml file in the supported format, and write a script to drop it in the Pickup folder on the Exchange server at the appropriate date/time to be delivered.