Wild guess. Have you checked for alternate data streams on the files? I had an issue where client notification wouldn't install on a primary, had to unstream all the files and then sitecomp could install it.
http://technet.microsoft.com/en-us/sysinternals/bb545027.aspx Streams.exe Thank you. Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Mark Mears Sent: Friday, October 25, 2013 11:36 AM To: [email protected] Subject: [mssms] Hash mismatch on SCEPInstall.exe (fresh client install) On many fresh client installs, the ccmsetup.log indicates a problem with the hash on ScepInstall.exe. The files in the Client folder on the primary site have been compared with other working sites and they are identical. Consequently client installs are failing because once it hits the error, ccmsetup bails. Troubleshooting steps we have already done: Client install from CAS console fails with hash mismatch on SCEPInstall.exe. We have tried directly copying the source files locally and using the /source:<Path> statement in the manual install scenario with no difference. We have copied the files from a different site with no change. We have removed AV from scanning on the folder and the ccmsetup.exe process with no change. Does anybody have any ideas how this can be remedied? Thanks, ________________________________ Mark Mears [email protected]<mailto:[email protected]%0d> Phone: (757) 945-2651 [cid:[email protected]]<http://www.cireson.com/> [cid:[email protected]]<http://twitter.com/teamcireson> Check out our System Center App Store: www.cireson.com/app-store ________________________________ This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.
<<inline: image001.png>>
<<inline: image002.jpg>>
