Sorry to appear stupid(too late), but I have a question about the M: drive on exchange 2000... I guess that this is some sort of virtual or logical drive created by EX2K... My question is this...EX2K is installed and running...We have a logon script that maps a shared folder on our File server to drive M: ... I also noticed that there is an Exchange O:drive with the domain name and sub folders: MBX,and Public...Is this my M:drive? Is this OK ?
Hi, It is possible to map the exchange virtual drive to another drive letter which must be what happened in your case. You should be able to see the choosen drive letter in this key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EXIFS\Parameters\Drive Letter A safer idea would be to hide the drive completely - see http://support.microsoft.com/default.aspx?scid=kb;en-us;305145&Product=exch2k I have had a client that also used a logon script on an exchange server to map the M drive to another server. This meant that the databases became corrupted and had to be repaired. Leif skrev i en meddelelse news:1123190461.253560.186000@g44g2000cwa.googlegroups.com... > Sorry to appear stupid(too late), but I have a question about the M: > drive on exchange 2000... I guess that this is some sort of virtual or > logical drive created by EX2K... My question is this...EX2K is > installed and running...We have a logon script that maps a shared > folder on our File server to drive M: ... I also noticed that there is > an Exchange O:drive with the domain name and sub folders: MBX,and > Public...Is this my M:drive? Is this OK ? >
In news:1123190461.253560.186000@g44g2000cwa.googlegroups.com, rpainter@randalllamb.com typed: > Sorry to appear stupid(too late), but I have a question about the M: > drive on exchange 2000... I guess that this is some sort of virtual or > logical drive created by EX2K... My question is this...EX2K is > installed and running...We have a logon script that maps a shared > folder on our File server to drive M: ... I also noticed that there is > an Exchange O:drive with the domain name and sub folders: MBX,and > Public...Is this my M:drive? Is this OK ? In addition to Leif's reply: You shouldn't map the M drive for users, and you shouldn't run login scripts on your server (at least, there should be no need to). I don't know where O came from, but it didn't show up on its own.....
wrote in message news:1123190461.253560.186000@g44g2000cwa.googlegroups.com... > Sorry to appear stupid(too late), but I have a question about the M: > drive on exchange 2000... I guess that this is some sort of virtual or > logical drive created by EX2K... My question is this...EX2K is > installed and running...We have a logon script that maps a shared > folder on our File server to drive M: ... I also noticed that there is > an Exchange O:drive with the domain name and sub folders: MBX,and > Public...Is this my M:drive? Is this OK ? I seem to recall that if a drive letter for M: exists at the time of Exchange 2K installation, the virtual drive will get the next available letter. If this is what happened, then drives M: and N: were already in use as either mapped or local drives, so the installation set up O: as the virtual drive. todd
