Slashdot Mirror


User: sdreher

sdreher's activity in the archive.

Stories
0
Comments
2
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 2

  1. Re:Punish those responsible... on US Busts Military Network Hacker · · Score: 1

    Face it. The US gov't has set itself up for this... Using Microsoft products extensively for example. Hell if I was someone who hated america why not use one of america's biggest corporate machines against us... see if "lil billy" cares enough to make reliable software instead of a buck even in the face of patriotism. Also, what makes any of us think that government can "churn out" good sysadmins? All the good ones are protecting corp. america because the pay is better and they were smarter not to enlist. I live next to a couple Air Force admins who make me laugh at what they don't know... makes me wonder how much is really at stake from a digital security perspective. Hell, send the politicians to jail for persuing corporate mandates against P2P sharing and whatnot instead of protecting everyone's interests of national security. Hell, we're doing EXACTLY what every terrorist wants us to do - go after our own to make a buck instead of going after them who are the real threat. *clap* *clap* to congress (dripping with sarcasm). We all need to elect leadership that knows how to turn on a computer rather than those who only know how to turn out oil. *sigh*

  2. NOC Howto (from someone who runs one) on Required Practices for a Network Operations Center? · · Score: 2, Interesting

    1. Simplicity - if you can't streamline all of your core operations you spend more time figuring it out when something breaks.
    2. Consistent Documentation/Knowledge Transfer among your technicians.
    3. Consistent equipment, stick with one vendor and develop excellent relations with that vendor. (Example, I stuck with dell on a big purchase, got my servers and 2 extra computers, a box of posters, shirts, and other dell junk and 16 switches for free just for "being cool")
    4. Adaquate troubleshooting database. Find a help desk software suite that fits the nature of your user/clients needs. Make sure it is scalable, and intuitive. Having a web based self-help package is also recommended... The more your clients can help themselves, the less your phone will ring.
    5. Document everything such as set up procedures to password databases. (don't post it on the web interface of your help desk software lol!)
    6. Have security a priority on every direction your NOC has a presence.
    7. Set up your equipment to talk to YOU. Most management software (openview, webtrends, help dest software, etc) can send you emails if not text messaging and whatnot... possabilities are endless, but its nice to know something is broke before your users/clients.

    Thats it. I can go on and on.