Archive for the ‘Windows’ Category

You are trying remove Exchange 2003, but you get an error similar to “you cannot remove a server that is a target bridgehead for a routing group connector. This server is a target bridgehead for the following connections”.You have removed the connector in ESM.

You have run the Remove-RoutingGroupConnector command on the Exchange 2007/2010 servers

(If you struggle with this step and get an error because you have bi-directional connectors, such as: Remove-RoutingGroupConnector : The operation could not be performed because “RGC NAME” matches multiple entries. Run this command:

get-routinggroupconnector -Identity “RGC NAME” |Remove-RoutingGroupConnector)

You still continue to get the error on the 2003 server.

You have checked in ADSI Edit and the connector isn’t there.

Have you checked the exchange services? Did you disable them for a while to check that Exchange would be OK to remove from the environment? Are they still disabled?

Re-enable them, and start them up. You should be able to remove Exchange 2003 now.

Advertisements

After upgrading an ESX cluster from vSphere 5.0 to vSphere 5.1 a VM failed to reboot.. Instead, an error message was issued:

Failed to start the virtual machine.  Module DevicePowerOn power on failed.  Could not set up “macAddress” for ethernet0. Invalid MAC address specified.  00:0C:29:A0:B0:1D is not an allowed static Ethernet address. It conflicts with VMware reserved MACs.

Troubleshooting

The VM used to run on VMware Server and was transferred later to the ESX infrastructure. It acts as a license server. The services installed are tied to the MAC address of the LAN adapter, Therefore, in the past, the virtual MAC address was assigned statically. Unfortunately the selected MAC address was in the range of VMware’s dynamically assigned addresses. That wasn’t a problem for previous ESX versions, although the method is not recommended. Since version 5.1 addresses in the range 00:0c:29:x:x:x are strictly reserved for dynamic allocation. In the VMX file of the VM, however, was the following entry:

I first put the adapter address in the vSphere Client to “dynamic” and on the next reboot I got an address from the range 00:50:56:x:x:x. The VM did start, but the license service stopped working. So I shut down the VM and edited the VMX file, by entering the original value for the MAC address.

ethernet0.address = "00:0C:29:A0:B0:1D"

Bug exchange

So I got a new error:

“00:0c:29:xx:xx:xx is not an allowed VPX assigned Ethernet address. Invalid MAC address specified. Failed to configure ethernet0.”

The problem was, that the changing from “static” to “dynamic” in the virtual machine settings the addresstype changed to “vpx” automatically.

ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:0c:29:xx:xx:xx"

At this point one has to understand, how addresses are generated.

  • generated : automatically generated by the MUI (MAC address starts with 00:0c:29)
  • vpx : generated automatically by vCenter (MAC address starts with 00:50:56)
  • static : manually assigned MAC address

A correct configuration must look like this:

ethernet0.addressType = "generated"
ethernet0.generatedAddress = "00:0c:29:xx:xx:xx"

(*) Please replace xx:xx:xx with desired bytes. Don’t enter xx:xx:xx into your VMX file! (Thanks for the hint, Al) :-)

After that, you can boot the VM normally again. If you look at the settings, you’ll see the correct MAC address.

MAC is still being generated

In some cases I could see, the correct MAC in the VM settings (while the VM was powered off) in the first place (as shown above), but after starting the VM the MAC has been regenerated. This was due to the UUID of the VM.

Here you have to adjust the last three bytes of uuid.bios to the last three bytes of the desired MAC address. On next boot of the VM you may be asked, whether you have copied or moved the VM. Here you have to choose the “I moved it” selection, because otherwise a UUID and a MAC will be generated on random.

The easiest way to fix the issue is to make a copy of the VMX file with the VM still running on a non upgraded host. Update the copy of the VMX file with the ethernetX.addressType, ExthernetX.generatedAddress and the uuid.bios values (for all the vNics attached), shut down the VM, upload the new VMX, and power the VM back on. This will have your licencing VM off for a very small amount of time.

Once powered up, you can vMotion it over to a 5.1 host and then upgrade the 5.0 host at leisure.

 

(credits to www.elasticsky.de for some of the content)

If you use Windows 7 and you have a touchpad on your laptop, you might find that the cursor jumps around while typing. It is a common issue with the Synaptics touchpad drivers (normally fixed by reinstalling them).

If that doesn’t work, simply install and run this neat application called TouchFreeze http://code.google.com/p/touchfreeze/ and the problem will be gone!

If you run, manage or maintain a computer network, Spiceworks is something you probably should be aware of.
“Spiceworks is the complete network management software, helpdesk, network configuration & IT reporting solution designed to manage everything IT in small & medium businesses.”


Spiceworks now has both an iPhone & Android app for remote management of devices & tickets.

I have been using Spiceworks since version 1.6, & I use it as a full helpdesk ticket system, and my main troubleshooting and network overview tool. The network inventory, which also includes timeline change tracking of devices, and many other useful tools for network administrators is invaluable. VMware & ESX Servers are also supported.
Spiceworks is totally free, supported by unobtrusive & useful IT related advertisements.
A summary of features are below, taken straight from the Spiceworks homepage (hyperlinked):

Inventory Your Network

Monitor Your Network

Run an IT Help Desk

Manage Configuration Changes

Map Your Network

Troubleshoot Network Problems

Be an MSP

Join an IT Pro Community

I really can’t give this product enough credit for what it does and the time it saves.
The community behind Spiceworks are also very knowledgeable, when you need help with pretty much any IT related issue.

You should also check out the “unofficial” SpiceWorks site, which has the latest unreleased news and hints, managed by Andy (akp982), a very active member/friend from the Spiceworks Community.

Click the button below, and try Spiceworks for yourself.
Set It Free!

Here is the situation: You have an Android device and a laptop. You want to transfer files from either the Android device to a laptop (photo’s for example), or from your laptop to the Android device (the latest ROM/Music etc.)

This is very easy, using a wireless router on your home LAN. But what if you are on the road, or at a friends house for example?
The solution is surprisingly simple.

First of all, convert your laptop (or wireless enabled PC) into an Access Point using Connectify for Windows

Connectify allows you to do all sorts of cool things, such as sharing a wired internet connection with multiple devices, as a LAN repeater etc. Check out their website for full details. It is pretty simple to set up, and you can choose whether you want to share the Windows PC’s internet, or just get file access in the setup wizard.
Once Connectify is installed and running, connect your Android device over WifFi using the password you set.

You now have two options, connecting to your Windows PC from the Android device, or vice versa.

Option one – Access files on your Android device from your Windows PC (You need a ROOTED device for this method):
Download the SambaFilesharing app from the Android Market and install it. Enter the relevant information for username and password in the app. Once the app is set up and enabled, simply open an Explorer (not Internet Explorer) window and type in the address bar “\\[android ip]” – (minus quotes and replace [android ip] with the IP shown on the Samba Fileshare screen. You will be prompted for the username/password you set in the app and then have full access to your SD card on the Android device, just like a normal folder on your PC.

Option two – Access files on your windows PC from your Android device:
You will need to have a user account and password on the PC in question in advance for this method.
Download the AndSMB app from the Android Market and install it.
Add a new “server using the same IP details as above, but for the last set of digits, use 1, so xxx.xxx.xxx.1, where the xxx are from the IP, either showing on the Connectify status, or the Samba FileShare app.
Use the windows username and password you set earlier, save the settings and click connect.

You will now be able to see the files on your Windows PC. Clicking “Device File browser” at the top of the AndSMB app will now allow you to upload and download files from whichever folders you have selected in each view. You can switch back again, by pressing “SMB File Browser”.

A really simple way to transfer files both ways from both devices, anywhere & without cables.