Jump to content

Recommended Posts

Posted
??? When I look at share and security permissions on the MSI folder - I don't have an authenticated computer option to add - the only thing starting authenticated is authenticated users

 

AFAIK that's a bit of a misleading name, and includes "Computer" accounts. Looked at our folder and Auth Users have Read & Execute, List Folder Contents and Read. (The latter may be unnecessary duplication!)

Posted

Gawd knows what i did but I've managed to get WindowsKey-E and WindowsKey-R working :)

 

So I've managed to manually install Scratch on 1 of the machines

 

Not going to be a productive method since I had to enter the Administrator name and password twice to get it to install but at least I have some method of installing an msi :)

 

- - - Updated - - -

 

Going home - back again next week!

Posted
UAC to the rescue! If installing via GP, it'll bypass that. When it works. If one has worked, you have the theory nailed. Now come the quirks, like GP installs over wifi being flakey.
Posted
Now come the quirks, like GP installs over wifi being flakey.

:(

 

All the computers are wireless :(

 

Give me strength!!!

 

How many years and OS iterations has MS had to get app deployment right.

 

If I want an app on my phone - I can logon onto t'internet on any computer - select the app from the store and deploy it to my phone (which can be anywhere in the world) and have it installed automatically.

 

It shouldn't be an order of 1000 times harder to deploy an msi to a bunch of computers on the same LAN!!!!!!!!

 

And people wander why I stuck to using WPKG automated script deployment and avoided MS domain management for all these years!!!! :-)

Posted
Log in to one of the laptops as admin, run cmd, type gpupdate /force and press enter. Reboot, machine should start to install your new shiny MSI's. Machines don't always syn group policy at startup (unless you enable it..)
Posted
Log in to one of the laptops as admin, run cmd, type gpupdate /force and press enter. Reboot, machine should start to install your new shiny MSI's.

 

Well it that works - I'd consider that a workable workaround :)

 

Machines don't always syn group policy at startup (unless you enable it..)

 

So how do I enable it ...... :)

Posted (edited)
Just try the cmd - gpupdate /force first and see if it starts to install, it'll give you an error if you have any underlying GP issues =] Edited by Patrick
Posted

app deployment is where SCCM picks up the slack gpo msi installs fail.....

run software center... select advertised app, install. (providing the administrator hasn't told the software center just to install it with out user notifications).

 

But SCCM is a different beast, but well worth looking into.

Posted
Cmd - gpresult /r will tell you what policies were processed. Sometimes it just doesn't process all the policies. Because /Microsoft?
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...