Tag Info

New answers tagged

0

While not specifically related to seeing this error code while running a Software Update Deployment Evaluation Cycle, other users have reported success using CCMCLEAN from the SMS 2003 toolkit to completely remove the ConfigMgr client and then re-install the client to resolve the same error code during the initial client installation. Please note that this ...


0

Open the SCCM Console, Assets and Compliance and Devices Right-click the computer receiving the error and select Install Client In the Installation Options for the Client Push, make sure to check the Uninstall existing Configuration Manager client before the client is installed checkbox


1

Is the experience common across all clients, or only a selection of clients? -If all clients, I would check the content status of your update packages -If only some clients, I would look at your boundary group configuration. I wasn't able to find much info on that particular error, as I'm sure you were not as well. CMTrace.exe (you should definitely be ...


0

After reading the source code I figured it out. Debian Squeeze is now named "oldstable". Here is the relevant section for Debian Squeeze: // Automatically upgrade packages from these (origin, archive) pairs Unattended-Upgrade::Allowed-Origins { "${distro_id} oldstable"; "${distro_id} ${distro_codename}-security"; "${distro_id} ...


1

Subscribe to Critical Patch Update Alert E-mails: http://www.oracle.com/technetwork/topics/security/securityemail-090378.html



Top 50 recent answers are included