Need Help with W2K Software Deployment

[budda]

Hi Guys.

Ok here is the deal. I have a big big problem as mentioned in topic that i can't deploy software for w2k properly. I use an open source server on debian 4.0 etch (opsi) for deploying. This works with PXE. I have a mini linux which is loaded and copying the i386 folder on the hdd and installs from there. Drivers and basic software deployment works well. To be mentioned there is a client named "preloginloader" which loads before login (between startup and login). Now there comes the problem.

I want to deploy i.e. microsoft visio 2000. With AutoIT v3 i created a script which works fine. BUT! When i want to deploy it, it hangs up while "installing". If i'm logged in i can run the script per hand and it works fine. I have this same problem with F-Prot.

Anyone has an idea which can help me out?

Thanks for trying to help.

Greetings from germany

[Tripredacus]

Hallo,

Are you running the install off the network resource? Do you have the option of copying the install to the client and then running it from there? Sometimes we have this problem also because the network traffic can interfere with running a program from the network share.

[budda]

First thanks Tripredacus for your help.

Well yes, i do run it off the network. But its the same effect. Actually the same problem if i deploy it from local drive. Funny is that i can run it local when i'm logged in without any problems. Logs say 0 errors and properly installed which is totally nonsense.

Greetings. Bda

[Tripredacus]

This could be a couple problems. I will ramble this off maybe it will help you.

1. The OPSI client is a service that you should see in the Services snap-in. See what account is used for Log On. Make sure that account has full permissions to anyplace it needs like Program Files or Application Data or Local Settings\Temp. If you have any GPOs running that disable any folder access, check those also. As a test, you could try setting the Log On account to something else if the account specified is not in an Administrators group. Alternatively, if it uses a special account, you could add that account to the Local Administrators group.

2. Check to make sure that the installation is not being blocked by any anti-virus programs. There are cases on our servers where the antivirus will halt a program from executing and not show anything about it, so at first we think that the program is just busted.

[budda]

This could be a couple problems. I will ramble this off maybe it will help you.

1. The OPSI client is a service that you should see in the Services snap-in. See what account is used for Log On. Make sure that account has full permissions to anyplace it needs like Program Files or Application Data or Local Settings\Temp. If you have any GPOs running that disable any folder access, check those also. As a test, you could try setting the Log On account to something else if the account specified is not in an Administrators group. Alternatively, if it uses a special account, you could add that account to the Local Administrators group.

2. Check to make sure that the installation is not being blocked by any anti-virus programs. There are cases on our servers where the antivirus will halt a program from executing and not show anything about it, so at first we think that the program is just busted.

Hey Tripredacus. Thanks again for trying to help.

Ok the account it uses is the local administrator account. Full permissions to do everything. Plan is just to deploy, nothing else. No GPO's at all. The server is based on Debian 4.0

I tried out to deploy everything else but the anti-virus plus the visio 2000. Started up, same problem as mentioned...

Pity

[Tripredacus]

Are you on a Windows domain? I am thinking perhaps you need to add the local admin account into the Group your account is located in.

[budda]

Nah sorry dude. Its not a windows domain.

As i mentioned before, its Linux Server and Windows Client

Other Software can be deployed without problems.

[Tripredacus]

OK if you are using a batch file then, try remaking using a scripting program like AutoIT or KIXtart and specify the RunAs and use your credentials to install. Of course there does appear to be an underlying problem on that machine but I'm not sure how to troubleshoot it.

[budda]

OK if you are using a batch file then, try remaking using a scripting program like AutoIT or KIXtart and specify the RunAs and use your credentials to install. Of course there does appear to be an underlying problem on that machine but I'm not sure how to troubleshoot it.

The script is written in autoIt v3

Any other software can be deployed without problems. Its just visio2000 and fprot which makes problems to deploy. I think that both of the software needs a login to be installed. But i'm not quite sure if i'm on the right way....

Ty anyway for helpin dude. Much appreciated.

Greetings Budda