Sysvol and login script

[kokousam]

After installing a new DC (DC2) I was having problem with sysvol
replication. When I investigated the problem I found out the first DC
(DC1, which is the global Catalog) sysVol is in JRNL_WRAP_error. I
found an article about that error that states I have to do some
changes on Regedit after stopping FRS, but when I did that the the
Sysvol\Domain\policies and script directoris blew up.The same thing
happen to Sysvol\Domain_name\policies and scripts. I called Microsoft
and they sent me the policies and script directories to put back in
their normal location whichis sysvol\..\...and also guided me change
the Registry keys.After that everything is working fine however I
don't have my old login script nor any other login script under the
script directory but the users still get all the Drive mappings that
they had before I had this problem. I am puzzled with this and I don't
know how they're still getting all the mappings. I did a search for
login script in the DC I didn't find anything hidden I looked under
their profiles and I didn't see anything out of the ordinary.
The environement is 2DC Win 2k Domain in Mixed mode with
trustrelationship with another Doamin and all users are Win2k Pro.

Does any one have any suggetion to how to solve this problem or what
is happening?.

Thanks guys

Sam

 

[Chriss3]

Hello, you may mapped the drives with the reconnect option, then they will
try to reconnect, if it founds out the mapped location is not available at
logon, a messages will appear to chose if you want to re connect at next
logon.

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

 

[kokousam]

But my concern is that the drives were mapped through Login script
(which it doesn't exixt anymore under script directory) not manually.

Thanks

Hello, you may mapped the drives with the reconnect option, then they will
try to reconnect, if it founds out the mapped location is not available at
logon, a messages will appear to chose if you want to re connect at next
logon.

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

Any help is appreciate it.

 

[kokousam]

But my concern is that the drives were mapped through Login script
(which it doesn't exixt anymore under script directory) not manually.

Thanks

Hello, you may mapped the drives with the reconnect option, then they will
try to reconnect, if it founds out the mapped location is not available at
logon, a messages will appear to chose if you want to re connect at next
logon.

--
Regards,

Christoffer Andersson
No email replies please - reply in the newsgroup
If the information was help full, you can let me know at:
http://www.itsystem.se/employers.asp?ID=1

Any help is appreciate it.

 

[John]

If your login script maps drives as persistant they will appear in the
clients registry and will re-map at next logon unless the share that
they map is unavailable.

 

[kokousam]

So if I understand you correctly any time you run a login script that
maps the drives few times through the login script I should remove it
from the script directory because it's already cashed out in the
client registry. I am trying to understand it once for all because I
noticed before the blew up (incident), the login script use to give me
an error stating " the drive is already in use...error 53..or
something to that affect, Which it makes sense because the loading of
the registry preceeds the login script execution.

Thanks for you help.

 

[Guest]

They are getting their drive mappings from thier PC's
local cache. if you added a new PC it will have no drive
mappings

 

[David Brandt [MSFT]]

If the script is in their local profile it appears that at one time it was
working or it would not have been copied there too, but are you using
roaming profiles for this. Anything change from the time it did work to
now?
Are they able to browse to sysvol and see it, and if they execute the logon
script manually does it run and map their drives?
Are any users successfully getting it like you want them too or is this
affecting all users?

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.