> -----Original Message----- > From: Jim Strowe [mailto:jstrowe@xxxxxxxxxxxxxxxx] > Sent: 09 December 2004 00:22 > To: Braebaum, Neil > Cc: thin@xxxxxxxxxxxxx > Subject: Scripting and bulk changes for AD-ah yes but where > to find learning examples > > "or rip off somebody else's script," Uh, no I don't think so.... BUT > > Neil, the only concern I have as a lurker to this > conversation is I have to do my own learning in a live environment. As do I - that's always been the case. And I didn't get the luxury of courses either. I'm not saying that as some kind of boast - merely to point out, there's nothing special about me, I just bought a few books, did some searching on the t'internet, got all friendly with MSDN, and started doing stuff. My first forays into ADSI / vbscript, were quite primitive, but ultimately with programming / scripting you learn by doing. > Is there any documentation out there for what the variable > names, syntax et al. are. I've seen scripts, (and have some > samples) but I would not just run somebody elses script > without a pretty GOOD understanding of what it does first. MSDN, and there are downloads as reference or CHMs. > Having done some C programming Me too. In fact it's a perfect analogy. Years ago when I first started working in a UNIX environment, I was pointed at a library of books and told to get up to speed. I did get courses on all the normal things - system admin, shell scripting, C programming et al, but all of these took the normal times to arrange, so by the time I got to do the courses, I had already had to be productive. It's the way I've been ever since. And it doesn't make me special - I'm not gifted, nor particularly sharp at these things - it's just a mindset thing. > I'd like to know: > Variable names > Key words > What syntax of something that works looks like. > Stuff like that so that if I fiddle with a simple script to > get my feet wet that I know what the heck I am manipulating. Well the thing to bear in mind with this sort of scripting, is that there are at least three layers, or aspect to it - there's ADSI, which is distinct, then there's WSH which is another distinct aspect and is the engine, then there's the choice of scripting language (jscript or vbscript). MSDN and Microsoft's scripting site are reasonable starting points. A lot here seem enamoured with the Microsoft admin scripting course, and there's countless books recommended. I regularly use three books when I've scripting work to do - plus HTML books, and these are focused on vbscript, WSH, and ADSI. But they are rarely detailed enough in their own right, so MSDN is a valuable resource. Other times I'll make use of Kixtart, because I find that very suitable for certain things (I think it's the ideal choice for the login environment). > Normally if I'm learning something I like to echo variables > to the screen or a file to make sure I'm actually got the > right stuff (before I try to re-populate it with something > I'd like) I've got 350 users to manipulate so yes kids I am motivated. Well it's only natural when writing a script to do something, that you use a non-destructive debugging iteration first. After a while, though, it's easy to get blasé - I know that when I'm doing something like scripting mass changes, that even if I do make a mistake, I'll easily be able to correct that by scripting, too. > I mean I don't even know with ADSI if I'm using VB to do it? > (sigh.another good reason to not just run a script > blindly......point me to a manual/web page et al and I will read it) > > Oh guys, don't put down CMD files and net commands. Batch is > a language too, (pretty crippled but it does manipulate stuff) I wouldn't put down cmd files and net commands, per se - I think they have a very valid place, and as always it's a case of the right tool for the job. My only point being that there always seems a desire to avoid something, and fudge round it, and realistically it would probably have been better to embrace the better solution at the outset. > Point me where the fishing poles are... <g> Well a good place to start is Microsoft's scripting site. Plenty of examples, and links to reference material. Neil *********************************************** This e-mail and its attachments are confidential and are intended for the above named recipient only. If this has come to you in error, please notify the sender immediately and delete this e-mail from your system. You must take no action based on this, nor must you copy or disclose it or any part of its contents to any person or organisation. Statements and opinions contained in this email may not necessarily represent those of Littlewoods. Please note that e-mail communications may be monitored. The registered office of Littlewoods Limited and its subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB. Registered number of Littlewoods Limited is 262152. ************************************************ ******************************************************** This Weeks Sponsor Activaeon.com Reduce licensing costs with activAeon XA and get one month completely free. http://www.activaeon.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm ThinWiki community http://www.thinwiki.com *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm