arussell Posted September 11, 2012 Report post Posted September 11, 2012 Hi, Need some advice please since the logs are not helping me here. Attempts to deploy software packages toclients are failing, the content does not even download to the local cache on the clients, no folders or content created. The packages are distributed to the DP's fine and the client can access the share without any issue. When sending a mandatory assignment to deploy the software, the client accepts the program but then simply displays 'Program received - no further status' The ContentTransferManager.log only shows entry 'In CTM startup task' CAS.log only shows: CContentAccessService::Initialize ContentAccess 05/09/2012 22:45:23 3512 (0x0DB8) CDownloadManager::InitializeFromWmi ContentAccess 05/09/2012 22:45:23 3512 (0x0DB8) CCacheManager::InitializeFromWmi ContentAccess 05/09/2012 22:45:23 3512 (0x0DB8) CacheConfig::InitializeFromWmi ContentAccess 05/09/2012 22:45:23 3512 (0x0DB8) CacheConfig::InitializeFromWmi succeeded ContentAccess 05/09/2012 22:45:23 3512 (0x0DB8) Cached CCM (user, session) is: (S-1-5-21-795088118-1101373457-3817326564-500,2). ContentAccess 05/09/2012 22:45:23 3512 (0x0DB8) We have a primary site and a secondary site. The secondary site is not a protected site system. Can you please advice on the following: How can I troubleshoot why the packages are not downloaded to the cache since the cas.log gives me nothing? Software deploy to other sites works fine Thanks Alistair Quote Share this post Link to post Share on other sites More sharing options...
KeithDib Posted September 12, 2012 Report post Posted September 12, 2012 Hi Can you give more details of the package? Also check your package is downloaded to the client cache folder Keith Quote Share this post Link to post Share on other sites More sharing options...
arussell Posted September 12, 2012 Report post Posted September 12, 2012 Hi Keith, Basically all the packages are fine. We have around 29 other sites and if we push any package to the machines in these they receive it and install fine. Boundaries are configured using IP subnets with the exception of the secondary site which is with IP address range. There is a configuration error somewhere that is preventing any packages being installed from the secondary DP on any clients assigned within the secondary site boundary. Nothing appears in the local client cache folder and logs show nothing useful. These clients simply receive the advertisements but never run them. It may be something simple but I cant seem to find the problem which is very frustrating. Alistair Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted September 12, 2012 Report post Posted September 12, 2012 What does it say in the execmgr.log? Quote Share this post Link to post Share on other sites More sharing options...
arussell Posted September 13, 2012 Report post Posted September 13, 2012 Hi Peter, The execmgr.log on the client machine goves little or no indication as to where the problems lies. The advertisement process appears to begin but never runs, please see log extract below for an example: Received creation notification for user 'S-1-5-18'. execmgr 9/11/2012 11:18:55 AM 5752 (0x1678) Policy arrived for parent package P010003B program Copy shortcuts execmgr 9/11/2012 11:18:55 AM 5752 (0x1678) Raising event: [sMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramOfferReceivedEvent { AdvertisementId = "P01200BE"; ClientID = "GUID:0DCB28A3-53CA-4396-BD7E-E2C036B15DB5"; DateTime = "20120911101855.141000+000"; MachineName = "TEST107"; ProcessID = 2660; SiteCode = "P01"; ThreadID = 5752; }; execmgr 9/11/2012 11:18:55 AM 5752 (0x1678) Now that I think about it, the advertisement process obviously is not working properly as mandatory assigments fail to run and scheduled assignements never gets displayed in the run advertised programs console. When running OSD, any task sequences that involve deploying software from the secondary site server work fine and software is successfully installed. It just doesnt work when deploying software packages to the secondary sites clients. The same packages work fine when deployed to primary site clients, though this will be getting deployed from the primary DP. Thanks Alistair Quote Share this post Link to post Share on other sites More sharing options...