Logon script not running?

[ddl]

Hi all,

I am in a Windows 2000 mixed mode AD environment. I have 2 domain
controllers setup.

I am trying to propagate software updates (update new versions of Norton
Corporate Edition) to Windows 9x PCs through logon scripts.

I do a initial test by using a logon script to display the user information
username, domainname and computer name. I choose a testing user account and
configured the account Profile-Logon script to point to
H:\WINNT\SYSVOL\sysvol\apmedia.com\scripts and the Home Folder to point to
H:\home\chandra.

The testing vbscript is put in the directory
H:\WINNT\SYSVOL\sysvol\apmedia.com\scripts.

But when the user log on the vbscript did not run.

Anyone knows what is wrong?

Also does anyone have good resources (with examples) of setting up profiles,
logon scripts and home dir mapping?

Thanks a million.

Starblazer

 

[Ace Fekay [MVP]]

In

Hi all,

I am in a Windows 2000 mixed mode AD environment. I have 2 domain
controllers setup.

I am trying to propagate software updates (update new versions of
Norton Corporate Edition) to Windows 9x PCs through logon scripts.

I do a initial test by using a logon script to display the user
information username, domainname and computer name. I choose a
testing user account and configured the account Profile-Logon script
to point to H:\WINNT\SYSVOL\sysvol\apmedia.com\scripts and the Home
Folder to point to H:\home\chandra.

The testing vbscript is put in the directory
H:\WINNT\SYSVOL\sysvol\apmedia.com\scripts.

But when the user log on the vbscript did not run.

Anyone knows what is wrong?

Also does anyone have good resources (with examples) of setting up
profiles, logon scripts and home dir mapping?

Thanks a million.

Starblazer

For Win9x and NT4 clients, why not just use the NETLOGON share?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Herb Martin]

I am in a Windows 2000 mixed mode AD environment. I have 2 domain

controllers setup.

Mixed mode has almost nothing to do with legacy clients but does imply
that you (may) have BDCs which will require special action to propagate
Login scripts for LEGACY client machines.

I am trying to propagate software updates (update new versions of Norton
Corporate Edition) to Windows 9x PCs through logon scripts.

Legacy clients don't use the Win2000 logon scripts specified through a GPO,
but rather use the logon script specified through the user properties for
legacy
support.

I do a initial test by using a logon script to display the user information
username, domainname and computer name. I choose a testing user account and
configured the account Profile-Logon script to point to
H:\WINNT\SYSVOL\sysvol\apmedia.com\scripts and the Home Folder to point to
H:\home\chandra.

I don't believe this is valid. You can only specify the FILE name for
legacy scripts;
they are presumed to be on the NetLogon share location. This is in a
slightly different
path on BDCs and Win2000+ DCs but the idea is the same.

BDCs expect this to be: %SystemRoot%\system32\repl\import\scripts
(although settable it is seldom changed by anyone knowledgable)
DCs expect this to be: SYSVOL in the subdirectory "domain-name"\Scripts.

Also does anyone have good resources (with examples) of setting up profiles,
logon scripts and home dir mapping?

Profiles pretty much take care of themselves if you just make the decision
about
Local vs. Roaming (or perhaps mandatory).

Logon scripts are pretty much self-explanatory, and directory mapping is
usually
persistant by default OR you can (if you're paranoid like many good admins)
set
this through a script.

Try asking you ssearches like this AT Google:
[ scripts logon 2000 | 2003 profiles microsoft: ] (note the colon:
after Microsoft:
[ scripts logon 2000 | 2003 profiles site:microsoft.com ]

Using a colon after Microsoft: when searching with Google specifies the
special
"Microsoft collection" (web wide, not just AT Microsoft.)

Most of the time you can search Microsoft more effectively through Google
than
by using Microsoft's own site searching tools. I haven't done a search AT
Microsoft
in months. (And I search for something there almost every (usually many
times every)
day.