Moving Drive Map role

Hi there,

Have question regarding Drive Mapping on Windows 2000 Server. We have one
box which is mainly acting as a Drive Map to one of the drives in SAN.

Domain users use this server to connect to the shared drive and map it as
driver letter "L:" . most of them have it set to Auto Reconnect (around 2500
users).

What we are planning to do is to virtualize this server on Windows 2003
Server.

What we did is built, a new virtual server / gave it same name+IP.
2. Disconnected the existing server from network.
3. Brought this new server online and confirmed that it was all connected etc.
4. Started one of the XP machines to see if the drive mapping workis or not
but it didn't.
5. Cleared DNS cache / did IP Config / release / renew but no luck..



Can some one tell what should be correct method of doing this? as the above
isn't working for us.

Thanks in advance.

 

Wanted to clear some thing....

The new server had new IP address but same HostName as the old one.

1 out of 10 XP workstations was able to gain access to the Mappes drive but
all the rest were out of luck.

Error = Connection lost.

"Imran Ali" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi there,
>
> Have question regarding Drive Mapping on Windows 2000 Server. We have one
> box which is mainly acting as a Drive Map to one of the drives in SAN.
>
> Domain users use this server to connect to the shared drive and map it as
> driver letter "L:" . most of them have it set to Auto Reconnect (around 2500
> users).
>
> What we are planning to do is to virtualize this server on Windows 2003
> Server.
>
> What we did is built, a new virtual server / gave it same name+IP.
> 2. Disconnected the existing server from network.
> 3. Brought this new server online and confirmed that it was all connected etc.
> 4. Started one of the XP machines to see if the drive mapping workis or not
> but it didn't.
> 5. Cleared DNS cache / did IP Config / release / renew but no luck..
>
>
>
> Can some one tell what should be correct method of doing this? as the above
> isn't working for us.
>
> Thanks in advance.
> <!--colorc--><!--/colorc-->

 

"Imran Ali" <Imran Ali@discussions.microsoft.com> wrote in message
news:9030DEA5-2639-4230-AB2C-CD6EF8141685@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Hi there,
>
> Have question regarding Drive Mapping on Windows 2000 Server. We have one
> box which is mainly acting as a Drive Map to one of the drives in SAN.
>
> Domain users use this server to connect to the shared drive and map it as
> driver letter "L:" . most of them have it set to Auto Reconnect (around
> 2500
> users).
>
> What we are planning to do is to virtualize this server on Windows 2003
> Server.
>
> What we did is built, a new virtual server / gave it same name+IP.
> 2. Disconnected the existing server from network.
> 3. Brought this new server online and confirmed that it was all connected
> etc.
> 4. Started one of the XP machines to see if the drive mapping workis or
> not
> but it didn't.
> 5. Cleared DNS cache / did IP Config / release / renew but no luck..
>
>
>
> Can some one tell what should be correct method of doing this? as the
> above
> isn't working for us.
>
> Thanks in advance.
><!--colorc--><!--/colorc-->

Using "Auto Reconnect" for 2,500 users is in my humble opinion totally
misplaced. If you want a robust and stable operation then you must map your
shared resources via your logon script or via Group Policy. When you do it
like this then you can make any modification centrally and people will see
the change immediately when they log on.

 

Thanks for your quick reply.

There are almost 5000 domain and 2500 out of them are using this shared
server as "L:" and others are using it as different drive letters. Its hard
to group them and then apply the policy or logon script.



"Pegasus [MVP]" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
>
> "Imran Ali" <Imran Ali@discussions.microsoft.com> wrote in message
> news:9030DEA5-2639-4230-AB2C-CD6EF8141685@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
> > Hi there,
> >
> > Have question regarding Drive Mapping on Windows 2000 Server. We have one
> > box which is mainly acting as a Drive Map to one of the drives in SAN.
> >
> > Domain users use this server to connect to the shared drive and map it as
> > driver letter "L:" . most of them have it set to Auto Reconnect (around
> > 2500
> > users).
> >
> > What we are planning to do is to virtualize this server on Windows 2003
> > Server.
> >
> > What we did is built, a new virtual server / gave it same name+IP.
> > 2. Disconnected the existing server from network.
> > 3. Brought this new server online and confirmed that it was all connected
> > etc.
> > 4. Started one of the XP machines to see if the drive mapping workis or
> > not
> > but it didn't.
> > 5. Cleared DNS cache / did IP Config / release / renew but no luck..
> >
> >
> >
> > Can some one tell what should be correct method of doing this? as the
> > above
> > isn't working for us.
> >
> > Thanks in advance.
> ><!--colorc--><!--/colorc-->
>
> Using "Auto Reconnect" for 2,500 users is in my humble opinion totally
> misplaced. If you want a robust and stable operation then you must map your
> shared resources via your logon script or via Group Policy. When you do it
> like this then you can make any modification centrally and people will see
> the change immediately when they log on.
>
>
> <!--colorc--><!--/colorc-->

 

KIX is a good scripting language for this. In my old job we have 5000+ users
who required access to different shared folders on a very granular level. We
wrote a KIX script to map drive letters based on AD group membership. That
way if a group membership was changed the drive mappings updated at next
logon automatically - very admin friendly.

"Imran Ali" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> Thanks for your quick reply.
>
> There are almost 5000 domain and 2500 out of them are using this shared
> server as "L:" and others are using it as different drive letters. Its hard
> to group them and then apply the policy or logon script.
>
>
>
> "Pegasus [MVP]" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> >
> > "Imran Ali" <Imran Ali@discussions.microsoft.com> wrote in message
> > news:9030DEA5-2639-4230-AB2C-CD6EF8141685@microsoft.com...<!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > Hi there,
> > >
> > > Have question regarding Drive Mapping on Windows 2000 Server. We have one
> > > box which is mainly acting as a Drive Map to one of the drives in SAN.
> > >
> > > Domain users use this server to connect to the shared drive and map it as
> > > driver letter "L:" . most of them have it set to Auto Reconnect (around
> > > 2500
> > > users).
> > >
> > > What we are planning to do is to virtualize this server on Windows 2003
> > > Server.
> > >
> > > What we did is built, a new virtual server / gave it same name+IP.
> > > 2. Disconnected the existing server from network.
> > > 3. Brought this new server online and confirmed that it was all connected
> > > etc.
> > > 4. Started one of the XP machines to see if the drive mapping workis or
> > > not
> > > but it didn't.
> > > 5. Cleared DNS cache / did IP Config / release / renew but no luck..
> > >
> > >
> > >
> > > Can some one tell what should be correct method of doing this? as the
> > > above
> > > isn't working for us.
> > >
> > > Thanks in advance.
> > ><!--colorc--><!--/colorc-->
> >
> > Using "Auto Reconnect" for 2,500 users is in my humble opinion totally
> > misplaced. If you want a robust and stable operation then you must map your
> > shared resources via your logon script or via Group Policy. When you do it
> > like this then you can make any modification centrally and people will see
> > the change immediately when they log on.
> >
> >
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->