Re: Roaming profile in problem
From: ptwilliams (ptw2001_at_hotmail.com)
Date: 02/24/05
- Next message: ptwilliams: "Re: Roaming profile in problem"
- Previous message: danieltan_at_time.net.my: "Re: Roaming profile in problem"
- In reply to: Herb Martin: "Re: Roaming profile in problem"
- Next in thread: Herb Martin: "Re: Roaming profile in problem"
- Reply: Herb Martin: "Re: Roaming profile in problem"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Feb 2005 08:13:23 -0000
Thanks! I'll take a look at those books.
I'm probably going to put it off to the summer -enjoying ADSI via VBS at the
moment. But a lot of people are telling me Perl is the way forward...
-- Paul Williams http://www.msresource.net/ http://forums.msresource.net/ "Herb Martin" <news@LearnQuick.com> wrote in message news:eHBcuIhGFHA.3376@TK2MSFTNGP14.phx.gbl... "ptwilliams" <ptw2001@hotmail.com> wrote in message news:u9YQTGfGFHA.2420@TK2MSFTNGP14.phx.gbl... > Ah...nice. I'll have a play with that tomorrow. I'm thinking about > learning Perl. I just downloaded and installed ActivePerl... Perl can be learned USEFULLY in stages. Just enough to solve a some problems with only a few lines of code, then later a bit more on how to use libraries provided by other, etc. Learning the regular expression syntax usally presents a steep learning curve but this curve puts you on a very useful plateau with just a bit more effort. And the RegExes are generally applicable to many other tools. Regexes work similarly in grep, sed, awk, many programmers' editors and so one. Once you know the principles then it is easy to adapt to small rule changes or increased features. Even the built-in FindStr has the /R switch for turning on RegEx capability -- meaning you can benefit even on systems that have no Unix-like tools. (Random workstations and servers etc.) If you want help, then let me know. The two class books are "Learning Perl" (14.75 on Amazon new&used) Programming Perl (18.72 new&used.) "Learning Perl" is MUCH simpler and in my opinion "Programming Perl" is MUCH better and an eventual necessity for almost all Perl programmers. But if you no nothing of programming then 'Learning' takes more baby steps. Another EXCELLENT book as you start to USE Perl is "Perl Cookbook" which offers working "snippet" programs and routines that no only solve a multitude of useful problems but stand as superior examples of how an expert programmer makes Perl simple yet amazingly effective. One of the best things about Perl is that 10 lines of Perl often does more than 10-100 lines of C or VB. Fewer lines almost always means faster to program, easier to understand and test, but most of all FEWER BUGS. -- Herb Martin > > I often use /whowill, but I'd forgotten about /finduser. > > nltest is a real handy tool alright!!! > > > -- > > Paul Williams > > http://www.msresource.net/ > http://forums.msresource.net/ > > "Herb Martin" <news@LearnQuick.com> wrote in message > news:OvlnAYVGFHA.4088@TK2MSFTNGP09.phx.gbl... > "ptwilliams" <ptw2001@hotmail.com> wrote in message > news:eiITfHSGFHA.3840@tk2msftngp13.phx.gbl... > > > I wonder if there is a built-in and direct way to tell if the machine > and > > > user are authenticated.... > > > > That would be nice! > > Maybe these are close enough: > > nltest /whowill:Domain.Com UserName > > nltest /finduser:UserName > > > Can you whip something up in Perl?!? ;-) > > Well, sure, though it wouldn't be direct but > just another hack <grin> > > #Perl begins > > $debug = 1; #set to 0 for less output > @services = `net start`; > foreach (@services) { > next unless /^\s+Net Logon\s*$/; > $dc = 1; > print if $debug; > last; > } > > print "DC\n" if $dc && $debug; > print "not DC\n" if $dc && $debug; > if (defined($ENV{LOGONSERVER})) { > $logonServer = $ENV{LOGONSERVER}; > $logonServer =~ s/.*\\+(.*)/$1/; > print "LogonServer: $logonServer\n" if $debug; > } > if (defined($ENV{COMPUTERNAME})) { > $computer = $ENV{COMPUTERNAME}; > print "Computer: $computer\n" if $debug; > } > > if ($dc || ($computer != $logonServer)) { > print "logged onto domain.\n"; > exit 0; > } else { #User is > print "NOT logged onto domain.\n"; > exit 1; > } > > # Perl ends > > -- > Herb Martin > > > > > > > > -- > > > > Paul Williams > > > > http://www.msresource.net > > http://forums.msresource.net > > > > > > "Herb Martin" <news@LearnQuick.com> wrote in message > > news:%23hHvvf4FFHA.2180@TK2MSFTNGP12.phx.gbl... > > "ptwilliams" <ptw2001@hotmail.com> wrote in message > > news:eZS4PC4FFHA.3888@TK2MSFTNGP12.phx.gbl... > > > The logonserver is the local machine if a DC cannot be found, e.g. the > > > computer name. > > > > > > > I was also leaving some wriggle room for > > things like DC available, authenticates, then > > DC does down (credentials might even expire.) > > > > I wonder if there is a built-in and direct way to > > tell if the machine and user are authenticated.... > > > > (Looking at the environment works for me, but > > seems a bit indirect or non-specific.) > > > > -- > > Herb Martin > > > > > > > > > > -- > > > > > > Paul Williams > > > > > > http://www.msresource.net/ > > > http://forums.msresource.net/ > > > > > > "Herb Martin" <news@LearnQuick.com> wrote in message > > > news:unSbSA3FFHA.1392@tk2msftngp13.phx.gbl... > > > <danieltan@time.net.my> wrote in message > > > news:1108908702.154362.35980@g14g2000cwa.googlegroups.com... > > > > Herb, firstly if i can set L to a DC and get result then my computer > is > > > > authenticated ? > > > > > > I think this is true -- were the the user not logged on > > > it would seem wrong to show a logon server. > > > > > > NLTest is more definitive but difficult to use (contrary > > > command line switches.) > > > > > > I was sort of hoping that someone would post a KB article > > > describing such tests. (Experience makes it pretty obvious > > > to me but that is NOT a good answer for someone trying to > > > learn.) > > > > > > > also if USE and ping can be used then it is > > > > authenticated also ? > > > > > > In no way does ping tell you this. > > > > > > Ping FAILURE would make it unlikely that authentication > > > worked but even that is not reliable unless you are very > > > certain why ping failed. > > > > > > For instance, any firewall including the XP-Win2003 built-in > > > firewall might block ping or IP might be broken a computer > > > still authenticate in some domains with another protocol but > > > this is less common today with IP required and few people > > > using other protocols. > > > > > > > What are the components required to have in order > > > > to have roaming profile works ? > > > > > > Authentication > > > Server with share, proper permissions on share and NTFS > > > Usually share and NTFS need to be Full Control for the > > > group or user to who will save a profile. > > > Network operation so that client can reach the share (timely > > > manner so that it doesn't timeout) > > > > > > -- > > > Herb Martin > > > > > > > > > > > > > > Regards > > > > Daniel > > > > > > > > > > > > > > > > > > > > > >
- Next message: ptwilliams: "Re: Roaming profile in problem"
- Previous message: danieltan_at_time.net.my: "Re: Roaming profile in problem"
- In reply to: Herb Martin: "Re: Roaming profile in problem"
- Next in thread: Herb Martin: "Re: Roaming profile in problem"
- Reply: Herb Martin: "Re: Roaming profile in problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
