adv_marhal Posted September 24, 2013 Report post Posted September 24, 2013 Hi! When the SCCM client is installing during the task it seems ok, but we alwasy get a non functional sccm client (the service is disabled). Looking through then ccmsetup.log I found that it looks ok until the installation of the client is to be verified. It ends up with this entries in the ccmsetup log MSI: Åtgärd 14:02:14: InstallValidate. Bekräftar installation ccmsetup 2013-09-24 14:02:14 2520 (0x09D8) File C:\WINDOWS\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603Action:ErrorMessages: Next retry in 1 minute(s)... ccmsetup 2013-09-24 14:02:16 2520 (0x09D8) If I check the Application log I have this entry at the exact same time as the verification fails: Msi Installer Product: Configuration Manager Client - - The disk is full: Out of diskspace - - Volume D:... I have tried with setting the CCMINSTALLDIR to c:\windows\ccm with no change in the result. This fails every time, and if I reinstall the client maually it works fine. Please help! /BR Martin Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 24, 2013 Report post Posted September 24, 2013 it's referring to volume D:\ and you are looking in C:\ so which is it, c or d ? Quote Share this post Link to post Share on other sites More sharing options...
adv_marhal Posted September 24, 2013 Report post Posted September 24, 2013 The d: volume is the dvd player, so it would be nice to have the check on c:. Quote Share this post Link to post Share on other sites More sharing options...
adv_marhal Posted September 25, 2013 Report post Posted September 25, 2013 Just to clearify, my c: volume is the only disk volume in the machine. The thing that I think is a bit strange is that when the verification runs and fails the application log show entries sugesting that the Config mgr client is trying to verify it's installation on the d: volume. If thats right (that it tries to verify the install on D: and I can't see why it shouldn't be right) why is it doing that and how to change this behavior. Quote Share this post Link to post Share on other sites More sharing options...