Remove an OEM Recovery/Boot Partition

Warning: This post deals with editing the boot configuration of your computer. If you don’t know what that is stop right here & ask someone else to help you. Editing the boot configuration incorrectly can cause serious problems that may require you to reinstall Windows. Use the steps below at your own risk.

I recently had a situation where Windows Server 2008 R2 was installed on a Dell OptiPlex 7010 that came with an OEM installation of Windows 7. During the  Windows Server 2008 R2 installation process all partitions were not properly deleted. The result was that the 10GB OEM recovery partition was left intact which also meant that it remained the boot partition. Fast forward a few months & I needed to P2V the computer. Now I’ve got a VM with 10GB of wasted space & a boot configuration which is a mess.

DM1

Now the following steps may vary depending on your situation. As always there are several ways to get the same result. In my case here’s what I did. Note that all commands should be run from an elevated command prompt.

First set the C drive as the active partition. Open Disk Management right click the C drive & select Mark Partition as Active. Now it should look a little more like this.

DM2

The issue now is that the actual boot files are on the Recovery drive & boot manager will still look to the recovery partition for the boot files.

EStillBoot

bootmgrE

Copy the boot file to the C drive by running bcdboot c:\windows /s c:

CBoot

Just in case make a backup of the boot configuration by running bcdedit /export c:\temp\bcs\backup

Note that the C:\Temp folder needs to exist or you will get an error.

Now set the C drive as the boot partition by running bcdedit /set {bootmgr} device partition=C:

Verify the change by running bcdedit as well as looking at Disk Management.

bootmgrC

DM3

Unfortunately with the recovery partition being at the beginning of the disk there is not a built-in way (that I’m aware of) to just delete the partition & reclaim the space without the use of 3rd party utilities. In my case the easiest option was to do a V2V migration (virtual to virtual) of the VM. During the process I did not migrate that partition since it is no longer a system partition. Once that is done I booted up the VM. Now no more OEM partition.

DM4

Error Upgrading vCOps from 5.8.0 to 5.8.1

March 17, 2014 1 comment

Description – When upgrading vCenter Operations Manager (vCOps) from 5.8.0 to 5.8.1 you get an error as the PAK file is being uploaded just before the EULA screen should appear.

1 Error

The error in red is long as can be. Here is just a snippet of the first few lines.

Update bundle ‘vcops-update.zip<script id=”lpjs_csid” defer=”” type=”text/javascript”>var do_experimental_popupfill=!0,MAGIC=”__lpform_”,MAGICIFRAME=”lpformframe”,verbose=!1,g_isie=!0,g_fillaid=null,g_port=!1,g_docnum=0,g_isloggedin=!1,lploggedin=!1,g_weasel_id=null,g_weaseled=!1;function sendBG(a){console_log(“IE skipped sendBG : “+a.cmd)}

If you go back & try again you will notice that the path says C:\fakepath\VMware-vcops-5.8.1-1637685.pak regardless of the path to the file. In my case the PAK file is in C:\Temp.

2 fakepath

Cause – Incompatibility with Internet Explorer 11.

Workaround – Use Firefox to upgrade vCOps. Now when you try the update it just says VMware-vcops-5.8.1-1637685.pak. But this time after clicking Update the update proceeds as normal.

3 pak file

C:\fakepath sounds a little fishy. Now surely VMware didn’t do that on purpose.

 

 

Categories: Computers Tags: , , , , ,

Sure Raise the FFL & DFL…No Problem

February 25, 2014 Leave a comment

They say raising the Forest Functional Level (FFL) & Domain Functional Level (DFL) aren’t a big deal…won’t affect anything. Well apparently I found one of the rare instances where it does & in a big noticeable way. About 9 hours after raising both the FFL & DFL from 2003 to 2008 R2, Exchange 2010 just stopped working. Long story short, restart the KDC service on all DC (or reboot if you can). I also rebooted all Exchange servers for good measure.

As you can see I’m not the only one:

http://visualplanet.org/blog/?p=20

http://www.winsysadminblog.com/2013/02/fixing-kdc-authentication-problems-when-upgrading-your-domain-and-forest-functional-level-from-2003-to-2008-r2/

Here were some of the errors I was getting:

Log Name: Application
Source: MSExchangeRepl
Date: 11/12/2013 6:36:54 PM
Event ID: 4123
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Failed to get the boot time of witness server ‘dc01.domain.com’. Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
 
 
Log Name: Application
Source: MSExchange ADAccess
Date: 11/12/2013 6:40:35 PM
Event ID: 2114
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Process MAD.EXE (PID=8580). Topology discovery failed, error 0×80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
 
 
Log Name: Application
Source: MSExchange ADAccess
Date: 11/12/2013 6:41:23 PM
Event ID: 2103
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=10908). All Global Catalog Servers in forest DC=domain,DC=com are not responding:
DC02.domain.com
DC01.domain.com
 
 
Log Name: Application
Source: MSExchange ADAccess
Date: 11/12/2013 6:42:14 PM
Event ID: 2130
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Process w3wp.exe () (PID=4212). Exchange Active Directory Provider could not find an available domain controller in domain DC=domain,DC=com. This event may be caused by network connectivity issues or configured incorrectly DNS server. This event may also occur if you have not configured correctly your multiple Active Directory sites.
 
 
Log Name: Application
Source: MSExchange ADAccess
Date: 11/12/2013 6:44:23 PM
Event ID: 2604
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Process MSEXCHANGEADTOPOLOGY (PID=10908). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object ABCEX01 – Error code=80040934.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
 
 
Log Name: Application
Source: MSExchange ADAccess
Date: 11/12/2013 6:44:23 PM
Event ID: 2102
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=10908). All Domain Controller Servers in use are not responding:
DC02.domain.com
DC01.domain.com
 
 
Log Name: Application
Source: MSExchange ADAccess
Date: 11/12/2013 6:47:23 PM
Event ID: 2501
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Process MSEXCHANGEADTOPOLOGY (PID=10908). The site monitor API was unable to verify the site name for this Exchange computer – Call=HrSearch Error code=80040934. Make sure that Exchange server is correctly registered on the DNS server.
 
 
Log Name: Application
Source: MSExchangeRepl
Date: 11/12/2013 6:48:14 PM
Event ID: 4116
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.domain.com
Description:
Failed to resolve the fully qualified domain name for the short name ‘EX02′. Verify that the computer account exists. Other operations may fail because of this problem. Error: An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node ‘EX02′ could not be found because of a problem accessing Active Directory: Could not find any available Global Catalog in forest domain.com.

Error powering on a vApp

February 23, 2014 Leave a comment

Description – When powering on a vApp you receive an error that says, “Cannot initialize property ‘vami.netmask0.VM_1′. Network ‘VM Network’ has no associated network protocol profile.”

vAppError

Cause – The IP Pool is not associated to a Virtual Machine Port Group.

Solution – Open the IP Pool settings & select the Associations tab. Put a check by the network that the vApp will run on (e.g. VMNetwork) & click OK. Now power on the vApp.

Categories: Computers Tags: , , ,

Can’t Delete Device From Wyse Device Manager

February 7, 2014 Leave a comment

When deleting a device from Wyse Device Manager (WDM) you may receive a message that say, “Are you sure you want to delete devicename? Note: Force delete command should only be used to delete a device that is no longer checking-in.”

It doesn’t matter if you click Yes or Force Delete the device does not get deleted.

Solution

In WDM browse to Update Manager>Real Time Commands. Select all the update for that device & press Delete. Now go back & delete the device.

Categories: Computers Tags: , ,

Error Activating KMS Server

December 19, 2013 Leave a comment

When activating a KMS server you receive an error that says, “Error: 0x80072EFD”

KMSError

This will happen when the server does not have Internet access. Temporarily allow the server to have Internet access then try again. You should get a message that says, “Product activated successfully.”

KMSWorking

 

Categories: Computers Tags: ,

Message Store Error in Oultook

December 4, 2013 Leave a comment

When a user tries to save an appointment on a shared calendar in Outlook she receives an error that said, “The message store has reached its maximum size. To reduce the amount of data in this message store, select some items that you no longer need, permanently (shift + del) delete them.”

Capture

This can happen if a Storage Quotas value has been set for Prohibit send and receive in Exchange.

Storage Limit

To resolve the issue you can either remove items from mailbox that are no longer needed or increase the storage limit. However if you increase the storage limit it can take up to 2 hours for the setting to take effect. See this link for more details.

A quick workaround (quick being relative to the size of the mailbox in question) is to move the mailbox to another database. Once the mailbox has been moved the updated storage quota setting will take effect.

 

Categories: Computers Tags: , ,

Error Performing Restore

December 3, 2013 Leave a comment

In Windows 8 when using the Windows 7 File Recovery tool to restore files to an alternate drive you may receive an error that says, “A file cannot be restored. Error: Short names are not enabled on this volume (0×80070131).”

1 Error

In Windows 8 all drives other than C have 8.3 name creation disabled. You can verify this by running the following commands from an elevated command prompt:

fsutil behavior query disable8dot3 c:

fsutil behavior query disable8dot3 e:

2 - current 8.3 settings

Notice that 8dot3 is enabled on the C drive but disabled on the E drive. To enable 8dot3 on the E drive running the following command from an elevated command prompt:

fsutil 8dot3name set e: 0

3 set 8.3 on e

Now attempt the restore again & you should not receive the error.

Ref – http://support.microsoft.com/kb/121007

Mail Applet in the Control Not Working

November 18, 2013 2 comments

Warning: This post deals with editing the registry. If you don’t know what that is stop right here & ask someone else to help you. Using the registry incorrectly can cause serious problems that may require you to reinstall Windows. Use the registry at your own risk.

In Windows 7 x64 or Windows Server 2008 R2 the Mail (32-bit) applet shows a blank icon & does nothing when you click on it.

1 not working (modified)

However if you run it manually using the following command it runs just fine.

c:\Windows\SysWOW64\control.exe mlcfg32.cpl

Use the following steps to resolve the issue.

  • Close the Control Panel.
  • Open Regedit & browse to HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Control
    Panel\Cpls
    .
  • Right click mlcfg32.cpl & select Modify.
  • The current value will be something like C:\PROGRA~2\MICROS~2\Office14\MLCFG32.CPL. Note that the path may be different in your case depending on where Office is installed.
  • Change any single character in the path then click OK. (e.g. C:\PROGRA~2\MICROS~3\Office14\MLCFG32.CPL.
  • Close Regedit.
  • Now open the Control Panel & notice that the applet is gone.

2 gone

  • Close the Control Panel.
  • Open Regedit & browse to HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Control
    Panel\Cpls
    .
  • Change the value of mlcfg32.cpl back to C:\PROGRA~2\MICROS~2\Office14\MLCFG32.CPL.
  • Close Regedit.
  • Now open the Control Panel & notice that the applet is back & the icon is displaying properly.

3 working (modified)

  • When you click on the applet the Mail Setup – Outlook dialog box opens.

4 mail setup

Quick Post: Which MSI Version is Installed?

November 9, 2013 Leave a comment

Click Start>Run then type msiexec & press Enter. The Windows Installer dialog box will pop up & show the version number at the top.

MSI_version

A good resource for MSI versions can be found at http://en.wikipedia.org/wiki/Windows_Installer#versions.

Categories: Computers Tags: ,
Follow

Get every new post delivered to your Inbox.

Join 123 other followers

%d bloggers like this: