Some responses to some of CCIS's comments...
Forensics teams are extremely expensive. Most large companies will cringe when even thinking of the price tag of a team of highly paid individuals showing up. Knowing what you have available is just good business practice. Auditing is crucial such as firewall logs, proxy logs, server auditing of logins/logouts and etc., workstation auditing, IDS, firewall, application logs, cameras, sign-in sheets, and the list goes on. These are the items that the forensics folks will try and locate. It is best when you can correlate incidents between multiple logs and etc.
You have to find out what IP it came from. Correlate and PROVE it came from a specific workstation (don't forget DHCP...save those logs!). Once you got the box...bag and tag it (note the time/date on box first). Turn off and store machine in secured location (note the turn off not shut down). Digital pictures of the box are always nice to have. Keep a journal(HANDWRITTEN) of everything has happened and everything you see and done. If multiple people involved...keep separate logs. Turn over drive to a forensics company if you are not trained. If you have firewall logs, proxy logs, and etc. save them. Again, audit logs are your friends
Sexual harassment may be criminal so I agree that a corporate lawyer should be consulted prior to reporting it. Now, corporate may believe this is an HR issue and not a legal issue...that is not unusual. HR can just fire the employee if he/she "broke the rules". Easier to fire then prosecute and less "messy".
Most law enforcements do not have computer forensics training and many times ship it out to another law enforcement group (FBI, another region, etc etc). There workload is sometimes extreme and they may turn down the case depending upon many factors (dollar figures, type of crime, willingness to prosecute the person by the company, etc. etc.) Again, consult the lawyers and find out what the corporate stance will be.
If your policies aren't up-to-date or basically non-existent you will fight an uphill battle. You can't just update the policies and then attempt to apply to a previous situation...it just don't work good

Same with auditing...turning on auditing to catch someone specifically may cause you a lot of grief in court but you do what you must to isolate the source.
If the computer belongs to the company then it is theirs...taking it back should be no issue

Again, consult the lawyers as your mileage may vary.
This is just a few items off the top of my bald head. I wish you the best of luck in stopping the person
