Enterprise Software Thread, ForeFront Endpoint Deployment Problem in Technical; Hi,
I am in abiut of a rush to get ForeFront Deployed to our LAN before the old AV expires. ...
5th April 2012, 11:47 AM #1
ForeFront Endpoint Deployment Problem
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?
10th April 2012, 02:24 PM #2
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.
10th April 2012, 02:26 PM #3
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.
10th April 2012, 02:42 PM #4
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?
10th April 2012, 02:47 PM #5
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.
Originally Posted by Duke5A
10th April 2012, 02:48 PM #6
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.
10th April 2012, 02:59 PM #7
10th April 2012, 03:02 PM #8
I am going to look at that soon.
Originally Posted by djwingfield
Originally Posted by synaesthesia
I am now getting allot of machines coming up as removed locally. These machine have never had FEP installed.
10th April 2012, 03:04 PM #9
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
10th April 2012, 03:11 PM #10
Sorry its 2007. I needed to get FEP running ASAP and when 2007 was setup 2012 wsnt ready for production use.
10th April 2012, 03:32 PM #11
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.
Last edited by djwingfield; 10th April 2012 at 03:39 PM.
Thanks to djwingfield from:
10th April 2012, 03:38 PM #12
Thanks i think its working now I am going to try some more machine in the morning.
Thanks for the help.
10th April 2012, 08:10 PM #13
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
10th April 2012, 08:17 PM #14
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
By local-lad-steve in forum O/S Deployment
Last Post: 22nd March 2010, 04:30 PM
By paulmc in forum Network and Classroom Management
Last Post: 9th March 2010, 03:13 PM
By SteveCIS in forum Windows Server 2000/2003
Last Post: 27th November 2009, 08:40 AM
By cheredenine in forum Windows
Last Post: 30th July 2008, 11:49 AM
By Southwell in forum Educational Software
Last Post: 18th July 2008, 03:27 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)