Ah... That stuff is useful, Roger, but it turns out I needed some GPO work. Specifically, in my test OU, I did not have the "Login Scripts are Visible" option enabled... Oops!
Thanks for all the help.. Looks like I'm all set, now. > -----Original Message----- > From: Roger Seielstad [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 10, 2002 6:40 AM > To: NT 2000 Discussions > Subject: RE: Monitoring login script progess (re-worded) > > > Alternately, cscript %0\..\logon.vbs will work, calling it > from the netlogon share of the authenticating DC. > > You might consider adding the line: > Cscript //h:cscript //s > Which will force cscript (command line interpreter) as the > default for all WSH scripts > > ------------------------------------------------------ > Roger D. Seielstad - MCSE > Sr. Systems Administrator > Inovis - Formerly Harbinger and Extricity > Atlanta, GA > > > > -----Original Message----- > > From: Tim George [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 09, 2002 11:32 AM > > To: NT 2000 Discussions > > Subject: RE: Monitoring login script progess (re-worded) > > > > > > You are on the right path with cscript... > > > > In my testing it appears that CScript handles > > UNC just fine... > > For example try executing from a dos prompt > > > > cscript \\tweety\netlogon\test.vbs > > > > (putting in your UNC path to the file...) > > > > I think your previous attempt may have > > failed because the working directory for > > the batch file was not what you expected or > > CScript looked in its directory for the login.vbs... > > > > -Tim > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Levis > > Sent: Monday, December 09, 2002 11:18 AM > > To: NT 2000 Discussions > > Subject: Monitoring login script progess (re-worded) > > > > > > (The first time I posted this, I must have been drunk... It > > didn't make > > much sense. I will reattempt): > > > > So my vbs login script is all written... But now, how to I > > get it to run (and display the echos) in a command window? > > > > In AD, I have a test OU with the login.vbs assigned by > > group policy... However, when the login script is running, > > I get pop-up boxes for the echoes, saying "Connecting > > this, doing that, etc". As I've said, I want these echoes > > to take place inside a black cmd-style box. > > > > I tried making a .bat (see below) that calls the > > login.vbs with cscript, so see if I could get a nice black > > box that way.... > > > > @echo off > > %0\..\cscript login.vbs > > exit > > > > It did not work, tho, due to the cmd's innability to > > handle UNC paths (I think). > > > > Hopefully it's something simple that I'm overlooking.... > > Thanks for any hints! > > > > ------ > > You are subscribed as [EMAIL PROTECTED] > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe send a blank email to %%email.unsub%% > > > > > > ------ > > You are subscribed as [EMAIL PROTECTED] > > Archives: http://www.swynk.com/sitesearch/search.asp > > To unsubscribe send a blank email to %%email.unsub%% > > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to %%email.unsub%% > ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
