OSD giving me unknown app issues when joining domain

[P3nnyw1se]

Hey so..

I created 10 apps, java, acrobat etc. in sccm2012
When I deploy these to machines in my domain. they install right away, they work as expected.
Silent install on all of them, some MSI, som exe files

Now I want to distribute the same apps during a PXE -> OSD

The computer will join the domain as part of the OSD.

Problem 1
of 10 apps.. 9 are installed during the OSD, and several show warnings
The one that osimply fails isan MSI file, small accounting tool, that use a server on the domain to share information between users.
And as expected that means I can't even manually install it either.

I'm thinking its a setting/rights issues in this newly deployed windows 7 enterprise

 

This is the error code I get
"This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic"
Note: The very same application works when deployed to other computers on the domain

I am using a domain administrator, trying to install the program, the domain administrator has full control and rights on the machine. and full rights on the file.
Its the exact same domain administrator as I use to manually install it on other computers that are already on the domain.
And I can't seem to tell the difference, why its allowed on one and not the other?.. what windows setting during an OSD needs to be put in order to change this.


------------------------------------
Problem 2:

Som programs will install, but take 20-25minutes to do so.
Like Java 7u40
Java takes almost half an hour to install during the OSD, and 40 seconds when I simply deploy it to a computer.
So maybe its the same thing? maybe its a right thing?
Anyways 3 java logs are created... this is what it gives me

I have added 4 files regarding java, that is placed in my 'c:\windows\temp after installation..
hopefully one of you will read this and can tell me why it takes 30 minutes to install.

 

if I had to guess from reading it.. its a rights issue just like problem 1.

------------------------

java_install.log

JavaDeployReg.log

java_install_reg.log

jusched.log

[P3nnyw1se]

well I figured out the first one, not the java one

The first program that doesn't get installed and calls unsafe, requires framework 4.0 which isn't in the wim.
but even after putting on 4.0 it gives the same error because windows installer keeps a reg key on the program.

if I deleted that req key I got to install it