asked on
Attempt to deploy software via GPO getting error.
Im attempting to deploy the office 2007 compatibility pack to all workstations XP and 2000 in my enviroment.
I downoloaded the compatibility pack and used the following command to extract the msi file
FileFormatConverters.exe /extract:c:\temp
I created a GPO and have linked the computer software install to the msi file.
I made sure the "everyone" group has read access to this GPO
I also logged in as a normal user and made sure they can read and execute the msi file.
If i look in application logs it give 3 error events
event id 1000
Windows cannot process extension application management processgrouppolicy. Return value (0x643)
event id 1000
the group policy client-side extension application management was passed flags (1) and returned a failure status code of (1603)
event id 108
failed to apply changes to software installation settings. software changes could not be applied. a previous log entry with details should exist. The error was a fatal error during installation.
if i simply try to double click on the extracted file called O12Conv.msi from both a windows 2000 or XP pc, i get the following error message
source file not found
\\server_name\Share_name\o
Verify that the file exists and that you can access it.
I downoloaded the compatibility pack and used the following command to extract the msi file
FileFormatConverters.exe /extract:c:\temp
I created a GPO and have linked the computer software install to the msi file.
I made sure the "everyone" group has read access to this GPO
I also logged in as a normal user and made sure they can read and execute the msi file.
If i look in application logs it give 3 error events
event id 1000
Windows cannot process extension application management processgrouppolicy. Return value (0x643)
event id 1000
the group policy client-side extension application management was passed flags (1) and returned a failure status code of (1603)
event id 108
failed to apply changes to software installation settings. software changes could not be applied. a previous log entry with details should exist. The error was a fatal error during installation.
if i simply try to double click on the extracted file called O12Conv.msi from both a windows 2000 or XP pc, i get the following error message
source file not found
\\server_name\Share_name\o
Verify that the file exists and that you can access it.
Active DirectoryNetwork Operations
Last Comment
Todd Gerbert
ASKER
yes they have permissions and still not working!
Might sound stupid but can you please check security permissions on the MSI file itself,just to be sure!
ASKER
i checked and everyone group has read and execute permissions on the file and they are inheriated.
My last two cents is to remember to restart PC even two times,because you applied this GPO to Computer configuration not User configuration
Also its not relevant with which account you are logging because GPO is applied to Computer Account not user accounts.
Also its not relevant with which account you are logging because GPO is applied to Computer Account not user accounts.
ASKER
i restarted 3 times and no change
Why not try linking GPO to user configuration,
then log off user and log on ,
so we can check if its the permission problem!
then log off user and log on ,
so we can check if its the permission problem!
ASKER
I have linked it to user config
It seems to install (says installing office 2007 comp pack when logging in)
It does appear in add / remove programs but it is not installed 100% it just lists the entry for the comp pack.
Everytime i reboot it says the same thing installing office 2007 comp pack.
It seems to install (says installing office 2007 comp pack when logging in)
It does appear in add / remove programs but it is not installed 100% it just lists the entry for the comp pack.
Everytime i reboot it says the same thing installing office 2007 comp pack.
Office 2007 compatability pack must be installed as a machine assignment, per-user assignment is not supported (according to microsoft).
I found this little blurp regarding one of the error messages you're receiving (http://support.microsoft.com/kb/323304):
When programs are assigned to a computer, the computer tries to access the software installation share by using the credentials of the computer account. Computers that are running Windows Server 2003, Windows XP Professional, or Windows 2000 require Kerberos authentication. Windows NT 4.0 is not Kerberos-aware and can provide only NTLM authentication. Therefore, authentication is unsuccessful.
So if you're not hosting these files on an NT4.0 system, you might have an issue with kerberos authentication - maybe try removing a client from the domain and re-adding it.
I found this little blurp regarding one of the error messages you're receiving (http://support.microsoft.com/kb/323304):
When programs are assigned to a computer, the computer tries to access the software installation share by using the credentials of the computer account. Computers that are running Windows Server 2003, Windows XP Professional, or Windows 2000 require Kerberos authentication. Windows NT 4.0 is not Kerberos-aware and can provide only NTLM authentication. Therefore, authentication is unsuccessful.
So if you're not hosting these files on an NT4.0 system, you might have an issue with kerberos authentication - maybe try removing a client from the domain and re-adding it.
ASKER
the article you refrence the resolution says
To resolve this issue, host software installation shares on Windows 2000-based or Windows Server 2003-based computers.
the software install files are on a windows 2003 server SP2 server
To resolve this issue, host software installation shares on Windows 2000-based or Windows Server 2003-based computers.
the software install files are on a windows 2003 server SP2 server
I figured as much...but more importantly, the article also pointed out that the cause is due to the fact that client computer accounts (not user accounts) authenticate against the server using kerberos.
If the client's computer account doesn't have access to the file shares the install will fail with this error.
If the client's computer account doesn't have access to the file shares the install will fail with this error.
ASKER
all the clients computer accounts have full access to the file shares so again im not sure why it is failing
Along with the .MSI, your installation source should also have an O12Conv.cab file and a Catalog folder - are these present on your share?
ASKER
No i do not i only have the original exe file that i downloaded from the msft site and then the msi file that i got after i ran the extract.
How do i get the files?
How do i get the files?
You should get these files out of the /extract command line.
Put FileFormatConverters.exe in a folder by itself, then go to a command prompt, cd to that folder and run
FileFormatConverters /extract:.
to extract all the files into the current directory. You'll need to copy everything except FileFormatConverters.exe to a share accessible by all the computers, then you can publish the .msi (or just copy the missing pieces into the share you already have)
Put FileFormatConverters.exe in a folder by itself, then go to a command prompt, cd to that folder and run
FileFormatConverters /extract:.
to extract all the files into the current directory. You'll need to copy everything except FileFormatConverters.exe to a share accessible by all the computers, then you can publish the .msi (or just copy the missing pieces into the share you already have)
ASKER
That did work, however it does not seem to work on PC were users are logging on with non admin privledges.
Is there any way around this?
Is there any way around this?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
and that everyone is added to "share permission" and to security tab too!