Still haven't cracked software deployment

I'm trying to deploy the recent versions of the Adobe reader, flash and shockwave.

On the workstation im getting the error that erm...bascially do i have permission to access it? I can run the program from the folder quite happily.

On the server yesterday it says...

Quote:

---

Software Installation encountered an unexpected error while reading from the MSI file \\Curricsvr1\packages\Adobe MSI's\install_flash_player_10_active_x.msi. The error was not serious enough to justify halting the operation. The following error was encountered: The operation completed successfully.

---

for each of them...

I am assuming that you are deploying them by Group Policy.

If this is so, then the share and files will have to allow "Authenticated Users" access so that the machine account in AD has permission to the files.

As for the server error, I am at a complete loss to help you there.

Hi

The new msi for flash are strange that I downloaded from the adobe site. i presume you have registered with them for distribution and have downloaded the latest version. I am not sure but during the install I think it trys to see if a newer version is available and gets stuck as you have not answered the question as its being installed by the computer at startup so you cannot see the question. For some reason on some computers it gives you an error and finishes on other it just sits and has to have a hard reboot. I have no idea why but my guess is its a poor msi. In either case it appears to have installed and works ok.

Richard

You might want to allow "domain computers" access to the share as well - if you've done the software install as a machine policy their won't be anyone logged onto it yet

Ok, what does this mean?!

Quote:

---

The assignment of application Adobe Reader 9.3 (2) from policy Adobe Reader failed. The error was : The group policy framework should call the extension in the synchronous foreground policy refresh.

---

Quote:

---

Originally Posted by Little-Miss

Ok, what does this mean?!

---

Do a gpupdate /force in a command prompt and reboot.

refresh phases: http://grouppolicy.editme.com/ClientSideProcessing

That's just because XP and later get to the logon screen before they connect to the network fully, so they need to be rebooted 2 or more times before stuff installs. I send a gpupdate command to all the computers before I restart them to speed it up a bit

Quote:

---

Originally Posted by Domino

You might want to allow "domain computers" access to the share as well - if you've done the software install as a machine policy their won't be anyone logged onto it yet

---

Psst.... "Domain Computers" are part of the "Authenticated Users" group.

Although to be fair, "Domain Computers" could be considered better, because it contains only computers whereas "Authenticated Users" is everything authenticated by the domain IIRC.

I used the Authenticated Users because everyone and everything require access to the files at some point, point in case is when a product tries to auto-heal and needs the original install .MSI.

Either way the share permission should be left at read, that way there aren't any unauthorised people moving / deleting files, it's also a good idea to hide the share.

Quote:

---

Originally Posted by powdarrmonkey

Do a gpupdate /force in a command prompt and reboot.

refresh phases: grouppolicy - Client Side Processing

---

Not sure if just /force will work, I think you may need a /sync too, I usually go belt and bracers with "gpupdate /boot /force /sync".

Ah, better warn that the /boot will reboot the PC as soon as the group policy update is complete - and it doesn't take long to complete!

Quote:

---

Originally Posted by TheLibrarian

Not sure if just /force will work, I think you may need a /sync too, I usually go belt and bracers with "gpupdate /boot /force /sync".

---

No, just /force, and you'll be prompted to log out or reboot.

Hi

I use gpupdate /force /boot and that works ok

Richard

Quote:

---

Originally Posted by powdarrmonkey

No, just /force, and you'll be prompted to log out or reboot.

---

I'll take your word for it. :)

You tend to know what you are talking about!

I'm getting the

Quote:

---

The installation source for this product is not available. Verify that the source exists and that you can access it.

---

Again...hmph

Definitely permissions.

Use the Advanced view of the security permissions to test the effective permissions.

Did you move the file within the file structure? That will retain the previous permissions and may mean that the permissions you think should be on the file actually aren't.


Check the share permissions too, that is just as effective a barrier as the NTFS permissions...

It's a while ago now, but when I was playing with deploying a new version of flash, I actually had to run an admin install of the msi to extract the actual msi that would let me deploy it. Not 100% sure why.

So on your flash msi run msiexec (msipath) /a, hop through the wizard and choose somewhere to extract the files to then try deploying the MSI that has been extracted and see if that makes any difference.