How to Deploy the FEP 2010 Client Via OSD and Test Deployment

How to Deploy the FEP 2010 Client Via OSD and Test Deployment


To deploy the FEP2010 client via OSD
  1. In the tree pane, expand Site Database, expand Computer Management, expand Software Distribution, expand Packages, expand Microsoft Corporation FEP-Deployment 1.0, and highlight Programs.
  2. From the Actions menu, click New Program.
  3. In the Name field, type a name for the program (for example, InstallFEPviaOSD). 
    1. Note: To ensure that the default FEP collection works, the program name must start with "Install".
  4. In the Command line, type:  "FEPInstall.exe /s /q "
  5. Change Run to Hidden.
  6. Click Next.
  7. In Requirements, in the Estimated disk space field, type "200" and select MB from the drop down list.
  8. In Maximum allowed run time (minutes), type "60".
  9. Click Next.
  10. In Environment, for Program can run, change it to Whether or not user is logged.
  11. Click Next.
  12. In Advanced, check Suppress program notifications and Allow this program to be installed from the Install Software task sequence without being advertised
  13. Click Next.
  14. Click Next.
  15. Click Finish.
  16. Click Next at the Summary page.
  17. On the Wizard Completed page, Click Close.
  18. Go back to the Microsoft Corporation FEP-Deployment 1.0 pane, and right-click Update Distribution Points.
  19. Click Yes when asked "Are you sure you want to update all distribution points?"
  20. In the tree pane, expand Site Database, expand Computer Management, expand Operating System Deployment and expand Task Sequences.
  21. Select your task.
  22. In the Task Sequence Editor, click Add -> General -> Install Software.
  23. Select Install a single application.
  24. In Package, click Browse…  and select Microsoft Corporation FEP-Deployment 1.0.
  25. In Program, select the InstallFEPviaOSD program that was created in previous steps.
  26. Click OK to save and close the window.

  Recommendation: To test the deployment

  1. Create a Custom task in the Task Sequence.
  2. In the Task Sequence Editor, click Add General Install Software.
  3. Select Install a single application.
  4. In Package, click Browse…  and select Microsoft Corporation FEP-Deployment 1.0.
  5. In Program, select the FEPviaOSDInstall program that was created in previous steps.
  6. Click OK to save and close the window.
  7. In the Task Sequence, select the newly created test task.
  8. From the Actions menu, select Advertise, and then select a test collection with a designated test client.
  9. Click the Star in the Mandatory assignments, and then click OK in the Schedule window.
  10. Finish the wizard with default parameters.
  11. Usually within 5 minutes the program should be installed.
  12. From SCCM Toolkit v2, use the PolicySpy to monitor the policy; press Ctrl+R to Request Machine Assignments.
  13. For more information on the deployment process at the client side, view the following logs:
    1. Execmgr.log
    2. Smsts.log -- This log will be available only when deployment starts.

This article is based on information from Daniel Klepner and Kurt Sarens.


REFERENCES

For more information about how to setup OSD, see the following articles:

1. http://blogs.technet.com/b/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx

2. http://blogcastrepository.com/blogs/brian_tucker/archive/2006/07/11/1680.aspx

 

 

 

 

 

 

 

 

 



 

Sort by: Published Date | Most Recent | Most Useful
Comments
  • Excellent article, thanks for sharing. It would be good to include the error that customers hit when trying to do this, to increase searchability of this wiki article.

  • I have a question with respect to the naming of the program that is to be created.  In step 3 you say to name it something that starts with "Install" to ensure the default FEP collection works.  Yet on step 25 you have Install at the end of the name of the program that was created.  Was this a transposition or does one of the steps have an error in it?

  • Thanks AKlein. I had transposed the program name in 25. Updated the article accordingly.

Page 1 of 1 (3 items)