Problem installing Windows Defnder using Group Policy

[Guest]

Hi All,

I am encountering a problem when trying to install Windows Defender using
Group Policy.
I have the .msi file assigned under User Configuration side of things, it is
set to assign and install during logon. I initially am applying the group
policy to my own computer to test before deploying to the rest of the company.

Windows Defender fails to install and several event log errors are logged, I
think the most relevant one is this

Event ID 11327
Product: Windows Defender -- Error 1327. Invalid Drive: Z:\

The Z drive is the Home folder specified on the Profile tab for each active
directory account. Why it is failing on this I dont know as its not
configured to install from there or anything.

I should point out that i can install Windows Defender manually on my
computer so shouldnt be a permissions based issue as far as I can tell.

Any advice or help much appreciated.

Andy Heywood

 

[Guest]

please read inline

Hi All,

I am encountering a problem when trying to install Windows Defender using
Group Policy.
I have the .msi file assigned under User Configuration side of things, it is
set to assign and install during logon. I initially am applying the group
policy to my own computer to test before deploying to the rest of the company.

Windows Defender fails to install and several event log errors are logged, I
think the most relevant one is this

Event ID 11327
Product: Windows Defender -- Error 1327. Invalid Drive: Z:\

The Z drive is the Home folder specified on the Profile tab for each active
directory account. Why it is failing on this I dont know as its not
configured to install from there or anything.

I should point out that i can install Windows Defender manually on my
computer so shouldnt be a permissions based issue as far as I can tell.

Any advice or help much appreciated.

Andy Heywood

Further to my original email I removed the Z drive Home folder setting and I
get a different error:

Event ID: 1013
Product: Windows Defender -- 1: ALLUSERS property is not 1 - this MSM cannot
be used for a per-user or fallback-to-per-user install 2:

Dont know if this helps any

 

[Bill Sanderson MVP]

I am way out of my depth here, but I think it is possible that the behaviors
discussed in this article are relevant:

http://blogs.msdn.com/astebner/arch...p-error-related-to-the-allusers-property.aspx

If they are, it seems to me that the fix might be to use msizap or the
Installer Cleanup Tool to remove traces of Windows Defender from your system
before testing the policy-based install.

I don't have any experience in doing such installs, Windows Defender or
otherwise. I suspect that a forum related to server admin work might get
better eyes on this.

--

 

[Guest]

I just had this problem. In GP where it asks for the location of the
WindowsDefender.msi, instead of just locating the file, put in a FQDM
(Example: \\server\updates\windowsdefender.msi) in the space where you would
normally just put in c:\updates\windowsdefender.msi.
this worked for me.

 

[Bill Sanderson MVP]

Thanks!