NAV Team: Retaining the Dynamics NAV 2009 SP1 Outlook Addin settings in a Terminal Server environment

[Blog bot]

With Dynamics NAV 2009 SP1, the Outlook Synch settings are no longer part of the IsolatedStorage but are now part of the Local Settings of the userprofile. This gives problems when implementing the solution on a Terminal Server. The Local Settings of a user profile do usually not roam. Especially when setting the GPO to delete the locally stored user profile, the settings are even no longer stored locally. The quick and dirty workaround is to implement a logoff and logon script that keeps the Outlook Addin settings up to date.

With Dynamics NAV 2009 SP1 running on Windows 7, the path to the Outlook Addin settings could be something like this:

%userprofile%AppDataLocalMicrosoft Dynamics NAVOutlookSynch

This folder may contain the following files after a full synchronization was executed successfully:
EntryIdStorage.xml
LastSynchronizationTime.xml
NavisionSynchronizationEntity.xml
OutlookSynchronizationEntity.xml
Settings.xml
SynchronizationConflict.xml
SynchronizationEntityFilter.xml
SynchronizationError.xml
SynchronizationSchema.xml
SynchronizationSchemaString.xml

These files are unique to every single users. The files itself cannot be modified manually. With a single logoff script, you could easily copy these files from %userprofile%AppDataLocalMicrosoft Dynamics NAVOutlookSynch to a shared folder on the network. E.g.: servernamesharenameOutlookSynch%username%

An example of such a logon script could look like this:

@echo off
GOTO BEGIN

:BEGIN
if not exist "%userprofile%Local SettingsApplication DataMicrosoft Dynamics NAVOutlookSynch" GOTO MKDIR
GOTO UPLOAD

:MKDIR
MKDIR "%USERPROFILE%Local SettingsApplication DataMicrosoft Dynamics NAVOutlookSynch"
GOTO UPLOAD

:UPLOAD
COPY "servernamesharenameOutlookSynch%username%" "%userprofile%Local SettingsApplication DataMicrosoft Dynamics NAVOutlookSynch*.*"
GOTO END

:END

An example of such a logoff script could look like this:

Dim sOriginFolder, sDestinationFolder, sFile, oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
Set objShell = CreateObject("WScript.Shell")
strUserProfile = objshell.ExpandEnvironmentStrings("%userprofile%")
strUserName= objshell.ExpandEnvironmentStrings("%username%")
sOriginFolder = strUserProfile & "Local SettingsApplication DataMicrosoft Dynamics NAVOutlookSynch"
sDestinationFolder = "servernamesharenameOutlookSynch" & strUserName
For Each sFile In oFSO.GetFolder(sOriginFolder).Files
oFSO.GetFile(sFile).Copy sDestinationFolder & "" & oFSO.GetFileName(sFile),True
Next
WScript.Echo "Copying of files succeeded"

There are of course other possibilities to explore here, but the basic idea is that those files are no longer part of the IsolatedStorage and therefore, a system implementer needs to manually ensure that these files roam along with the user profile.

Hope this helps.

Marco Mels

Microsoft Customer Service and Support (CSS) EMEA
These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.



Источник: http://feedproxy.google.com/~r/Micro...vironment.aspx