[mdt] PCE6 installation "error" during MDT/WDS deployment

[woreilly]

Apologies if this is in the wrong section. I am attempting to deploy Policy Central Enterprise v6 via MDT. I have set it up as an application with a batch script running "msiexec /i PCEgpo.....msi /qn".

 

I have Java 8.66 also deploying via MDT application (this works perfectly with a /s after the .exe name).

 

However, PCE6 is failing to actually install even though Event Viewer logs and MDT deployment logs both say it was successful. I am using the Combo MSI and .NET 4.5.2 is in my custom WIM.

 

Does anyone have any ideas where to look? I have previously tried having the msiexe /i [msi name] /qn as the application command line but nothing doing.

 

It is MDT 2012 Update 1 with ADK version 8.59.25584 and Windows 7 x86 clients.

[Michael]

I've had similar issues (not deploying via MDT), but deploying via Group Policy. Looking at the event logs, the PCE MSI installer doesn't correctly detect Java is installed and consequently abandons the install.

 

I modified the MSI using Orca so it skips detection of Java and it was problem solved. I've also noticed, despite requiring NET 4.5.1 or later, it doesn't attempt to detect it but will still install, but then the processes in Task Manager aren't visible as it won't run.

 

Is there any reason why you don't install .NET 4.6 on Windows 7 from the start, instead of installing it as part of a sequence?

 

There's now a new .29 version of Policy Central just released, so will be looking into this in the near future.

[woreilly]

I've had similar issues (not deploying via MDT), but deploying via Group Policy. Looking at the event logs, the PCE MSI installer doesn't correctly detect Java is installed and consequently abandons the install.

 

I modified the MSI using Orca so it skips detection of Java and it was problem solved. I've also noticed, despite requiring NET 4.5.1 or later, it doesn't attempt to detect it but will still install, but then the processes in Task Manager aren't visible as it won't run.

 

Is there any reason why you don't install .NET 4.6 on Windows 7 from the start, instead of installing it as part of a sequence?

 

There's now a new .29 version of Policy Central just released, so will be looking into this in the near future.

 

We have had direct face to face contact with Simon Rogers from Future Digital (formerly Forensic Software) who informed us the Java issue is due to the MSI not installing a certain part of Java that makes Java detect work. If you install via the exe instead, it works a treat. Just use javaexename.exe /s in a batch script and it installs fine.

 

I installed .NET 4.5.2 via windows updates & WSUS in my custom WIM. I haven't been able to pull through 4.6 yet (assuming it is available in WSUS).

 

There's now a new .29 version of Policy Central just released, so will be looking into this in the near future.

 

.29 does not have a combo MSI installer and there are no plans for them to create one "due to there being issues with previous versions". That was from the Future Digital support team! They supply a separate MSI installer for C++ redistributable. Feels like a step backwards for me.

 

I may try bundling Java and the .28 MSI together in one MDT application to see if that makes it any better!

[Michael]

So the question is, does the .29 update fix all these issues I wonder?

 

.NET 4.6 isn't available via WSUS (as far as I can tell), but there is an offline file which you may be able to include.

 

I'm not surprised they've abandoned the combo update. It's just far too big and better off broken up into bits, or as I suggested, install the likes of .NET Framework on your base image. Windows 10 of course already has .NET 4.6 which is one less hassle.