Category Archives: Microsoft

28 Jul

How to fix blank System Tray icons

Introduction

Sometimes, you may hover over the system tray and notice missing icons, but there are still blank spaces in their place. This is caused by cached registry settings and can be fixed by following the steps below.

Steps (3 total)

1. Backup Registry

Go to Start > Run (or Windows-key + R), type in regedit and hit OK. Before doing anything else, backup the registry.

2. Navigate to the key:

HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\TrayNotify.

Delete the values IconStreams and PastIconsStream.

3. Restart Windows Explorer

Open up the Task Manager (Ctrl + Shift + Esc), go to the Processes tab, select explorer.exe and click End Process.

Open the Applications tab and click New Task at the bottom-right of the window.

In the message box that pops up type in explorer.exe and hit OK.

Conclusion

Explorer.exe will reload, and the missing icons should now be back in the system-tray where they belong. Then if the volume bar isn’t there, go to taskbar properties (where the volume was gray) and simply tick the box.

Article Source: Click Here

23 Jul

Determining the UEFI BIOS OEM Embedded System Locked Preinstallation Key

The OEM product key (SLP key) is hidden within the UEFI BIOS. In order to determine your product key, the RWEverything utility is recommended as it looks at the systems hardware to determine the Windows product key and not at the registry, meaning it does not give bogus results like other utilities:

Download Link: http://rweverything.com/download/

To find out the OEM BIOS Embedded System locked Product Key, install RWEverything and then select ACPI Tables and the MSDM tab, copy down your product key.

rweverything

Note no MSDM tab = No Windows 8.0/8.1 BIOS Embedded SLP key.

This key is classified as hardware (part of the motherboard) and so Microsoft will not be able to help you if this tab is missing.
Systems which shipped with Windows XP, Vista or 7 have no MSDM tab as these versions of Windows used a generic key for OEM SLP; you need to purchase a retail product key for these systems. Note if you have purchased a retail license for such systems there will be no MSDM tab.
If you have a systems which came with Windows 8.0/8.1 and no MSDM tab then you need to contact your OEM for a motherboard replacement or purchase a retail license. Its extremely rare for an OEM motherboard to lose its Windows 8.0/8.1 key but I have seen a few examples.
While this utility gives your product key. It should be noted that it does not give you the Edition of Windows 8.1 this product key is for however at least you can confirm you have an OEM product key. If you have tried the 5 “Editions” and they all reject your product key then it is likely you have a Bing Edition which Microsoft chose not to support with this tool.

Article Source: Click Here

05 Dec

No Remote Desktop Client Access Licenses Available

Here is a fix to the following error message with Remote Desktop Connection when you try to connect to a machine from Windows 7: “Remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator“

rdp1

The solution is delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing

Try connecting in again. If it doesn’t work and you get the following error message: “The remote computer disconnected the session because of an error in the licensing protocol“;

Then all you need to do is Right-Click on the Remote Desktop Connection icon and select “Run as Administrator“.

20 Nov

How to Repair a Windows Corrupt Profile

How to Repair a Windows Corrupt Profile

By Chris Hoke, eHow Contributor – Original Post

When logging in to your Windows 7,Vista, or XP operating system, you may be creating a new temporary profile instead of logging in with your regular user profile. If so, Windows has a profile list error, caused by an error in your profile settings. The system attempts to fix the problem by loading a temporary profile. Fortunately, Windows typically backs up your profile settings so you can restore them by using the Registry Editor program.

Instructions

  • 1 Click the “Start” menu button after logging in as the temporary profile. Type “regedit” into the “Search” field; then press “Enter”.
  • 2 Double-click to expand the “HKEY_LOCAL_MACHINE” key in the left pane.
  • 3 Double click “SOFTWARE”, “Microsoft”, “Windows NT”, “CurrentVersion”, and then “ProfileList”.
  • 4 Locate the two SID (Security Identification) keys that correspond to your user profile. Both keys are named “S-1-5-21-S” (where “X” is your security profile identification number), but one key has “.bak” at the end of the name. If you have more than one user on your computer, you can identify your SID keys by clicking on each key in the left pane and checking the user name data column located to the right of the “ProfileImagePath” field in the right pane.
  • 5 Right-click on your SID key name that does not end in “.bak” and click “Rename”. Type “_corrupt” at the end of the key name and press “Enter”.
  • 6 Right-click on your SID key name that ends with “.bak” and click “Rename”. Remove the “.bak” from the key name and press the “Enter” key.
  • 7 Close the “Registry Editor” window.
  • 8 Click the “Start” button, “Shut-Down” menu, “Log Off”.
  • 9 Log back into Windows with your regular profile to restore your user profile.
  • 31 Oct

    Step-by-Step Windows 8 Upgrade Instructions

    25 Oct

    Remote Desktop Services deployment using Windows PowerShell

    Excerpt from MSDN.

    Hi, my name is Omair Gillani and I’m a program manager on the Remote Desktop Virtualization team. Remote Desktop Services (RDS) for Windows Server 2012 Release Candidate offers an integrated management experience in the new Server Manager, which makes it easy to deploy, configure, and manage RDS end-to-end. For admins who prefer scripting and automation, one of the great new capabilities added to RDS for Windows Server 2012 Release Candidate is a new Windows PowerShell layer. This provides a powerful mechanism to automate setup for, configure, and manage a complete Remote Desktop Services deployment.

    I hope that this post helps you get started deploying Remote Desktop Services by using the Windows PowerShell script.  We focused on providing a great GUI administration experience as well as a great scripting experience.

    In this post I focus on using script to deploy a single server virtual machine-based desktop deployment by using a Windows 7 Service Pack 1 (SP1) virtual desktop template image.

    Let’s start with the prerequisites.

    Prerequisites

    The requirements for setting up a Remote Desktop Services deployment are as follows:

    1. Install Windows Server 2012 on a Hyper-V capable computer.
    2. Join your server to a domain.
      1. RDS requires all its servers to be added to a domain. The domain needs to have a DHCP server so that IP addresses can be assigned to desktops in a new virtual desktop collection.
    3. Create a virtual desktop template to be used when creating a virtual machine-based desktop deployment.
      1. Specify Win7Gold as the virtual machine name; this virtual desktop template will be used by the Windows PowerShell cmdlets to create virtual desktops for the managed pooled virtual desktop collection.  · The detailed process can be found at Create Virtual Machines.
      2. Install Windows 7 Enterprise with SP1.
      3. Install Hyper-V Integration Services  · From the Hyper-V manager console, select Connect under the Actions pane to launch the virtual machine connection.  · On the Action menu, select Insert Integration Services Setup Diskclip_image002  · In the AutoPlay dialog box, select Install Hyper-V Integration Servicesclip_image004
      4. On the virtual machine, ensure that the operating system has been sysprep generalized by using the following command line:  · sysprep.exe /generalize /shutdown /oobe
    4. Use a domain admin account or a domain user joined to the local Administrators group to run the Windows PowerShell script. The local admin account will not work in this case.
      1. Also ensure that the Windows PowerShell window is launched as administrator.

    New Remote Desktop Services deployment

    The new Remote Desktop Services virtual machine-based desktop deployment will be set up in two main steps:

    1. Create a new deployment
    2. Create a new Windows 7 SP1 managed pooled virtual desktop collection

    You can find the complete script for creating a single server Windows 7 SP1 virtual machine-based desktop deployment on the Script Center http://gallery.technet.microsoft.com/scriptcenter/Create-a-new-WS2012-Remote-f7f06d53. The script takes the name of your server as well as the domain it is joined to as parameters.

    Create a new deployment

    The first step in creating an RDS virtual machine-based desktop deployment is installing and configuring the relevant role services. In Windows Server 2012, a single Windows PowerShell cmdlet will both install and configure the RD Connection Broker, RD Web Access, and RD Virtualization Host role services. The cmdlet also allows for any number of RD Virtualization Host servers to be specified for larger deployments.

    Figure 1 below shows the first 14 lines of the Windows PowerShell script that will set up a new RDS deployment on a single server. It takes the name of the Hyper-V capable server as a parameter. The script will install all required RDS role services on this single server. The script imports the RemoteDesktop Windows PowerShell module. It then calls the Windows PowerShell New-RDVirtualDesktopDeployment cmdlet to install the RD Connection Broker, RD Web Access, and RD Virtualization Host role services on the server and configure them to have a working RDS deployment.

      1 param (
      2     [Parameter(Mandatory=$TRUE, HelpMessage="FQDN of RD Web Access\RD Connection Broker and RD Virtualization host roles")]
      3     [String]
      4     $serverName,
      5 
      6     [Parameter(Mandatory=$TRUE, HelpMessage="Domain name to be used for new desktops created")]
      7     [String]
      8     $domain
      9 )
     10 
     11 # Import the RemoteDesktop module
     12 Import-Module RemoteDesktop
     13 
     14 # Create a new RDS deployment
     15 New-RDVirtualDesktopDeployment -ConnectionBroker $serverName `
     16    -WebAccessServer $serverName `
     17    -VirtualizationHost $serverName
     18 Write-Verbose "Created new RDS deployment on: $serverName"

    Figure 1: Script lines 1-18

    Note: This Windows PowerShell script needs to be run on a remote computer because it requires a restart after installing the RD Virtualization Host role service.

    You can use the Get-RDServer cmdlet to get the list of servers and role services that were installed for the newly created RDS deployment.

    Create a new managed pooled virtual desktop collection

    Now that we have a working RDS deployment, let’s create a new managed pooled virtual desktop collection by using Windows PowerShell. Figure 2 shows the remaining part of the Windows PowerShell script; this will use the New-RDVirtualDesktopCollection cmdlet to create a managed pooled virtual desktop collection by using the virtual desktop template created as part of the prerequisites.

      1 Grant-RDOUAccess -Domain $domain  -OU "Computers" -ConnectionBroker $serverName
      2 
      3 # Create a new pooled managed desktop collection
      4 New-RDVirtualDesktopCollection -CollectionName demoPool -PooledManaged `
      5    -VirtualDesktopTemplateName Win7Gold `
      6    -VirtualDesktopTemplateHostServer $serverName `
      7    -VirtualDesktopAllocation @{$serverName = 1} `
      8    -StorageType LocalStorage `
      9    -ConnectionBroker $serverName `
     10    -VirtualDesktopNamePrefix msVDI

    Figure 2: Script lines 20-29

    This cmdlet will export the template virtual hard disk (VHD) and then create a single virtual machine in the pool and publish this on the RD Web Access portal. We can now connect to the desktop by going through the RD Web Access portal.

    This single Windows PowerShell script enabled us to have a completely automated working RDS deployment. The RemoteDesktop module offers the complete range of Windows PowerShell cmdlets that you need to set up, configure, and manage your Remote Desktop Services deployments.

    For more information on using Windows PowerShell for Remote Desktop Services also see Travis’s blog at http://blogs.msdn.com/b/rds/archive/2012/06/28/introduction-to-windows-powershell-scripting-in-windows-server-2012-remote-desktop-services.aspx.