Frustrated, turning here for help again. I have a couple issue that I believe are all related. My only problem is that I think I am caught in a "chicken and egg" situation, where I have to get the right order of things fixed before moving on, so here goes.Background info:Environment:ConfigMgr 2007 R2 running on Server 2003 64-bit R2 SP2Clients are mostly XP SP2 and SP3, very few Windows 7 (IT only for testing) - approximately 700 totalSCCM server is up-to-date with all Windows updatesMain server has the following roles on it: OOB Service Point (not configured yet) Component Server Distribution Point Fallback Status Point Management Point PXE Service Point Reporting Point Server locator Point Site Server Site System Software Update PointAlso, it has WSUS 3.0 SP2 installed (was installed with default configuration)Most sites have Branch DPs, and there are only two other full DPs (but none are configured as a parent/child/replica/etc.)On 10/8/09 and 10/14/09 I had to install several hotfixes to the server, as well as do site resets. Prior to this, the SUP client install worked fine. Within the next few days, I noticed nothing strange, as in the SUP Clinet Installation properties, it showed the published and available versions as the same.One of the hotfixes I had installed was to allow for support of Windows 7 and Server 2008 R2 clients (http://support.microsoft.com/default.aspx/kb/974236/en-us). This also required a site reset. After the site reset on this one, everything seemed fine.Yesterday(10/26/09), I was going through checking on various things, and noticed that the SUP Client Installation no longer had a client published. It prompted me to publish a client (available is 4.00.6221.1000) and I told it yes. I went in to check on it throughout the day yesterday, and each time it prompted me to publish the client, which I told it to do. It still would not publish it, even overnight. To the best of my knowledge, there have been no GPO updates/changes. I went in and looked at a couple of the logfiles:Old WCM logfile (when everything appeared to be working)Trigger event array index 1 ended. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)File notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)File notification triggered WCM Inbox. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>ab62c5bd-5539-49f6-8aea-5a114dd42314</Id>~~ <Id>26bb6be1-37d1-4ca6-baee-ec00b2f7d0f1</Id>~~ <Id>84a54ea9-e574-457a-a750-17164c1d1679</Id>~~ <Id>0a487050-8b0f-4f81-b401-be4ceacd61cd</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>a0dd7e72-90ec-41e3-b370-c86a245cd44f</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>4217668b-66f0-42a0-911e-a334a5e4dbad</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>e164fc3d-96be-4811-8ad5-ebe692be33dd</Id>~~ <Id>60916385-7546-4e9b-836e-79d65e517bab</Id>~~ <Id>c8a4436c-1043-4288-a065-0f37e9640d60</Id>~~ <Id>f61ce0bd-ba78-4399-bb1c-098da328f2cc</Id>~~ <Id>d22b3d16-bc75-418f-b648-e5f3d32490ee</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>4e487029-f550-4c22-8b31-9173f3f95786</Id>~~ <Id>e3fde9f8-14d6-4b5c-911c-fba9e0fc9887</Id>~~ <Id>06bdf56c-1360-4bb9-8997-6d67b318467c</Id>~~ <Id>7e5d0309-78dd-4f52-a756-0259f88b634b</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ae4483f4-f3ce-4956-ae80-93c18d8886a6</Id>~~ <Id>c5f0b23c-e990-4b71-9808-718d353f533a</Id>~~ <Id>22bf57a8-4fe1-425f-bdaa-32b4f655284b</Id>~~ <Id>8bc19572-a4b6-4910-b70d-716fecffc1eb</Id>~~ <Id>7cf56bdd-5b4e-4c04-a6a6-706a2199eff7</Id>~~ <Id>79adaa30-d83b-4d9c-8afd-e099cf34855f</Id>~~ <Id>48ce8c86-6850-4f68-8e9d-7dc8535ced60</Id>~~ <Id>6d992428-3b47-4957-bb1a-157bd8c73d38</Id>~~ <Id>504ae250-57c5-484a-8a10-a2c35ea0689b</Id>~~ <Id>35c4463b-35dc-42ac-b0ba-1d9b5c505de2</Id>~~ <Id>d6f0ca45-14e4-4d82-9183-020a0a157cd3</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>e0789628-ce08-4437-be74-2495b842f43b</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>68c5b0a3-d1a6-4553-ae49-01d3a7827828</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)Configuration successful. Will wait for 1 minute for any subscription or proxy changes SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:02:20 PM 5220 (0x1464)Waiting for changes for 2 minutes SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:03:20 PM 5220 (0x1464)Trigger event array index 1 ended. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:03:20 PM 5220 (0x1464)File notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:03:20 PM 5220 (0x1464)File notification triggered WCM Inbox. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:03:20 PM 5220 (0x1464)Waiting for changes for 2 minutes SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:03:20 PM 5220 (0x1464)Wait timed out after 2 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:44 PM 5220 (0x1464)Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)The installed WSUS build has the <site name>id and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:49 PM 5220 (0x1464)Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:58 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:58 PM 5220 (0x1464)Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:59 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:59 PM 5220 (0x1464)Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:05:59 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:06:04 PM 5220 (0x1464)Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>ab62c5bd-5539-49f6-8aea-5a114dd42314</Id>~~ <Id>26bb6be1-37d1-4ca6-baee-ec00b2f7d0f1</Id>~~ <Id>84a54ea9-e574-457a-a750-17164c1d1679</Id>~~ <Id>0a487050-8b0f-4f81-b401-be4ceacd61cd</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>a0dd7e72-90ec-41e3-b370-c86a245cd44f</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>4217668b-66f0-42a0-911e-a334a5e4dbad</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>e164fc3d-96be-4811-8ad5-ebe692be33dd</Id>~~ <Id>60916385-7546-4e9b-836e-79d65e517bab</Id>~~ <Id>c8a4436c-1043-4288-a065-0f37e9640d60</Id>~~ <Id>f61ce0bd-ba78-4399-bb1c-098da328f2cc</Id>~~ <Id>d22b3d16-bc75-418f-b648-e5f3d32490ee</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>4e487029-f550-4c22-8b31-9173f3f95786</Id>~~ <Id>e3fde9f8-14d6-4b5c-911c-fba9e0fc9887</Id>~~ <Id>06bdf56c-1360-4bb9-8997-6d67b318467c</Id>~~ <Id>7e5d0309-78dd-4f52-a756-0259f88b634b</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ae4483f4-f3ce-4956-ae80-93c18d8886a6</Id>~~ <Id>c5f0b23c-e990-4b71-9808-718d353f533a</Id>~~ <Id>22bf57a8-4fe1-425f-bdaa-32b4f655284b</Id>~~ <Id>8bc19572-a4b6-4910-b70d-716fecffc1eb</Id>~~ <Id>7cf56bdd-5b4e-4c04-a6a6-706a2199eff7</Id>~~ <Id>79adaa30-d83b-4d9c-8afd-e099cf34855f</Id>~~ <Id>48ce8c86-6850-4f68-8e9d-7dc8535ced60</Id>~~ <Id>6d992428-3b47-4957-bb1a-157bd8c73d38</Id>~~ <Id>504ae250-57c5-484a-8a10-a2c35ea0689b</Id>~~ <Id>35c4463b-35dc-42ac-b0ba-1d9b5c505de2</Id>~~ <Id>d6f0ca45-14e4-4d82-9183-020a0a157cd3</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:06:04 PM 5220 (0x1464)Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>e0789628-ce08-4437-be74-2495b842f43b</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>68c5b0a3-d1a6-4553-ae49-01d3a7827828</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:06:04 PM 5220 (0x1464)Configuration successful. Will wait for 1 minute for any subscription or proxy changes SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:06:04 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:07:04 PM 5220 (0x1464)Successful published and approved package a331d4c8-8ba4-4791-a35f-9fa475a7a0d4 - 0 for Install to a0a08746-4dbe-4a37-9adf-9e7652c0b421, Deadline UTC time= 7/2/2009 6:08:20 AM SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:07:04 PM 5220 (0x1464)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:07:04 PM 5220 (0x1464)completed unpublishing previous clients SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:07:04 PM 5220 (0x1464)completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:07:04 PM 5220 (0x1464)Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 10/14/2009 2:07:04 PM 5220 (0x1464)Current WCM logfile (broken)Wait timed out after 10 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:09 AM 4412 (0x113C)Timed Out... SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)The installed WSUS build has the <site name>id and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:14 AM 4412 (0x113C)Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:23 AM 4412 (0x113C)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:23 AM 4412 (0x113C)Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:24 AM 4412 (0x113C)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:24 AM 4412 (0x113C)Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:25 AM 4412 (0x113C)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:30 AM 4412 (0x113C)Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>ab62c5bd-5539-49f6-8aea-5a114dd42314</Id>~~ <Id>26bb6be1-37d1-4ca6-baee-ec00b2f7d0f1</Id>~~ <Id>84a54ea9-e574-457a-a750-17164c1d1679</Id>~~ <Id>0a487050-8b0f-4f81-b401-be4ceacd61cd</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>a0dd7e72-90ec-41e3-b370-c86a245cd44f</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>4217668b-66f0-42a0-911e-a334a5e4dbad</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>e164fc3d-96be-4811-8ad5-ebe692be33dd</Id>~~ <Id>60916385-7546-4e9b-836e-79d65e517bab</Id>~~ <Id>c8a4436c-1043-4288-a065-0f37e9640d60</Id>~~ <Id>f61ce0bd-ba78-4399-bb1c-098da328f2cc</Id>~~ <Id>d22b3d16-bc75-418f-b648-e5f3d32490ee</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>4e487029-f550-4c22-8b31-9173f3f95786</Id>~~ <Id>e3fde9f8-14d6-4b5c-911c-fba9e0fc9887</Id>~~ <Id>06bdf56c-1360-4bb9-8997-6d67b318467c</Id>~~ <Id>7e5d0309-78dd-4f52-a756-0259f88b634b</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ae4483f4-f3ce-4956-ae80-93c18d8886a6</Id>~~ <Id>c5f0b23c-e990-4b71-9808-718d353f533a</Id>~~ <Id>22bf57a8-4fe1-425f-bdaa-32b4f655284b</Id>~~ <Id>8bc19572-a4b6-4910-b70d-716fecffc1eb</Id>~~ <Id>7cf56bdd-5b4e-4c04-a6a6-706a2199eff7</Id>~~ <Id>79adaa30-d83b-4d9c-8afd-e099cf34855f</Id>~~ <Id>48ce8c86-6850-4f68-8e9d-7dc8535ced60</Id>~~ <Id>6d992428-3b47-4957-bb1a-157bd8c73d38</Id>~~ <Id>504ae250-57c5-484a-8a10-a2c35ea0689b</Id>~~ <Id>35c4463b-35dc-42ac-b0ba-1d9b5c505de2</Id>~~ <Id>d6f0ca45-14e4-4d82-9183-020a0a157cd3</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:30 AM 4412 (0x113C)Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>e0789628-ce08-4437-be74-2495b842f43b</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>68c5b0a3-d1a6-4553-ae49-01d3a7827828</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:30 AM 4412 (0x113C)Configuration successful. Will wait for 1 minute for any subscription or proxy changes SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:41:30 AM 4412 (0x113C)Successfully connected to server: <fqdn server name>, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)PublishApplication(a331d4c8-8ba4-4791-a35f-9fa475a7a0d4 - 0) failed with error System.In<site name>idOperationException: Verification of file signature failed for file: d:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\ccmsetup-sup.cab~~ at Microsoft.UpdateServices.Internal.BaseApi.Publisher.ExpandPackageCabFile(String sourceCabFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishSignedPackage(String sourceCabFile, String packageDirectoryName)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, Int32 nRevision, String sSDPFile, String sCabFile) SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)ERROR: Failed to publish sms client to WSUS, error = 0x80131509 SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)STATMSG: ID=6613 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=<main server> SITE=<site name> PID=3496 TID=4412 GMTDATE=Tue Oct 27 15:42:30.297 2009 ISTR0="a331d4c8-8ba4-4791-a35f-9fa475a7a0d4" ISTR1="4.00.6221.1000" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)Failed to publish client with error = 0x80131509 SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)HandleSMSClientPublication failed. SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 10/27/2009 10:42:30 AM 4412 (0x113C)Looked at the WSUSCtrl log, but it says that everything is fine.Timed Out...SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)The installed WSUS build has the <site name>id and supported WSUS Administration DLL assembly version (3.1.7600.226)SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Successfully connected to local WSUS serverSMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Successfully connected to local WSUS serverSMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)There are no unhealthy WSUS Server components on WSUS Server <main sccm server>SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Successfully checked database connection on WSUS server <main sccm server>SMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)Waiting for changes for 57 minutesSMS_WSUS_CONTROL_MANAGER10/27/2009 10:37:01 AM4464 (0x1170)I'm just trying to get the client to publish now, but it doesn't. I've gone through another post that I had that was marked as answered by people other than me, because I was still having issues. Posted in it, never saw responses, so I gave up on that one. I was basically pointed to the same URL multiple times (http://technet.microsoft.com/en-us/library/bb633194.aspx), which makes it sound super-simple. It's not. Or at least, not for me.Am I even really looking in the right logs? There are tons of them (and in our environment at least) in different locations. I'm also having an issue/non-issue with WDS, but believe that it may be tied in with this. Also, those errors aren't specific to one machine, but rather to both PXE points - but PXE deployment works fine. I'll deal with that issue later (unless it's a prereq for this one).Anyone? If I've missed including some info here, by all means ask and as long as it's allowed (internally), I'll post.

Left off a little bit. The Advertised version is still 4.00.6221.1000. I have installed seveal hotfixes that theoretically should have updated it to 4.00.6221.1188, but when I look at the properties for SUP Client installation, it only ha 4.00.6221.1000. Don't know if this info is relevant, but included it as a matter of completeness.

Fixed!!As was stated in the log, PublishApplication(a331d4c8-8ba4-4791-a35f-9fa475a7a0d4 - 0) failed with error System.In<site name>idOperationException: Verification of file signature failed for file: d:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\ccmsetup-sup.cabI do not know how it either got hold of an old .cab file, or why it waited until now to throw a hissy-fit, but the .cab file was apparently not the right one. As stated at the beginning of the post, we are running the R2 build. The .cab file that was failing was about 242KB. The .cab file that was inside the R2 folder was about 250KB. I backed up the 242KB file to another location, then copied the 250KB .cab to its location (<%Windir%>\Program Files (x86)\Microsoft Configuration Manager\bin\i386). Went to publish, and this time it actually did.

Thanks for your post. I ran into the same issue when trying to update our Site to SP2 from R2 version. I was pulling my hair out (what little I have left) until I found your post. Thanks again.

...and me also. After the SP2 update, but much later, we started receiving these errors. Replacing with the file in the SP2 folder fixed it.

We are receiving the same error but I can't seem to find another copy of the .cab file. Is there any place I can download or pull it from?

Just a note, I know this is almost a year old, but someone might gain some help from this. I had this same problem, and found the ccmsetup-sup.cab file located in my c:\windows\$ntuninstallKB977203$ folder. This is from installing that particular hotfix and could have been the root of that problem. Anyway, I copied it over to the <SMS Directory>\bin\i386\ directory after renaming the old ccmsetup-sup.cab file to .old and boom, it worked. probably not best practice, but whatever.