Archive for November, 2009
Yeh after a week has been released, ESX 4.0 update 1 now temporarily suspended from download. The issue is something to do with HP agent running while you patch your ESX will result your system completely unable to boot. The worst thing is, you will not able to recover your system once you reboot and fresh installation may needed. This is not happen to server which don’t have monitoring agent running in the system but, there must be something bigger than that when VMware decided to removed it from download isn’t?. Still remember ESX 3.5 update 2 time bomb?. Then, before you update your ESX 4.0 to ESX 4.0 update 1, better check it out! linkComments are off for this post
[Security-announce] UPDATED VMSA-2009-0014.1 VMware ESX patches for DHCP Service Console kernel and JRE resolve multiple security issues
Twice happened to me when I install and configure windows 2008 64 bit + sql 2008 using 32 bit DSN, my “sqlserveragent” service couldn’t be started and I cant proceed with vCenter installation. No problem with 32 bit DSN creation and same goes to SQL 2008 installation since all services has been configured to run as “NT AUTHORITY\SYSTEM” users.
The error I got is something about “unable to start dependencies program”. However, my sqlserver already started and few changes has been made as below without joice :
- Changed logon user for that service from “NT AUTHORITY\SYSTEM” to other user.
- Add user to SQLSERVER & SQLSERVERAGENT group.
- Changed permission and etc
When I checked the agent log from SQL Server Management Studio, found out “sqlserveragent” was tried to logon as user “NT AUTHORITY\ANONYMOUS LOGON“.No comments
Another woes with HP hardware recently which cost longer downtime to our customer production site. This latest issue related to new patch deployed by HP and caused SAN connectivity issue not only to ESX cluster servers (3.5 U3) but also happened to number of physical blade servers running WIN2K3 operating system. Read moreNo comments
Another my reference.
Scenario : OES Linux running on ESX vm need to join existing tree
- Install SLES + OES
- Pointing ESX Time Server to Master DS
- Make sure edir database, sync & report status OK
- Run $ntpq -p on new sles
- setup slp if possible
- Configure eDir and time server pointing to Master DS
- Configure SLP or scp from existing OES linux server
- Add new server to replica i.e RW
- Verify database, timesync, replica status OK
Note: Failed to point ESX time server to Master DS can caused time drift on OES vm.No comments
Just for my reference :
Scenario : One of OES linux server need to be remove from eDir
- Check Time Sync report $ndsrepair -T
- Check Replica Status $ndsrepair -E
- Everything fine, remove the server from replica $ndsrepair -P -Ad
- Remove Server from edir & uninstall edir $ndsconfig -rm -a admin.novell
- Clean up server object in ConsoleOne
- Server-to-server sync with $ndstrace
- Replica sync status with $ndstrace
- Schema Sync with $ndstrace