Fiserv to employ 419 in Hickory - Charlotte Business Journal:

Guess where cheaper than India and Canada:

Fiserv to employ 419 in Hickory - Charlotte Business Journal:

ULS Logging location

I've been working the last few days to fix permissions for the ULS logging location in SharePoint. When this gets moved don't forget to add modify permissions for the account that runs the service "Windows SharePoint Services Tracing". Depending on how the permissions are configured on a new volume for logging, the default rights for a new account will be read/write without modify on the folder.

The ULS log files begin showing errors where it cannot delete each log file at the beginning instance of a new log file. The number of log files continues to grow until it fills the volume.

Fun going in after people to figure out why things are happening. This is very bad if the pemissions get changed/hardened in the default location "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS".

LANManager part Duex

What goes around comes around... Seems there's lots of people setting this back...

So to add to fgdump/pwdump, Cain&Able, etc. I found some nice tools from Security Friday that are not generally easy to find on other boards.

ScoopLM

http://www.securityfriday.com/tools/ScoopLM.html

Theres several nice tools and articles here, so poke around a little. Take note for the article on "Hazard of 'My Network Places; on Windows XP". With a little imagination and virtualization you can create you own LM Honey pot to put on networks and grab hashes as users around you use "My Network Places"