User Independent Mapped Drive

Currently, I'm managing a network that has (about) 5 different
physical locations. The network has been configured as one giant
domain. Most users stay at one specific office, but there are times
when a user from one location will be sent to a different location for
coverage purposes.

Each location has it's own OU in AD. Right now, we have a GPO for each
OU that runs a batch file (when the user logs on) to map the drives.
The problem is that when a user goes to a different office, they need
to map to the server of the office they're currently in and NOT the
server of where they're from.

Moving the Users from one OU to another isn't feasible, as the company
(in the future) would like to be able to have a user visit several
different offices a day without having to call support to change their
mappings.

A quick work around we've been using is put a batch file in the
startup folder of each PC (so no matter who logs on the mappings are
correct), but I know that this is not a long term solution.

I have tried putting the batch file to map the drives as a startup
script (vs. a login script which is based on user and not PC), but the
script doesn't map the drives.


So at this point I'm stumped. The short summary of what I'm trying to
do is create a script (or batch file) that will always map the same
drives base on computer location and not user location via the server.


Thanks!

Hello (E-Mail Removed),

Check out Distributed file systems:
http://www.microsoft.com/windowsserv...s/default.mspx


Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Currently, I'm managing a network that has (about) 5 different
> physical locations. The network has been configured as one giant
> domain. Most users stay at one specific office, but there are times
> when a user from one location will be sent to a different location for
> coverage purposes.
>
> Each location has it's own OU in AD. Right now, we have a GPO for each
> OU that runs a batch file (when the user logs on) to map the drives.
> The problem is that when a user goes to a different office, they need
> to map to the server of the office they're currently in and NOT the
> server of where they're from.
>
> Moving the Users from one OU to another isn't feasible, as the company
> (in the future) would like to be able to have a user visit several
> different offices a day without having to call support to change their
> mappings.
>
> A quick work around we've been using is put a batch file in the
> startup folder of each PC (so no matter who logs on the mappings are
> correct), but I know that this is not a long term solution.
>
> I have tried putting the batch file to map the drives as a startup
> script (vs. a login script which is based on user and not PC), but the
> script doesn't map the drives.
>
> So at this point I'm stumped. The short summary of what I'm trying to
> do is create a script (or batch file) that will always map the same
> drives base on computer location and not user location via the server.
>
> Thanks!
>

hi,
try to put the logon script on the site if you have defined the sites, not
on the OU. in that case when the user will move from one site to another will
have different logon scripts.
--
Dragos CAMARA
MCSA Windows 2003 server


"(E-Mail Removed)" wrote:

> Currently, I'm managing a network that has (about) 5 different
> physical locations. The network has been configured as one giant
> domain. Most users stay at one specific office, but there are times
> when a user from one location will be sent to a different location for
> coverage purposes.
>
> Each location has it's own OU in AD. Right now, we have a GPO for each
> OU that runs a batch file (when the user logs on) to map the drives.
> The problem is that when a user goes to a different office, they need
> to map to the server of the office they're currently in and NOT the
> server of where they're from.
>
> Moving the Users from one OU to another isn't feasible, as the company
> (in the future) would like to be able to have a user visit several
> different offices a day without having to call support to change their
> mappings.
>
> A quick work around we've been using is put a batch file in the
> startup folder of each PC (so no matter who logs on the mappings are
> correct), but I know that this is not a long term solution.
>
> I have tried putting the batch file to map the drives as a startup
> script (vs. a login script which is based on user and not PC), but the
> script doesn't map the drives.
>
>
> So at this point I'm stumped. The short summary of what I'm trying to
> do is create a script (or batch file) that will always map the same
> drives base on computer location and not user location via the server.
>
>
> Thanks!
>
>

MyWeb:

No good. Each branch has it's own location specific data. DFS would
not work in this situation.


On Jun 28, 5:10 pm, Myweb <mei...@gmx.de> wrote:
> Hello hallen.eagle...@gmail.com,
>
> Check out Distributed file systems:http://www.microsoft.com/windowsserv.../storage/dfs/d...
>
> Best regards
>
> Myweb
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > Currently, I'm managing a network that has (about) 5 different
> > physical locations. The network has been configured as one giant
> > domain. Most users stay at one specific office, but there are times
> > when a user from one location will be sent to a different location for
> > coverage purposes.
>
> > Each location has it's own OU in AD. Right now, we have a GPO for each
> > OU that runs a batch file (when the user logs on) to map the drives.
> > The problem is that when a user goes to a different office, they need
> > to map to the server of the office they're currently in and NOT the
> > server of where they're from.
>
> > Moving the Users from one OU to another isn't feasible, as the company
> > (in the future) would like to be able to have a user visit several
> > different offices a day without having to call support to change their
> > mappings.
>
> > A quick work around we've been using is put a batch file in the
> > startup folder of each PC (so no matter who logs on the mappings are
> > correct), but I know that this is not a long term solution.
>
> > I have tried putting the batch file to map the drives as a startup
> > script (vs. a login script which is based on user and not PC), but the
> > script doesn't map the drives.
>
> > So at this point I'm stumped. The short summary of what I'm trying to
> > do is create a script (or batch file) that will always map the same
> > drives base on computer location and not user location via the server.
>
> > Thanks!

I don't believe that sites have been defined, where would I check to
see?

The most I know is that each location has it's own OU in the Group
Policy.


Thanks!

On Jun 29, 9:26 am, Dragos CAMARA <drago...@remove-this.hotmail.com>
wrote:
> hi,
> try to put the logon script on the site if you have defined the sites, not
> on the OU. in that case when the user will move from one site to another will
> have different logon scripts.
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
> "hallen.eagle...@gmail.com" wrote:
> > Currently, I'm managing a network that has (about) 5 different
> > physical locations. The network has been configured as one giant
> > domain. Most users stay at one specific office, but there are times
> > when a user from one location will be sent to a different location for
> > coverage purposes.
>
> > Each location has it's own OU in AD. Right now, we have a GPO for each
> > OU that runs a batch file (when the user logs on) to map the drives.
> > The problem is that when a user goes to a different office, they need
> > to map to the server of the office they're currently in and NOT the
> > server of where they're from.
>
> > Moving the Users from one OU to another isn't feasible, as the company
> > (in the future) would like to be able to have a user visit several
> > different offices a day without having to call support to change their
> > mappings.
>
> > A quick work around we've been using is put a batch file in the
> > startup folder of each PC (so no matter who logs on the mappings are
> > correct), but I know that this is not a long term solution.
>
> > I have tried putting the batch file to map the drives as a startup
> > script (vs. a login script which is based on user and not PC), but the
> > script doesn't map the drives.
>
> > So at this point I'm stumped. The short summary of what I'm trying to
> > do is create a script (or batch file) that will always map the same
> > drives base on computer location and not user location via the server.
>
> > Thanks!

hi,
go to site and services and see the sites defined.
--
Dragos CAMARA
MCSA Windows 2003 server


"(E-Mail Removed)" wrote:

> I don't believe that sites have been defined, where would I check to
> see?
>
> The most I know is that each location has it's own OU in the Group
> Policy.
>
>
> Thanks!
>
> On Jun 29, 9:26 am, Dragos CAMARA <drago...@remove-this.hotmail.com>
> wrote:
> > hi,
> > try to put the logon script on the site if you have defined the sites, not
> > on the OU. in that case when the user will move from one site to another will
> > have different logon scripts.
> > --
> > Dragos CAMARA
> > MCSA Windows 2003 server
> >
> > "hallen.eagle...@gmail.com" wrote:
> > > Currently, I'm managing a network that has (about) 5 different
> > > physical locations. The network has been configured as one giant
> > > domain. Most users stay at one specific office, but there are times
> > > when a user from one location will be sent to a different location for
> > > coverage purposes.
> >
> > > Each location has it's own OU in AD. Right now, we have a GPO for each
> > > OU that runs a batch file (when the user logs on) to map the drives.
> > > The problem is that when a user goes to a different office, they need
> > > to map to the server of the office they're currently in and NOT the
> > > server of where they're from.
> >
> > > Moving the Users from one OU to another isn't feasible, as the company
> > > (in the future) would like to be able to have a user visit several
> > > different offices a day without having to call support to change their
> > > mappings.
> >
> > > A quick work around we've been using is put a batch file in the
> > > startup folder of each PC (so no matter who logs on the mappings are
> > > correct), but I know that this is not a long term solution.
> >
> > > I have tried putting the batch file to map the drives as a startup
> > > script (vs. a login script which is based on user and not PC), but the
> > > script doesn't map the drives.
> >
> > > So at this point I'm stumped. The short summary of what I'm trying to
> > > do is create a script (or batch file) that will always map the same
> > > drives base on computer location and not user location via the server.
> >
> > > Thanks!
>
>
>

Yes, the sites are defined. Where do I add the batch file to run in
sites and services?


On Jun 30, 12:28 am, Dragos CAMARA <drago...@remove-this.hotmail.com>
wrote:
> hi,
> go to site and services and see the sites defined.
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
> "hallen.eagle...@gmail.com" wrote:
> > I don't believe that sites have been defined, where would I check to
> > see?
>
> > The most I know is that each location has it's own OU in the Group
> > Policy.
>
> > Thanks!
>
> > On Jun 29, 9:26 am, Dragos CAMARA <drago...@remove-this.hotmail.com>
> > wrote:
> > > hi,
> > > try to put the logon script on the site if you have defined the sites, not
> > > on the OU. in that case when the user will move from one site to another will
> > > have different logon scripts.
> > > --
> > > Dragos CAMARA
> > > MCSA Windows 2003 server
>
> > > "hallen.eagle...@gmail.com" wrote:
> > > > Currently, I'm managing a network that has (about) 5 different
> > > > physical locations. The network has been configured as one giant
> > > > domain. Most users stay at one specific office, but there are times
> > > > when a user from one location will be sent to a different location for
> > > > coverage purposes.
>
> > > > Each location has it's own OU in AD. Right now, we have a GPO for each
> > > > OU that runs a batch file (when the user logs on) to map the drives.
> > > > The problem is that when a user goes to a different office, they need
> > > > to map to the server of the office they're currently in and NOT the
> > > > server of where they're from.
>
> > > > Moving the Users from one OU to another isn't feasible, as the company
> > > > (in the future) would like to be able to have a user visit several
> > > > different offices a day without having to call support to change their
> > > > mappings.
>
> > > > A quick work around we've been using is put a batch file in the
> > > > startup folder of each PC (so no matter who logs on the mappings are
> > > > correct), but I know that this is not a long term solution.
>
> > > > I have tried putting the batch file to map the drives as a startup
> > > > script (vs. a login script which is based on user and not PC), but the
> > > > script doesn't map the drives.
>
> > > > So at this point I'm stumped. The short summary of what I'm trying to
> > > > do is create a script (or batch file) that will always map the same
> > > > drives base on computer location and not user location via the server.
>
> > > > Thanks!

bump

On Jul 5, 9:07 am, hallen.eagle...@gmail.com wrote:
> Yes, the sites are defined. Where do I add the batch file to run in
> sites and services?
>
> On Jun 30, 12:28 am, Dragos CAMARA <drago...@remove-this.hotmail.com>
> wrote:
>
> > hi,
> > go to site and services and see the sites defined.
> > --
> > Dragos CAMARA
> > MCSA Windows 2003 server
>
> > "hallen.eagle...@gmail.com" wrote:
> > > I don't believe that sites have been defined, where would I check to
> > > see?
>
> > > The most I know is that each location has it's own OU in the Group
> > > Policy.
>
> > > Thanks!
>
> > > On Jun 29, 9:26 am, Dragos CAMARA <drago...@remove-this.hotmail.com>
> > > wrote:
> > > > hi,
> > > > try to put the logon script on the site if you have defined the sites, not
> > > > on the OU. in that case when the user will move from one site to another will
> > > > have different logon scripts.
> > > > --
> > > > Dragos CAMARA
> > > > MCSA Windows 2003 server
>
> > > > "hallen.eagle...@gmail.com" wrote:
> > > > > Currently, I'm managing a network that has (about) 5 different
> > > > > physical locations. The network has been configured as one giant
> > > > > domain. Most users stay at one specific office, but there are times
> > > > > when a user from one location will be sent to a different location for
> > > > > coverage purposes.
>
> > > > > Each location has it's own OU in AD. Right now, we have a GPO for each
> > > > > OU that runs a batch file (when the user logs on) to map the drives.
> > > > > The problem is that when a user goes to a different office, they need
> > > > > to map to the server of the office they're currently in and NOT the
> > > > > server of where they're from.
>
> > > > > Moving the Users from one OU to another isn't feasible, as the company
> > > > > (in the future) would like to be able to have a user visit several
> > > > > different offices a day without having to call support to change their
> > > > > mappings.
>
> > > > > A quick work around we've been using is put a batch file in the
> > > > > startup folder of each PC (so no matter who logs on the mappings are
> > > > > correct), but I know that this is not a long term solution.
>
> > > > > I have tried putting the batch file to map the drives as a startup
> > > > > script (vs. a login script which is based on user and not PC), but the
> > > > > script doesn't map the drives.
>
> > > > > So at this point I'm stumped. The short summary of what I'm trying to
> > > > > do is create a script (or batch file) that will always map the same
> > > > > drives base on computer location and not user location via the server.
>
> > > > > Thanks!