|
During a rollout of the SCCM agent we ran into the following issue: CCMsetup dowloasd normally and started. At the end of the ccmsetup.log we found: the client.msi.log reported the following: Property(S): ROOTDRIVE = C:\ Property(S): CostingComplete = 1 Property(S): OutOfDiskSpace = 0 Property(S): OutOfNoRbDiskSpace = 0 Property(S): PrimaryVolumeSpaceAvailable = 2219873544 Property(S): PrimaryVolumeSpaceRequired = 89797 Property(S): PrimaryVolumeSpaceRemaining = 2219783747 Property(S): INSTALLLEVEL = 1 Property(S): SmsSoftwareDistributionCacheSize.8AE6A59B_5597_4D75_9BFD_7F566BF56500 = 5120 Property(S): CcmAdministratorsGroupName = Administrators Property(S): CcmUsersGroupName = Users Property(S): CcmCreatorOwnerAccountName = CREATOR OWNER Property(S): PrimaryVolumePath = C: MSI (s) (20:8C) [10:01:03:829]: Note: 1: 1708 MSI (s) (20:8C) [10:01:03:829]: Product: Configuration Manager Client -- Installation operation failed. - MSI (s) (20:8C) [10:01:03:829]: Cleaning up uninstalled install packages, if any exist
MSI (s) (20:8C) [10:01:03:829]: MainEngineThread is returning 1603 MSI (s) (20:30) [10:01:03:938]: Destroying RemoteAPI object. MSI (s) (20:C8) [10:01:03:938]: Custom Action Manager thread ending. === Logging stopped: 25/04/2008 10:01:03 === MSI (c) (B8:EC) [10:01:03:938]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (B8:EC) [10:01:03:938]: MainEngineThread is returning 1603 === Verbose logging stopped: 25/04/2008 10:01:03 === The system has a 1.3 Tb C: drive (customer decision) with lots of free space. Apparently Sccm does not know how to handle this enormous amount and stops the installation. Did anybody saw this before and is this a bug? Anybody knows a workaround, because the customer has other systems with the same disk layout. Cheers, Marc
_____________________________
MarcT
|