In Windows 10, 8, 7, or Vista, un-register the file and then re-register it (see. That the version of any file provided for download will be compatible with other.
![]() -->
Before deploying Windows 10, it's a good idea to check the readiness of your existing machines running Windows 7, 8/8.1, Or even Windows 10.
In this blog post I will use setup.exe with /compat scanonly switch to check the compatibility without performing the upgrade. The reason for not choosing the Upgrade task sequence for this job is to avoid sending the whole 3.5 GB source files over the network.
Package & Command line
Here's the command line with switches to silently check the compatibility. setup.exe /Auto Upgrade /Quiet /NoReboot /Compat ScanOnly
Since the clients don't need to download the full set of source files to check the compatibility, as the setup.exe only validates the existence of the files which can be even on a network share. Instead of creating a package with full set of source files, all i am using is a 1KB batch file to call a network share where the source files are located.
Command line of the batch file: -
start /wait <ServerShare>setup.exe /Auto Upgrade /Quiet /NoReboot /Compat ScanOnly
![]() ![]()
exit /b %errorlevel%
The client will still download some source files which is significantly less than the whole set. Here's a snapshot of the SMB traffic during this operation -
Program
The program for the package above simply executes the batch file. Based on the above network traffic, you might want to set the estimated disk space and the Max allowed run time.
It should run regardless a user is logged on or not.
Results
The resultant output of the scan results is not the typical 0 for success, refer the table below for the list expected Decimal Output returned by ConfigMgr and Hex Code returned by the windows setup log files.
Reporting
For reporting purposes, you can leverage the attached report which takes the package name as input. Refer the screenshot below.
The above package can also be called out in a Task Sequence where you can add additional steps to capture logs in case of failure. Attaching the exported TS for reference.
Step 1 – Add an Install Package step to run the above package. Make sure you check the box Continue on error in the Options tab.
Step 2- Add a group to Capture Logs if the result is anything other than -1047526896 which is Success/No issues found.
Step 3 – Map Network Drive to a server share where you want to dump the log files
Step 4 – Create Folder for each computer.
Step 5 – Copy the Log files to the network share.
Step 6 – Copy the XML files to the network share.
Step 7 – Disconnect the Network Drive
Reporting – TS
Refer the attached report which takes the Task Sequence name as input to display the compatibility results. Screenshot below.
Download Reports - Note – The reports are built using SSRS 2016 schema.
Legacy Reports - For importing into SSRS 2008 R2, 2012 & 2014
Thanks,
Arnab Mitra
Many Windows System files (typically ending in .ocx or .dll) are shared by multiple programs. Installing or un-installing programs (including trial versions of programs such as Microsoft Office) into Windows, or running free registry cleaners can remove or corrupt shared files, or break interdependent links between files. Also, the User Account Control in Windows Vista and later can block CTI Navigator's access to Windows system files.
First, run a virus/malware scan of your entire computer system to ensure that the problematic file is not infected and is not a non-Microsoft file masquerading as a Windows System file. For links to free virus diagnostic scans, see 'Cleanup and Prevent Virus or Spyware' in the Related Articles at the bottom of this web page.
To confirm whether or not a specified Windows system file is missing, and then to register or repair it:
Hidden Files Note: To view hidden system files in Windows Explorer, select Tools > Folder Options > View tab > check 'Show Hidden Files and Folders' > un-check 'Hide extensions for known file types'.
System Note: To determine whether your Windows is 32-bit or 64-bit, open the Windows Control Panel, select System, and look for 'System Type'.
Disclaimer. Information in any form is provided by Creative Technology of Sarasota, Inc. (CTI) only as a convenience to licensed users of CTI products. CTI cannot warrant that the version of any file provided for download will be compatible with other programs on your computer or with your version of Windows. See related article, 'Windows File Protection.'
Register a Windows File
System files need to be registered for use by Windows. Instructions to register a file are described in detail in the related article 'Register dll or ocx file' below. These steps are summarized as follows*:
Note 1: There is one space between regsvr32 and the filename. Do not type the {} braces.
Note 2: To register or unregister a file not in the Windows system folder, you must enter the full path to the file enclosed by quotation marks after the Regsvr32or Regsvr32 /u command. For example, to register the Announcement file in CTI Navigator that is installed in the normal default location on C drive, run Regsvr32'C:Program Files (x86)Cti NavigatorCtiAnnouncement.dll'. Ensure that you type the correct drive letter and the correct Program Files (x86) for 32-bit Windows, or Program Files for 64-bit Windows, in the path.
* Windows XP and Vista users may see the Registration Shortcut note below for an alternative method.
Unregister and re-register a Windows file
If the same error persists after replacing and/or registering a file, it may need to be un-registered and then re-registered (especially in Windows Vista or Windows 7). To un-register a file and then re-register it:
Warning: See disclaimer above. Also, before making any registry changes, Microsoft highly recommends that you make a backup of your registry (see 'How to backup and restore the registry...' in related articles below).
Older Installations in Vista or Windows 7
To fix an error message such as 'Component {Filename.ocx} or one of its dependencies not correctly registered; a file is missing or invalid' when logging into an older installation of CTI Navigator in Windows Vista or Windows 7:
Compatibility Note. There usually is no Compatibility tab for new installations of CTI Navigator. The program automatically installs with administrative privileges. However, sometimes you may need to set the CTI Navigator.exe program file to 'Run as an Administrator'. To do so, right-click on the Windows Start icon > select Explore, File Explorer, or 'Open Windows Explorer' > browse to C:Program Files [or Program Files (x86) in a 64-bit version of Windows]CTI Navigator > right-click on CTI Navigator.exe > check 'Run as Administrator' > close the Windows Explorer.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |