vCenter 4.1 upgrade with vCenter Update Manager

Strange catch in this upgrade. vCenter requires a 64 bit Systen DSN to access the database. Update manager requires a 32 bit DSN. On Windows you cannot create 32bit DSN in the ODBC Data Source Administrator found in the control panel.

Instead you have to create your 64 bit like normal from control panel, and create your 32 bit using:


vCenter Update Manager DSN

Making shortcuts on remote PCs using vbscript and psexec

Most of this information I'm taking from other websites, but I wanted a copy all in the same place.
sysinternals tools from technet icon finder for Shell32 with numbers!

Basically you create a vbscript that makes a shortcut, using the chart to assign the icon image you want, and then push that vbs file out using psexec cli tool from the sysinternals suite.

' Create ShortCut.vbs - Create a Desktop Shortcut.
' VBScript to create .lnk file
' Author Guy Thomas
' Version 2.4 - July 2006
' ----------------------------------------------------------'
Option Explicit
Dim objShell, objDesktop, objLink
Dim strAppPath, strWorkDir, strIconPath

' --------------------------------------------------
' Here are the variables that to change if you are making a 'real' script

strWorkDir ="C:\windows"
strAppPath = ""
strIconPath = "%SystemRoot%\system32\SHELL32.dll,74"

Set objShell = CreateObject("WScript.Shell")
objDesktop = objShell.SpecialFolders("Desktop")
Set objLink = objShell.CreateShortcut(objShell.SpecialFolders("AllUsersDesktop") & "\Mikeal's Tech Blog.lnk")

' ---------------------------------------------------
' Section which adds the shortcut's key properties

objLink.Description = "Mikeal's Tech Blog"
objLink.HotKey = "CTRL+SHIFT+S"
objLink.IconLocation = strIconPath
objLink.TargetPath = strAppPath
objLink.WindowStyle = 3
objLink.WorkingDirectory = strWorkDir


' End of creating a desktop shortcut

  1. strIconPath The 74 value in the is the number that selects the icon image. Check to find the image and value you want.
  2. strAppPath is the url, or executable path for the shortcut.
  3. objShell.CreateShortcut Set the to the location you want the shortcut created.
  4. Modify the objLink.Description, and Hotkey as needed.
  5. Save the file as 'create myshortcut.vbs' and test it. If everything works correctly you can now take psexec and execute the script on other remote computers.
  6. To push out the vbs file you will need to make 2 batch files and a text file. You must place all these files, along with the psexec.exe file from the sysinternals package, on a network share. Make sure the share is accessible PCs the shortcut will be deployed to. The executable path has to work for the computers you are pushing it to.
  • Launch.bat:
    cscript "\\server\share\create myshortcut.vbs"
  • Install.bat:
    psexec @workstations.txt -u domain\domainadmin -p myadminpwhere "\\server\share\launch.bat"
  • workstations.txt:

You can use IP address instead of DNS names in workstations.txt if needed.

When finished run the install.bat file from dos. install.bat will execute launch.bat on the remote computers listed in workstations.txt.

URL Rewrite for IIS7 http to https redirection

This is a great addition.  Finally we have an easy way to redirect users.  I'm using this to rewrite all http connections as https.

You can use the web installed for URL Rewrite here.

After you have the extension loaded you can make rules 2 ways.  Either by editing the web.config file in the root of your website, or with the GUI in IIS7.  I find working with the web.config easier.


Using the GUI look for the icon selected below.


Select Add Rule(s) from the right menu, then blank rule.  The settings for http to https redirection are shown below.


The last setting is to change the redirection type to Found(302).





« 1 2 3 4 5 6 7 8 9 10 11 12 »