What is your preferred scanning method?
.NET is widely installed across the Windows platform, but it’s not always present on every device that needs to be scanned (i.e. Windows XP or Windows Server 2000/2003). To accommodate, Movere has three scanning modes.
All Available (recommended)
When targeting a device, Movere evaluates which version of the .NET framework is installed on the target device, and depending on the result, deploys the most appropriate scanning technology. The ‘All available’ option will leverage either the System Account for access or the user-provided Local Admin account.
Using this option a temporary local service is created which controls the capture of primary data (Windows) and the intelligent gathering of secondary data such as SQL and Exchange Server.
The .NET scanning method is preferred. If .NET is unavailable on the target device, then Movere will attempt a Remote/WMI scan.
Local Scan + Remote (WMI)
In option one, all of the commands required to gather the scan data are triggered using a temporary local service. In some cases it is not possible to use this method, so the commands are run locally on the target device. This method is still able to gather both primary and secondary data using a lower privilege account: Local Admin.
Remote (WMI) Only
WMI is an older technology that has some limitations. Using WMI will typically yield all of the data that is required to complete the inventory, but it is much slower and should only be used when the .NET option is unavailable.
Manual Local Scan
Occasionally there will be devices that have been deliberately isolated, e.g. DMZ. Typically these devices cannot be targeted from the primary internal network and cannot be scanned by copying the Movere Console locally, unless the .NET 4.5.2 framework has already been installed, which in most cases isn’t practical or possible. Movere can still inventory such devices by performing a manual local scan. Manual scans can be run locally from the targeted endpoint or from attached flash drive. The device being scanned must have the .NET 2.0 (or above) framework installed.
Running Movere Locally:
From the directory housing the Movere Console, copy the ‘Bot2’ folder (and the two files it contains), to the device, or flash drive, you want to run the scan from. Once you have copied the ‘Bot2’ folder, create a text file in the ‘Bot2’ folder and insert the following command:
cmd /c Movere.Bot2.Local.exe localhost:80
Save the file then change its ‘.txt’ extension to ‘.bat’. To start a scan, simply double click on the .bat file you created.
IMPORTANT: When running Movere locally, if you are on a SQL Server that you are attempting to collect SQL based data from e.g. SCCM, vCenter, SharePoint etc. then you MUST open a command prompt using the ‘Run as administrator’ option.
If you created (and double clicked on) a .bat file using the procedure above or open a regular command prompt and entered the command string manually, Movere will still scan the device, but no SQL based data will be returned.
An average scan takes between 30-45 seconds to complete. The appearance of a zip file in the ‘Bot2’ folder indicates that the scan has completed. When this occurs you must terminate the scan within 5 mins by pressing Ctrl-C on your keyboard. If you do not terminate the scan, then after 10 minutes, Movere will terminate itself and delete ALL files in the Bot2 folder, including the scan output.
Before you upload the scan file(s), open the Movere Console on the device you want to upload them from. Opening the Console creates a new upload folder with today’s date (UTC). Close the Movere Console and move the zip file(s) you have manually collected into the folder with today’s date which you will find within the ‘Uploads’ folder. Opening the Movere console now reveals the ‘Upload Scans’ tab. From this tab click the ‘Upload’ button to send the output files to the Movere cloud.
NOTE: You must place output file(s) you want to upload to the Movere cloud in the folder with today’s date (UTC). This is the only folder Movere will search for uploads.