RE: Problems after migrating from Novell 5.1 to Windows Server 200

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Do you have any idea of why, after migrating, when I log into the computer, I
do not see the users profile? Is there a way I can manually link the domain
profile with the local profile?

"Frances [MSFT]" wrote:

> Hello Rashan,
>
> Good to hear from you.
>
> According to the message, I understand that you use Quest software to
> migrate Novell 5.1 to win2k3 domain. Now you find that users cannot logon
> to the machines. Is this correct?
>
> Since you are using Quest to perform the migration task, we don't support
> this in your scenario. Please understand that we lack the related resources
> regarding Quest, and are not sure whether Quest is the cause of this issue.
> I suggest that you contact with Quest support engineers and they may have
> more useful suggestions on it.
>
> In addition, regarding the scenario of migration from Novell to win2k3
> domain, we suggest using MSDSS. Please refer to the following article for
> more information.
>
> NetWare to Windows Server 2003 Migration Planning Guide
> http://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspx
>
>
> Thank you for your understanding.
>
> Best regards,
>
> Frances He
>
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>
> If you are outside the United States, please visit our International
> Support page: http://support.microsoft.com/common/international.aspx.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.

Relevant Pages

  • RE: NTUser.Dat error when translatin profiles on workstation
    ... as Administrator and adding the Windows 2003 user w/Full Control ... or the User State Migration Tool for Windows 2000/XP clients. ... Microsoft Online Partner Support ... The roaming profile cannot be ...
    (microsoft.public.windows.server.migration)
  • Re: Swing Migration from SBS 2003 to new SBS 2003 box
    ... If a typical migration used to ... You can swing from a plain old NT4 non-Exchange domain to a 2003 ... Microsoft offered nothing like this in the form of documentation, ... they did not want to support the process I had outlined, ...
    (microsoft.public.windows.server.sbs)
  • Re: Swing Migration from SBS 2003 to new SBS 2003 box
    ... If a typical migration used to ... You can swing from a plain old NT4 non-Exchange domain to a 2003 ... Microsoft offered nothing like this in the form of documentation, ... did not want to support the process I had outlined, ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating from SBS 2000 to SBS 2003 onto new hardware
    ... First, you posted a request for Swing Migration, but perhaps you didn't know ... Microsoft offered nothing like this in the form of documentation, ... they then or will they now provide you support in doing a "Swing Migration". ... "Microsoft Small Business Server 2003 Advanced Best Practices" ...
    (microsoft.public.windows.server.sbs)
  • Re: SwingIt Pain and Suffering
    ... Thanks for the clear explanation of your support policies. ... There's documentation on the website about the firewall and the checklist ... if the replication doesn't seem to be going according to plan. ... I did complete the AD replication from the migration computer to the ...
    (microsoft.public.windows.server.sbs)