Comments for Richard Balsley

Comment on Using Your Distribution Points for FEP Definitions with the Software Update Automation Tool – Forefront Endpoint Protection 2010 Update Rollup 1 by Michael V

Michael V — Thu, 17 May 2012 20:35:05 +0000

It is NOT easy to install and get working!

Comment on Using Your Distribution Points for FEP Definitions with the Software Update Automation Tool – Forefront Endpoint Protection 2010 Update Rollup 1 by Michael V

Michael V — Thu, 17 May 2012 20:18:04 +0000

One more thing that helped fix mine.

14.Click Next at the Download Location step (unless you have downloaded the defs manually to a location on the local network)

In my case this needed to be directed at my Source Files for the FEP Defs because it needed to know after sync and after the SUAT tool ran that there was new files out there to be installed.

Comment on Using Your Distribution Points for FEP Definitions with the Software Update Automation Tool – Forefront Endpoint Protection 2010 Update Rollup 1 by Michael

Michael — Tue, 15 May 2012 20:07:28 +0000

UPDATE: This is potentially the issue many of you are having.

In addition to increasing the Syncronization of Patches from once per week to once per 4 hours, I was having SUAT issues where it would fail to run. I changed \AdminUI\bin\SoftwareUpdateAutomation.exe where was E:\ to being \\sccmserver\e$\ and the task ran successfully and life is good!

Hope this helps some of you.

Comment on A Simple Tip to Test Software Installation Using the Local System Account by Test Your Command-Line Before Pushing a Package! – Adventures in Software Deployment

Mon, 14 May 2012 23:27:49 +0000

[...] -Derived from Richard Balsley’s post, found here [...]

Comment on Using Your Distribution Points for FEP Definitions with the Software Update Automation Tool – Forefront Endpoint Protection 2010 Update Rollup 1 by Michael

Michael — Mon, 14 May 2012 13:47:11 +0000

I may have found my issue as well. While the SoftwareUpdateAutomation.exe Tool (SUAT) runs in the background, it does nothing to pull the FEP Defs from the internet, it simply gets them ready for deployment once SCCM downloads them. So, in order for this to work as advertised, we had to bump our Software Update Point Component Syncronization up to happen more frequently (sooner than we had it looking to the alternative source). I am still confirming this has fully fixed our issue, but some of you may want to explore this as a resolution as well.

Comment on Using Your Distribution Points for FEP Definitions with the Software Update Automation Tool – Forefront Endpoint Protection 2010 Update Rollup 1 by Dan

Dan — Mon, 14 May 2012 12:53:18 +0000

Hi Michael,

I managed to get it working. When creating the deployment template make sure the duration is set to something large like 2 weeks. I had it set to two hours and didn't realize this meant the updates where only available for 2 hours.

Comment on Using Your Distribution Points for FEP Definitions with the Software Update Automation Tool – Forefront Endpoint Protection 2010 Update Rollup 1 by Michael

Michael — Fri, 11 May 2012 17:46:18 +0000

Well, I have the same thing. After following this document all seems to work as it should EXCEPT FEP Def Files are coming from the update.microsoft.com instead of my file share on SCCM Server. I also noticed that looking at my Package Source Location, no new Def Files are there.

Any help would be appreciated. I am opening a case with MS and will post if I get a resolution.

Thanks

Comment on SCCM: How to Determine Content Download to Cache Issues by Bill

Bill — Sat, 05 May 2012 00:14:22 +0000

Great find! I've been fighting with a few packages that I've had this issue with. I went though and looked at the source packages and sure enough there was at least 1 "+" character in each one! What was really stumping me was that if the package ran as part of a Task Sequence it was downloaded fine, but when it was run form Run Advertised Programs it would either not start downloading or stop at some percentage. Thanks so much!

Comment on A Simple Tip to Test Software Installation Using the Local System Account by Mark

Mark — Fri, 27 Apr 2012 15:40:29 +0000

I put PsExec in the Program Files (x86) folder and created a desktop shortcut on my test machine with the following target (sub in domain/admin account as needed):

C:\Windows\System32\runas.exe /user:[domain]\[admin account] "c:\program files (x86)\psexec -si cmd.exe"

The normal account I use on the test machine doesn't have admin privs, so this speeds up the process by a decent amount.

Comment on How to Turn Off Compression in Configuration Manager 2007 Software Distribution by ConfigMgr Admin

ConfigMgr Admin — Thu, 05 Apr 2012 14:23:49 +0000

Mate, show us some more tips! This is gold ;)