computer install fails.
Hi.
I am trying to deploy an app with group policy. I seem to have some kind of file system security problem that I cant find. The install works on the server share if I install by user but it fails if I try to install per computer. I have actually gotten the install to work by sharing a folder off my desktop and installing by computer but I need to get it to work off our file server. I have added file sharing and file system permissions for the computers but this does not fix it.
Is there some kind of security policy setting that would let users install but would block computers from loging on?
I am trying to deploy an app with group policy. I seem to have some kind of file system security problem that I cant find. The install works on the server share if I install by user but it fails if I try to install per computer. I have actually gotten the install to work by sharing a folder off my desktop and installing by computer but I need to get it to work off our file server. I have added file sharing and file system permissions for the computers but this does not fix it.
Is there some kind of security policy setting that would let users install but would block computers from loging on?
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
nheim
16 years ago
Hi K_N,
does the Computer-Account have the right to 'Apply Group Policy'?
What are you getting back in the Application Event log?
Have you turned on MSI-Logging? The logs for a machine install go to %systemroot%\temp.
Regards, Nick
does the Computer-Account have the right to 'Apply Group Policy'?
What are you getting back in the Application Event log?
Have you turned on MSI-Logging? The logs for a machine install go to %systemroot%\temp.
Regards, Nick
Posted by:
razor0690
16 years ago
Do you have Domain Computers with read and execute on the file share?
Posted by:
K_N
16 years ago
Computer has rights to apply group policy.
Event logs say
Event ID 102 and 108
The installation source for this product is not available. Verify that the source exists and that you can access it.
MSI log gets created but is blank.
appmgmt.log
Calling the Windows Installer to install application gw7software from policy gw7installpolicy.
The install of application gw7software from policy gw7installpolicy failed. The error was : %1612
I can find no login attempts on the server security logs for any computers ever. Only users.
If I move the whole package off this server and on to a different share/server it works fine.
The problem seems to be the server is only allowing users to logon or computers cant see it to to try to logon.
Event logs say
Event ID 102 and 108
The installation source for this product is not available. Verify that the source exists and that you can access it.
MSI log gets created but is blank.
appmgmt.log
Calling the Windows Installer to install application gw7software from policy gw7installpolicy.
The install of application gw7software from policy gw7installpolicy failed. The error was : %1612
I can find no login attempts on the server security logs for any computers ever. Only users.
If I move the whole package off this server and on to a different share/server it works fine.
The problem seems to be the server is only allowing users to logon or computers cant see it to to try to logon.
Posted by:
razor0690
16 years ago
Have you compared the Share / Nt permissions between to two systems? Also what operating and service pack level are they on?
Posted by:
K_N
16 years ago
Yes I have compared permissions on working shares vs the non working one.
The server that does not work is running Win 2000 sp3. It is a Dell powervault NAS server. I am starting to think the OS is specialized and not capable supporting computer$ logins.
The server that does not work is running Win 2000 sp3. It is a Dell powervault NAS server. I am starting to think the OS is specialized and not capable supporting computer$ logins.
Posted by:
K_N
16 years ago
This is solved. Thanks for your help all.
The problem was in the name of the server. The suffix was not complete. It should of been server.something.domain.com and it was set for server.domain.com.
The problem was in the name of the server. The suffix was not complete. It should of been server.something.domain.com and it was set for server.domain.com.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.