Navision 3.70A in a Windows 2012 AD Domain

mazer9

We are running a heavily-customised version of Navision 3.70A SQL Server Edition (SQL Server 2000 on Windows Server 2003 Std). We are not quite ready to move to a new version as of yet, and I want to update the domain controller from 2003 SP2 to 2012 R2. Anyone running Navision 3.70A as a legacy application in a 2012 domain? I understand that the client/server can't run on modern OSes but I was wanting to make sure the client and server can still function in a modern AD Domain before updating domain controllers.

Any insight is appreciated.

zpgm

Hi mazer9,

Probably this isn't the answer you'd like but take this post as an example:
http://forum.mibuso.com/discussion/54810/navision-3-70b-client-on-windows-server-2008-32bit

kylehardin

It really isn't about NAV 3.70A - it's about the operating system on the workstations. NAV, if you are using Windows Authentication, simply asks the operating system "please go authenticate DOMAIN\User for me." So you need to find out whether the OS can talk to a 2012R2 Active Directory domain controller.

Also keep in mind that a 2012R2 domain controller can run different functional levels, so you may be able to keep your Active Directory forest at a lower level - basically emulating an older version of active directory - so that your workstations can still authenticate.

https://technet.microsoft.com/en-us/library/cc787290(v=ws.10).aspx

Another option you have is to upgrade your NAV executables. You could run the latest update version of 2009R2 using the classic client against your 3.70 database and not have to do any changes to your objects. But as long as you don't change the workstation OS versions, you should be able to stay with 3.70A executables.