David (who didn't wish to sign up for this forum) kindly emailed me today with the following info, I'm note quite sure about all of it, since my installs went well, and David used the RTM EVAL download instead of the MSDN/TechNet download I documented. Pay particularly close attention to what I bolded below. Can you try that and see if you have reliable automatic updates?
Hi, Good post. I have had some success with the forefront client on WHS and now on WHS 2011. I have used the command line method to install, very quick and easy.
In the Forefront download (the one I have from technet is labeled FCS_RTM_EVAL_en-us_1703.0.iso), drill down to the client install directory, to the folder with CLIENTSETUP.exe, (or x64/CLIENTSETUP.exe). Save those directories, the rest of the disk is unneeded.
I usually copy the directory to the root of the C:drive so it is easy to navigate to (c:\\x64).
Then I copy and paste:
clientsetup.exe /I \ "C:\Program Files\MS Forefront Client" /L "C:\Program Files\MS Forefront Client\logs" /nomom
The only problem that I have had is that it does not always auto update itself. I had found that sometimes it would and sometimes not. Going to the online manual update page would also not bring joy even after installing 20 or more manual downloads. Then sometimes it would be mysteriously updated a day or two later.
The trick turned out to be getting Windows Update to be configured to also check for other Microsoft product updates. Go to the Windows Update screen, find and click on the Change Settings link. This should give you a view of option of what and when to downlaod Updates. Make sure that the Microsoft Update checkbox is selected. Thats it. You should get any and all needed updates for the Forefront Client the next time you have it Check for Updates.
I went the the Home Server site to share this, but I apparently need a Twitter account to post. Too complicated for me. Let me know if this helps. If it does please feel free to share it with the world. It was devilishly hard for me to discover this, and I would have loved to find a clean, simple post like the kind you make. Thanks,
If there's good info in this email, I'll go ahead and add it to my instructions, of course. But getting the forum reader's feedback is key.
After posting last night I read thru some of the material I had collected -- in particular the info on TechNET.
One article in particular: http://technet.micro...y/bb625083.aspx
involved installing FF on home computers. A few parts of that article are worth quoting IMHO.
===== Configuring your computer to use Microsoft Update
For the home computer to receive definition updates, you must configure it to use Microsoft Update. It is highly recommended you do this first, so that the Client Security agent can immediately connect to Microsoft Update and get definition updates.
The steps to do this are different for Windows Vista and Windows XP.
To configure a computer running Windows Vista to use Microsoft Update
Click Start, point to All Programs, and click Windows Update.
In the Windows Update window, next to You receive updates, verify that it states For Windows and other products from Microsoft Update Service.
The presence of this statement indicates that the computer is configured to use Microsoft Update. No further steps are necessary.
If the statement For Windows only is present, click Get updates for more products.
If the User Account Control dialog box appears, click Continue.
After again reading this [note the section highlighted and underlined] I realized I should have set WHS2011 up for Microsoft updates before I did your install. I went into Windows update and made the change which you can see below highlighted.
I believe this has fixed the issue I may have had but I plan to wait a couple days before coming to a conclusion.
As of right now FF is:
Is that the client version you're seeing in your setup?
The rest of the article in TechNET confirms "Dave's" process. I plan to test that step with another Clone later this week or weekend.
Here's the relevant section IMHO from http://technet.micro...y/bb625083.aspx
Distributing the Client Security agent installation program
The Client Security agent installation program, clientsetup.exe, is located in the Client folder on the Client Security installation CD. Clientsetup.exe calls the Windows Installer files needed for the Client Security components. For this reason, when distributing the Client Security agent to home users, you must distribute both the appropriate processor platform version of clientsetup.exe and the supporting MSI installer files.
The following table lists the files you need to include for each processor platform when distributing the Client Security agent for home use.
Files needed for x86-based computers (from the Client folder)
Windowsxp-kb914882-x86-LNG.exe where LNG is the language of the operating system installation
Files needed for x64-based computers (from the Client\x64 folder)
Installing the Client Security agent
To install the Client Security agent in a home-use scenario, you must install it without the reporting and alerting component.
To install the Client Security agent on Windows Vista without the reporting and alerting component
On computers running Windows Vista, click Start, point to All Programs, and then click Accessories.
Right-click Command Prompt, and then click Run as administrator.
In the User Account Control dialog box, click Continue.
In the Command Prompt window, change to the location of the Client Security Client folder, type the following command, and then press ENTER:
I hope you find this helpful! [Note the tables in the TechNET notes didn't copy over well so I had to fiddle with the file lists]
Edited by Joe_Miner, 03 October 2011 - 07:40 PM.