AX with NT Domain !! is it possible .

(0) Share

Report

Posted on by BBARHUM

130

Dear All

Im facing a problem in my current environment in the company , mainly we got windows NT as our domain
and the main problem here that our old ERP system is required windows NT as a domain , so now im in a big problem
i can have a new domain license and hardware but the main problem how i can apply the both systems at the same time for the same users . i am sure that AX need windows 2003 or higher as a domain controler and our old systems need the NT

the users will have to work on both systems till we megrate fully to the new one , can our both systems work under NT domain , im little bit confused and even i dont know what choices i got

any idea ??

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

user5555 7,437 on at

Like (0)

Report

Hi,

I think speeding up the migration and having a short time frame in which both systems up with different logins. Or maybe request the vendor of the old erp for help. I think NT is from 2000..that is 10 years old.

J.

Was this reply helpful? Yes No
Glen Hassell 225 on at

Like (0)

Report

It depends on if you’re planning on using AX 2009. In short Windows 2000 mode is the standard operational level but if you want to use Role Centres / Enterprise Portal / Reporting Services / Analysis Services, you will also need to use Kerberos authentication which in short..
No.
For this type of functionality you will need to raise to Windows Server 2003 domain controller.
You are going to have to raise your functional domain level - sorry to be the bearer of bad news but your domain is no longer supported and I suspect that you were already aware of that prickly banana, miles before you even threw it out there.

What I would consider doing in the situation is using the standard AX 2009 VPC and modifying the domain - CONTOSO - to suit your needs and then potentially building an isolated domain that you can join to your existing NT domain.

Another way might be to host the AX 2009 VPC in Virtual Server 2008 and start from there with a decent set of virtualised machines, retiring redundant hardware along the way as you virtualise the entire network. You might be able to consolidate a lot of hardware but it sounds like that would create quite a lot of work, as you would be rebuilding the entire infrastructure from the ground up.

With that in mind, it sounds like it needs to be done at some point anyway.

Was this reply helpful? Yes No
user5555 7,437 on at

Like (0)

Report

Hi,

What about reversing the situation? Use the 2003 domain controller. I read somewhere that in 2003 still process is running for old NT (Kerbos?) authentication. Maybe 2003 can till work with the old 2000 NT domain. Maybe some migration specialist (now busy migration to Windows 7 can help you). In many situation is it likely that similar situations / deadlock happens and for major migrations it is common to migrate in clusters. So I would suspect there is some backward compatibility possible here.

J.

Was this reply helpful? Yes No
Glen Hassell 225 on at

Like (0)

Report

Computers with Windows 3.11, Windows 95, Windows 98, or Windows NT 4.0 will use the NTLM protocol for network authentication in Windows 2000 domains. Computers running Windows 2000 will use NTLM when authenticating to servers with Windows NT 4.0 and when accessing resources in Windows NT 4.0 domains. But the protocol of choice in Windows 2000, when there is a choice, is Kerberos version 5.
I've never been able to have consistent authentication between Reporting Services and SharePoint in a Windows 2000 functional domain level. It work's periodically and eventually crumples, at least based on my experiences with Role Centers this is what I have found to be the case as the Windows Server 2003 Kerberos Extensions do not exist at the Windows 2000 Level.
NT 4.0 does have Kerberos v4.0 support. Windows 2000 uses v5.0 but the way in which 'mixed mode' environments work are based on NTLM authentication so you have an issue of 'double hop'. With NT 4.0 the account is based around SAM.
Can't be done!
http://technet.microsoft.com/es-es/library/cc780332%28WS.10%29.aspx

Was this reply helpful? Yes No
BBARHUM 130 on at

Like (0)

Report

Thanks alot for the valuable data

That was very help for me , at least i got an image to the situation now .

Was this reply helpful? Yes No
Christopher Navarro 695 on at

Like (0)

Report

BBARHUM,

I suggest to get yourself a couple of servers and setup a new domain 2003+. Then setup a two-way trust relationship to the NT domain, setup AX on the new domain and slowy start migrating users from one domain to the other.

In order to allow users access to the two systems, try the following in this order:

- Use the trust relationship to allow users form the NT domain to access resources in the AD (i.e. AX), then see if you can import a user into AX. I've never tried this so please tell me if it works!

If this does not work then;

- Create duplicate accounts for the NT users in the AD and allow them to access AX client by logging in through a Terminal Server (very easy to do but you'll need a TS), this will set the stage for a full migration and finally bring your network to the XXI century!

Good Luck!

Was this reply helpful? Yes No

Community site session details

AX with NT Domain !! is it possible .

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates

Community site session details

AX with NT Domain !! is it possible .

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Featured topics

Product updates