

We have a custom executable in our “Startup Group” called “CompanyPersonalization.exe”. Ok, so we now have our Outlook.NK2 file sitting on a network share that will be accessible to that user from their new Windows 7 PC.lets get AppSense involved. If enough people shout I will think about it. There are lots of ways to achieve this export and file rename but I have not included that in this Post. We then look at the most recently modified NK2 file and ensure it is called Outlook.NK2. Normally (well in our experience) it is called …Our script exports *.NK2 files from the users profile to a network share. *something* = what ever their old outlook profile was called. The NK2 file will be called *something*.NK2. Part of this script locates the users NK2 file (If you dont know what an NK2 file is then you probably shouldn’t be reading this post) and exports it to a file share which will be accessible from his new Windows 7 PC.

The last thing we do before John Doe logs off their old XP PC is run our Export Script. The nickname cache can now be viewed from the “Suggested Contacts” address book in Outlook 2010. Yipeee.no more corrupt flat file NK2 files. Outlook 2010 doesn’t use the NK2 file anymore, it stores the nickname cache in a hidden message in the users mailbox store. “John Doe” is about to be relieved of his/her (can a girl be called John?.whatever) 6 year old Windows XP desktop PC and presented with his/her shiny new Dell Optiplex 790 with Windows 7 installed. We have to visit each user anyway to give them new hardware and because we are very customer centric we give them about half an hour overview on their new Windows 7 PC…because we care 🙂 For various reasons, partly due to how our desktop estate was configured horribly historically, we decided to export our Windows XP users “Vital” settings using a simple script. Sometimes that's just what the end user wants.AppSense Environment Manager can help you migrate an XP User to Windows 7 very easily and seemlessly. But in the real world, scenarios do arise when you have to go back in time technologically. I have to admit I was little surprised that it worked so seemlessly as it seems that software in general is never designed well for 'backwards compatability'. (Well, it was exactly what we needed anyway). nk2 file for the user and then would appear on the autocomplete seletion list.

On the Outlook 2010 computer, I was able to export the Suggested Contacts to a csv file (Windows format) and then use that file as input when I run the n2kedit program on the As it turned out, the nk2edit freeware program from Nirsoft that Andy_Ch recommended has been tried out and seems to do exactly what we need to do - which was migrate backwards the informationįor Autocomplete from and Outlook 2010 account to an Outlook 2003 account. Yes, I can see the Suggest Contacts as well as the Contacts.
