17 Posts
0
5958
Can't silently deploy exe/msi since version 10
Hello
I'm having trouble deploying DDPE since version 10. I can't seem to deploy this via GPO since it requires the user to be logged in.
I've tried running the installation with the user logged in and it installs fine. However, when attempting to deploy it as a gpo at startup, it doesn't install.
How can I fix this? It's been working with version 8 but with ddpe 10 it doesn't work.
Smidaren
17 Posts
0
December 2nd, 2018 23:00
I think I "solved" the problem.
I took the extracted MSI and made a startup script (computer level) in the GPO launching the msi with /passive (/quiet or /qn does not work).
dell-dale p
156 Posts
0
December 1st, 2018 10:00
Hi Smidaren,
Sadly installing via GPO is a pretty complex process that may not be easily troubleshot through a forum. The one item that i have seen affect these pretty heavily is the method that was used to extract the MSI from the Dell Encryption installation executable.
Do you have more information on the failure? If you do not have a ticket open, opening a ticket with Dell Prosupport for Software, i would suggest opening a ticket so we can help interactively.
If you do have a ticket open, would you be willing to Direct Message me the case #? I can look up the additional information to see how we can assist better :)
-Dale
Smidaren
17 Posts
0
December 1st, 2018 22:00
I get permission errors in the log but you can ignore that. The gpo runs with highest privileges.
Smidaren
17 Posts
0
December 1st, 2018 22:00
I’ve tried to reply 3 times but my post always disappears.
trying a forth time...
dell-dale p
156 Posts
0
December 2nd, 2018 08:00
Hi Smidaren,
Thank you for the logs! It looks like we are hitting permissions issues when installing this variant. I've sent over a pre-extracted MSI that was pulled by running the executable, and then extracting the MSI from the temporary directory.
Using /a may not include all of the files necessary in the MSI to perform a successful install based on some of our testing, though from the logs it looks like it may be due to the user context in which we are running.
for GPO pushes, we typically suggest running through a login script, which will force the context to run as "SYSTEM" on the target machine.
I hope these suggestions help!
Smidaren
17 Posts
0
December 2nd, 2018 13:00
dell-dale p
156 Posts
0
December 3rd, 2018 07:00
Smidaren,
That's great news! Thank you for the update! I'll do some research to see why /passive may be properly functioning, where /q or/qn was working before.
from some quick research, it looks like /passive is equivalent to /qb!
We'll do some research on this side and get some information out in our Technical Advisories over the next few releases :)