I have a few clients that can't be managed due to the same error on both of them, I've fixed everything else I can think of and still no joy. I look in the log and I have an error saying Couldn't verify 'C:\WINNT\system32\ccmsetup\wimgapi.msi' authenticode signature without revocation ccmsetup 2/25/2010 6:50:29 AM 2100 (0x0834)IsMSSignedByFileHash Can't verify that file 'C:\WINNT\system32\ccmsetup\wimgapi.msi' is digitally signed. ccmsetup 2/25/2010 6:50:29 AM 2100 (0x0834)Anyone have any idea on this, it driving me crazy, thanks!!

Hi,What version of your ConfigMgr ... SP1/SP2 ? What version of OS clients that have this pb ? ConfigMgr agent has succefully installed on other machines ? Wich method do you use to install client (push, manual, GPO, ...) ? See this link : http://technet.microsoft.com/en-us/library/bb693607.aspxThank's.Bechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

The configuration manager is R2 SP2 and the client version that is on the setup log is Version: 4.0.6487.2000, I have tried the client push and manual install with no luck.

Hi,Your client machines are Windows Xp SP2 or later, Windows vista or Windows 7 ?On ConfigMgr Server, verify that the i386 folder from C:\Program Files\Microsoft Configuration Manager\Client still exists. Check if any firewall exist between Server and client machines. Also, BITS is used to download the required files from the Management Point. Check BITS with the bitsadmin.exe tool for queued jobs or backlogs. bitsadmin.exe /list /allusers (show queued jobs) bitsadmin.exe /reset /allusers (deletes all the jobs) And Restart the ccmsetup again. Thank's. Bechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

Great, this is a place to start, ok this is a windows 2000 box and we have been trying to get them all out of our network for some time now, I know for a fact that all of the windows firewalls are turned off and there are no firewalls in between these servers. I don't have bitsadmin installed so I suppose I will need to find that, do you have a link to that install by chance?I have done a reboot to try and clear anything that might be interrupting the install and tried it right after the reboot with no luck, does bits not clear the jobs after a reboot? Ok get back with me, thanks!!!

Hi,Windows 2000 must be Service pack 4 before installing ConfigMgr Client. For more information : http://technet.microsoft.com/en-us/library/ee344146.aspxAlso, have you checked that the i386 folder from <Installation path>\Microsoft Configuration Manager\Client still exists ?Thank's.Bechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

Ok, sorry for the long time between entering replies, been a busy day, ok it is on SP4 and I am not entirely sure about the second question, the install logs are in the ccmsetup folder which still exists, but I don't know what else you would like.

Ok thank's.On your ConfigMgr Server, checked that the i386 folder from <Installation path>\Microsoft Configuration Manager\Client still exists.Also on your ConfigMgr Server, under IIS/Default Web Site/CCM_Client checked that the i386 and BITS20 still exists (and no empty). If you have a Windows XP SP2 or SP3 machine, then try to install on it the ConfigMgr Client. If the pb still exist, from SCCM DVD try to copy CLIENT folder from \SMSSETUP\ to <Installation path>\Microsoft Configuration Manager\ on your SCCM Server, and try to install client again.Bechir Gharbi. MCP, MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

Ok, all the folders are there and I have installed an agent with no issues on a different windows XP system and tried an install from the DVD files, any other ideas? Still spitting out the same error, and I also deleted the ccmsetup folder and recreated it with no luck.

i have the same issue with all the setups, SCCM r2 sp2 , client issue windows 2000 sp2 server. all paths are there. was there ever a solution found? thanks Pete

client issue windows 2000 sp2 server. Windows 200 needs to be at SP4, otherwise it's not supported. See the link Bechir already provided.

Same issue here... Client is Windows 2000 SP4, have done a clean reboot, all server-side files must be OK as we use client push all the time when necessary. ConfigMgrr server version is R3 SP2. Not sure if now that W2K is not supported that the ConfigMgr clients on W2K is also not supported?