Transfer of Lookout.sec file to new PC does not move user account information

[ICI]

I have a user account setup on a client/server PC. The customer has purchased a new PC and we have the process working on it. I transferred the Lookout.sec file to the new PC but it does not contain any user account information from the old PC.

[Remzi]

Hi,
All network security settings for a process are saved in the .lka file. This file must be in the same directory as the process.l4p. file. if you take the server or client process to another computer, you need to include all four Lookout files: .l4p, .lst,.l4t,.lka
I hope this helps.
Best Regards,
Remzi A.
Applications Engineering
National Instruments

[ICI]

All 4 files are in the same directory, could there be another problem?

[Remzi]

Hi,

Make sure that the lookout.sec is copied to the Windows System directory. There is a Lookout example that transfers this file programatically if both PCs are on the network. Here's the link.

http://venus.ni.com/stage/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3E56156A4E034080020E74861&p_node=DZ52192&p_submitted=N&p_rank=&p_answer=&p_source=Internal

Also , review the Lookout developer's manual as suggested in the KB linked below.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/9a116ca020b9c0c386256e6e00716642?OpenDocument

Best Regards,
Remzi A.

[ICI]

If the PC is running Windows 2000, then the lookout.sec file needs to be placed in C:\Winnt\system32 not in C:\win\system

[ICI]

Thanks for the reply but the link to http:// venus... is not valid, web page cannot be displayed. I figured out the problem, you have to use the windows system32 directory if Windows 2000 is the operating system.

[JTJams]

ALso make sure that the file is not configured as read only - I know this will prevent any future modifications, but may not open correctly on some systems.