Upgrading from VMWare GSX to VMWare Server

gsx3-2-0.gifVMWare-Server

Well, yesterday evening I said goodbye to VMWare GSX and installed the free successor: VMWare Server !

I knew it had to come sooner or later but due to my crappy Speedtouch 716v5 modem (New post about this modem will be soon available) I was unable to use my real firewall and Copfilter so I had to speed up my plans and upgrade sooner than hoped.
What a night it was. Beforehand, I removed the snapshots of a few of my virtual machines just to make sure everything was in synch.
Started the setup and promptly Server detected that I already had GSX Server installed.
Setup is going to uninstall GSX first is that ok..? [Yes fine]
Setup is uninstalling but in a split second a new screen (with only the top bar visible) popped up with no message. Setup was still trying to uninstall GSX…after some tea and some more waiting and finally after feeling the life flowing from my body, setup had still not uninstalled GSX!
I ran task manager to see what was going on…2 setups were running.
I decided to kill the top one. (nail biting at the same time!)
The popup screen dissappeared and GSX was uninstalled! After that the setup continued with installing VMWare Server….[“Feeeeeehhhhwww”] I thought.
After the Pearl thingies were installed, setup got reminded that I killed his poor little popup brother and decided to repay me by rolling back all actions and leaving me with a Windows 2003 server with NO VMWare Server and NO GSX Server anymore….oh the horror of it all…unbelievable but nonetheless true..

What now..? First some Yoga to kill my natural instinct of throwing my server out, through the window…
That helped!
Now rebooted my box, logged in as a local administrator, checked the VMWare directory (there were a few files left), deleted the whole directory, cleaned out the HKLMVMWare key and started setup again..!

This time VMWare Server did not detect GSX anymore and installed without hassle.
I still have to upgrade my virtual hardware but all things in due time…
So these are the tips I can give you when you are going to upgrade from a production GSX server to VMWare Server:
– Stay calm
– Stay calm (breathe in, breathe out)
– You may be best of, de-installing GSX yourself instead of leaving it to the installer of Server.
– Have a copy of your GSX software ready in case of disaster
– Make sure all VM’s have no more snapshots on them
– Login as local administrator (not sure, but it helped me make it true this ordeal)

 

Upgrading Debian Sarge Kernel Image

debian.jpg
Yep, decided to pay attention to the Debian Security Advisory 1103 :

DSA-1103-1 kernel-source-2.6.8 — several vulnerabilities
Well I tried doing my usual apt-get upgrade, but the update didn’t show up. I must have had a hole in my head or something…I asked around on IRC what the correct syntax was for installing this update because I forgot:
apt-get install kernel-image-2.6.8-3-386 did the trick.

After that I rebooted my Virtual Machine, I saw that my virtual network adapter was no longer working..!
That problem lies in the fact that I compiled my VMWare Tools with the kernel-headers from before the update. Now that I booted into the new kernel: no more VMWare-Tools….so now what ?!
First, I reverted my snapshot 🙂
Now, let’s install the kernel-headers that go with the new kernel:
apt-get install kernel-headers-2.6.8-3-386
after that installed the update again

I rebooted, of course no more network because of what I described above.
Now, login through the console and run the following command:
./usr/bin/vmware-config-tools.pl
This command will recompile your VMWare Tools and VMX-Net adapter !

One thing is still bugging me, when I boot my machine, I still see the “older” kernel image listed in my Grub boot loader. I don’t know if I can easily remove it. If Debian releases a couple more Kernel patches like this, I’ll have 10 kernel options to choose from when booting (every kernel image also has a “safe” boot mode)
If someone has a clue on what best practice for this situation, please send me a mail…just put info and a @ infront of my domain and I’ll be waiting 😉

Error 51 or 53 when accessing a W2K share on Terminal Server

Windows logo
Just to remind you that sometimes solutions are much simpler than expected! Never look past the obvious..

All of a sudden my Windows 2000 Terminal Server was not responding to net use commands and shares where unreachable. After looking waaay too deep for the solution, this is what fixed it..:
When you try to use a net view, net use, or a UNC path to access a Windows 2000 based share, you receive one of the following:
System error 53 has occurred. The network path was not found.

System error 51 has occurred. The remote computer is not available.
If you use Server Manager on a Windows NT 4.0 Domain Controller to view the Properties of the Windows 2000 computer, you receive:
The remote computer is not available. net use * \servershare System error 53 has occurred. The network path was not found.

Network Neighborhood may not show the Windows 2000 computer.

If File and Printer Sharing for Microsoft Networks is disabled on the associated network connect, or uninstalled entirely, the above errors will be generated.

To fix the problem, on the Windows 2000 computer that should be hosting the share:
1. Double-click My Computer.
2. Double-click Control Panel.
3. Double-click Network and Dial-Up Connections.
4. Right-click the network connection you want to change and press Properties.
5. If File and Printer Sharing for Microsoft Networks is NOT listed on the General tabs’ Components checked are used by this connection area, press the Install button and double-click Service. Select File and Printer Sharing for Microsoft Networks and press OK.
6. Check the File and Printer Sharing for Microsoft Networks box on the General tab.
7. Press OK. NOTE: Think of File and Printer Sharing for Microsoft Networks as the equivalent of the Windows NT 4.0 Server service.

NOTE: On a Windows 2000 Active Directory domain controller, File and Printer Sharing for Microsoft Networks must be enabled on the ‘network’. NOTE: You can uncheck File and Printer Sharing for Microsoft Networks on specific interfaces where it is not required, such as on a dedicated internet connections

subprocess post-installation script returned error exit status 255

debian.jpg
Uhhhh…that’s what I thought when I tried to patch my mysql package with security updates.
I did a apt-get upgrade as usual and this was the full error I received:
Setting up mysql-client (4.0.24-10sarge2) …
Setting up mysql-server (4.0.24-10sarge2) …
Stopping MySQL database server:
mysqld.dpkg: error processing mysql-server (–configure): subprocess post-installation script returned error exit status 255
Starting MySQL database server: mysqld Errors were encountered while processing: mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1)
mailserver:~# .Checking for crashed MySQL tables in the background.
Now thank the lords of Kobol for VMWare Snapshot technology …I’m running my debian mailserver under VMWare GSX server 🙂 I reverted to my snapshot and tried again…I did two things different (stupid I know but I was in a hurry!)
I closed my mailclient still connected to my mailserver (using mysql as backend) I also did the apt-get upgrade command from the console instead of using SSH. I don’t know why but did not show up this time so all is well for now…

Windows XP AutoAdminLogon

Windows logo
NOTE FROM ME: WHEN YOUR COMPUTER IS IN A DOMAIN I THINK YOU HAVE TO USE DOMAINNAMEUSERNAME INSTEAD OF JUST USERNAME.
You can use Registry Editor to add your log on information. To do this, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsNTCurrentVersionWinlogon
3. Using your account name and password, double-click the DefaultUserName entry, type your user name, and then click OK.
4. Double-click the DefaultPassword entry, type your password under the value data box, and then click OK. If there is no DefaultPassword value, create the value. To do this, follow these steps:
a. In Registry Editor, click Edit, click New, and then click String Value.
b. Type DefaultPassword as the value name, and then press ENTER.
c. Double-click the newly created key, and then type your password in the Value Data box. If no DefaultPassword string is specified, Windows XP automatically changes the value of the AutoAdminLogon registry key from 1 (true) to 0 (false) to turn off the AutoAdminLogon feature.
5. Double-click the AutoAdminLogon entry, type 1 in the Value Data box, and then click OK. If there is no AutoAdminLogon entry, create the entry. To do this, follow these steps: a. In Registry Editor, click Edit, click New, and then click String Value. b. Type AutoAdminLogon as the value name, and then press ENTER. c. Double-click the newly created key, and then type 1 in the Value Data box.
6. Quit Registry Editor.
7. Click Start, click Restart, and then click OK. After your computer restarts and Windows XP starts, you can log on automatically. If you want to bypass the automatic logon to log on as a different user, hold down the SHIFT key after you log off or after Windows XP restarts. Note that this procedure applies only to the first logon. To enforce this setting for future logoffs, the administrator must set the following registry key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsNTCurrentVersionWinlogon
Value:ForceAutoLogon
Type: REG_SZ Data:
1 You can also use turn on automatic logon without editing the registry in Microsoft Windows XP Home Edition and in Microsoft Windows XP Professional on a computer that is not joined to a domain.
To do this, follow these steps:
1. Click Start, and then click Run.
2. In the Open box, type control userpasswords2, and then click OK. Note When users try to display help information in the User Accounts window in Windows XP Home Edition, the help information is not displayed. Additionally, users receive the following error message: Cannot find the Drive:WindowsSystem32users.hlp Help file. Check to see that the file exists on your hard disk drive. If it does not exist, you must reinstall it.
3. Clear the “Users must enter a user name and password to use this computer” check box, and then click Apply.
4. In the Automatically Log On window, type the password in the Password box, and then retype the password in the Confirm Password box.
5. Click OK to close the Automatically Log On window, and then click OK to close the User Accounts window.

The following packages have been kept back

debian.jpg
I run a Debian Mailserver with Postfix..(the best MTA available in my opinion!) within my Debian box, I use the apt-get upgrade functions for security updates. for a little while I kept seeing this message when upgrading:
The following packages have been kept back
Well Google is your best friend and helped find this article which explains why this happens:
Some upgrades show packages being kept back
In short: to fix it you type the command: apt-get dist-upgrade