<?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 Nine traits of the veteran Windows administrator ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154]]></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/102-342154/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-06-18T17:54:34-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[lol]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3475698]]></link>
        <description><![CDATA[just you my friend.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3475698]]></guid>
        <dc:creator><![CDATA[samjenko]]></dc:creator>
        <pubDate>Sun, 24 Jul 2011 16:27:24 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[hahaha]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3456219]]></link>
        <description><![CDATA[Where is ability to shut down and reboot repeatedly? That should be number 1. MSCE, sure I read the book and passed the test, I'm capable. Riiiiggght. A monkey could shut down and reboot. Unix ftw.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3456219]]></guid>
        <dc:creator><![CDATA[kathismom]]></dc:creator>
        <pubDate>Wed, 01 Jun 2011 15:34:25 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I also Agree.]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428333]]></link>
        <description><![CDATA[I read all of the comments and suggestion.I agree all of these and using these we can become ]beitcertified.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428333]]></guid>
        <dc:creator><![CDATA[aaronangelle]]></dc:creator>
        <pubDate>Fri, 11 Mar 2011 22:17:46 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Yes Process Monitor. Also another idea]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428246]]></link>
        <description><![CDATA[As ultimitloozer suggests Process Monitor is a good choice. One drawback is the volume of output it produces. It can be reduced by spending some time configuring its exclusion list. Or if you are facile with a good editor you can quickly exclude unrelated records from a large output.You don't mention how long a space issue event lasts. If it's on the order of a minute or more then I would do the following as a first approach.Create a script that every 20 seconds:   1) echo %date% %time%                       &gt;&gt; file   2) runs Sysinternals Pslist                      &gt;&gt; file   3) runs Sysinternals  Du -q -l 1 [target]   &gt;&gt; fileWhere [target] is either entire drive                     e.g.  c:\or a dir if the space problem is in a known dir     e.g.  c:\dataThe Pslist data will point to which program is getting CPUThe Du data will show where the space usage is occurring.After an occurrence or two you can narrow the Du [target]When really close add to the script a   4) dir /a /s /od [target]   &gt;&gt; fileand perhaps comment out the DuI know from long experience that on any decently performing server such a script will have little detrimental impact on performance.edit: [target] was missing]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428246]]></guid>
        <dc:creator><![CDATA[Cmd_Line_Dino]]></dc:creator>
        <pubDate>Fri, 11 Mar 2011 13:36:30 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Yes Process Monitor. Also another idea]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428244]]></link>
        <description><![CDATA[As ultimitloozer suggests Process Monitor is a good choice. One drawback is the volume of output it produces. It can be reduced by spending some time configuring its exclusion list. Or if you are facile with a good editor you can quickly exclude unrelated records from a large output.You don't mention how long a space issue event lasts. If it's on the order of a minute or more then I would do the following as a first approach.Create a script that every 20 seconds:   1) echo %date% %time%                       &gt;&gt; file   2) runs Sysinternals Pslist                      &gt;&gt; file   3) runs Sysinternals  Du -q -l 1 [target]   &gt;&gt; fileWhere [target] is either entire drive                     e.g.  c:\or a dir if the space problem is in a known dir     e.g.  c:\dataThe Pslist data will point to which program is getting CPUThe Du data will show where the space usage is occurring.After an occurrence or two you can narrow the Du [target]When really close add to the script a   4) dir /a /s /od [target]   &gt;&gt; fileand perhaps comment out the DuI know from long experience that on any decently performing server such a script will have little detrimental impact on performance.edit: [target] was missing]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428244]]></guid>
        <dc:creator><![CDATA[Cmd_Line_Dino]]></dc:creator>
        <pubDate>Fri, 11 Mar 2011 13:31:04 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Ditto]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428129]]></link>
        <description><![CDATA[My last project, we had a mix of 2/3 Linux, 1/3 Windows servers ... yet 2/3 of our time maintaining/fixing things was on the Windows servers. That's a 4:1 ratio per server, Windows:Linux. I just laugh when I hear people arguing that Windows saves money. (and yes, this was professional, experienced admins using good tools, on both the Windows and Linux sides).]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428129]]></guid>
        <dc:creator><![CDATA[daboochmeister]]></dc:creator>
        <pubDate>Fri, 11 Mar 2011 08:14:21 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[AMEN mate]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428067]]></link>
        <description><![CDATA[you hit that right on the head.  What is funny is the PS commands that I am most comfortable with are dealing with Exchange - and that is becuase I am finding the Exchange management console to be clunky in comparison to using the PS commands. However for other repeditive tasks batch/cmd work a treat , same with VBS .. sort of like the saying in the old VHS/Betamax tape days - save time rewind ... scrippting has saved me plenty of time.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428067]]></guid>
        <dc:creator><![CDATA[jstevens@...]]></dc:creator>
        <pubDate>Fri, 11 Mar 2011 06:00:51 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[SysInternals Process Monitor]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428020]]></link>
        <description><![CDATA[You can watch this type of information from the Sysinternals Process Monitor if you know when it starts happening.  You can watch only the file activity you want and see its associated process.  Don't know of anything that shows all of the information you are looking for with a single utility, but at least it will allow you to identify the culprit.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3428020]]></guid>
        <dc:creator><![CDATA[Bruce Epper]]></dc:creator>
        <pubDate>Fri, 11 Mar 2011 01:21:52 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Responses.]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427924]]></link>
        <description><![CDATA[&quot;...you need ALL the tools ( both in M$ and UNIX/LINUX environments )...&quot;Not if you're in a Windows-only shop.&quot;Now there is truly no difference between LINUX and Windows for the end user.&quot;Except in the apps available to them.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427924]]></guid>
        <dc:creator><![CDATA[CharlieSpencer_Palmetto]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 16:07:11 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Sometimes you've got to cut your losses.]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427922]]></link>
        <description><![CDATA[If the problem has only occurred once, it may not be worth the time to determine the root cause.  Reboot it, re-image it, reload it; whatever.  And it's not my time that's all that important; it's the user's productivity that can't be sacrificed on the altar of troubleshooting.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427922]]></guid>
        <dc:creator><![CDATA[CharlieSpencer_Palmetto]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 16:03:51 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Disappointing]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427909]]></link>
        <description><![CDATA[If the first article was troll bait, someone got baited and felt they had to do some one-ups-manship.These lists have more in common than people are letting on. Win #3 &quot;Workstations count more than servers&quot; on this list, and Unix #8 &quot;We know more about Windows than we'll ever let on&quot; are obvious: At the end of the day both are still supporting users. Postmortems? Don't tell me that Windows admins don't do this because they have more important things to do. Oh gosh, the server blue screened, reboot it? No, they check the basics - check the logs, check the disk, and so forth. Just hoping for the best without troubleshooting is a recipe for disaster. &quot;Prefer elegant solutions&quot; gets the retort &quot;Prefer tested solutions&quot;? Are you serious? As if the Unix admin duct tapes everything with perl script while all Windows admins only use canned software? I've known plenty of Windows admins that spend inordinate amounts of time juggling VB code for their operations. Seriously, Unix admins can get along just fine without having to wrap everything in a bash or perl script. Plenty of Windows admins use text editors extensively, whether they are writing a clever SQL expression or manually checking a sprawling pile of XML output to find a problem... and even a Unix admin knows when a text editor isn't the right tool for the job. And last, don't tell me that Windows admins are ok with bouncing servers like yo-yos just because there's a problem and they don't have time to troubleshoot it. If you treat your PDCs like this you might want to brush up your text editor skills and update your resume soon.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427909]]></guid>
        <dc:creator><![CDATA[michaelh.tek@...]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 15:50:38 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[It's a case of diminishing returns]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427914]]></link>
        <description><![CDATA[As a Windows Admin, I too agree with the points on the list.  As somewhat of a perfectionist, I also can identify with a Unix SysAdmin's desire to find the root cause and address it.The issue becomes one of time/resources:  how much time can reasonably be spent determining the root cause of an issue before you say &quot;The heck with it, lets address the symptom&quot;.  Of course, if the problem is chronic, it then becomes most cost effective to resolve the underlying issue(s)....]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427914]]></guid>
        <dc:creator><![CDATA[poppaman2]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 14:13:32 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I agree]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427903]]></link>
        <description><![CDATA[Which is soo sooo soo sad:(]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427903]]></guid>
        <dc:creator><![CDATA[PrincessMilissa]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 13:43:57 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[You lose more then just the company]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427900]]></link>
        <description><![CDATA[and our jobs]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427900]]></guid>
        <dc:creator><![CDATA[PrincessMilissa]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 13:31:56 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Scripting]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427883]]></link>
        <description><![CDATA[I'm surprised when people don't know about scripting. Coming from a (home) linux background and using DOS, I find scripting can be really useful. Is much more powerful and accessbile under linux, but can be just as useful under Windows, and there are tools from Linux ported to Windows, eg cygwin or indivudual tools such as wingrep.On the gui side, I'ev been known to script repetitive tasks with AutoIt.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427883]]></guid>
        <dc:creator><![CDATA[zenoscope]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 12:27:28 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Thank you, thank you, thank you]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427844]]></link>
        <description><![CDATA[And, just one more thing to add. As supports for our non-IT organisations, we are part of the solution having to deal with all the bugs and threats in the hardware and software worlds.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427844]]></guid>
        <dc:creator><![CDATA[ScarF]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 10:52:59 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[How much have you used Unix-like systems?]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427782]]></link>
        <description><![CDATA[&gt;  Last but not least do think about the fact that if Unix is the best and I am not denying that, how is it that in 40+ years of development/evolution it is unable to make solid inroads to the desktop segment?   A good windows Administrator who is upto date on technology can actually spend time with family and friends as he/she does not need to worry about postmortems but only about the living.That's amusing.I was the netadmin for a defense contractor.  85% of the network was Unix-like systems (primarily Mandriva and RedHat at the time), and 65% of my time was spent fighting MS Windows fires, dealing with licensing (yes, we were one of a small percentage of the companies using MS Windows that took pains to be license compliant), and maintaining all the excess third-party BS that was needed to keep the MS Windows systems working properly.  The Unix-like systems just ran themselves.Half of the time I spent dealing with the Unix-like systems was dealing with the problem of ensuring proprietary software the company used would actually run properly on those Unix-like systems -- so even in the relatively rare case of having to do any work with the Unix-like systems, half our problems were still proprietary software issues (mostly Maya for rendering servers).If it wasn't for the MS Windows issues, they probably would have only needed me part-time, so don't try to tell me a netadmin's life is easier with MS Windows.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427782]]></guid>
        <dc:creator><![CDATA[apotheon]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 08:27:51 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[That calls for a toast...]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427740]]></link>
        <description><![CDATA[Very well said.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427740]]></guid>
        <dc:creator><![CDATA[jbenito00]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 07:18:41 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Harrassed]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427639]]></link>
        <description><![CDATA[Windows admins are constantly under fire. Everything from outlook to terminal services requires reboots or tool that take for ever to run. If MS fixes this stuff we would be out of a job.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427639]]></guid>
        <dc:creator><![CDATA[Here2serveu@...]]></dc:creator>
        <pubDate>Thu, 10 Mar 2011 03:37:12 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[This is really sad...]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427558]]></link>
        <description><![CDATA[It is truer that Unix administrators have a very tough job, and they do it very well, I have seen this a lot but there are some things that need to be clarified here:Windows Administrators also do a great job and we rarely write scripts because 1. we have tools that we can use to do the same thing or we know where we can find a good tested script and edit it to our needs. Has for Microsoft borrowing ideas from Unix and others, What is wrong in that? In today's world we are constantly influenced by the world around us and Microsoft is no exception. It might sound very strange to you but most of us find things easier with the Windows File System, and if we need a single place to search we just search the entire computer. The number of tools that are available to a Windows Admin is Hugh and growing, almost all of them help people to be more productive. Most Windows Administrators I know have a passion for taking a holistic view and supporting/learning things that help take I.T to the next level in the company. Last but not least do think about the fact that if Unix is the best and I am not denying that, how is it that in 40+ years of development/evolution it is unable to make solid inroads to the desktop segment?  A good windows Administrator who is upto date on technology can actually spend time with family and friends as he/she does not need to worry about postmortems but  only about the living. A healthy respect for all Operating Systems and their focus areas is a must for all Administrators from all platforms.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-342154-3427558]]></guid>
        <dc:creator><![CDATA[contactasv@...]]></dc:creator>
        <pubDate>Wed, 09 Mar 2011 22:49:50 -0800</pubDate>
    </item>
    </channel>
</rss>

