SCCM 2012 SP1 Error connecting console after upgrade to SP1

I decided to upgrade SCCM 2012 to SP1. The upgrade went thru with no issues.

However when i tried opening SCCM 2012 Management console Iwould get an error connecting to SCCM site.

I looked in the event viewer and saw the following error:

Description = “Please upgrade your Admin Console to newer version”;
Operation = “ExecMethod”;
ParameterInfo = “SMS_Identification”;
ProviderName = “WinMgmt”;
StatusCode = 2147749889;

Which led me to the conclusion that there must be a seperate intall for the management console. Opened the install splash screen and saw the option to “Install Configuration Manager Console”.


Click that option and install the new console.

All is good and working now.


Updating vDisk on Citrix Provisioning server.

Updating vDisk in Citrix Provisioning (PVS) server (Load Balanced PVS configuration)


  • Microsoft Patches
  • AV DAT
  • Software Updates/Installations


  • vDisk Modes
    • Private
    • Standard (Only copy if in Standard-if there are connections)
  • Copy vDisk (.pvp,.vhd)
  • Right Click vDisk – >Add or Import Existing Disks
    • Click Search
    • Click Add
  • Deselect “Enable Load Balancing”
  • Put disk in private
  • Set load balancing to one PVS server.


  • Assign new vDisk to a VM that we will use to update disk with
  • Boot machine
  • Perform changes
  • Get the server ready for provisioning
    • Run XenApp Server Role Manager
    • Click Edit Configurations
  • 8.2a-EditConfig
  • 8.2a-PrepareServ
  • You can uncheck “remove server from farm”
  • 8.2a-UncheckFarm
  • Finish and SHUT DOWN ONLY.
  • Go back to PVS
  • Change disk to Standard and Cache on Device Hard Drive


  • Enable Load Balancing on Vdisk
  • Drag the new vDisk to Device Collection
  • Click yes on replace screen
  • Reboot the XenApp Farm server to get the new image
  • Copy the update vDisk and .pvp file to the other PVS server.

Configuring Host Headers to use SSL in IIS 7 or 7.5

Ever try to apply a Wildcard certificate in IIS to multiple sites and use Host Headers?

IIS allow you to use one SSL certificate for multiple IIS websites on the same IP address via Host Header values. Through the IIS Manager interface, IIS only allows you to bind one site on each IP address to port 443 using an SSL certificate. If you try to bind a second site on the IP address to the same certificate, IIS 7 will give you an error when starting the site up stating that there is a port conflict. In order to assign a certificate to be used by multiple IIS sites on the same IP address, you will need to set up SSL Host Headers by following the instructions below.

Setting up SSL Host Headers on IIS 7

  1. Obtain an SSL certificate and install it into IIS 7
  2. Once you have the Certificate installed open a Command Prompt with elevated permissions
  3. Change directory to C:\Windows\System32\Inetsrv\ (“cd C:\Windows\System32\Inetsrv\” )
  4. Run the following command for each site that you need SSL host headers configured for.
    • appcmd set site /”<IISSiteName>” /+bindings.[protocol=’https’,bindingInformation=’*:443:<hostHeaderValue>‘]
    • Replace <IISSiteName> with the name of the IIS web site and <hostHeaderValue> with the host header name for that site
  5. Open IIS and validate that the IIS Site binding is configured with HTTPS and the Host Header Value
  6. Test your site(s).