Re: File Server Migration: W2K to WSS2K3
- From: "Alice" <alice@xxxxxxxxxxxxx>
- Date: Mon, 11 Apr 2005 12:42:43 -0400
Thanks for the reply. We've Active Directory deployed and will be utilizing
group policy and login scripts to update the mapped drives that users are
using to connect to the file server. However, we've a significant amount of
users/applications that are using UNCs + share names to locate the file
server that we can't really track down & update them remotely. I like your
suggestion for installing a DFS tree on the W2K file server, but since there
are a high number of shares (DFS was not being used before), we can only
maintain one share name on that server that points to the migrated volume on
the WSS2K3 server.
Another option that we were considering was to create multiple DFS roots on
the original file server, which is a Windows 2000 server, to represent the
original UNC + share names that users are using to access. However, since
only Windows Server 2003 Enterprise & Datacenter Editions support multiple
DFS roots, we'll have to upgrade the OS from Windows 2000 to Windows Server
2003 Enterprise. But because our Exchange 5.5 also resides on the Windows
2000 server and Microsoft does not support Exchange 5.5 on Windows Server
2003 OS, that option seems impossible. One of the reasons (that we've
heard) why Exchange 5.5 is not supported on a WS2K3 machines is because it
doesn't recognize VSS. Even if we've VSS disabled, I've learned that there
are other issues that will cause problems ?!
Any additional insights would be appreciated!
Alice
"Olaf Engelke [MVP]" <oenews01@xxxxxxxx> wrote in message
news:e3Fhd8APFHA.2532@xxxxxxxxxxxxxxxxxxxxxxx
> Hello Alice,
> Alice wrote:
>> We've recently purchased a Windows Storage Server 2003 and in the
>> process of migrating our primary file server, Windows 2000, to the
>> new server. One problem that we've encountered is not being able to
>> maintain the directory paths (UNC) and share names that users are
>> currently using after the file volume is migrated from W2K to WSS2K3
>> server.
>
> this is one of the purposes to use login scripts with drive mappings to
> shares and printer assignments.
> Which machine is the Domain controller for you Active Directory? Or don't
> you even use Active Directory?
>
>> Our biggest constraint is that our current Exchange 5.5
>> application is installed on the same machine as our file server.
>> Therefore, we cannot rename the original server and utilize the DFS
>> root consolidation scheme from FSMT (renaming the server that
>> Exchange 5.5 resides, based on our initial research, will cause problems
>> to
>> how users connect to Exchange 5.5). We also looked at workarounds
>> like creating mount points or junction points with shares on the
>> original W2K server, but those utilities (mountvol, fsutil, or linkd)
>> only work with local NTFS volumes, not even mapped drive. Does anyone
>> has any insight/suggestions as to how we can approach the problem?
>
> DFS can be taken from two sides, so you can have sitting your DFS root on
> the original server and have the shares within on the Storage Server
> linked to it. But the details (and your workload) depend from more details
> than you just described here. And don't forget - the users are able to
> learn, especially if you can tell them, that there are technical
> requirements (what you can with the new storage device in the background)
> to change some configurations.
>
> Best greetings from Germany
> Olaf
>
>
>
.
- References:
- File Server Migration: W2K to WSS2K3
- From: Alice
- Re: File Server Migration: W2K to WSS2K3
- From: Olaf Engelke [MVP]
- File Server Migration: W2K to WSS2K3
- Prev by Date: ADMT - password questions
- Next by Date: Re: DNS Name Convention or Spaces
- Previous by thread: Re: File Server Migration: W2K to WSS2K3
- Next by thread: Migrating from NT to 2003
- Index(es):
Relevant Pages
|
