by lunarg on February 20th 2017, at 14:53
When provisioning non-Cisco phones on a Cisco-switched network, you may notice that the configured voice VLAN is not correctly provisioned to the phone. The phone ends up in the data VLAN, rather than the voice VLAN even though the switch port has been correctly configured.

There are two protocols which can be used to provision the correct VLAN to your phones: Cisco Discovery Protocol (CDP) and Link-Layer Discovery Protocol (LLDP). CDP is a proprietary protocol and is only supported on Cisco-switches and Cisco-phones. Non-Cisco devices usually use LLDP, which is an open standard supported by most other vendors. Although Cisco switches also support LLDP, it is by default not enabled, resulti  ...
by lunarg on February 16th 2017, at 10:08

It is possible to install the integration plugins for VMware on an ESX host directly from the Nimble website, provided your hosts have internet access:

  1. Place the host into maintenance mode.
  2. Connect to the host through a shell (e.g. SSH).
  3. Run the command:
    esxcli software vib install -d http://update.nimblestorage.com/esx5/ncm
    Wait for the installation to complete.
  4. Take the host out of maintenance mode and continue with the configuration.
by lunarg on February 6th 2017, at 16:30
A list with direct links to VMware vSphere clients. Saves you a lot of time when you need to (re)install many different versions.

Starting with 6.5, the vSphere client is no longer available.

VMware vSphere Client 6.0 Update 2a: VMware-viclient-all-6.0.0-4437566.exe

VMware vSphere Client 6.0 Update 2: VMware-viclient-all-6.0.0-3562874.exe

VMware vSphere Client 6.0 Update 1: VMware-viclient-all-6.0.0-3016447.exe

VMware vSphere Client 6.0: VMware-viclient-all-6.0.0-2502222.exe

VMware vSphere Client 5.5 Update 3d: VMware-viclient-all-5.5.0-3705931.exe

VMware vSphere Client 5.5 Update 3: VMware-viclient-all-5.5.0-3024345.exe

VMware vSphere Client 5.5 Update 2: VMware-viclient-all-5.5.0-1  ...
by lunarg on January 31st 2017, at 15:55
When using credentials in Powershell, you usually use Get-Credential, which essentially creates PSCredential objects. Creating such an object prompts the user to enter a username and password, which is not really usable in unattended scripts. There's a method where you can specify an unencrypted password but this is not secure. Fortunately, there's also a method where you can store the encrypted password in a file and use it to set the password.

To create a password file, run this from a Powershell window:

Read-Host -AsSecureString | ConvertFrom-SecureString | Out-File path-to-file

You will not get a real prompt: simply type the password will show * in the console. Type the password twice  ...
by lunarg on January 31st 2017, at 08:55
When installing Sonicwall NetExtender 8.0.241 or later on Windows 7, you may get the following error:

"Damaged version of net extender detected on your system. Please re download net extender"

The reason for this error is you probably are missing Windows Update KB3033929, which adds SHA256 support into Windows. Because SHA256 certificates are now the new norm, the latest Sonicwall certificates also use this hashing algorithm. Without the update, Windows 7 and Server 2008R2 do not have support for SHA256.

You can resolve the issue by installing the update, then reinstalling NetExtender:

Download and install KB3033929.

Uninstall Sonicwall NetExtender (via Control Panel).

Delete  ...
by lunarg on January 30th 2017, at 11:33
Since Mac OSX Lion (10.7), it is possible to open a Terminal from a Finder window, similar to "Open Command Prompt" in Windows. The feature is available as a service and is by default disabled, but when enabled, it allows you to click a folder and then perform "Open Terminal", which will launch a terminal window at the specified folder.

To enable the "Open Terminal" service:

From Finder, click the Finder application menu, then under the Services menu, click Services Preferences.Alternatively, open System Preferences, click Keyboard, then Shortcuts and in the left pane, click Services.

In the right pane, scroll down to Files and Folders, and look for New Termi  ...
by lunarg on January 23rd 2017, at 11:03
In a hybrid Exchange environment, you may get an error when attempting to log in to Office 365 when performing a management task involving Office 365. When clicking the "Sign in to Office 365" link, the following error is displayed:

critical error
The web page isn't loading correctly. Please reload the page by refreshing your browser.

Technical information: Unable to set the property "mkt" of a null reference or undefined

Not really a solution, but you can work around the issue by performing these steps:

In EAC, navigate to Hybrid.

Click Modify.

Click Sign in to Office 365, type in your Office 365 username and password.

Once logged in, click on the Enterprise tab and try per  ...
by lunarg on January 23rd 2017, at 10:17

If you have the Exchange Management Tools installed, you can easily import the Exchange module into a standard Powershell by running the Add-PSSnapin cmdlet.

Depending on the Exchange version, the module to add is slightly different:

Exchange 2007Microsoft.Exchange.Management.PowerShell.Admin
Exchange 2010Microsoft.Exchange.Management.PowerShell.E2010
Exchange 2013Microsoft.Exchange.Management.PowerShell.SnapIn

If you're not sure about the version, you can also use wildcard characters:

Add-PSSnapin *Exchange*

If you don't want to install the management tools, you can also use PS remoting to remotely access the management shell from a standard Powershell.

 
 
« March 2017»
SunMonTueWedThuFriSat
   1234
567891011
12131415161718
19202122232425
262728293031
 
Links
 
Quote
« If the batteries of a TV remote run out, why do we press the buttons so much harder? »