In Dynamics NAV 2009 in RTC client if you are accessing files located on network machines, these files can be accessed when each service is running on single machine, when SQL and NST are on same machine (2 tier) or each service is running on separate machine (3 tier).

However when accessing such network files in (2 and 3 tier) environment there might be some additional Delegation requirements.

As best practice i will summarize these requirements as following.

(Here NAV Server Service is runnign under Domain User account, Service Account for SQL can be same or separate dedicated Domain User account and NAV Server Service account is currently set to allow Kerberos only)

This msdn article can be followed with additional steps as described below

Managing network files in RTC (Setting Delegation)

http://msdn.microsoft.com/en-us/library/dd568720.aspx

1. Additional steps required:

    in Adsiedit.msc console Windows Server 2003 Service Pack 2 32-bit Support Tools, Open the User that is running in NAV Server Service in AD and go to the Delegation Tab

• Click on ‘Add’
• Select ‘Users or Computers’
• Enter in the name of the machine that is hosting the Shared Folder
• Click ‘Check Names’ and now it should show an underline below the servername
• Click ‘OK’
• Now you should see a list of Services for this machine that contains the shared folder
• Click on the Service called ‘cifs’
• Click ‘OK’

2. Please check the following Local Group policy on Middle tier machine and add this for NAV Service account domain user.

     Add these policies for this domain user under which NAV middle tier service runs.

• "Enable computer and user accounts to be trusteted for delegation” under computer Configuration -> Security Settings -> Local Policicies -> User Rights Assignment
• After this from Windows Start -> Run and type gpupdate /force in CMD prompt to refresh/update the policy.

 3. If the above steps does not work, additionally you can set the value of “UserAccountControl” flag value to 17367552 (To do this adsiedit.msc console can be taken)

     (TRUSTED_FOR_DELEGATION+TRUSTED_TO_AUTH_FOR_DELEGATION)
     According to following KB:

     http://support.microsoft.com/kb/305144/en-us

 4. After this please copy the “Kerbtray.exe” on the Middle tier and client machine and aftre running (double click on kerbtray.exe) right clickt -> purge the Tickets. So that on next RTC connection attempt it will automatically receive new Kerberos ticket.

     Kerbtray Tool you can download from the the „Windows Server 2003 Service Pack 2 32-bit Support Tools“.

5. With new RTC start this time now you are able to access the network files, (you may need to performance step 4 more than one time)

6. If it is still not working then probably Kerberos is failing back to NTLM, so you may also allow NTLM to the NAV Server service account "Use any authentication protocol" in the property of this Domain user or you are hitting the issue as described in below KB article.

   Delegation errors when working with file shares in the Microsoft Dynamics NAV RoleTailored client

   https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2621984

Hope with this way you can get access to network files from RTC client.

Mainstream support for Microsoft Dynamics NAV 5.0, including 5.0 SP1, ends April 2012 per the Microsoft Support Lifecycle Policy. Customers who are current on a service plan can continue to access the following benefits through CustomerSource:

• Previously released Upgrades, Updates, Service Packs, Fixes and Regulatory/Tax Updates 
• Self-Help Support through Knowledge Base articles and online content 
• Unlimited Online Training 

Paid support (including Premier, Essential, Pay-Per incident, and Microsoft Dynamics Advantage and Advantage Plus plans or any other paid support plan) will be available through the length of extended support.

For more information related to Microsoft Support Lifecycle policies and product dates for all Microsoft Dynamics NAV products, see the Support Lifecycle Page. For support lifecycle information for Microsoft Dynamics NAV in particular, see Microsoft Dynamics NAV Support Lifecycle Information.

The Microsoft Dynamics business is using Diagnostics to help automate Data Collection and Data Analysis when troubleshooting support incidents. Diagnostics allow our support teams to capture certain pieces of data about an environment to more efficiently resolve a customer case.  Diagnostics can do basic data collection to gather information about product version, system configurations and settings, as well as do a deeper analysis of this and other data collected to determine the root cause of an issue.    

The Microsoft Dynamics business has been working with Diagnostics for the past 2-3 years, but just recently made changes to the online incident submission process. Steps on how to run a Diagnostic will now be presented after submitting most cases on CustomerSource/PartnerSource.  If you have recently logged a support incident via CustomerSource/PartnerSource you may have noticed this new information after submitting the support incident. 

When presented with this information, please follow the steps provided to run the Diagnostic and upload the results to the Microsoft Dynamics Support team.  Diagnostics allow us to capture necessary product versions, system configuration, log files and other information to allow our support teams to more effectively and efficiently troubleshoot and solve support cases.  Running Diagnostics and uploading these results will reduce the number of questions support engineers will need to ask you, reduce the amount of information you need to manually gather and send us, and ultimately allow us to resolve cases quicker. The Diagnostics will automatically capture and upload the information to our support teams.  You do have the ability to view the information that is being collected prior to uploading it to Microsoft.  

In the Microsoft Dynamics NAV 2009 R2 RoleTailored client environment the Shortcuts Menu feature, which was present in earlier versions of Dynamics NAV for Classic client, has not been added.

In Classic client it is actually possible to Create and Open Shortcut from this Menu.

I have then tried, in this blog, to mimic what Classic client does and developed a couple of pages and one table to let users achieve a similar functionality for RoleTailored client. The text object in this blog contains:

1. Table 50300 “Shortcut”
2. Page 50300 “Shortcut List”
3. Page 50301 “Create Shortcut Worksheet”

The first task is to add Page 50300 “Shortcut List” to a Department MenuSuite like in the below example:

Secondarily it is needed to customize Navigation Pane using RoleTailored client in order to add a new Menu called, for example, “Shortcuts” with Page 50300 “Shortcut List” added to it.

This could be done manually

http://blogs.msdn.com/b/nav/archive/2011/03/30/nav-2009-tips-and-tricks-personalize-the-departments-menu.aspx

or configuring that for a profile

http://msdn.microsoft.com/en-us/library/dd301231.aspx

Once you have fulfilled those 2 steps then your users may be good to go to Create and Open shortcuts in a similar way as it was and as it is actually for Classic client.

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Duilio Tacconi (dtacconi)

Microsoft
Dynamics Italy

Microsoft Customer Service and Support (CSS) EMEA