How often do you wonder if a peticular phone will work in some country?
Now you can just lookup the band of the phone e.g. 850/1900 and go to GSM World :
1. Search the country you want your phone to work
2. lookup the phone company
3. check if your phone's band is the same as the phone company
That's it folks....
woensdag 29 september 2010
donderdag 23 september 2010
Taskbar Repair Tool Plus!
Needing a way to restore your taskbar to the the default settings?
Have a look at Taskbar Repair Tool Plus! to fix it.
When your at ;-) Look for the other Windows XP info/tweaks and goody found at: http://www.kellys-korner-xp.com
Have a look at Taskbar Repair Tool Plus! to fix it.
When your at ;-) Look for the other Windows XP info/tweaks and goody found at: http://www.kellys-korner-xp.com
Repair the Windows SBS 2008 Console
When running Windows 2008 or SBS 2008 Server, the console may pop-up with a message that is has stopped running. This seems to be related to installing SQL Server, installing som MS Updates or installing Internet Explorer 7 or 8.
I fixed this by just repairing the console and do a reboot when asked.
Check this link (Technet) for the precise repair instructions.
Please follow the index at the left to read other interesting info.
In short, do a repair of: Windows Small Business Server 2008.
You may need the original Windows CD/DVD (I just ignored it, and that worked out for me ;-))
I fixed this by just repairing the console and do a reboot when asked.
Check this link (Technet) for the precise repair instructions.
Please follow the index at the left to read other interesting info.
In short, do a repair of: Windows Small Business Server 2008.
You may need the original Windows CD/DVD (I just ignored it, and that worked out for me ;-))
vrijdag 17 september 2010
Attachment size in exchange 2003
1. Open ESM ( Exchange System Manager ) > Expand Global Settings > Right click Message Delivery then click Properties.
2. Click on Defaults TAB , set your Message size limit then click OK to accept changes .
2. Click on Defaults TAB , set your Message size limit then click OK to accept changes .
CallerID Blocking
CallerIDBlock allows you to selectively decide for which phone numbers CallerID (your phone number) is sent and for which it is suppressed. This little utility is especially useful, since the standard phone CallerIDfeature is limited to only 3 rather restrictive options: No CallerID,
CallerID for contacts only, and CallerID for all.
Lets face it, in the real world you need to have the flexibility to decide whether to send your
CallerID for every phone number individually or not.
With CallerIDBlock you can add phone numbers manually, by importing your contacts automatically, or whenever you dial a new number. Imported contact numbers do not block CallerID (by default), whereas newly dialed numbers automatically block CallerID.
Explanation from Microsoft how CallerID works on Windows Mobile.
http://www.microsoft.com/windowsmobile/en-us/help/v6-0/set-up-caller-ID-touch.aspx
CallerID Managing Application for Windows Mobile (Shareware $10.00)
http://mobiletimes.site50.net/html/calleridblock_pr1.html
Download Link App: http://calleridblock.googlecode.com/files/CallerIDBlock100d.ZIP
CallerID for contacts only, and CallerID for all.
Lets face it, in the real world you need to have the flexibility to decide whether to send your
CallerID for every phone number individually or not.
With CallerIDBlock you can add phone numbers manually, by importing your contacts automatically, or whenever you dial a new number. Imported contact numbers do not block CallerID (by default), whereas newly dialed numbers automatically block CallerID.
Explanation from Microsoft how CallerID works on Windows Mobile.
http://www.microsoft.com/windowsmobile/en-us/help/v6-0/set-up-caller-ID-touch.aspx
CallerID Managing Application for Windows Mobile (Shareware $10.00)
http://mobiletimes.site50.net/html/calleridblock_pr1.html
Download Link App: http://calleridblock.googlecode.com/files/CallerIDBlock100d.ZIP
dinsdag 7 september 2010
How to DELETE Windows Local & Domain Cached Credentials
To delete locally cached credentials you could type the following command in the 'Run' prompt:
CONTROL USERPASSWORDS2 or rundll32.exe keymgr.dll,KRShowKeyMgr
(The user may have to be a local administrator to remove the caches password. This is not conclusive yet.)
Not many of us would have come across the interfaces which get launched after executing the above mentioned commands. Browse to Advanced>Manage Passwords, and you'll see all the credentials which are locally cached. You could Add/Delete them, bear in mind that you need to run this command as an Administrator.
Now, coming to an interesting part which I recently came across; where do we look out for user credentials cached at the domain level??
If you launch Windows registry with SYSTEM level privilege and browse to "HKEY_LOCAL_MACHINE\SECURITY\CACHE", you will find a total of 10 entries starting from NL$1 to NL$10. These binary entries contain users cached credentials at the domain level.
By default Windows allows a total of 10 credentials to be cached and if all 10 entries are full, any new credential to be cached will be overwritten by the Value Date in the oldest NL$ entry.
Also, to know how many free entries are left, simply count the number of entries whose binary value data is full of '0'.
For those who wish to know how to gracefully clear the domain cached credentials, this cannot be achieved by deleting these entries.
If you delete the NL$ entries, Windows will never cache any users credentials in the future.
Simply edit the "Value Data" in each NL$ entry and replace the data with '0' (ZERO). This will clear all the existing cached credentials.
A key thing to note over here is:
Windows Registry with SYSTEM level privilege cannot be launched by simply executing REGEDIT.EXE from the RUN prompt. You will need to launch it as follows:
at xx:xx /interactive "regedit.exe"
Where XX:XX is the time in the FUTURE when you would want to launch the registry. Suppose if the system time on your Server/Desktop shows 23:50 then you could type
at 23:51 /interactive "regedit.exe
This would launch the registry with SYSTEM level privilege when your server/desktop clocks 23:51.
Again, you will succeed to launch this only if you are logged onto the system as an Administrator.
This works with Windows XP/2000/2003 and may also work with 2008 but I have not tried it there.
CONTROL USERPASSWORDS2 or rundll32.exe keymgr.dll,KRShowKeyMgr
(The user may have to be a local administrator to remove the caches password. This is not conclusive yet.)
Not many of us would have come across the interfaces which get launched after executing the above mentioned commands. Browse to Advanced>Manage Passwords, and you'll see all the credentials which are locally cached. You could Add/Delete them, bear in mind that you need to run this command as an Administrator.
Now, coming to an interesting part which I recently came across; where do we look out for user credentials cached at the domain level??
If you launch Windows registry with SYSTEM level privilege and browse to "HKEY_LOCAL_MACHINE\SECURITY\CACHE", you will find a total of 10 entries starting from NL$1 to NL$10. These binary entries contain users cached credentials at the domain level.
By default Windows allows a total of 10 credentials to be cached and if all 10 entries are full, any new credential to be cached will be overwritten by the Value Date in the oldest NL$ entry.
Also, to know how many free entries are left, simply count the number of entries whose binary value data is full of '0'.
For those who wish to know how to gracefully clear the domain cached credentials, this cannot be achieved by deleting these entries.
If you delete the NL$ entries, Windows will never cache any users credentials in the future.
Simply edit the "Value Data" in each NL$ entry and replace the data with '0' (ZERO). This will clear all the existing cached credentials.
A key thing to note over here is:
Windows Registry with SYSTEM level privilege cannot be launched by simply executing REGEDIT.EXE from the RUN prompt. You will need to launch it as follows:
at xx:xx /interactive "regedit.exe"
Where XX:XX is the time in the FUTURE when you would want to launch the registry. Suppose if the system time on your Server/Desktop shows 23:50 then you could type
at 23:51 /interactive "regedit.exe
This would launch the registry with SYSTEM level privilege when your server/desktop clocks 23:51.
Again, you will succeed to launch this only if you are logged onto the system as an Administrator.
This works with Windows XP/2000/2003 and may also work with 2008 but I have not tried it there.
Network Password Recovery
Location Network Password
Windows Network Passwords (XP/Vista/2003): When you connect to the file system of another computer on your network (something like \\MyComp\MyFolder), Windows allows you to save the password. If you choose to save the password, the encrypted password is stored in a credential file.
The credential file is stored in the following locations:
Where the network passwords are stored?
Older versions of Windows (Windows 95,98 and ME) stored the network passwords in pwl files located under the main Windows folder.
Starting from Windows XP, the network passwords are encrypted inside the Credentials file, located under Documents and Settings\\Application Data\Microsoft\Credentials\. Some passwords may also be stored in the Credentials file under Documents and Settings\\Local Settings\Application Data\Microsoft\Credentials\.
In addition to the passwords of network shares, Windows XP also stores the passwords of .NET Passport (MSN Messenger) in the same Credentials files
(Info from Nirsoft)
Windows Network Passwords (XP/Vista/2003): When you connect to the file system of another computer on your network (something like \\MyComp\MyFolder), Windows allows you to save the password. If you choose to save the password, the encrypted password is stored in a credential file.
The credential file is stored in the following locations:
- Windows XP/2003: [Windows Profile]\Application Data\Microsoft\Credentials\[User SID]\Credentials and [Windows Profile]\Local Settings\Application Data\Microsoft\Credentials\[User SID]\Credentials
- Windows Vista: [Windows Profile]\AppData\Roaming\Microsoft\Credentials\[Random ID] and [Windows Profile]\AppData\Local\Microsoft\Credentials\[Random ID]
Where the network passwords are stored?
Older versions of Windows (Windows 95,98 and ME) stored the network passwords in pwl files located under the main Windows folder.
Starting from Windows XP, the network passwords are encrypted inside the Credentials file, located under Documents and Settings\
In addition to the passwords of network shares, Windows XP also stores the passwords of .NET Passport (MSN Messenger) in the same Credentials files
(Info from Nirsoft)
Abonneren op:
Posts (Atom)