Wednesday, July 15, 2009
Wednesday, June 17, 2009
Create .cab file to install your OWA certificate on Windows Mobile device
If your company uses exchange Activesync to allow users to synchronize their email boxes with Windows Mobile or Activesync enabled OSs.
Some companies might use its own SSL certificate that is signed by internal CA so when mobile device user tries to configure his mobile to sync, he will need to install the root cert for his server to be able to establish the SSL channel.
In this article I have shown the instruction on how to create cab file(Windows mobile setup file) so users can download prior to configure their mobiles.
This steps requires two tools
sslchainsaver mail.company.com
It will also create one folder contain the certificates named mail.company.com and two files called
MAIL.Company.COM.wm5.xml
MAIL.Company.COM.wm6.xml
you can view the contents of the file by typing
type MAIL.Company.COM.wm6.xml
to create the cab file rename the mail.company.com.wm6.xml to _setup.xml
use the command makecab to create the cab file
makecab _setup.xml companycert.cab
then copy companycert.cab file to your Windows Mobile device and run the file.
To download makecab click on this link http://support.microsoft.com/kb/310618
To download Windows Mobile SSLChainSaver http://www.microsoft.com/downloads/details.aspx?FamilyID=6123EB55-6590-4643-8E7F-11C177104DE2&displaylang=en
Sunday, June 14, 2009
Installing SQL Cluster in Windows 2008
Installation of Cluster service consists of certain stages
1- Configure Hardware(shared Storage, Heartbeat NIC)
2- Install Failover Cluster feature
3- Create Cluster Group
4- Add shared Hardware
5- Install SQL 2005
6- Install SQL 2005 SP2
Here below some details.
Install Failover Cluster through Add features
Create Cluster Group
Add shared disk to the cluster group
Add more cluster nodes
Start Installing SQL Server 2005 on one of the cluster nodes.
The installation of SQL server 2005 is now completed.
if you look at the Failover Cluster Management Snap-in, you will find that the Cluster resources( Name of the cluster and IP and the SQL services) one of these services is failed to start, this is because compatibility issues with Windows Server 2008; the minimum supported version is SQL Server 2005 SP2, once it get installed everything will work fine.
Friday, May 15, 2009
Uninstall Products using VB script
The below lines are for VBS script file you can use to uninstall
| 1 | strComputer = "." |
| 2 | Set objWMIService = GetObject("winmgmts:" _ |
| 3 | & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") |
| 4 | Set colSoftware = objWMIService.ExecQuery _ |
| 5 | ("SELECT * FROM Win32_Product WHERE Vendor = 'Hewlett-Packard'") |
| 6 | For Each objSoftware in colSoftware |
| 7 | objSoftware.Uninstall() |
| 8 | Next |
in Line 1 you define variable called strComputer which is the computer you would like to execute this script against, in this case the value is “.” so this means localhost (locally)
Line 2 is to define Variable named objWMIService and to call WMI functions which is defined by winmgmts:
in the background the system loads Wbemdisp.dll which contains the Scripting Library functions
In VBS script they always split the functions in multiple lines although it can be used as one line, anyway
Line 3 which privilege level will be used in access the WMI
impersonationLevel=impersonate then the computer we are connecting to which is strComputer variable then the WMI class location "\root\cimv2”
Line 4 and 5 is one line but we use _ underscore to allow go to the next line (something like escape character) line 4 we define variable to contain the previously called data plus the function we are interested to call like query the WMI we use ExecQuery function. in line 5 we type our WMI QUERY Language where we select all columns available in class name win32_product and for not displaying all product we can filer the data by using certain colmn value like name of the product or vendor
SELECT * FROM Win32_Product WHERE Vendor = 'Hewlett-Packard'
I have to sleep now
lets continue tomorrow
Upgrade from the Windows 7 beta to the Release Candidate
Source:http://windowsitpro.com/
Q. How do I upgrade from the Windows 7 beta to the Release Candidate?
A. There's no officially supported way to upgrade from the beta of Windows 7 (build 7000) to the Windows 7 Release Candidate (build 7100). Microsoft developers wanted to focus on the common end user upgrade experience, which will be from Windows Vista to Windows 7, and didn't want to waste cycles on getting a perfect upgrade experience from a beta. It is also expected that there will be no direct upgrade from the Release Candidate to the final release.

There is, however, a way you can do an in-place upgrade. This method will probably also work for an upgrade from RC to final.
- Copy the contents of the Windows 7 RC to your local hard disk.
- Access the Source directory within the copied Windows 7 RC location.
- Open cversion.ini in Notepad.
- Change the MinClient value from 7100 to 7000, as shown here:
[HostBuild]
MinClient=7000
MinServer=7000
- Save the file.
- You'll now be able to perform an in-place upgrade from the beta to the RC.