Armann Posted October 21, 2010 Report post Posted October 21, 2010 Hi... I'm deploying ForeFront Endpoint, that works fine, I had to uninstall it on one machine and now it doesn't reinstall. One more thing, I'm deploying Forefront definition updates, they install fine on 32 bit machines but not on 64 bit. I'm a SCCM virgin so go easy on the flame I would include the logs but I really don't know what log to look at on the client side why the update failed. I can see in the event viewer on the 64 bit machines: "The contents for update e1df4ef2-2882-4613-87da-49b6fe29a63f could not be located." I have a bunch of those, the update source share has the correct perms, thinking it has more to do with the machines being 64 bit since they are the only machines having this issue Thanks... Quote Share this post Link to post Share on other sites More sharing options...
0 Lucid Posted November 1, 2010 Report post Posted November 1, 2010 I don't use Forefront, but since nobody chimed in I thought I'd toss this out... First, you may want to look at deploying definitions via WSUS if you have that running: http://support.microsoft.com/kb/977939 Secondly, there are updates for 32-bit which is one download, and then there are 64-bit updates, which is a different download. So you'll need to either use a VBScript wrapper to kick off the needed installer, or target your 64-bit machines separately to deploy those updates. Oh, and you might try checking the "execmgr.log" log on the client machine for clues what may be going wrong if the logs presented to you within the ConfigMgr console aren't helping (each advertisement has a log)... Quote Share this post Link to post Share on other sites More sharing options...
Hi...
I'm deploying ForeFront Endpoint, that works fine, I had to uninstall it on one machine and now it doesn't reinstall.
One more thing, I'm deploying Forefront definition updates, they install fine on 32 bit machines but not on 64 bit.
I'm a SCCM virgin so go easy on the flame
I would include the logs but I really don't know what log to look at on the client side why the update failed.
I can see in the event viewer on the 64 bit machines: "The contents for update e1df4ef2-2882-4613-87da-49b6fe29a63f could not be located."
I have a bunch of those, the update source share has the correct perms, thinking it has more to do with the machines being 64 bit since
they are the only machines having this issue
Thanks...
Share this post
Link to post
Share on other sites