Monday, November 12, 2012

HOW TO: Install Imported Certificates on a Web Server in Windows Server 2003

Assign the Imported Certificate to the Web Site



  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. In the left pane, click your server.

  3. In the right pane, double-click Web Sites.

  4. In the right pane, right-click the Web site you want to assign the certificate to, and then click Properties.

  5. Click Directory Security, and then click Server Certificate.

  6. On the Welcome to the Web Certificate Wizard page, click Next.

  7. On the Server Certificate page, click Assign an existing certificate, and then click Next.

  8. On the Available Certificates page, click the installed certificate you want to assign to this Web site, and then click Next.

  9. On the SSL Port page, configure the SSL port number. The default port of 443 is appropriate for most situations.

  10. Click Next.

  11. On the Certificate Summary page, review the information about the certificate, and then click Next.

  12. On the Completing the Web Server Certificate Wizard page, click Finish, and then click OK.


http://support.microsoft.com/kb/816794

Thursday, November 8, 2012

VMWARE: Where can i find the Dell VMware 5.1 ISO for R620 / R720

As you may be aware finding the VMware 5.1 ISO for Dell is a bit challenging.  The Dell Driver and Support page is not working properly and it is a bit frustrating.

Please see the direct link to the Dell FTP server below.

Dell VMware 5.1 ISO for R620 / R720

 

Thanks to a twitter response Dell provided the following link.

http://www.dell.com/support/drivers/us/en/04/DriverDetails/Product/poweredge-r620?driverId=XWYR5&osCode=XI51&fileId=3005015335

Friday, November 2, 2012

MDT 2012 stuck on Processing Bootstrap Settings

This can happen if you are not logged in with "the" local administrator account.

I normally create a scratch "Build" account then shortly delete it after I enable the local admin account and finish the build under the local admin account before sysprep and capture

VMWare error: Unable to perform the operation. There is no available vRam capacity.

Cannot Add or Connect an ESXi Host to vCenter Server
You cannot add an ESXi host to vCenter Server.

Problem
You attempt to add or connect an ESXi host to vCenter Server but the operation is unsuccessful and you receive
the following error message.

"Unable to perform the operation. There is no available vRAM capacity."

Cause 

The vCenter Server system to which you tried to add the host to is licensed with a license key of vCenter Server Essentials that is part of the Essentials Kits. vCenter Server 5.0 Essentials licenses are hard-enforced, you cannot exceed the amount of pooled vRAM for vSphere 5.0 Essentials license keys that are assigned to the ESXi 5.0 hosts while the hosts are managed by vCenter Server. The memory that is configured to the powered-on virtual machines on the host that you try to add or reconnect exceeds the amount of pooled vRAM for vSphere Essentials. For details about vRAM and vRAM pooling, see “Licensing for ESXi 5.0 Hosts,” on page 68.

Solution
Reduce the amount of memory that is configured for the powered-on virtual machines and retry to add or
connect the ESXi host to vCenter Server.

Thursday, November 1, 2012

"Bootmgr is missing" from deployed .wim file

BOOTMGR errors is if your PC is trying to boot from a drive that is not properly configured.  In other words, it’s trying to boot from a non-bootable source.

Cause:

This error occurs when either of the following conditions is true:

  • The Windows Boot Manager (Bootmgr) entry is not present in the Boot Configuration Data (BCD) store.

  • The Boot\BCD file on the active partition is damaged or missing.


It is most likely the captured wim image had a corrupt/missing Bootmgr record.

Open WInPE and run the command below.

bcdboot c:\windows /s c:

Now you should recapture the Wim and test a new Task Sequence deployment.

Bootrec.exe /RebuildBcd

 

http://support.microsoft.com/kb/927391

Here is the content of that article:

Resolution:


Method 1: Repair the BCD store by using the Startup Repair option


You can use the Startup Repair option in the Windows Recovery Environment to repair the BCD store. To do this, follow these steps:

  1. Put the Windows Vista installation disc in the disc drive, and then start the computer.

  2. Press a key when you are prompted.

  3. Select a language, a time, a currency, and a keyboard or another input method, and then click Next.

  4. Click Repair your computer.

  5. Click the operating system that you want to repair, and then click Next.

  6. In the System Recovery Options dialog box, click Startup Repair.

  7. Restart the computer.


Method 2: Rebuild the BCD store by using the Bootrec.exe tool


If the previous method does not resolve the problem, you can rebuild the BCD store by using the Bootrec.exe tool in the Windows Recovery Environment. To do this, follow these steps:

  1. Put the Windows Vista installation disc in the disc drive, and then start the computer.

  2. Press a key when you are prompted.

  3. Select a language, a time, a currency, and a keyboard or another input method, and then click Next.

  4. Click Repair your computer.

  5. Click the operating system that you want to repair, and then click Next.

  6. In the System Recovery Options dialog box, click Command Prompt.

  7. Type Bootrec /RebuildBcd, and then press ENTER.

    • If the Bootrec.exe tool runs successfully, it presents you with an installation path of a Windows directory. To add the entry to the BCD store, type Yes. A confirmation message appears that indicates the entry was added successfully.

    • If the Bootrec.exe tool cannot locate any missing Windows installations, you must remove the BCD store, and then you must re-create it. To do this, type the following commands in the order in which they are presented. Press ENTER after each command.
      Bcdedit /export C:\BCD_Backup

      ren c:\boot\bcd bcd.old

      Bootrec /rebuildbcd



  8. Restart the computer.


Method 3: Rebuild the BCD store manually by using the Bcdedit.exe tool


If the previous method does not resolve the problem, you can rebuild the BCD store manually by using the Bcdedit.exe tool in the Windows Recovery Environment. To do this, follow these steps:

  1. Put the Windows Vista installation disc in the disc drive, and then start the computer.

  2. Press a key when you are prompted.

  3. Select a language, a time, a currency, and a keyboard or another input method, and then click Next.

  4. Click Repair your computer.

  5. Click the operating system that you want to repair, and then click Next.

  6. In the System Recovery Options dialog box, click Command Prompt.

  7. Type the following command, and then press ENTER:
    cd /d Partition:\Windows\System32

    Note Partition represents the letter of the partition on which Windows Vista is installed. Typically, this is partition C.

  8. Type the following command, and then press ENTER:
    bcdedit /enum all

    In the Windows Boot Loader section of the output from this command, note the GUID that is listed for resumeobject. You will use this GUID later.

  9. Type the following command, and then press ENTER:
    bcdedit -create {bootmgr} -d “Description

    Note Description represents the description for the new entry.

  10. Type the following command, and then press ENTER:
    bcdedit -set {bootmgr} device partition=Partition:

    Note Partition represents the letter of the partition. Typically, the letter is C.

  11. Type the following command, and then press ENTER:
    bcdedit /displayorder {GUID}

    Note GUID represents the GUID that you obtained in step 8.

  12. Type the following command, and then press ENTER:
    bcdedit /default {GUID}

    Note GUID represents the GUID that you obtained in step 8.

  13. Type the following command, and then press ENTER:
    bcdedit /timeout Value

    Note Value represents the time in seconds before the Windows Boot Manager selects the default entry that you created in step 12.

  14. Restart the computer.


If you are booting from a Server 2008 install disk, when you use the “Repair your computer” option, the available options look like this:

You can access the repair option on a Server 2008 disk by choosing “command prompt”, then running  “x:\sources\recovery\StartRep.exe”.

I did this and it worked like a champ!  It found an error, corrected it, and the server was back up and running 10 minutes later.

I have also done this on Server 2008 using a Windows Vista install disk.  Slightly risky, but the server was down anyway, and I was in a pinch.  That also worked.  Along the same lines, I would guess that a Windows 7 install disk would work for Server 2008 R2 if you had no other option.  But don’t hold me to that!