ADMT and log on scripts

G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Hi all

I have succsefully migrated user account and computer accounts from my NT
domaiin to my 2003 AD domain using ADMT version2. Users who have been
migrated along with there comptuter acounts can log onto the AD domain with
there current profile. Some of my migrated users have log in scripts in the
NT domain. When i migrate these users, the users log in scripts seem to also
get migrated because when the user logs into the AD domain the users mapped
drives are there, and when i look at the properties of the user account in AD
on the profile tab i can see the log in script. But what i cant figure out is
how is AD able to use the log in script or know where the script lives?
becaue when I look in the C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts on
one of my DC's in my AD domain I see *no scripts* in this folder, so how is
AD able to fire the script if the script doesn live in
C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?

thanks
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Are you sure the script is running? Mapped network drives can be cached
within the user profile.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
> Hi all
>
> I have succsefully migrated user account and computer accounts from my NT
> domaiin to my 2003 AD domain using ADMT version2. Users who have been
> migrated along with there comptuter acounts can log onto the AD domain
> with
> there current profile. Some of my migrated users have log in scripts in
> the
> NT domain. When i migrate these users, the users log in scripts seem to
> also
> get migrated because when the user logs into the AD domain the users
> mapped
> drives are there, and when i look at the properties of the user account in
> AD
> on the profile tab i can see the log in script. But what i cant figure out
> is
> how is AD able to use the log in script or know where the script lives?
> becaue when I look in the C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
> on
> one of my DC's in my AD domain I see *no scripts* in this folder, so how
> is
> AD able to fire the script if the script doesn live in
> C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
>
> thanks
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

It looks like it is. In the profile tab on the account properties in AD i can
see the script from NT, and the account that was migrated hasnt called me
complaining that his drives arent mapped. If the script was migrated then the
script should live in C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts by defautlt
correct?

So are you scrathing your head like i am or is there an explanation for this?

"Chriss3 [MVP]" wrote:

> Are you sure the script is running? Mapped network drives can be cached
> within the user profile.
>
> --
> Regards
> Christoffer Andersson
> Microsoft MVP - Directory Services
>
> No email replies please - reply in the newsgroup
> ------------------------------------------------
> http://www.chrisse.se - Active Directory Tips
>
> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
> news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
> > Hi all
> >
> > I have succsefully migrated user account and computer accounts from my NT
> > domaiin to my 2003 AD domain using ADMT version2. Users who have been
> > migrated along with there comptuter acounts can log onto the AD domain
> > with
> > there current profile. Some of my migrated users have log in scripts in
> > the
> > NT domain. When i migrate these users, the users log in scripts seem to
> > also
> > get migrated because when the user logs into the AD domain the users
> > mapped
> > drives are there, and when i look at the properties of the user account in
> > AD
> > on the profile tab i can see the log in script. But what i cant figure out
> > is
> > how is AD able to use the log in script or know where the script lives?
> > becaue when I look in the C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
> > on
> > one of my DC's in my AD domain I see *no scripts* in this folder, so how
> > is
> > AD able to fire the script if the script doesn live in
> > C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
> >
> > thanks
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Yes it should, but also if you migrated SID History the particular user
still has read rights to the NETLOGON share in the source domain, but the
destination domain has know knowledge about this as you said. I will guess
for it's stored in the profile, you can simply verify that by disconnect a
drive that trying to map or is mapped and see if it maps again, at next
logon?

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
news:4A44E809-0FF4-4090-8888-0B9AC48A21DD@microsoft.com...
> It looks like it is. In the profile tab on the account properties in AD i
> can
> see the script from NT, and the account that was migrated hasnt called me
> complaining that his drives arent mapped. If the script was migrated then
> the
> script should live in C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts by
> defautlt
> correct?
>
> So are you scrathing your head like i am or is there an explanation for
> this?
>
> "Chriss3 [MVP]" wrote:
>
>> Are you sure the script is running? Mapped network drives can be cached
>> within the user profile.
>>
>> --
>> Regards
>> Christoffer Andersson
>> Microsoft MVP - Directory Services
>>
>> No email replies please - reply in the newsgroup
>> ------------------------------------------------
>> http://www.chrisse.se - Active Directory Tips
>>
>> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
>> news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
>> > Hi all
>> >
>> > I have succsefully migrated user account and computer accounts from my
>> > NT
>> > domaiin to my 2003 AD domain using ADMT version2. Users who have been
>> > migrated along with there comptuter acounts can log onto the AD domain
>> > with
>> > there current profile. Some of my migrated users have log in scripts in
>> > the
>> > NT domain. When i migrate these users, the users log in scripts seem to
>> > also
>> > get migrated because when the user logs into the AD domain the users
>> > mapped
>> > drives are there, and when i look at the properties of the user account
>> > in
>> > AD
>> > on the profile tab i can see the log in script. But what i cant figure
>> > out
>> > is
>> > how is AD able to use the log in script or know where the script lives?
>> > becaue when I look in the
>> > C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
>> > on
>> > one of my DC's in my AD domain I see *no scripts* in this folder, so
>> > how
>> > is
>> > AD able to fire the script if the script doesn live in
>> > C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
>> >
>> > thanks
>>
>>
>>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Ok i will log the user off log the user back on disconnect the drives and
then the log the user back on and see what happens. Also I chose to disbale
the source account during the migration, so the only way the migrated user
accoutn can still have access that i can think of would be because of the
trust relationship between the NT domain and AD

"Chriss3 [MVP]" wrote:

> Yes it should, but also if you migrated SID History the particular user
> still has read rights to the NETLOGON share in the source domain, but the
> destination domain has know knowledge about this as you said. I will guess
> for it's stored in the profile, you can simply verify that by disconnect a
> drive that trying to map or is mapped and see if it maps again, at next
> logon?
>
> --
> Regards
> Christoffer Andersson
> Microsoft MVP - Directory Services
>
> No email replies please - reply in the newsgroup
> ------------------------------------------------
> http://www.chrisse.se - Active Directory Tips
>
> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
> news:4A44E809-0FF4-4090-8888-0B9AC48A21DD@microsoft.com...
> > It looks like it is. In the profile tab on the account properties in AD i
> > can
> > see the script from NT, and the account that was migrated hasnt called me
> > complaining that his drives arent mapped. If the script was migrated then
> > the
> > script should live in C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts by
> > defautlt
> > correct?
> >
> > So are you scrathing your head like i am or is there an explanation for
> > this?
> >
> > "Chriss3 [MVP]" wrote:
> >
> >> Are you sure the script is running? Mapped network drives can be cached
> >> within the user profile.
> >>
> >> --
> >> Regards
> >> Christoffer Andersson
> >> Microsoft MVP - Directory Services
> >>
> >> No email replies please - reply in the newsgroup
> >> ------------------------------------------------
> >> http://www.chrisse.se - Active Directory Tips
> >>
> >> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
> >> news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
> >> > Hi all
> >> >
> >> > I have succsefully migrated user account and computer accounts from my
> >> > NT
> >> > domaiin to my 2003 AD domain using ADMT version2. Users who have been
> >> > migrated along with there comptuter acounts can log onto the AD domain
> >> > with
> >> > there current profile. Some of my migrated users have log in scripts in
> >> > the
> >> > NT domain. When i migrate these users, the users log in scripts seem to
> >> > also
> >> > get migrated because when the user logs into the AD domain the users
> >> > mapped
> >> > drives are there, and when i look at the properties of the user account
> >> > in
> >> > AD
> >> > on the profile tab i can see the log in script. But what i cant figure
> >> > out
> >> > is
> >> > how is AD able to use the log in script or know where the script lives?
> >> > becaue when I look in the
> >> > C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
> >> > on
> >> > one of my DC's in my AD domain I see *no scripts* in this folder, so
> >> > how
> >> > is
> >> > AD able to fire the script if the script doesn live in
> >> > C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
> >> >
> >> > thanks
> >>
> >>
> >>
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Ok yes you were correct about mapping still being stored in the users cached
profile, i disconnected the drives loged the user off and hten back on and
the drives didnt show up. So I guess my next question is all i need to do is
copy the scripts from he repl fodler on NT to
C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts on AD and then configure the
users properties show the script in the profile tab?

I should be all good right?

Thanks again

"Chriss3 [MVP]" wrote:

> Yes it should, but also if you migrated SID History the particular user
> still has read rights to the NETLOGON share in the source domain, but the
> destination domain has know knowledge about this as you said. I will guess
> for it's stored in the profile, you can simply verify that by disconnect a
> drive that trying to map or is mapped and see if it maps again, at next
> logon?
>
> --
> Regards
> Christoffer Andersson
> Microsoft MVP - Directory Services
>
> No email replies please - reply in the newsgroup
> ------------------------------------------------
> http://www.chrisse.se - Active Directory Tips
>
> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
> news:4A44E809-0FF4-4090-8888-0B9AC48A21DD@microsoft.com...
> > It looks like it is. In the profile tab on the account properties in AD i
> > can
> > see the script from NT, and the account that was migrated hasnt called me
> > complaining that his drives arent mapped. If the script was migrated then
> > the
> > script should live in C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts by
> > defautlt
> > correct?
> >
> > So are you scrathing your head like i am or is there an explanation for
> > this?
> >
> > "Chriss3 [MVP]" wrote:
> >
> >> Are you sure the script is running? Mapped network drives can be cached
> >> within the user profile.
> >>
> >> --
> >> Regards
> >> Christoffer Andersson
> >> Microsoft MVP - Directory Services
> >>
> >> No email replies please - reply in the newsgroup
> >> ------------------------------------------------
> >> http://www.chrisse.se - Active Directory Tips
> >>
> >> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
> >> news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
> >> > Hi all
> >> >
> >> > I have succsefully migrated user account and computer accounts from my
> >> > NT
> >> > domaiin to my 2003 AD domain using ADMT version2. Users who have been
> >> > migrated along with there comptuter acounts can log onto the AD domain
> >> > with
> >> > there current profile. Some of my migrated users have log in scripts in
> >> > the
> >> > NT domain. When i migrate these users, the users log in scripts seem to
> >> > also
> >> > get migrated because when the user logs into the AD domain the users
> >> > mapped
> >> > drives are there, and when i look at the properties of the user account
> >> > in
> >> > AD
> >> > on the profile tab i can see the log in script. But what i cant figure
> >> > out
> >> > is
> >> > how is AD able to use the log in script or know where the script lives?
> >> > becaue when I look in the
> >> > C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
> >> > on
> >> > one of my DC's in my AD domain I see *no scripts* in this folder, so
> >> > how
> >> > is
> >> > AD able to fire the script if the script doesn live in
> >> > C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
> >> >
> >> > thanks
> >>
> >>
> >>
>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

That is not true if you migrated SID History, it can still use it's old SID
to gain access to the source domain whether the account in source is
disabled or not, but it's not related in this case, just a FYI.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
news:288F8307-FE37-43D8-B4C2-CB96E79B9FA9@microsoft.com...
> Ok i will log the user off log the user back on disconnect the drives and
> then the log the user back on and see what happens. Also I chose to
> disbale
> the source account during the migration, so the only way the migrated
> user
> accoutn can still have access that i can think of would be because of the
> trust relationship between the NT domain and AD
>
> "Chriss3 [MVP]" wrote:
>
>> Yes it should, but also if you migrated SID History the particular user
>> still has read rights to the NETLOGON share in the source domain, but the
>> destination domain has know knowledge about this as you said. I will
>> guess
>> for it's stored in the profile, you can simply verify that by disconnect
>> a
>> drive that trying to map or is mapped and see if it maps again, at next
>> logon?
>>
>> --
>> Regards
>> Christoffer Andersson
>> Microsoft MVP - Directory Services
>>
>> No email replies please - reply in the newsgroup
>> ------------------------------------------------
>> http://www.chrisse.se - Active Directory Tips
>>
>> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
>> news:4A44E809-0FF4-4090-8888-0B9AC48A21DD@microsoft.com...
>> > It looks like it is. In the profile tab on the account properties in AD
>> > i
>> > can
>> > see the script from NT, and the account that was migrated hasnt called
>> > me
>> > complaining that his drives arent mapped. If the script was migrated
>> > then
>> > the
>> > script should live in C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts by
>> > defautlt
>> > correct?
>> >
>> > So are you scrathing your head like i am or is there an explanation for
>> > this?
>> >
>> > "Chriss3 [MVP]" wrote:
>> >
>> >> Are you sure the script is running? Mapped network drives can be
>> >> cached
>> >> within the user profile.
>> >>
>> >> --
>> >> Regards
>> >> Christoffer Andersson
>> >> Microsoft MVP - Directory Services
>> >>
>> >> No email replies please - reply in the newsgroup
>> >> ------------------------------------------------
>> >> http://www.chrisse.se - Active Directory Tips
>> >>
>> >> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
>> >> news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
>> >> > Hi all
>> >> >
>> >> > I have succsefully migrated user account and computer accounts from
>> >> > my
>> >> > NT
>> >> > domaiin to my 2003 AD domain using ADMT version2. Users who have
>> >> > been
>> >> > migrated along with there comptuter acounts can log onto the AD
>> >> > domain
>> >> > with
>> >> > there current profile. Some of my migrated users have log in scripts
>> >> > in
>> >> > the
>> >> > NT domain. When i migrate these users, the users log in scripts seem
>> >> > to
>> >> > also
>> >> > get migrated because when the user logs into the AD domain the users
>> >> > mapped
>> >> > drives are there, and when i look at the properties of the user
>> >> > account
>> >> > in
>> >> > AD
>> >> > on the profile tab i can see the log in script. But what i cant
>> >> > figure
>> >> > out
>> >> > is
>> >> > how is AD able to use the log in script or know where the script
>> >> > lives?
>> >> > becaue when I look in the
>> >> > C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
>> >> > on
>> >> > one of my DC's in my AD domain I see *no scripts* in this folder, so
>> >> > how
>> >> > is
>> >> > AD able to fire the script if the script doesn live in
>> >> > C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
>> >> >
>> >> > thanks
>> >>
>> >>
>> >>
>>
>>
>>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

You just need to copy the script, since the name of the script already is
within the logon script attribute.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
news:7FB07071-28CB-4C05-B1AC-6791C3BA911D@microsoft.com...
> Ok yes you were correct about mapping still being stored in the users
> cached
> profile, i disconnected the drives loged the user off and hten back on and
> the drives didnt show up. So I guess my next question is all i need to do
> is
> copy the scripts from he repl fodler on NT to
> C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts on AD and then configure the
> users properties show the script in the profile tab?
>
> I should be all good right?
>
> Thanks again
>
> "Chriss3 [MVP]" wrote:
>
>> Yes it should, but also if you migrated SID History the particular user
>> still has read rights to the NETLOGON share in the source domain, but the
>> destination domain has know knowledge about this as you said. I will
>> guess
>> for it's stored in the profile, you can simply verify that by disconnect
>> a
>> drive that trying to map or is mapped and see if it maps again, at next
>> logon?
>>
>> --
>> Regards
>> Christoffer Andersson
>> Microsoft MVP - Directory Services
>>
>> No email replies please - reply in the newsgroup
>> ------------------------------------------------
>> http://www.chrisse.se - Active Directory Tips
>>
>> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
>> news:4A44E809-0FF4-4090-8888-0B9AC48A21DD@microsoft.com...
>> > It looks like it is. In the profile tab on the account properties in AD
>> > i
>> > can
>> > see the script from NT, and the account that was migrated hasnt called
>> > me
>> > complaining that his drives arent mapped. If the script was migrated
>> > then
>> > the
>> > script should live in C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts by
>> > defautlt
>> > correct?
>> >
>> > So are you scrathing your head like i am or is there an explanation for
>> > this?
>> >
>> > "Chriss3 [MVP]" wrote:
>> >
>> >> Are you sure the script is running? Mapped network drives can be
>> >> cached
>> >> within the user profile.
>> >>
>> >> --
>> >> Regards
>> >> Christoffer Andersson
>> >> Microsoft MVP - Directory Services
>> >>
>> >> No email replies please - reply in the newsgroup
>> >> ------------------------------------------------
>> >> http://www.chrisse.se - Active Directory Tips
>> >>
>> >> "Skipster" <Skipster@discussions.microsoft.com> skrev i meddelandet
>> >> news:8571631A-E2D9-4B45-8EC4-6A727C49B653@microsoft.com...
>> >> > Hi all
>> >> >
>> >> > I have succsefully migrated user account and computer accounts from
>> >> > my
>> >> > NT
>> >> > domaiin to my 2003 AD domain using ADMT version2. Users who have
>> >> > been
>> >> > migrated along with there comptuter acounts can log onto the AD
>> >> > domain
>> >> > with
>> >> > there current profile. Some of my migrated users have log in scripts
>> >> > in
>> >> > the
>> >> > NT domain. When i migrate these users, the users log in scripts seem
>> >> > to
>> >> > also
>> >> > get migrated because when the user logs into the AD domain the users
>> >> > mapped
>> >> > drives are there, and when i look at the properties of the user
>> >> > account
>> >> > in
>> >> > AD
>> >> > on the profile tab i can see the log in script. But what i cant
>> >> > figure
>> >> > out
>> >> > is
>> >> > how is AD able to use the log in script or know where the script
>> >> > lives?
>> >> > becaue when I look in the
>> >> > C:\WINDOWS\SYSVOL\sysvol\domainname.com\scripts
>> >> > on
>> >> > one of my DC's in my AD domain I see *no scripts* in this folder, so
>> >> > how
>> >> > is
>> >> > AD able to fire the script if the script doesn live in
>> >> > C:\WINDOWS\SYSVOL\sysvol\nwpsc.com\scripts ?
>> >> >
>> >> > thanks
>> >>
>> >>
>> >>
>>
>>
>>
 

TRENDING THREADS