Lookout and NT domains

[Anonymous]

Hi,

Has anyone else ever tried using Lookout in a client/server
configuration with PC's that are domain members.

I suspect from my experience in doing this recently, that the answer is
NO, but would be useful to have this confirmed.

[MEWART]

We have been doing it for 3 yrs now, and having no problems. We have one server process and five clients. We also have lookout publishing an HTML site for remote status monitoring.

What problems are you having?

Mark.

[Anonymous]

Hi Mark,

Thanks for your comments.

The main problem I am having is that as a "Domain User" the Lookout
server PC is unable to access (read) the section of the registry were
the "client license" is stored ("HKEY_LOCAL_MACHINE\SOFTWARE\National
Instruments\Lookout\Client Licensing"). The information is there and is
correct but as a "Domain User" it might as well not be, as Lookout is
convinced that no client licensing has been entered. How have you
overcome this situation?

David.

Mark E. wrote:
> We have been doing it for 3 yrs now, and having no problems. We have
> one server process and five clients. We also have lookout publishing
> an HTML site for remote status monitoring.
>
> What problems are you having?
>
> Mark.

[MEWART]

David, one option is to have the client machines logon as an admin., but have lookout logged on as a user without "windows" rights.

The other option is share the parent directory on the Lookout server side. Have the client application reside on the server also. Map the shared directory on your client machines, and load the client application from the mapped drive. Set the "Graphics" files location in the Lookout.ini files to point to the shared directory\graphics on the server. Use IP adresses instead of machine names to speed things up. This works well for us, and we have 4 clients on a server at any one time. For what it's worth, this will work without the client license. The server will "complain", but will work fine. Our corp. policy is to licens
e everything, so we have the reqired licenses. Good luck, Mark.

[Anonymous]

Hello Mark,

Two things really.

Firstly when I initially posted this question to this group you
responded by saying that you had no problems operating Lookout in a
Domain environment. It now seems that you may of indeed had problems and
adopted the strategy you detailed below to overcome them. Have you? also
found that "Domain user" accounts cannot retrieve "client licenses"?

The second question is, have you ever spoken to NI regarding any
problems with Lookout and Windows domains. As I suggested in my first
posting to this thread, I suspect that it is just you and I that have
run Lookout in a domain environment.

David


Mark E. wrote:
> David, one option is to have the client machines logon as an admin.,
> but have lookout logged o
n as a user without "windows" rights.
>
> The other option is share the parent directory on the Lookout server
> side. Have the client application reside on the server also. Map the
> shared directory on your client machines, and load the client
> application from the mapped drive. Set the "Graphics" files location
> in the Lookout.ini files to point to the shared directory\graphics on
> the server. Use IP adresses instead of machine names to speed things
> up. This works well for us, and we have 4 clients on a server at any
> one time. For what it's worth, this will work without the client
> license. The server will "complain", but will work fine. Our corp.
> policy is to license everything, so we have the reqired licenses. Good
> luck, Mark.

[MEWART]

David, as I first posted, we don't have any problems due to our Lookout client machines being logged on as admin. and controling access to the machine via Lookout security. Prior to getting all of the required client licesnes, we would get an alarm indicating more clients than licenses. We filtered out the alarm, and have since rounded out the reqired # of liceses, but havn't cleared the alarm filter. Basicly, no reason to as we know we are complient and "it ain't broken, so we don't fix it".

As far as contacting NI, we ran the configuration I had mentioned right out of te box, because it seemed like the logical way to do it, so we had no reason to call. If the Lookout server machine is a server, let it serve everything. We also pas
s the lookout.sec file from the server to the clients on a daily basis via schedueler (sp) in windows.

I find it hard to accept that we are the only ones running under a domain. Hope this helps, Mark