Wrong FSP configured in client configuration settings
Hi All,
I have pushed ccm client through client push method and found the installation were successful but showing "sending
with winhttp failed; 80072ee7" error, I checked and found that the FSP is configured wrongly.
If I set the FSP correctly, Will I need to re-push the CCM client for all the machines installed successfully previously???
Kindly suggest me as soon as possible.Stephene
June 7th, 2012 12:44am
Client commandlines are used when installing the client. If you modify the FSP it will work nicely for all new clients that you install. The FSP is written to hklm\software\microsoft\ccm\FSP\hostname. Changing that value should reflect on existing clientsKent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2012 2:04am
Client commandlines are used when installing the client. If you modify the FSP it will work nicely for all new clients that you install. The FSP is written to hklm\software\microsoft\ccm\FSP\hostname. Changing that value should reflect on existing clientsKent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund
June 7th, 2012 2:07am
Hi Kent,
Thanks for your replay.Need one more query.
let me know what about existing installed clients,also how to make the changed FSP value to reflect in
existing installed clientsStephene
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2012 2:26am
Hello Stephne343
As kent,rightly pointed out,changing the value in the registry should help resolve this issue.the changes will be effective depending on the polling period which is set,which is by default 24 hours.or you can force the same on the clients by having the Machine
policy evaluation option under Client Actions when you right click on the client.
let me know if that helps.
Thanks
Arvind
June 7th, 2012 2:51pm