[THIN] Re: Home directory and Profile Script
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 21 Oct 2005 09:20:17 -0700
Sorry, no Delorean here.
Joe
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Braebaum, Neil
Sent: Friday, October 21, 2005 9:08 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Home directory and Profile Script
Sure - just switch on the flux capacitor, and hit 88 miles per hour.
Neil
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx
> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Lilley, Brian
> Sent: 21 October 2005 13:42
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Re: Home directory and Profile Script
>
> yes, yes Neil... we hear what you're saying... but can we
> actually travel back in time with this baby?
>
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
> Behalf Of Braebaum, Neil
> Sent: 21 October 2005 09:31
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Home directory and Profile Script
>
>
> > -----Original Message-----
> > From: thin-bounce@xxxxxxxxxxxxx
> > [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk
> > Sent: 20 October 2005 21:46
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] Re: Home directory and Profile Script
> >
> > If I may, the whole point of the script is to extract the
> TS Profile
> > Path for all users in AD. Correct? Is it really worth trying to
> > optimize the code and resources used?
>
> Nope, that wasn't really why I posted my example.
>
> I posted my example, because given what the OP had original
> posted, it was nearest in terms of simplicity and being easy
> to follow.
>
> Optimisation came up as something of a fallacy, due to Andrew
> objecting to one of my comments, and they spent ages trying
> to refute it, and still throwing snake eyes ;-)
>
> > Especially when a script like this is used once every full moon?
> > Shouldn't the goal be to get the job done? So it takes a few extra
> > seconds to process or an extra megabyte of RAM on your PC doing one
> > way vs. the other. Most people use the ADO method because
> that's what
> > Microsoft has posted on the script site. A simple cut and paste,
> > change a few parameters and you're up and running...
>
> Exactly - that's why most people do it that way - they got a
> sample script, and never gave it a moments more thought.
> Having to do it yourself, or follow some very simplistic
> script on how it's done, gives you future scope and evolving further.
>
> Simply downloading an ADO example - as we've seen - more than
> likely means most people never understand what's going on
> with it, and have to add a whole load more stuff to their
> script that they don't understand.
>
> The reason why I posted the examples I did, being that it's
> not much more complex that what they've already got.
>
> > Granted, shifting
> > the workload from your workstation to the DC isn't the best idea.
>
> Agreed - in the main.
>
> > Using a recursive routine is not going to kill anything.
> > It's quite effective when sorting through hierarchical data.
> > The amount memory used going to be first incursion
> variables plus the
> > variables for each recursion.
> > The total memory used at a given time may actually be less that a
> > single filtered query as ALL of the filtered objects will
> be returned
> > in one large array. The disadvantage of using a recursive
> routine is
> > that you will perform a query for each recursion.
>
> Or not, as the case may be.
>
> > Now on the flip side... Recursive routines are difficult to
> > troubleshoot and understand... Sure, it's easy for me
> understand and I
> > use them from time to time, but it's not so easy for most
> people out
> > there.
>
> If you look at the code I posted, it is *very* simple, and
> easy to follow.
>
> > (These are admins, not
> > programmers... Remember, they are working on Microsoft products, not
> > Linux) Sure it's cute to do things like use foo and bar for
> > variables, but do it for yourself... If you're writing the
> code for a
> > customer, write it so that they can understand and support it.
>
> Which is why I wrote what I did, given *all* the examples, I
> still think it's the most *simplistic* code, which given what
> was written originally, is *why* I posted what I did. I did
> comment about countless other techniques, too.
>
> > Efficiency is more than just how much memory or CPU is utilized or
> > even how short the code it. It also includes readability and
> > supportability (if that's a word)
>
> Agreed.
>
> And that's what I focused on - what was nearest, simplistic
> and easy to follow from what the OP had originally posted. I
> said as much in my reply to Rick's suggested script:
> "Ultimately, doing stuff like this comes down to how best you
> can establish the info you want to process, and how best it
> matches or develops the skills you have."
>
> Neil
****************************************************************************
*
This email 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 email 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 Shop Direct
Group Limited or its subsidiaries. Please note that email communications may
be monitored. The registered office of Littlewoods Shop Direct Group Limited
is 100 Old Hall Street Liverpool L70 1AB registered number 5059352
****************************************************************************
*
This message has been scanned for viruses by BlackSpider MailControl -
www.blackspider.com
********************************************************
This Weeks Sponsor: Cesura, Inc.
Know about Citrix end-user slowdowns before they know.
Know the probable cause, immediately.
Know it all now with this free white paper.
http://www.cesurasolutions.com/landing/WPBCForCitrix.htm?mc=TBCC
********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Excellent SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Weeks Sponsor: Cesura, Inc.
Know about Citrix end-user slowdowns before they know.
Know the probable cause, immediately.
Know it all now with this free white paper.
http://www.cesurasolutions.com/landing/WPBCForCitrix.htm?mc=WETBCC
********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Excellent SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
