Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Windows Operating Systems Software

A Linux Admin's Guide to Windows? 86

Rexburg asks: "I recently took a job managing an all Windows network. While my knowledge of the OS is enough to perform the functions of my job, I want to have my bases covered. Naturally, I began the hunt for documentation, but all I can find are books to help Windows users/admins understand and use Linux. I need the opposite. Can the Slashdot crowd point a fellow OSS-head in the right direction?"
This discussion has been archived. No new comments can be posted.

A Linux Admin's Guide to Windows?

Comments Filter:
  • Hmm... (Score:2, Funny)

    by Coyote67 ( 220141 )
    No
    • by leonbrooks ( 8043 ) <SentByMSBlast-No ... .brooks.fdns.net> on Saturday July 26, 2003 @06:53AM (#6538961) Homepage
      I've seen the Bible (0.75 megawords) summarised as "In the end, God wins"; I think a book teaching Linux admins how to admin MS-Windows could be summarised much more quickly: "Don't".

      A slightly longer summary would have a subtitle "How to run for your life in order to stand still" and an overview like this:

      Stuff changes by itself, you're running the security equivalent of a black colander (leaky and the holes are really obvious), everything costs heaps and much of it still doesn't work. If you're hoping to escape the command line, be prepared to at least RegEdit regularly if not hit CMD.EXE more than once a week. If you want to understand how something works, buy a book on it and bear in mind that it will have changed since the book will written. If the drivers for something are broken, stiff bikkies. Microsoft will be running the system directly soon, putting out of a job (since that will screw things up so totally at least twice that the site will switch to Linux out of self-defense anyway). It is very point-and-click but the letters on the front are neither warm nor friendly [ever actually read a EULA] and they left the first and most important word ("don't") off.

      The actual content will say:

      Reboot it. If that doesn't fix the problem, install the latest upgrades. If still no go, reboot from a write-protected floppy and format every hard disk, then reinstall everything. If that doesn't fix it, install the latest upgrades again. Still sad? Then
      PANIC!
    • Check out www.bpbatch.org.

      The general idea is before the PC boots off the hard drive, you set it up to boot off the NIC. It searches for a DHCP server, uses TFTP to download a command interpreter called BpBatch.

      Bpbatch is an extremely powerful tool. It can run scripts (stored on your hidden Linux server) which control the booting process. It can partition/format the local hard drive and download images (using a utility called MrZip (like Ghost)).

      It has a bunch of capabilities. You seriously need to re

  • Picky? (Score:2, Insightful)

    What, you have to have something marketed directly at you?

    I don't think I've seen any of them titled "Windows HowTo: Don't read me if you know anything about Linux"

    Face it, if you're going from Linux to Windows, you're in a pretty small minority.
    • by BoomerSooner ( 308737 ) on Friday July 25, 2003 @06:50PM (#6536422) Homepage Journal
      TechNet [microsoft.com]

      If you're admining a winblows system you need to check for security releases daily and run every single piece of shit software they offer to harden your system.

      Good luck, you'll need it.

      BTW I admin about 10 windows machines, 8 linux machines, 1 solaris machine and 2 os x servers. By far I spend most of my time admining the Windows boxes. I would venture to guess around 90-95% of the time. Windows sucks but until it no longer pays the bills, I'm stuck.
  • by floydman ( 179924 ) <floydman@gmail.com> on Friday July 25, 2003 @05:52PM (#6535871)
    really, i mean if you are a unix/linux admin, then Windows to you should be very clear and straight forward. A few testing(i am sure you can spare the time and hardware, even at work, temporarirly)...The dialogs in Windows are self explanatory...

    but just in case you get stuck, the best resource is the MSDN [microsoft.com] library..

    • "...if you are a unix/linux admin, then Windows to you should be very clear and straight forward."

      That is total bollocks and you know it. I'd like to see someone who knows Exim and Postfix walk into an clustered Exchange 2000 site and hit the ground running. Yet more FUD from the "I know *NIX so therefore I know everything" crowd.

      • by Anonymous Coward
        Someone that knows Exim and Postfix would probably only be showing up at a site with clustered Exchange 2000 to replace it with something smarter. See, that's the point. UNIX IS smarter than windows for soooo many reasons. Chances are (like I did) a highly skilled Sendmail and Qmail admin can pickup Exchange over a weekend. I know I learned enough Exchange to help them significantly by replacing 4 clustered Exchange servers with 1 FreeBSD machine running qmail with tarpitting and spamassassin. Turns out the
        • So I suppose that seeing as the site you were at had no requirement for groupware then no-one else does either?

          Let's face reality, there are a lot of very complex Windows networks out there. You may deride them, but they do exist and they need competant admins. You can try to run them with a bunch of monkeys, but that's why issues like code red and SQLslammer are such a pain, bad software + incompetant admins = disaster.

          No matter how good your UNIX skills are you still won't have a thorough understanding
  • Uh... Oh.... (Score:3, Insightful)

    by coloclone ( 552113 ) <clifford_ireland ... m ['oo.' in gap]> on Friday July 25, 2003 @05:52PM (#6535873)

    "I recently took a job managing an all Windows network...."

    Run...... run fast!!!

    No.... seriously good luck. I went from a pure HP-UX enviroment to a Windows one... It's really fun to try and script mass file renames among other things

    BE PATIENT AND YOU'LL LIVE!

    • Re:Uh... Oh.... (Score:2, Insightful)

      by temojen ( 678985 )
      Uhh huh... we've got a heterogeneous network... some Linux, some Windows... Try explaining to windows users why they aren't allowed to have administrator access.... Or why you won't install ICQ (it requires admin access to run)
      • Yes! When I took over our HP System the old admin gave out the su password to EVERYONE! Then guess who has to be an asshole and tell everyone they can't install their own webshots anymore.

        • Re:Uh... Oh.... (Score:5, Insightful)

          by Sevn ( 12012 ) on Friday July 25, 2003 @06:45PM (#6536361) Homepage Journal
          Get used to that. Being an admin means being an
          "asshole" a lot. You have to learn now to be firm
          and tell people how it is. It's one of the reasons
          why a lot of ex-admin types make great managers.
          A good admin has no problem telling people how
          things are.
      • Atleast your users know what ICQ is. If my users dont see the shortcut on the desktop, the program is not installed. They wont even check the start menu . . . its an instant phone call.
    • coping with the WinTel Software Distribution (WSD)
      5 Minute mini lecture using WinInternals only!

      introduction
      WSD, it seemes to be allmost forgotten here in the civilised worlds but here and there you still need to bring support to some legacy systems as the WSD-2K/XP or the even more archane WSD-03
      luckally there ARE ways to allmost be as productive in your new login shell CMD.EXE (aka Command Prompt or DosBox) as you where in your shell, *cough*

      documentation
      When you expect your now fairly standa

    • Re:Uh... Oh.... (Score:5, Insightful)

      by belroth ( 103586 ) on Saturday July 26, 2003 @09:20AM (#6539231)
      It's really fun to try and script mass file renames among other things
      Install cygwin.

      Assuming your machines are all networked and you are administrator for all of them you only need to install cygwin on your box, you can then do most things remotely, probably using the '$' shares.
      Learn how to use the 'net' and other commands, I have a script to create new folders, share them and then set share pemissions and folder security to allow a group to have access - then another sets up users as members of that group. You can do somethings reasonably easily from the CMD prompt, others from cygwin. It's worth finding the non-gui ways to set things up, where they exist.

      • Re:Uh... Oh.... (Score:5, Informative)

        by sql*kitten ( 1359 ) * on Saturday July 26, 2003 @12:59PM (#6540102)
        Install cygwin.

        Agreed. And then read this [labmice.net]. And learn to use Perl's Win32::API. Most Unix people have no idea that Windows has all this stuff available - it's a bit different from Unix but if you want to use a command line a script everything, you can.
  • by Anonymous Coward
    Click Start, Help! Look, no man pages or Engrish documentation!
  • I recently took a job managing an all Windows network.

    Were they aware that you have no idea what you're doing when they hired you?
    • by Anonymous Coward
      And this is different from an MCSE how?

      Oh yeah, there's a chance he knows how computers & networks work, not just how to use version x.yy of the config wizard.
    • Re:Windows admin? (Score:5, Insightful)

      by linuxwrangler ( 582055 ) on Friday July 25, 2003 @06:22PM (#6536071)
      Not true. I've read plenty of stories and reports that *nix admins typically have a far better foundation in the fundamentals. My experience has been similar. *nix gurus tend to know what happens under the surface and can often do a much faster/better job of debugging and engineering. I'll wager that if you were to compare *nix admins with Windoze admins, you would find a far higher percentage of *nix admins understand http/smtp/pop well enough to use telnet to access and debug a web/mail/pop server.

      Also, as a couple of articles have pointed out, almost all *nix admins have at least some experience with Windows while Windows admins with *nix skills are less common.

      If I were the employer, however, I'd be concerned about interest level. If you are dying to learn Windows and increase your overall skill level then go for it. For others, being forced to deal with Windows would be like sitting listening to blackboards being scratched all day. Still, you gotta eat.
      • Not true. I've read plenty of stories and reports that *nix admins typically have a far better foundation in the fundamentals. My experience has been similar. *nix gurus tend to know what happens under the surface and can often do a much faster/better job of debugging and engineering

        Yes and no. Yes, *nix people do tend to know a lot more about computers. On the other hand, they expect things to make sense and to behave deterministically, and on Windows, sometimes they don't.

        I develop for and occasio

  • by adamy ( 78406 ) on Friday July 25, 2003 @05:58PM (#6535911) Homepage Journal
    Look at the O'REilly series for NT/2K/XP system admin. They talk about doing the types of things you are used to on Unix (Scripting etc).
  • by Rxke ( 644923 )
    Looks like Cliff wants to be excommunicated by the slashdotcrowds. Average slashdot user: 'WTF? A linux guy as windows admin? /popping artery/
  • by reallocate ( 142797 ) on Friday July 25, 2003 @06:01PM (#6535936)
    Can't recommend titles of any specific texts. Go fr a rummagein the nearest Border's or B&N. Then check online.

    Microsoft does publish large, thick texts on their network platforms. I remember them as being much better than most 3rd-party books.

    Also, if you can get your hands on the books used in an MCSE course, you'll at least have something. My boss sent me to an MCSE course a long time ago. I remember the notebooks as being long on "click here" and short on "here's what the code does after you click", but you will get an overview of Microsoft's network model.
  • As somebody else pointed out, there's lots of information online at msdn.microsoft.com

    For other needs, you can google your way out of most problems (since the chances of you being the first person to run into an issue with Windows are slim).

    Learn vbscript, they're the only way to get things done sometimes (unless you want F2 to be your new best friend). Also, learn some of the old Batch scripting, many of those tricks can be applied to the vbscript tools.
    Oh, and learn all the hotkeys, it'll speed things u
  • Search MSN (Score:4, Interesting)

    by SoCalChris ( 573049 ) on Friday July 25, 2003 @06:08PM (#6535976) Journal
    Go to MSN.com, and search for "Linux" [msn.com]. The third result is how to switch from Linux to Windows.

    I'm serious.
    • by Anonymous Coward
      I clicked on the the third result, but when the page came up, it crashed my browser. I'm not sure whether to laugh or to cry.
      • Laugh! (Score:2, Funny)

        by leonbrooks ( 8043 )
        when the page came up, it crashed my browser. I'm not sure whether to laugh or to cry.

        Laugh! If you start crying at what Microsoft says and does, you'll never stop.\

        (-: The page was probably trying to install an ActiveX wizard to do the changeover for you, and assumed you were using Exploder :-)

  • by linuxwrangler ( 582055 ) on Friday July 25, 2003 @06:10PM (#6535992)
    I mostly deal with *nix but need to deal with Windoze from time to time. I got the Universal Command Guide: http://www.ucgbook.com

    There's plenty to complain about starting with the hubris of the "Every Command Every Operating System Cross-Referenced Together" subtitle Apparently TRON, Plan 9, vxWorks, etc. aren't operating systems (or "Some of the More Common Operating Systems, Many of the Common Commands" didn't get past the marketing department). The selection of commands in the book can sometimes seem odd and at $70 it isn't cheap, either.

    Still, when you are used to "w", "ifconfig", "passwd" and the rest but find yourself sitting in front of a Netware/Mac/DOS/Windows machine thinking "there must be an equivalent instruction if I only knew what/where it is", then the cross reference in this book should at least get you pointed in the right direction.

    I only pick it up every few months but even at $70 it doesn't take much time and frustration savings to pay for itself.
  • by Anonymous Coward
    The Bible, but it looks like you have already sold your soul to Satan.
  • JSI (Score:5, Informative)

    by altp ( 108775 ) on Friday July 25, 2003 @06:14PM (#6536014)
    http://www.jsiinc.com/ [jsiinc.com]

    There is an incredable wealth of information on that site.

    altp
  • by Sevn ( 12012 ) on Friday July 25, 2003 @06:16PM (#6536023) Homepage Journal
    AND THEY ARE FREE!!!

    And this old white haired guy that has trained the
    whole world is selling them and stuff. Strangely,
    the shipping is 7 bucks.

    Seriously though,

    I knew UNIX first. When my buddies were raving about
    dos and windows 3.0 being the next big thing, I was
    busy with other stuff and kinda ignored them. Next
    thing I knew I had NT 3.51 on a DEC workstation
    staring me in the face in the form of a new
    flight scheduling system. FUN! NOTHING like UNIX
    in any way shape or form. So I started with the
    basics. Operating systems all do pretty much the
    same types of things. The idea is to find out how
    to do those things. How do you:

    Set up a network card

    Install drivers

    Configure user accounts

    Change passwords

    Modify the filesystem

    Schedule jobs

    and so on and so on.

    The way I learned windows was to make a list of
    all the things I could think of that I had to do
    on a daily basis to admin a UNIX machine, and
    do research to find out how to accomplish those
    things on windows. After you've done that, you
    can fill in the rest of the blanks later. I spent
    a lot of time on USENET searching newsgroups for
    answers to silly things. The Microsoft Knowlege
    Database is an excellent tool. In the end, I
    learned something truly valuable. Windows NT 3.51
    sucked. Thoroughly. And I threw a party 5 months
    later when they scraped the NT Alpha box and
    replaced it with a Sparc running SunOS. Still,
    that initial exposure to Windows NT has helped
    me fix all kinds of things on family and friends
    Windows machines for quite some time. You just
    have to get used to touching a mouse a lot more
    than a UNIX person should. You have to get
    comfortable navigating point and click mazes
    to find things that aren't always were you'd think
    they would be logically. You have to get used to
    not always having the blessed log file to look at
    for help when something isn't working right, and
    being fed error messages that make no sense at all
    and give you no clue as to what the actual problem
    is. Today, USENET can be searched very easily with
    groups.google.com. A short time ago, you used
    deja.com. :) It's very rare if I run into a
    problem with any OS platform that someone else
    hasn't already run into that problem and asked
    someone on a newsgroup how to fix it. Hope this
    helps.
  • by Anonymous Coward


    Uh, the door?
  • Being a cross-platform admin myself, I feel your pain.

    The only usefull and/or needed reference guide I've ever found for Win32 server platforms are the (I'm sad to say) Microsoft Press, Windows Administrator's Pocket Consultant books.

    They are more to the point and have much less fluff than most other books on the subject.They are a lot more like the books we Unix/AIX/AS400 guys are used to reading.

    Just remember, a book about an OS can only be as good as that OS.
  • by Anonymous Coward on Friday July 25, 2003 @06:32PM (#6536215)
    Just pretend that FisherPrice or Hasbro or Mattel rewrote UNIX for 5 year olds. That's all windows is. When you start thinking of it as a pretty, underpowered version of UNIX for "special" people, it's very easy to use.
    • I laughed my 'arse' off when I read your post! That's the funniest analogy I've heard in a long time.
  • Wrong place, wrong question. Doh!

  • Cygwin and Python should be your new best friends. They turn Windows into a very administrator-friendly system. Cygwin will give you all the great commandline tools you need, and Python is just about the best scripting language there is. Together, they rock Windows harder than you can imagine.
  • The only "dummies" book with a redundant title.

    But if you mean a book specifically pointing out the similarities between powerful unix/linux commands and their few, watered-down, dos/windows counterparts, you probably won't find one. There just isn't a enough of a market for migrations in that direction for something like that to get published. You know what they say, 'Once you go hack, you never go back.'
  • It's pretty easy (Score:3, Interesting)

    by duffbeer703 ( 177751 ) on Friday July 25, 2003 @11:47PM (#6537992)
    You need to learn how windows authentication and permissions work. The NT model is more robust than most default Unix implementations, and difficult for many Unix-people to grasp.

    If you are using active directory, you need to understand ldap.

    If you are a good Linux admin, you'll be a good Windows admin too. Remember that groups.google.com is your friend.
  • I want to have my bases covered.

    All your bases are covered by us!
  • Except for learning and using the MS tools (Active Directory, IIS, ACLs etc.), making yourself a home is the best thing you can do.

    Most *nix Software has been ported either directly by the developers (Emacs, Vim, nmap etc.), MinGW [mingw.org] or CygWin [cygwin.com]. Insecure.org's tool list [insecure.org] gives a nice overview over the essential networking programs and ActiveState [activestate.com] has Ports of your three favourite scripting languages already.

    After installing all these tools, Win2k becomes a pretty usable OS.

  • Go get a copy of Master Windows 2000 Server, or Server 2003, whichever is most appropriate. It's big, but it cuts through the crap rather nicely. More importantly, it's not focused on MCSE test objectives like so many other Windows books tend to be, so it's applicable to the real world. As a bonus, Minsai doesn't work for MS, so when something sucks, he says so, and explains how to work with/around it in the real world.
  • by Rexburg ( 203940 ) on Saturday July 26, 2003 @04:51PM (#6541269)

    To everyone who has had something useful to say, thank you. Your suggestions are what I was looking for. I have found a few resources in my own searching's, but felt that having the eyes and minds of the /. crowd helping would yield far greater results.

    As for the rest of you: I have long wondered how many /.'ers were real sysadmins and hackers and who wasn't. Thank you for removing all doubt I may have had about your status.

    Several of you have tried to make an argument that I am under qualified for the job I've taken. I read over my submission again, and at no point do I say "I've never seen one of these new-fangled Windows machines before". My specialty has been with implementing Linux solutions to Windows networks via Samba. I have a fair grasp of Windows technologies and am quite comfortable in said environment. However, it would be foolhardy to assume that I know all there is to know about Redmond's offering.

    It is made clear to me by your statements that either you are wishful thinkers straining to install Corel's distro or that you haven't the self motivation necessary to stay competitive in this field. To the later, I look forward to cleaning up your network once you've been dismissed.

    I realize this is a bit off topic, but I felt that it would be unfair to those in similar straits watching if I didn't address these comments. Now, as promised, the links which I have found most useful.

    • http://www.ss64.com [ss64.com] - A helpful listing and translation of Windows NT, BASH and Oracle commands.
    • http://isg.ee.ethz.ch/tools/realmen/index.en.html [ee.ethz.ch] - Real Men Don't Click is a site by "a merry band of system managers from the Department of Electrical Engineering at the Swiss Federal Institute of Technology" and catalogues their efforts to manage a Win2K network with Linux know-how.
    • Sigh...Unfortunately for you, you'll never be a Jedi Knight...you've been taken by the forces of the dark side! How do I know? Because you can't see the Source, Luke! You'll never be able to see the Source for Dark Side, you'll only be their pawn. How sad, to lose a worthy *nix sys admin to the Dark Side. However, the Sources of the Light Side are continuing to gain strength, so perhaps you'll be rescued/liberated in the near future. Let's hope so! :-)
    • Thanks for summarizing. It should be a standard feature on ask Slashdot to allow the original submitter to post a summary of what he learned and let this appear at the top at the question.

      This would allow the rest of us to sort out the /. "M$ is 3v1l, bad boy!!! bad boy!!!" kneejerkers.

  • by 1iar_parad0x ( 676662 ) on Saturday July 26, 2003 @10:41PM (#6542668)
    All it took was one look at the headline and I could imagine all of the jokes . However, let's look at reality. If you're a real bonafide sysadmin, you're probably going to have to deal with Windows.

    I remember at one point I was having to write some VB code. It was during the dot com boom. There where certainly jobs for C++/Java people. However, there was a real demand for VB COM programmers. So I figured, I should at least take a look and try to figure out how the dark side works. Of course my first idea was to go around the office and ask if anyone had ever heard of a VB book for C++/Java programmers. (Actually I did run across a VB for COBOL programmers.) The immediate response was chuckles and outright laughter. Of course, my smart ass smirk probably didn't help. Anyway, there was a book that dove that deeply into VB. It was "Hardcore Visual Basic". There where a couple of good O'Reilly books as well. (As an ironic side note, the author stopped updating the book because he got so sick of microsoft abusing a perfectly good RAD tool).

    Yes, programming a glorified GUI sucks. Yes, you're ultimately going to cut and paste and cleverly misuse the IDE when you write code. Yes, VB is a painful. It like trying to ride a tricycle when you've got a Harley in the garage. However, most of the world runs Microsoft products and from time to time I have to work with Windows. So I getting sick of the snide comments. The submitter is definitely NOT A TROLL! I don't claim to be a hacker or an ubergeek but I'm kind of sick of the unprofessional nature of the Slashdot crowd.

    So, my best advice is that you take a look at some of the O'Reilly books and stroll through some of the reviews at Amazon. Let their data miners do the work for you.
    • So I getting sick of the snide comments. The submitter is definitely NOT A TROLL! I don't claim to be a hacker or an ubergeek but I'm kind of sick of the unprofessional nature of the Slashdot crowd.

      Not to be a troll either or anything, but... why do you think the Slashdot crowd is supposed to be professional? Slashdot is just an overgrown blog populated by a slightly more tech-savvy subset of the regular population. It's more like a subway in Silicon Valley than it is like your average board room. If y
  • by jregel ( 39009 ) on Sunday July 27, 2003 @01:43PM (#6545328) Homepage
    The best (IMHO) Windows administration book is Mastering Windows 2000 Server by Mark Minasi. The writing style is informal and Minasi has experience with other OSes and doesn't automatically take the view that Windows is the best for everything. The book doesn't cover how to use the GUI like some do, but does provide an overview of stuff like remote installation services, Active Directory, policies etc.

    Ignore what some other posts say - knowing UNIX will not automatically mean you know everything about Windows. To be a *good* Windows admin takes time and effort in the same way being a *good* UNIX admin takes time and effort.

    My perspective is as a primarily UNIX based consultant / administrator who needs to know about Windows. This book gets five stars for providing the info I need to understand the basics.

    Mod me up - this was informative.
  • Run *nix on the server(s) then use vmware or wine or whatever your preferance is to emulate windows. (Heck, even a screenshot might do). Let *nix run stable in the background, and whenever someone comes around or you go home for the night, just open up the emu. You might even get a reputation for running the most stable and efficient windows server ever, hehehe.

    If your going to need to work on workstations, then you will need to get more creative. Hire one of those 11 year old windows addicts (you prob

A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson

Working...