Server 2019 and MSI deployment

[Warwick_Tech]

Hi All,

 

Mentioned this as a bug, sorry - Feature of Server 2019 ages ago, but not sure if it was a big enough thing.

 

The traditional way to create and deploy an MSI was create a network share for 'everyone' to have read access and add it to software distribution via GPO.

 

This however seems broken in 2019 as it always prompts for network credentials on accessing a server share on a local account, meaning the programs cannot install.

 

I got around this on MDT by entering admin credentials on the scripts, but cannot find a way round for regular PC's;

 

I know security is important, but sometimes you need these unsecure folders to host EXE's and MSI's your users need.

 

Anyone got any further on this?

 

Also upgrading my DC to 2019 as we speak - 77% wish me luck

[6Foot2]

...Also upgrading my DC to 2019 as we speak - 77% wish me luck

Good luck.

 

I can't remember when I found out about this method of software deployment (it was long ago) But when I did I wanted every bit of software to be distributed as MSIs, it was just so much easier than the other methods I was using at that time.

 

 

Now we use SCCM, so no worries.

 

[FishCustard]

Really?! If this is true, then Server 2019 will break over half of the corporate software deployment systems in the world.

 

Does it work if you give "Authenticated Users" read access? That's how we do it on 2016.

[localzuk]

I believe you may want to look at this - Server 2019 Anonymous File and Printer Sharing | DataOne

[FishCustard]

Ohhh so this only applies to non-domain PCs. That makes more sense.

[Warwick_Tech]

Thanks for the replies all -

 

I tried various methods to get it to work when 2019 was released, it was for domain PC's -

 

The update of the DC went flawlessly (concerning) so now just some VH left (Is there still the bug where you can't update these properly?) and the file server with the MSI's, but that's going to be a pain if the feature remains.

 

If you use SCCM you won't be affected I guess :shrugs:

[Cache]

I can't remember whether it was was everyone or authenticated users I tried to use previously (and we're talking many years ago) and it didn't work properly, since then I've stuck with Domain Computers having read permissions to the share and never had an issue since. Might be worth a go?