ForeFront Endpoint Deployment Problem

[FN-GM]

Hi,

 

I am in abiut of a rush to get ForeFront Deployed to our LAN before the old AV expires. I am having probelms deploying it with the built in MS package. It keeps failing. I cant find any logs as to why.

 

If i run a batch file manually on the machines like this install fine and reports back to the server

 

"\\SCCM-SERVER\c$\Program Files\Microsoft Forefront\Client\FEPInstall.exe" /s /q /policy "\\SCCM-SERVER\c$\Program Files\Microsoft Forefront\Client\Policies\FPHS FEP Desktop Policy.xml"

 

Any thoughts as to why the provided microsoft package doesnt seem to work please?

 

Thanks

[Duke5A]

How are you trying to push it out remotely? I'm grasping at straws here, but it could be that it works when you run it by hand because it is using user credentials to access to the share that it sits on, but when trying to push it out it has to rely on machine credentials and those don't have access.

[FN-GM]

I am pusshing it out using SCCM. It wont deploy automatically. If i go onto the client and install it from Run advertised Programs it downalods and installs perfectly.

[Duke5A]

Huh... Well, I don't use SCCM, but since it's just an EXE with command line switches, what about pushing it out using GPO and setting it as a start-up or shutdown script?

[FN-GM]

Huh... Well, I don't use SCCM, but since it's just an EXE with command line switches, what about pushing it out using GPO and setting it as a start-up or shutdown script?

 

Kind of defeats the whole object of SCCM. Plus if i do it that way i wont get the full install reporting features. I will probably have to do that if i cant figure it out. I have only anther 10 days of the current AV.

 

Thanks anyway

[djwingfield]

Hi

 

I use SCCM but I do the following "FEPInstall.exe /s /q" then SCCM client will apply the policy after a hardware and software inventory.

[synaesthesia]

2007 or 2012?

[FN-GM]

Hi

 

I use SCCM but I do the following "FEPInstall.exe /s /q" then SCCM client will apply the policy after a hardware and software inventory.

 

I am going to look at that soon.

 

2007 or 2012?

 

2010

 

I am now getting allot of machines coming up as removed locally. These machine have never had FEP installed.

[synaesthesia]

I meant SCCM. Assuming it's 2007 as 2012 deploys it as part and parcel of the client anyway. Didn't get far enough with 2007 (didn't see the point) to deal with EP deployments

[FN-GM]

Sorry its 2007. I needed to get FEP running ASAP and when 2007 was setup 2012 wsnt ready for production use.

[djwingfield]

synaesthesia - That’s for SCCM 2007.

 

FN-GM - Any luck? You get "removed locally" when you deploy FEP Via the console and its not installed correctly on the client or a software or hardware inventory hasnt taken place since the install.

Edited April 10, 2012 by djwingfield

[FN-GM]

Thanks i think its working now I am going to try some more machine in the morning.

 

Thanks for the help.

[Gatt]

Have you removed all traces of any previous AV products?

I found that although FEP was supposed to do that anyway it had trouble with McAfee Agent

 

Glad it's all working now

[FN-GM]

I made another package to remove the old av and set it to run before the FEP deployment. It works a treat.

 

I have been spending nearly a week on this and i have no idea what i did to fix it!!

 

Thanks for the input guys