- logon script
- Posted by Seetal R Patel on July 1st, 2003
@Echo OFF
CLS
Echo.
Echo Welcome to COMPANY NAME
Echo.
Echo Please Wait, Connecting to Network Resources......
NET USE w: \\bdcname\common /PERSISTENT:NO >null
NET USE h: \\\\pdcname\home\username /PERSISTENT:NO >null
Save the above in a batch file e.g. logonscr.bat into the NETLOGON (e.g.
C:\WINNT\SYSTEM32\REPL\IMPORT) share of your PDC. The last two lines map the
drives (the mapping will not persist after logging off i.e. mapping will not
be remember after the user logs off).
Thanks,
Seetal.
"Harvey" <hvli@yahoo.com> wrote in message
news:0c7b01c33fdb$55a6fa60$a501280a@phx.gbl...
- Posted by harvey on July 1st, 2003
Thanks for help! However, I could not make it working:
When I set User Environment Profile, I put the following:
User profile path: \\pdcname\netlogon
Login Script Name: logonscr_ts.bat
Are they correct? I test it for a couple of users, but
when I logon, I got the error messages:
Windows did not load your roaming profile and is
attempting to log you on with your local profile.
Changes to the profile will not be copied to the server
when you logoff.
Windows did not load your profile because a server copy
of the profile folder already exists that does not have
the correct security.
Either the current user or the Administrator's group must
be the owner of the folder.
Contact your network administrator.
When I log off, I got:
Windows cannot update your roaming profile.
Possible causes of this error include network problems or
insufficient security rights.
If this problem persists, contact your network
dministrator.
DETAIL - Access is denied.
I checked the file logonscr_ts.bat, it is ownered by the
administrator and has the permission Read by Everybody. I
even add the read permission for the test user. The
\\pdcname\netlogon (that is C:\WINNT\SYSTEM32
\REPL\IMPORT\Scripts) is shared by everybody and has read
permission for everybody. However, it just does not
work. Any suggestion?
Thanks!
Harvey
- Posted by Seetal R Patel on July 2nd, 2003
The error message you are getting is actually to do with the roaming
profiles (not the logon scripts). For testing purposes I suggest that you
tackle these two issues separately, i.e. only specify the logon script name
and leave out the profiles path.
For info on Roaming Profile, try the following link:
http://support.microsoft.com/?kbid=161070
Thanks,
Seetal.
"harvey" <hvli@yahoo.com> wrote in message
news:356301c34014$36ae44e0$a601280a@phx.gbl...