> System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors > : Query execution failed for dataset ‘PackageName’.
> : An error has occurred during report processing. Any help is appreciated.Īn error has occurred during report processing. I used this recently and noticed below while running the report. I am not sure if this actively montiored. You can download this free report by visiting our product page. The Asset – Compatibility Check report is available in the Report / Asset Section. The only thing you need to do is to select your Compatibility package and run the report ! We also included basic hardware inventory information for you to refer if a computer is not compliant because of hardware limitation. Luckily for you, we created a report which will give you a quick overview of your compatibility success or failure. Once we tested on a couple of test machine and are happy with results, we can expand our deployment to all computers.įrom there, what’s the easy way to check your compatibility results? You could go in the Monitoring / Deployment section in the console… or you build a custom report.
We cover the topic on how to troubleshoot Windows 10 error in this blog post (Or in the specified path if you use the /CopyLogs parameter in your command line. They are located in C:\$WINDOWS.~BT\Sources\Panther folder. If you need more information about the error, look at Setupacr.log or Setuperr.loggenerated by Setup.exe. This is normal as the error code returned by the compatibility check will always be an error. It will take about 5 minutes to complete… and it will fail.
On a targeted computer, run the program manually in the Software Center (Available) or wait for the schedule to trigger your deployment (Required).
Command Line : SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Enable /Compat ScanOnly.If you have EN-US machine, you must provide EN-US media Be aware that setup.exe is language specific.
Name your package and specify your Windows 10 installation media as the source file.In the SCCM Console, go to Software Library / Application Management / Packages.Using our proposed methods, you’ll be using about 250mb on the client drive instead of 5gb. If they are not set correctly you’ll end up sending the complete installation media (including Install.wim) to the computers only for a compatibility check which is not really effective. The deployment option and command line is important here. The source of this package must be the Windows 10 installation media.
We will start by creating a package for Windows 10 compatibility check. SCCM Windows 10 Compatibility Check Package Creation This report can be used to detect and fix migration errors before the actual Windows 10 deployment.
Using SCCM, we will run this Windows 10 compatibility check, return the results in the SCCM database and use this data to build a comprehensive report. This command can be used on a Windows 7,8 or 10 devices before a migration in order to see if those devices are Windows 10 compatible. Luckily, Windows 10 setup comes with command line options which one of them is an excellent compatibility check (/Compat ScanOnly).
When planning for a Windows 10 migration, understanding your environment is the key.