<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Novice net admins: Sidestep problems with these simple rules ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/11-121841/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-22T22:31:11-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[EXPERT help is usually wrong]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1522931]]></link>
        <description><![CDATA[Throughout the last fifteen years I have found that the Expert help is usually wrong.  When I first started out in netwk admin, it was for the State Government.  Well it didn't take me long to figure out that they subcontracted to the cheapest bidder, which means they didn't know anything.  I managed 4 counties of a 99 county network with hundreds of servers and thousands of pc's and because it was such a huge installation, they contracted out everything. To make matters worse, the servers, printers and user mgmt were controlled by the head office 3 hours away!  It didn't take long to figure out that they didn't know what they were doing either.  A lot of times in Government, it's not always your qualifications that gets you the job unfortunately.  Anyway, come to find out the installers told me they were out of work people hired by Manpower at the last minute and had never done any networking before!  There was one guy in the crew of 7 that knew what he was doing and he tried to show the rest what to do.  Nothing was labeled, most runs weren't tested, in most cases the server wasn't installed properly or the connect disk wouldn't work, server wouldn't boot.  They forgot the admin password and had to start over, etc.  It was a joke.  Every office was a nightmare.  After they left, I went to each office and labeled every port so I knew exactly what was connected where. Years later on a diff job a tech from the now history Digital came to our site to &quot;fix&quot; our server over the lunch hour.  At the time my position as net admin was under the controller and he was calling the shots, I protested but he ruled.  After the tech got the new motherboard in the server and it wouldn't boot we ended up being down for the rest of the afternoon.  It wasn't long after that management created a separate IT dept and made me head of it - no more controller.  If you are the network admin then you need to take control and take responsibility of everything that you are held accountable for.  If you don't know then you need to learn but I would not always rely on outside help because they might not be so quick to want to educate you and might mislead you.  After all, the longer it takes for you to figure it out, the longer they will be there making money.  Also, I would not alwasy trust what they are telling you.  I would need a calculator to figure out how many times I've seen a company do pretty much anything to extend the life of a service contract.  Furthermore, I'd be careful of letting them know exactly how green you are, If my company was in there I'd take that opportunity to inform mgmt that you didn't know what the heck you were doing and show them how much money they could save without you just so I could pick it up on the other end!  My advice to you is to start from the beginning.  The only way to learn how your network is setup is to go through it and document it.  There are plenty of shareware/freeware utilities out there that can help you.  Print it out and put it all in a three ring binder and put it on your desk.  Fancy On-line html manuals aren't always the best way to go, what good will they do you if your system or network is down?  Get some non-biased advice, take a network+ training class, and always Cover Your *ss.  There is a lot of competition in this world and unfortunately not everyone plays fair!  Hope this helps.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1522931]]></guid>
        <dc:creator><![CDATA[ServerJockey]]></dc:creator>
        <pubDate>Mon, 08 Sep 2003 07:23:29 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[What to secure]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1520197]]></link>
        <description><![CDATA[The issue is very dicey. Users pose the most headaches for net admins. I believe in-house training could create a fair playing gound. Like in your case, the user is ignorant as in &quot;Oh, I thought you just meant not to use Kazaa&quot;Teach them and they will love you.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1520197]]></guid>
        <dc:creator><![CDATA[Uch]]></dc:creator>
        <pubDate>Tue, 02 Sep 2003 03:46:36 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Never forget that your in charge of your network]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1518647]]></link>
        <description><![CDATA[As the person who will take the heat from the users it is up to you to make shore that you get the best value for money out of out side contractors. If you think their stuffing it up then you need to take charge of the situation. Remember: they are their working for you not the other way around. Just because some one is an ?Expert? doesn?t mean you should let them push you around or ignore you.Be assertive. If your not they will own you. And at the end of the day their stuff ups will reflect badly on you ass well. On the other hand if you manage to solve the problem you just may earn their respect and your future dealings with them will be on a much more equal footing.Never be afraid to look stupid and ask stupid questions if you think the answers will benefit you. It?s not a crime to look stupid in front of the heired help.I spent a long time in a work place where I was the in house admin but at the time I was still green as far as server admin was concerned. Until I asserted my self as the person running the show our outside contractors were happy to do what ever they felt like. Once I showed them that I wasn?t stupid and was willing to help them out as well things began to go a lot more smoothly.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1518647]]></guid>
        <dc:creator><![CDATA[nospamthanks@...]]></dc:creator>
        <pubDate>Wed, 27 Aug 2003 23:20:03 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Document with Screenshots]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1518337]]></link>
        <description><![CDATA[I know everyone hates to take the time to document, but it really is worth it.  My favorite tool is Fullshot, from inbit.com.  Just keep it loaded on every server and when you've changed a setup somewhere take a quick screensnap.It automatically puts the date and time and you can add a quick note about what you did if necessary, then print it.  I keep my printer loaded with 3-hole punched paper so I can just stick the printout in a binder or save the screenshot to a directory for config notes.  It's easy to take shots of a two or three screens or parts of windows and print them all on a single page.  The latest version of Fullshot even lets you email directly.A picture is worth a thousand hours of reinventing the wheel.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1518337]]></guid>
        <dc:creator><![CDATA[jmp2000]]></dc:creator>
        <pubDate>Wed, 27 Aug 2003 12:33:06 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Plan for the future as well]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1517303]]></link>
        <description><![CDATA[Plan for growth - growth is a CONSTANT in this world and plan for changes and upgrades.  Labeling is fundamental as is training.  Ensure you have adequate training resources available.  Call someone if you don't know and (wherever possible) test new things before you implement them.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-1517303]]></guid>
        <dc:creator><![CDATA[Digi-Tal]]></dc:creator>
        <pubDate>Mon, 25 Aug 2003 11:19:27 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Depends]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-788437]]></link>
        <description><![CDATA[Unfortunately, the only window of opportunity I have for server maintenance is Friday evenings....well, Sunday too but since Friday is already a workday, coming back at night isn't as bad as coming in on Sunday.  But those of us in the IT field who run servers that have to be up during business hours don't have the luxury of taking them down except during the window hours.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-788437]]></guid>
        <dc:creator><![CDATA[transit_Admin]]></dc:creator>
        <pubDate>Mon, 23 Jun 2003 07:26:35 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Documentation and Server logs]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782966]]></link>
        <description><![CDATA[DO keep detailed documentation of every aspect of your network and update it frequently.  I keep a binder with support info for software, hardware, etcDO insist that IT support staff become diligent about documentation.  It can save you hours (anddays) in a crisis.DO keep a checklist of daily, monthly tasks.  Not only will it help someone else but helps you, too.I keep a date book in the server room....anyone who logs onto a server must put what they did, etc.  Nice ref when your trying to track patterns in problems.  &quot;All backups ok&quot; &quot;Dat files updated correctly&quot; &quot;Full scan of PDC OK&quot;--CYA you're doing what you should be doing!]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782966]]></guid>
        <dc:creator><![CDATA[mas43]]></dc:creator>
        <pubDate>Thu, 12 Jun 2003 02:17:27 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Plan For Change]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782388]]></link>
        <description><![CDATA[When you design the network for existing conditions, give some thought to how the configuration might change.  Get a growth projection for the organization and location.Create a plan for additional hubs, swithes, and wiring where the network is most likely to change.  Allow extra length in cables to reach to alternate positions.  In some cases, pull extra cables.  Two cables can be pulled at the same time.  That saves time and expense when the additional one is needed.  Plan adequate power for all the pieces.  Provide a light in those wiring closets and cabinets.  Sounds basic, but you would be surprised how many times these things are overlooked.Label according to use.  Locations are fixed.  Cables to locations are not likely to change, but systems, people, and functions at the location will.  Label cables by location, not by the system that is connected.  Use a separate identification system for locations, systems, people, and functions.  It seems like overkill until pieces get shuffled.  An inadequate identification system can become a burden and lead to confusion.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782388]]></guid>
        <dc:creator><![CDATA[C_Tharp]]></dc:creator>
        <pubDate>Wed, 11 Jun 2003 06:01:17 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Backup]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782108]]></link>
        <description><![CDATA[Rather than backing up each individual workstations data, map a home directory for each user and instruct them to save all of their vital information there.  This way you know for sure that all of their data is safe due to your usual server backup strategy.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782108]]></guid>
        <dc:creator><![CDATA[bmorse@...]]></dc:creator>
        <pubDate>Tue, 10 Jun 2003 23:54:00 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Your next move]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782039]]></link>
        <description><![CDATA[Now, three things you need are managed PCs, a quality VPN client, and, remote desktop. I love remote desktop!]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-782039]]></guid>
        <dc:creator><![CDATA[cameroge@...]]></dc:creator>
        <pubDate>Tue, 10 Jun 2003 22:47:59 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Down boy, Down!]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781813]]></link>
        <description><![CDATA[It was 5:30 in the morning and I was rambling.  I would like to say it was to make a point, but there was none.  I've documented all my day to day admin tasks to an intranet site for the new IT employees specifically so I can go on vacation once in a while.  I have my fresh out of college totally inexperienced Help Desk staff adding users to the system in their first weeks, including email accounts and logon scripts.  I spend all my time on &quot;special projects&quot; and server maintenance now.  I even have a general troubleshooting guide for each server so that most problems can be solved without help by even our least experienced staff.  The up side of this is that I can work on the more visible projects that actually get noticed by the guys in the big offices, and I have the  time to get it done ahead of schedule.  Good documentation done right can be very useful.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781813]]></guid>
        <dc:creator><![CDATA[Roger99a]]></dc:creator>
        <pubDate>Tue, 10 Jun 2003 13:04:54 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Password Hacks]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781749]]></link>
        <description><![CDATA[I forgot to say that I also keep my password &quot;hacks&quot; in the same bag. I can not tell you how many ways there are for users to screwup with passwords.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781749]]></guid>
        <dc:creator><![CDATA[Al K]]></dc:creator>
        <pubDate>Tue, 10 Jun 2003 08:39:01 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Password Hacks]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781748]]></link>
        <description><![CDATA[I forgot to say that I also keep my password &quot;hacks&quot; in the same bag. I can not tell you how many ways there are for users to screwup with passwords.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781748]]></guid>
        <dc:creator><![CDATA[Al K]]></dc:creator>
        <pubDate>Tue, 10 Jun 2003 08:37:54 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[And then some]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781746]]></link>
        <description><![CDATA[Been there and sone that. Keep everyone posted, document everything, and let them know . Then create a &quot;Little Black Book&quot; that has all your extra tips, tricks, techniques and phone numbers (especially the extention of the tech/admin who saved your butt last time - Along with what snack they like and how to get it to them). I put that along with CD's, documentation and my few favorite tools in a plain black brief case that no gets but me. It makes life so much nicer to &quot;Be Prepared&quot;. Yes I was a Boy Scout.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781746]]></guid>
        <dc:creator><![CDATA[Al K]]></dc:creator>
        <pubDate>Tue, 10 Jun 2003 08:33:44 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Policies, aren't the best option]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781224]]></link>
        <description><![CDATA[IMHO the best option is to lockdown the workstations, based both user-level and machine level security - hey it takes quite a bit longer (to perfect it) but it is definately worth it in the long run...... Also tell users verbally and via email, that if it isn't saved on the server, and it gets deleted/corrupted or mysteriously vanished, it is their responsibility to replace the data. Tell your boss as well.  Every now and then, when you dfiscover that a user has been saving data locally, send out a company-wide &quot;reminder&quot;.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781224]]></guid>
        <dc:creator><![CDATA[greggl@...]]></dc:creator>
        <pubDate>Mon, 09 Jun 2003 17:48:19 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[More (must live by ) rules]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781222]]></link>
        <description><![CDATA[3.) If something goes wrong... STOP!, have a look at the appropriate website for their FAQ's and KB documents. This can save hours of work4.) Never fry bacon whilst naked.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781222]]></guid>
        <dc:creator><![CDATA[greggl@...]]></dc:creator>
        <pubDate>Mon, 09 Jun 2003 17:33:47 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Color coding]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781214]]></link>
        <description><![CDATA[Many organisations also use the patch panel for their inhouse PABX phone system.I HIGHLY recommend using a different colour cable for those non server related functions.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781214]]></guid>
        <dc:creator><![CDATA[greggl@...]]></dc:creator>
        <pubDate>Mon, 09 Jun 2003 17:25:19 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Be wary of &quot;expert help&quot;]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781020]]></link>
        <description><![CDATA[I totally agree with getting help when you need it , for example with a server running an OS that you are not versed on... BUT, always watch closely what is being done and DO NOT BE AFRAID to ask a lot of questions, especially when something is not making sense.I had an expert waste 12 hours because he would not listen to me, he had enabled two NICs on a Novell sever and they were creating a storm and not allowing anyone on the system.I tried to point this out because this had happened whenthe server first went online, but, he thought he new better than me... You need to speak LOUDLY even if you think you may look foolish, I wish I had.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-781020]]></guid>
        <dc:creator><![CDATA[Liv&DieN LA]]></dc:creator>
        <pubDate>Mon, 09 Jun 2003 09:39:21 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[color cables]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-780830]]></link>
        <description><![CDATA[I just thought of a good idea.  Buy cables that are in a different color from normal computers for your most important servers and dedicated devices.  Also, we do label the port, and the patch panel, and we have a map for when the cabling was originally done to the building listing every port.  I think wireless is the best way to go now on new installations since it is cheap to install the access points, and then very easy to add new connections without running new cables.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-780830]]></guid>
        <dc:creator><![CDATA[hackersdontgetpaid]]></dc:creator>
        <pubDate>Mon, 09 Jun 2003 03:57:15 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Written Policy - enforcement]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-780796]]></link>
        <description><![CDATA[Policy writing is only half the answer. Enforcement is required. Write an effective policy and show that the end user can and will be held responsible and their departments budget is liable for the lost revenue. It really keeps people working cohesive. (and systems up and running smoothly).I make sure I have full buy in from the powers that be and a sign off from temps to tenure...union to non-union before anyone logs in. I let the board members know I am not CYA, rather I am covering their butt. It is a bit tough to swallow at first, but it weeds out problem children, and keeps the IT ROI huge.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/11-121841-780796]]></guid>
        <dc:creator><![CDATA[mmaserati]]></dc:creator>
        <pubDate>Mon, 09 Jun 2003 03:03:37 -0700</pubDate>
    </item>
    </channel>
</rss>

