gunman v different MS groups

What different MS internal groups would do if the gunman were in their
building:

NT: Deny him permissions. He would not be validated by the REDMOND
domain, and would have to leave.

Office: It's up to each individual app to get rid of the gunman.
Consistently.

Excel: Resolved, Won't Fix. Not concerned with the gunman's effect on
boot or recalc speed.

Word: As soon as the gunman typed something he'd be overwhelmed by
red squiggles and AutoRemoved.

PowerPoint: Can we get a gunman from Office?

Bob: The Bob group is not aware of a problem.

PSS: The gunman would know exactly how long his wait to speak to a
negotiator would be.

Works: We don't have a gunman. We have three teenagers with pointed
sticks.

Internet Division: This problem wouldn't have happened if the campus
had been written in HTML

Games Group: Would immediately buy the gunman's story for a CD-ROM
version.

Front Page: We have open reqs. We'll take him.

Exchange: After updating his client, rebooting, creating a new
profile, and waiting to Exchange to start-up and find its server, the
gunman surrenders rather than allow his ordeal to continue.

ITG: The guman's log number is 983274.

Cairo: We anticipated this problem early on in our designs; we begin
by creating a new class for gunpeople in general=85

Forms^3: We plan to write our own native ActiveGunman(tm) control. It
will be delivered with Trident.

Travel: We allow him to book his getaway, but he has to wait for
somebody in Atlanta to go pick up the ticket and put it in the mail.