Re: File Server Migration Toolkit

Tech-Archive recommends: Fix windows errors by optimizing your registry

If you are using logon scripts to connect your users to their home folders,
it is just a matter of changing the script. If you are using "Home folder
path" parameters on each user in AD you can use vbscript to change this
setting for all users. Its pretty easy to do, and shouldnt take more than a
couple of seconds, even with a 6000-user base.

best regards
Trond Hindenes
Norway

"Maxim Stepin [MSFT]" <maximst@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:u2RmB%23A7FHA.2092@xxxxxxxxxxxxxxxxxxxxxxx
> FSMT does understand cluster resource optimization and will do it for you
> and will retain original shares names. As correctly noted below you will
> lose individual shares permissions, what can be mitigated by using proper
> NTFS security.
>
> -- Maxim
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Please do not send e-mail directly to this alias. This alias is for
> newsgroup purposes only.
>
> "EDAWG" <EDAWG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:72DFA1AA-9167-42CA-BB9A-74547B117F56@xxxxxxxxxxxxxxxx
>> Sam-
>> Thank you for the advise. Couple of questions. Apologize ahead of time
>> if
>> I seem ignorant. How do I recreate the actual shares on the Powervault?
>> Also, do I need to modify the individual log inscripts to change the home
>> share from \\servername\%username% to \\servername\homes\%username%?
>>
>> Thanks again,
>>
>>
>> "sam_price@xxxxxxxxxxx" wrote:
>>
>>> Hi EDAWG,
>>>
>>> I ran into a similar problem. All you need to do is drop having a
>>> resource
>>> (share) for each folder. You can go from needing 6000 to 1 single
>>> resource
>>> (share). This is loads quicker for starting cluster admin and failover
>>> etc.
>>>
>>> If you're running Win2k clients and up you can map beyond the share name
>>> from login scripts, i.e.
>>>
>>> "net use f: \\servername\homes\%username%" instead of "net use f:
>>> \\servername\%username%"
>>> Note - this doesn't work on 9x/NT4!!! (direct to share mappings
>>> required)
>>>
>>> The cluster resource is the homes folder in this example, and you can
>>> have
>>> your 6000 folders below this.
>>>
>>> You lose share permissions but personally I dont see this as a problem.
>>> NTFS perms can be set to provide adequate file security for most
>>> situations.
>>> You could set NTFS perms on the homes folder for system and domain
>>> admins
>>> only to stop users seeing other users folders.
>>>
>>> If the migration toolkit isn't flexible enough (which in its current
>>> build
>>> is still a bit limited) then standard xcopy with appropriate switches
>>> (acl's
>>> etc) can be used to copy ntfs perms & data (permcopy or equiv for
>>> keeping
>>> shares not required). CACLS can be used to force system perms etc if
>>> anythings missing.
>>>
>>> Hope that helps. I've just starting moving users towards this very
>>> successfully. Unfortunately I still have some NT4 so cant do it across
>>> the
>>> board :(
>>>
>>> regards,
>>>
>>> Sam
>>> "EDAWG" wrote:
>>>
>>> > Hello-
>>> > I have two 1850 PowerEdge servers with 2003 Enterprise installed.
>>> > They are
>>> > setup as a cluster connected to a Powervault 220S. I want to use the
>>> > FSMT to
>>> > migrate roughly 6000 shares from older Windows 2000 boxes to my new
>>> > cluster
>>> > servers, but the FSMT toolkit states I can only create 1674 file share
>>> > resources on the cluster. Is there a way around this?
>>> >
>>> > Thanks,
>
>


.