disk Archives - Squidworks

Cleaner for LabTech

We Empower the Global Management of CCleaner

CCleaner for LabTech is a CCleaner manager that deploys, licenses, analyzes, cleans, stores data inside LabTech, displays computer level and global level statistics of each PC and uninstalls (de-enable) CCleaner all from a simple set of consoles. Let me show you some of what we are doing.

This is the Computer level interface

With very simple controls, you can Analyze a PC which will do several things.

Checks for and processes old log just in case they had been missed by previous jobs
Verifies the licensed install of CCleaner and installs if needed
Sets system to Enabled in Global Manager
Analyzes system
Retrieves all log details needed and stored data into LabTech
Refreshes the results tab

Cleaning will do.

Verify CCleaner install
Clean system
Retrieves all log details needed and stored data into LabTech
Refreshes the results tab

Computer-DiskClean

The results tab displays the results from the last scans and cleans and displays that data in both graphical and dataset views.

Registry Cleaner will do

Scan Registry based on user setting
Create a full backup of the root registry keys
Clean selected results from registry

Computer-regscan

You can manage individual CCleaner cleaning directives using Bulk Config, each system managed can have separate sets of added rules to customize the cleaning experience for each PC under management.

Bulk Configurations will do

Add, edit and delete CCleaner configuration directives per PC

Computer-Config

Global Manager

The Global Manager is the heart of the system. This is where you configure the global settings for each computer, control the master on/off switch, manage your licenses, enable your computer systems for auto installs and auto cleans, deal with failed CCleaner installs and view the data from all clients combined.

ViewMenu-Main

The CCleaner engine manages the temp and junk files for hundreds of applications. In fact there is so many application that CCleaner works on that it was found to be impractical to try to stuff all that in a plugin. We still want to deliver that flexibility but in a simple and easy manner for you to manage. To do this we created a Bulk Configuration manager that allows you to add and remove any setting that CCleaner supports. These get applied to all clients enabled for CCleaner automation.

ViewMenu-Config

We have provided a Failed CCleaner Install Manager that will allow you to identify problem systems and from here you can reinstall and see the direct output of the efforts from behind the scenes.

ViewMenu-LicenseManager

We provide a 30 day look back window to see overall where and how the storage is being consumed and reclaimed.

ViewMenu-GlobalStats

ViewMenu-Graphs

We provide long term history views into several key aspects of the data being collected picking out the high end consumers by client, computer and application type for both the Analyzers and the Cleaners.

ViewMenu-Reports

Now let’s talk a little about behind the scenes, What you do not see is the back-end processes that are working to automate the entire process. When you turn Cleaner for LabTech on it starts a set of processes that manage the deployment, licensing scanning and cleaning based on your configurations. As Cleaner for LabTech starts its tasks it is ticketing its time spent and recording those results in the tickets. This adds the value and tractability to the work performed by Cleaner.

Now Available

Go Forth and Clean!

[Kaseya Agent Procedure] – Run CHKDSK And Repair If Needed.

Free Kaseya Script – Run CHKDSK And Repair

Here is another free script from Cubert’s Dwelling, An Agent procedure that will run a CHKDSK in read only mode. Parse the output and run a chkdsk /F if it meets the criteria set forth in the script. It then emails an alert with the scan results to a email address provided before it uploads a copy of the scan to the get file for storage and review. Finally it updates 2 custom fields in the system info table with a brief result and the last run time. If it finds the disk healthy it will report as such if not it will report one of several error types.

Download Script Here

You will need to unzip the script and import it into Kaseya. Once imported edit the script and find the 2 places it email out and update the email address(es), Then you will need to add the 2 custom fields into your System-info table.

To add the custom fields:
1# Open Kaseya and go to [Audit] – [View Individual Data] – [System Information] and select the button marked [New Custom Field]

2# The next box that pops up will create a new field, We will need to add 2 fields the first is CheckDisk Status and it will be a type String and Check Disk Updated with a type String.

Now run your disk check and see what it shows. If it meets with the right disk errors, a repair is sent to the system and a email to you to reboot system when you can so the repair can complete. You can add another execute command under where we call the chkdsk /F with a shutdown -r -t 3 and that will cause the system to reboot its self after issuing the fix cmd. This is great for servers where your scheduling the disk scans during maintenance cycles but not so good with workstations where user gets booted up then a scan runs that then reboots the system will only inflame your users. So be mindful of how you use a shutdown cmd.

Enjoy

Cubert 🙂

Error during the configuration of the host: Failed to update disk partition information

VMware ESX 4 -> Failed to update disk partition information.

After creating a new LUN on a Dell MD3000i, I wanted to add the new iSCSI LUN to my ESXi server. Everything went fine, the LUN was presented and the Add storage wizard has found the new LUN. But when i wanted to complete the wizard, the following error came up:

VMware ESX 4 -> Failed to update disk partition information.

Now if you go on the Internet a search around you will find several references to this issue. Most if not all of them tell you to:

1. Use fdisk on the /dev/sd[a-z]* device. Create a partition with type 0xfb.
2. Format the VMFS datastore using
vmkfstools -C vmfs3 vmhbaI:T:L:P
In this example, I corresponds to the initiator of the VMware host bus adapter, T corresponds to the target number of the disk, L is the LUN number, and P is the partition number of the newly created partition.

3. Reboot ESX server

This is not always required, It may be just a hickup in your ISCSI registration on the ESX servers. Here is how I fixed mine and it worked with out any reboots or major adjustments.

Steps to take first before following the CLI instructions:

Go create another 5Gb LUN on Power Vault.
Set the access group assigned to new LUN to allow ESX servers
On ESX Host GUI go back to configuration menu and select Storage Adapters menu
Select your ISCSI Software Adapter from Storage Adapter list and select “Rescan” (even if you see your LUN)
Go back to the Storage menu and select add storage, select Disk/LUN and follow through the menus to mount and format the 5gb LUN and it should go through now.
Remove the 5gb LUN from the ESX Storage menu.
Remove the 5gb LUN from Dell Vault.
Go back to your ESX and rescan HBAs and make sure the 5gb LUN is gone and you see your original LUN you want to mount.
Go back to the Storage menu and select add storage, select Disk/LUN and follow through the menus to mount and format the LUN and it should go through now.

If this does not work then change the access to the LUN on the vault to a new access group. Rescan for LUN on ESX then go reset the LUN back to the original access group you want to use and then rescan again from ESX. Try to remount LUN and format. This should now connect and no errors should appear. If you still are getting errors then you may have other issues and you can now try the CLI method or call in support.

Good Luck, I hope this helps a few of you out there from dealing with production systems and not wanting to spend all day VMotioning, reboots and such.

Enjoy