HP LaserJet P4014 , P4015 Reset the maintenance count instructions

Resetting the maintenance count.
After installing a maintenance kit, you should reset the printer's "Maintenance Count".
There are two ways to do this, depending on your firmware revision.
Method 1
1. Turn the product off.
2. Turn the product on.
3. Press and hold down the OK button while the memory is counting. The memory starts counting at 000MB immediately after you turn the power on.
4. Continue to hold down the OK button until all three LEDs are illuminated.
5. Release the OK button.
6. Press the up arrow (Navigation) button until the message New Maintenance Kit appears on the control panel display. If New Maintenance Kit is not an option then you have an old firmware version (see below).
7. Press the OK button once. Your maintenance count is reset.
Method 2
Some of the older firmware versions did not have the "New Maintenance Kit" option mentioned in the above procedure. In this case you can either update the printer's firmware to ad this feature or manually reset the maintenance count in the service menu as described below.
Enter the Service Menu -- Press the MENU button, and scroll through the list of menus until you see "SERVICE". Press OK.
Before you can enter the Service Menu, you will see a blank line on the screen where you are supposed to enter an access code:
On a LaserJet P4014, the access code is 05401408
On a LaserJet P4015, the access code is 05401508
On a LaserJet P4515, the access code is 05451508
Enter the code and press OK.
You will now be allowed into the Service Menu. Scroll through the list of options until you see, "Maintenance Count." Press OK.
Change the current maintenance count to "0" by pressing the number "0", and then pressing OK.
To confirm this, you can print an Information page.


Original:

VMware Virtual Machine Reporting from VSphere

VMware PowerCLI is a powerful utility to generate virtual machine information and status. This is very cool and handy tool. I use to generate VMTools status, Datacenter and ESX host name information.

Command to connect vCenter:
Connect-VIServer vcenter1, vcenter2, vcenter
Initialize VMTools Version:
New-VIProperty -Name ToolsVersion -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Config.tools.ToolsVersion’ -Force
Initialize VMTools Status:
New-VIProperty -Name ToolsVersionStatus -ObjectType VirtualMachine -ValueFromExtensionProperty ‘Guest.ToolsVersionStatus’ -Force
Verify VMTools status on all virtual machines and export the output to excel:
Get-VM | Select Name, ToolsVersion, ToolsVersionStatus | Export-Csv -NoTypeInformation -UseCulture -Path C:\Temp\VMToolsInfo.csv
Export VM name, cluster and ESX Host:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}}, @{N=”ESX Host”;E={Get-VMHost -VM $_}} | Export-Csv -NoTypeInformation C:\temp\VM_CLuster_Host-.csv
Export VM name and Cluster name:
Get-VM | Select Name, @{N=”Cluster”;E={Get-Cluster -VM $_}} | Export-Csv -NoTypeInformation C:\temp\test-VM_CLuster.csv

Original:

Error: Could not access VBscript run time for custom action.

Recently got an update from the application team that they are unable to install and software. When executing the setup file they are getting an error pop-up window stating “Could not access VBscript run time for custom action.”. This issue was fixed using below steps:

1. Open Registry Editor” and locate the below key.

HKEY_Local_Machine\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

2. Expand {B54F3741-5B07-11CF-A4B0-00AA004A55E8} key, locate InprocServer32 and click on it.
In the right column you should see two values.

3. Right-click InprocServer32 > Permissions > Advanced > Permissions > highlight Administrators, choose Edit > and in the Permissions check box next to Full Control; Save all changes;

4. Then in the right column or Registry Editor right-click (Default) > Modify, and insert the correct path in Value Data:

C:/Windows/system32/vbscript.dll

5. If you have 64-bit Windows repeat steps 3 – 5 for next registry keys:

HKEY_Local_Machine\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

HKEY_Local_Machine\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8

6. After that close Registry Editor.

After the above changes when we tried executing the same setup it went success.

Original:

AD update for mobile number from CSV

#1. Have to have permissions to the OU or organization


Import-module ActiveDirectory 


#Imports CSV file - change location as neccessary
Import-CSV "C:\users\Test\desktop\mobilenumber.csv" | % {

#Variables created to correspond with headers in CSV File.  Make sure the variables match your csv headers.

$Title = $_.EmployeeTitle
$Location = $_.Location
$IDnumber = $_.EmploeeID



# Getting user based on employee number then setting user with that employee id the following variables
Get-ADUser -Filter {EmployeeID -eq $IDnumber}| set-aduser -Description $Title -Office $Location -Title $Title}

Original:

VMware Tools is no more depended on vSphere/Esxi release.

VMware tools 10.0.0 is now no more dependent on vSphere release/Esxi builds. I think this is the first time when VMware released VMware Tools separately. As per release note its backward compatible, compatible with Esxi 5.0 and also compatible with Workstation 12.0 and VMware Fusion 8.0. It will allow to get the latest new features and enhancements made to the VMware tools faster to the customers.

You can download and install the latest version of VMware Tools from Here.

Thanks,
WintelAdmin

Original: