Highlighted
tvandael Absent Member.
Absent Member.
3744 views

Need help with file server migration... From NW to MS :-)

Hello all,

we are currently looking for a way to migrate our user data from our Netware server to a 2008R2 server.
So far everything is running fine, except one thing... the login script...
I wrote some powershell script to migrate all the data and set the rights, so far no problem.
But when the data is migrated, the user has to have a new mapping to that folder.
For now we only use novell login scripts 'MAP ROOT H:=SERVERNAME/DATA:/users/%CN'
I also created a windows logon-script that maps the H: to the MS server
'net use h:\ \\servername\users\%username%'

For some reason, the windows logon-script is not executed at logon.
Has any of you guys a good ieda on how to make the data migration easy?
A big-bang migration is not something we want to do.

Thnx!

Tim
Labels (1)
0 Likes
7 Replies
Micro Focus Expert
Micro Focus Expert

Re: Need help with file server migration... From NW to MS :-)

Make sure Client32 is fully patched.
I recalled an issue about that, but dont recall which patch fixed it.

On 2/17/2011 10:36 AM, tvandael wrote:
>
> Hello all,
>
> we are currently looking for a way to migrate our user data from our
> Netware server to a 2008R2 server.
> So far everything is running fine, except one thing... the login
> script...
> I wrote some powershell script to migrate all the data and set the
> rights, so far no problem.
> But when the data is migrated, the user has to have a new mapping to
> that folder.
> For now we only use novell login scripts 'MAP ROOT
> H:=SERVERNAME/DATA:/users/%CN'
> I also created a windows logon-script that maps the H: to the MS
> server
> 'net use h:\ \\servername\users\%username%'
>
> For some reason, the windows logon-script is not executed at logon.
> Has any of you guys a good ieda on how to make the data migration
> easy?
> A big-bang migration is not something we want to do.
>
> Thnx!
>
> Tim
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Need help with file server migration... From NW to MS :-)

For starter remove the \ from h:\

On 2/17/11 10:36 AM, tvandael wrote:
>
> Hello all,
>
> we are currently looking for a way to migrate our user data from our
> Netware server to a 2008R2 server.
> So far everything is running fine, except one thing... the login
> script...
> I wrote some powershell script to migrate all the data and set the
> rights, so far no problem.
> But when the data is migrated, the user has to have a new mapping to
> that folder.
> For now we only use novell login scripts 'MAP ROOT
> H:=SERVERNAME/DATA:/users/%CN'
> I also created a windows logon-script that maps the H: to the MS
> server
> 'net use h:\ \\servername\users\%username%'
>
> For some reason, the windows logon-script is not executed at logon.
> Has any of you guys a good ieda on how to make the data migration
> easy?
> A big-bang migration is not something we want to do.
>
> Thnx!
>
> Tim
>
>


--
--
tBM 🙂
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Need help with file server migration... From NW to MS :-)

I would be interested in your pwershell script, I am right in the middle
of an NDS to AD migration.


On 2/17/2011 7:36 AM, tvandael wrote:
>
> Hello all,
>
> we are currently looking for a way to migrate our user data from our
> Netware server to a 2008R2 server.
> So far everything is running fine, except one thing... the login
> script...
> I wrote some powershell script to migrate all the data and set the
> rights, so far no problem.
> But when the data is migrated, the user has to have a new mapping to
> that folder.
> For now we only use novell login scripts 'MAP ROOT
> H:=SERVERNAME/DATA:/users/%CN'
> I also created a windows logon-script that maps the H: to the MS
> server
> 'net use h:\ \\servername\users\%username%'
>
> For some reason, the windows logon-script is not executed at logon.
> Has any of you guys a good ieda on how to make the data migration
> easy?
> A big-bang migration is not something we want to do.
>
> Thnx!
>
> Tim
>
>


0 Likes
tvandael Absent Member.
Absent Member.

Re: Need help with file server migration... From NW to MS :-

craig_wilson;2076649 wrote:
Make sure Client32 is fully patched.
I recalled an issue about that, but dont recall which patch fixed it.

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


So the normal behavior would be that the windows net use has the upper hand over Novell's MAP command?

Thnx!

Tim
0 Likes
tvandael Absent Member.
Absent Member.

Re: Need help with file server migration... From NW to MS :-

tBM;2076697 wrote:
For starter remove the \ from h:\
--
--
tBM 🙂


This is so in my script, this is a typo 🙂

Thnx!
0 Likes
tvandael Absent Member.
Absent Member.

Re: Need help with file server migration... From NW to MS :-

Mr. Beer;2076793 wrote:
I would be interested in your pwershell script, I am right in the middle
of an NDS to AD migration.


$username = "XXX"
Echo "--- Start $username ---"
$directory = "\\Windows-server\d$\users\$username"
New-Item $directory –Type Directory
sleep 2
echo "Directory Created"
#Get-Acl $directory | Format-List
$acl = Get-Acl $directory
$acl.SetAccessRuleProtection($True, $False)
sleep 1
echo "Inheritance Disabled"
$identityAdd = "NT AUTHORITY\SYSTEM"
$rightsAdd = "FullControl"
$InheritanceAdd = "ContainerInherit, ObjectInherit"
$PropagationAdd = "None"
$TypeAdd = "Allow"
$rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
$acl.SetAccessRule($rule2add)
SLEEP 1
echo "SYSTEM FullControl"
$identityAdd = "DOMAIN\Domain Admins"
$rightsAdd = "FullControl"
$InheritanceAdd = "ContainerInherit, ObjectInherit"
$PropagationAdd = "None"
$TypeAdd = "Allow"
$rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
$acl.SetAccessRule($rule2add)
SLEEP 1
echo "Domain Admins FullControl"
$identityAdd = "DOMAIN\GL_FileServerAdmins"
$rightsAdd = "FullControl"
$InheritanceAdd = "ContainerInherit, ObjectInherit"
$PropagationAdd = "None"
$TypeAdd = "Allow"
$rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
$acl.SetAccessRule($rule2add)
SLEEP 1
echo "FileServerAdmins FullControl"
$identityAdd = "DOMAIN\$username"
$rightsAdd = "Modify", "Synchronize"
$InheritanceAdd = "ContainerInherit, ObjectInherit"
$PropagationAdd = "None"
$TypeAdd = "Allow"
$rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
$acl.SetAccessRule($rule2add)
SLEEP 1
echo "$username Modify"
Set-Acl $directory $acl
echo "Rights Set"
#Get-Acl $directory | Format-List
New-Item \\NetwareServer\data\users\$username\MIGRATED.txt -ItemType file
echo "Create MIGRATED file H"
New-Item \\NetwareServer\data\users_reserve\$username\MIGRATED.txt -ItemType file
echo "Create MIGRATED file R"
# psexec has to be in c:\
Invoke-Expression "c:\psexec \\WindowsServer dirquota quota modify /path:d:\users\$username /status:disabled"
echo "Disabled Quota"
Invoke-Expression "mkdir \\WindowsServer\d$\users\$username\USERS_RESERVE"
echo "Create USERS_RESERVE directory"
# robocopy has to be in c:\
Invoke-Expression "c:\robocopy \\NetwareServer\data\users\$username\ \\WindowsServer\d$\users\$username /MOVE /E /Z /R:10 /XF MIGRATED.txt /TEE /LOG+:'C:\RoboCopyHLogFile$username.txt'"
echo "RoboCopy H files"
# robocopy has to be in c:\
Invoke-Expression "c:\robocopy \\NetwareServer\data\users_reserve\$username\ \\WindowsServer\d$\users\$username\USERS_RESERVE /MOVE /E /Z /R:10 /XF MIGRATED.txt /TEE /LOG+:'C:\RoboCopyRLogFile$username.txt'"
echo "RoboCopy R files"
# psexec has to be in c:\
Invoke-Expression "c:\psexec \\WindowsServer dirquota quota modify /path:d:\users\$username /status:enabled"
echo "Enabled Quota"
Echo "--- Finished $username ---"


I trimmed the servernames and some stuff out but this should do your trick 🙂
Hope it helps you...

Greetz

Tim
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Need help with file server migration... From NW to MS :-)

Thank you very much.

On 2/20/2011 10:36 AM, tvandael wrote:
>
> Mr. Beer;2076793 Wrote:
>> I would be interested in your pwershell script, I am right in the
>> middle
>> of an NDS to AD migration.
>>

>
>
> Code:
> --------------------
> $username = "XXX"
> Echo "--- Start $username ---"
> $directory = "\\Windows-server\d$\users\$username"
> New-Item $directory –Type Directory
> sleep 2
> echo "Directory Created"
> #Get-Acl $directory | Format-List
> $acl = Get-Acl $directory
> $acl.SetAccessRuleProtection($True, $False)
> sleep 1
> echo "Inheritance Disabled"
> $identityAdd = "NT AUTHORITY\SYSTEM"
> $rightsAdd = "FullControl"
> $InheritanceAdd = "ContainerInherit, ObjectInherit"
> $PropagationAdd = "None"
> $TypeAdd = "Allow"
> $rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
> $acl.SetAccessRule($rule2add)
> SLEEP 1
> echo "SYSTEM FullControl"
> $identityAdd = "DOMAIN\Domain Admins"
> $rightsAdd = "FullControl"
> $InheritanceAdd = "ContainerInherit, ObjectInherit"
> $PropagationAdd = "None"
> $TypeAdd = "Allow"
> $rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
> $acl.SetAccessRule($rule2add)
> SLEEP 1
> echo "Domain Admins FullControl"
> $identityAdd = "DOMAIN\GL_FileServerAdmins"
> $rightsAdd = "FullControl"
> $InheritanceAdd = "ContainerInherit, ObjectInherit"
> $PropagationAdd = "None"
> $TypeAdd = "Allow"
> $rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
> $acl.SetAccessRule($rule2add)
> SLEEP 1
> echo "FileServerAdmins FullControl"
> $identityAdd = "DOMAIN\$username"
> $rightsAdd = "Modify", "Synchronize"
> $InheritanceAdd = "ContainerInherit, ObjectInherit"
> $PropagationAdd = "None"
> $TypeAdd = "Allow"
> $rule2add = New-Object System.Security.AccessControl.FileSystemAccessRule($identityAdd ,$rightsAdd ,$inheritanceAdd, $propagationAdd, $typeAdd)
> $acl.SetAccessRule($rule2add)
> SLEEP 1
> echo "$username Modify"
> Set-Acl $directory $acl
> echo "Rights Set"
> #Get-Acl $directory | Format-List
> New-Item \\NetwareServer\data\users\$username\MIGRATED.txt -ItemType file
> echo "Create MIGRATED file H"
> New-Item \\NetwareServer\data\users_reserve\$username\MIGRATED.txt -ItemType file
> echo "Create MIGRATED file R"
> # psexec has to be in c:\
> Invoke-Expression "c:\psexec \\WindowsServer dirquota quota modify /path:d:\users\$username /status:disabled"
> echo "Disabled Quota"
> Invoke-Expression "mkdir \\WindowsServer\d$\users\$username\USERS_RESERVE"
> echo "Create USERS_RESERVE directory"
> # robocopy has to be in c:\
> Invoke-Expression "c:\robocopy \\NetwareServer\data\users\$username\ \\WindowsServer\d$\users\$username /MOVE /E /Z /R:10 /XF MIGRATED.txt /TEE /LOG+:'C:\RoboCopyHLogFile$username.txt'"
> echo "RoboCopy H files"
> # robocopy has to be in c:\
> Invoke-Expression "c:\robocopy \\NetwareServer\data\users_reserve\$username\ \\WindowsServer\d$\users\$username\USERS_RESERVE /MOVE /E /Z /R:10 /XF MIGRATED.txt /TEE /LOG+:'C:\RoboCopyRLogFile$username.txt'"
> echo "RoboCopy R files"
> # psexec has to be in c:\
> Invoke-Expression "c:\psexec \\WindowsServer dirquota quota modify /path:d:\users\$username /status:enabled"
> echo "Enabled Quota"
> Echo "--- Finished $username ---"
> --------------------
>
>
> I trimmed the servernames and some stuff out but this should do your
> trick 🙂
> Hope it helps you...
>
> Greetz
>
> Tim
>
>


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.