Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » Login script not running
Login script not running [message #159576] Fri, 31 July 2009 21:00 Go to next message
Chris  is currently offline Chris
Messages: 343
Registered: July 2009
Senior Member
Dear All,

In summary, how can the login run be execute and when the first time a new
user login, the home folder of the user connected to M:\ is created. I only
want to use the login.cmd. Thanks


Case 2 – Login.cmd
net use P: \\ssiatfileprd01\shared
net use m: \\ssiatfileprd01\home\%username%



Case 1- Login.cmd
net use P: \\ssiatfileprd01\shared

In user profile m:\ connect \\ssiatfileprd01\home\%username% - The drive
also mapped.

The issue with this case two is that when user is on wireless, they cannot
see the m:\. Only the P:\



Case 2 – Login.cmd
net use P: \\ssiatfileprd01\shared
net use m: \\ssiatfileprd01\home\%username%

If I create a new user and assign the login.cmd, the m:\ cannot be mapped
to user because the home folder does not exits. If you manually create the
folders e and assign permission, then it will mapped or If I create a new
user, I put the connect M:\ \\ssiatfileprd01\home\%username% first and
once the folder is created, I remove the connect M:\ and the user used only
login.cmd and it will work.

In this case, after reboot the two drive is there.

Just wonder if there is other ways to ensure the login can create the user
script automatically.




Case 1- Login.cmd
net use P: \\ssiatfileprd01\shared

In user profile m:\ connect \\ssiatfileprd01\home\%username% - The drive
also mapped.

The issue with this case two is that when user is on wireless, they cannot
see the m:\. Only the P:\
Re: Login script not running [message #159608 is a reply to message #159576] Sat, 01 August 2009 20:14 Go to previous messageGo to next message
Paul Yhonquea  is currently offline Paul Yhonquea  United States
Messages: 13
Registered: August 2009
Junior Member
In the end, do you want all users to have an M: drive mapped as their home
folder? If so, it would probably be better to use Active Directory to
accomplish this (user properties > Profile tab > Home folder section >
Connect M: To \\ssiatfileprd01\%username%). This way, the folder is created
as soon as the account is configured in AD. The user will always have that
account mapped as well, even if the logon script does not run. The logon
scrip as written can then be used to map other drives besides the home
folder.

Hope this helps.

Paul Yhonquea



"chris" <chris@discussions.microsoft.com> wrote in message
news:8CD42AF7-0DEC-416F-8352-05AD87F15AE0@microsoft.com...
> Dear All,
>
> In summary, how can the login run be execute and when the first time a new
> user login, the home folder of the user connected to M:\ is created. I
> only
> want to use the login.cmd. Thanks
>
>
> Case 2 - Login.cmd
> net use P: \\ssiatfileprd01\shared
> net use m: \\ssiatfileprd01\home\%username%
>
>
>
> Case 1- Login.cmd
> net use P: \\ssiatfileprd01\shared
>
> In user profile m:\ connect \\ssiatfileprd01\home\%username% - The
> drive
> also mapped.
>
> The issue with this case two is that when user is on wireless, they cannot
> see the m:\. Only the P:\
>
>
>
> Case 2 - Login.cmd
> net use P: \\ssiatfileprd01\shared
> net use m: \\ssiatfileprd01\home\%username%
>
> If I create a new user and assign the login.cmd, the m:\ cannot be mapped
> to user because the home folder does not exits. If you manually create
> the
> folders e and assign permission, then it will mapped or If I create a
> new
> user, I put the connect M:\ \\ssiatfileprd01\home\%username% first and
> once the folder is created, I remove the connect M:\ and the user used
> only
> login.cmd and it will work.
>
> In this case, after reboot the two drive is there.
>
> Just wonder if there is other ways to ensure the login can create the user
> script automatically.
>
>
>
>
> Case 1- Login.cmd
> net use P: \\ssiatfileprd01\shared
>
> In user profile m:\ connect \\ssiatfileprd01\home\%username% - The
> drive
> also mapped.
>
> The issue with this case two is that when user is on wireless, they cannot
> see the m:\. Only the P:\
>
>
>
Re: Login script not running [message #159624 is a reply to message #159608] Sun, 02 August 2009 09:17 Go to previous message
Chris  is currently offline Chris
Messages: 343
Registered: July 2009
Senior Member
Dear Paul,

Yes, the user want m:\ for home.

I have try your suggestion before and it work on local LAN. Howerver, when
user access via wireless m:\ cannot be mapped. Only P:\ can be mapped.

If I put in the login script, the both drive can be mapped. I do not want to
manually create the folder to assign rights.


"Paul Yhonquea" wrote:

> In the end, do you want all users to have an M: drive mapped as their home
> folder? If so, it would probably be better to use Active Directory to
> accomplish this (user properties > Profile tab > Home folder section >
> Connect M: To \\ssiatfileprd01\%username%). This way, the folder is created
> as soon as the account is configured in AD. The user will always have that
> account mapped as well, even if the logon script does not run. The logon
> scrip as written can then be used to map other drives besides the home
> folder.
>
> Hope this helps.
>
> Paul Yhonquea
>
>
>
> "chris" <chris@discussions.microsoft.com> wrote in message
> news:8CD42AF7-0DEC-416F-8352-05AD87F15AE0@microsoft.com...
> > Dear All,
> >
> > In summary, how can the login run be execute and when the first time a new
> > user login, the home folder of the user connected to M:\ is created. I
> > only
> > want to use the login.cmd. Thanks
> >
> >
> > Case 2 - Login.cmd
> > net use P: \\ssiatfileprd01\shared
> > net use m: \\ssiatfileprd01\home\%username%
> >
> >
> >
> > Case 1- Login.cmd
> > net use P: \\ssiatfileprd01\shared
> >
> > In user profile m:\ connect \\ssiatfileprd01\home\%username% - The
> > drive
> > also mapped.
> >
> > The issue with this case two is that when user is on wireless, they cannot
> > see the m:\. Only the P:\
> >
> >
> >
> > Case 2 - Login.cmd
> > net use P: \\ssiatfileprd01\shared
> > net use m: \\ssiatfileprd01\home\%username%
> >
> > If I create a new user and assign the login.cmd, the m:\ cannot be mapped
> > to user because the home folder does not exits. If you manually create
> > the
> > folders e and assign permission, then it will mapped or If I create a
> > new
> > user, I put the connect M:\ \\ssiatfileprd01\home\%username% first and
> > once the folder is created, I remove the connect M:\ and the user used
> > only
> > login.cmd and it will work.
> >
> > In this case, after reboot the two drive is there.
> >
> > Just wonder if there is other ways to ensure the login can create the user
> > script automatically.
> >
> >
> >
> >
> > Case 1- Login.cmd
> > net use P: \\ssiatfileprd01\shared
> >
> > In user profile m:\ connect \\ssiatfileprd01\home\%username% - The
> > drive
> > also mapped.
> >
> > The issue with this case two is that when user is on wireless, they cannot
> > see the m:\. Only the P:\
> >
> >
> >
>
>
>
Previous Topic:Serious AD Replciation Problems - Help Needed
Next Topic:Can't authenticate against the same username (identical usernames) in different domains
Goto Forum:
  


Current Time: Wed Jan 17 05:32:33 MST 2018

Total time taken to generate the page: 0.46375 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software