Error:
Steps:
1.verify the hard disk source storage
2.These error came when mounted LUN inaccessible
3.Try to remove the vm hard disk
4.If error persists remove the VM from inventory
5.Take the backup of .vmx file and download
6.Edit the .vmx file and remove the scsi(x:x) id for the disk
7.save the file and upload it into datastore and add to inventory
8.Now power on the VM
9.Once LUN comes back online add that .vmdk which was removed from .vmx file earlier
1. Right click the RHEL 5.4 VM and click “Install/Upgrade VMware Tools”
2. Create one folder. I created folder in desktop and named as “Test”
3.Copy the media files from CD drive to “Test” folder
4.Open the Terminal,
5. Unzip the archive file by using tar command
6. Go to “vmware-tools-distrib” directory
7. install the tools by executing ./vmware-install.pl
8. While installing choose number for screen resolution ( I selected 12=1024*768)
9. After few seconds vmware tools installed successfully.
We can see safely remove hardware option in windows guest operating system. This is critical one, if we remove network adapter it will cause VM unreachability.
We need to enable one option after power off the VM to hide this “Safely Remove Hardware” Option.
Power off the VM and right click “Edit Settings”
Go to Options and General,
Go to Configuration Parameters
Add Parameter “devices.hotplug” = “false” without quotes
Now, Power On the VM and you can see the task bar, Safely Remove Hardware Hided.
Problem:
Microsoft products such as Windows Server Update Services (WSUS) 3.0 and Windows Sharepoint Services (WSS) 3.0 ship with SQL Server 2005 Embedded Edition. Now called the Windows Internal Database, more and more system administrators charged with managing WSUS and WSS are faced with the challenge of managing these databases. Since most of these system administrators are not full-fledged DBAs, how do they manage the Windows Internal Database?
Solution:
The Windows Internal Database is an embedded data service that can only be used by a handful of Windows Services. It is designed in such a way that you are not allowed to connect to and use this particular database service for non-Microsoft products. By default, installing either WSUS 3.0 or WSS 3.0 will create the databases on the C:\ partition and will cause administration issues such as insufficient disk space. It is quite confusing to manage this SQL Server instance as it does not appear as a SQL Server service nor are there management tools included with the products. The easiest way is to use SQL Server Management Studio Express. You can install a copy of SQL Server Management Studio Express on the server running your WSUS 3.0 or WSS 3.0. You then register this instance using Named Pipes as this is the only configuration for connectivity. Use this server name when you register this instance
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
If you prefer to use scripts to manage these databases, you can download and install the SQL Server 2005 Command Line Query Utility – sqlcmd . This tool will be installed, by default, on this directory
C:\Program Files\Microsoft SQL Server\90\Tools\binn
To connect to the database instance, you need to run the sqlcmd.exe utility, passing the instance name and your credentials
sqlcmd -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query –E
You can then run your administrative T-SQL scripts once connected to this database instance.
Considerations
While these are possible reasons to administer the Windows Internal Database, it is not recommended to do anything beyond performing backups, moving or shrinking the database files. Modifying database schema or database properties would break supportability of these products. Plus, any changes made to these databases can be overwritten by the products’ service packs or cumulative updates.
Reference: Internal DB Access
Dhakshinamoorthy's Blog 