SamuelOlssonNobia
New Member
- Messages
- 1
- Reaction score
- 1
- Points
- 3
Hi,
We have an SCCM enviroment containing 6000+ devices and have recently run into an issue when troubleshooting a critical deployment of an application update.
We've discovered a number of devices where the deployment failed and have been able to resolve most of them by reinstalling the client and fixing WMI, but we have a few devices where nothing seems to help.
After manually installing the client we can see that ccmsetup exits with code 0, the device checks in fine and the device starts gathering the log files at a steady pace. But this is where the problem starts. AppDiscovery, AppIntenteval and AppEnforce logs aren't created no matter how we try. We've run all possible evaluation cycles, re-installed the client multiple times (both from the console and manually) and tried fixing WMI.
Any ideas how to fix would be greatly appreciated.
We're running Configuration Manager 2303 with client version 5.00.9106.1000
Br
Samuel
We have an SCCM enviroment containing 6000+ devices and have recently run into an issue when troubleshooting a critical deployment of an application update.
We've discovered a number of devices where the deployment failed and have been able to resolve most of them by reinstalling the client and fixing WMI, but we have a few devices where nothing seems to help.
After manually installing the client we can see that ccmsetup exits with code 0, the device checks in fine and the device starts gathering the log files at a steady pace. But this is where the problem starts. AppDiscovery, AppIntenteval and AppEnforce logs aren't created no matter how we try. We've run all possible evaluation cycles, re-installed the client multiple times (both from the console and manually) and tried fixing WMI.
Any ideas how to fix would be greatly appreciated.
We're running Configuration Manager 2303 with client version 5.00.9106.1000
Br
Samuel
