There is a limitation in the number of logon that a user can perform in a computer that has not connection with its domain controller. In this case, the logon process use the cached logon information stored in the computer.
This number is by default 10 for Windows XP and Windows Vista.
This default behaviour could be changed using the Key CachedLogonsCount stored in the Registry Path HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\winlogon
Valid values for this key are from 0 to 50.
In case you want to deny logon for domain login accounts if the active directory domain is not reachable you can set this value to 0.
Logon with cached identity : [CachedLogonsCount]
Posted in Registry Tips.
– June 20, 2008
Extending Windows Vista and Windows Server 2008 evaluation period : [ Rearm]
The installation of Windows Vista and Windows Server 2008 includes an evaluation period that allows you to using full features of both products for a period of 30 days for Windows Vista and 60 days for Windows Server 2008 without having a valid and legal product key.
Also, Microsoft includes by default a supported and legal way to extend that evaluation period for three more times. In this way, you can evaluate Windows Vista without having a valid product key for a period of time of 120 days and Windows Server 2008 for a period of time of 240 days.
The procedure is so easy as to execute a .vbs script that is included by default into C:\Windows\System32 directory. This script .vbs script is named slmgr.vbs and the commando to execute before the evaluation period expires, for example the day before, is the following :
C:\Windows\System32\slmgr.vbs –rearm
You must to restart the computer to apply the new evaluation period after the command execution.
You have the chance to apply this procedure for three times.
There are many options related to licensing topic that you can manage with this .vbs script, as you can see in the following usage instructions:
Usage: slmgr.vbs [MachineName [User Password]] [Option]
MachineName: Name of remote machine (default is local machine)
User: Account with required privilege on remote machine
Password: password for the previous account
Global Options:
-ipk
Install product key (replaces existing key)
-ato
Activate Windows
-dli [Activation ID | All]
Display license information (default: current license)
-dlv [Activation ID | All]
Display detailed license information (default: current license)
-xpr
Expiration date for current license state
Advanced Options:
-cpky
Clear product key from the registry (prevents disclosure attacks)
-ilc
Install license
-rilc
Re-install system license files
-rearm
Reset the licensing status of the machine
-upk
Uninstall product key
-dti
Display Installation ID for offline activation
-atp
Activate product with user-provided Confirmation ID
– June 5, 2008
Install Windows Components in an unattended manner : [ sysocmgr.exe]
Microsoft provides a tool to install and uninstall from command prompt the same components and subcomponents that you can manage from Control Panel -> Add/Remove Programs. This tool is named SYSOCMGR.EXE and is located by default into %systemroot%\system32 folder.
So, in this way you have the opportunity to install in an unattended manner whatever Windows component.
The syntax to run the tool is the following :
SYSOCMGR.EXE /i:%windir%\inf\sysoc.inf /u:c:\components.txt
Where sysoc.inf is the file used by Windows every time you launch Add/Remove programs from Control Panel.
And the second one, components.txt in this example, is the file where we are going to set what componentes/subcomponentes to install/uninstall. The name of the file can be whatever you like.
And the content of the file is something like the next one, in this case an example about how to install MS Radius Server (Internet Authentication Service) :
[Components]
netoc = on
[NetOptionalComponents]
IAS = 1
You can use in the text file just on/off and 1/0 for installation/uninstallation of Components and Subcomponets.
– May 16, 2008
Manage WLAN Profiles in Windows Vista : [netsh wlan]
Windows Vista includes a new feature that allow us to manage Wireless connection profiles as .xml files. In this way we can export all or just some of the wireless connections defined in a Windows Vista (or Windows 2008) machine. After that we can manipulate that files to make changes in the connection properties that we can´t do it using the GUI. Once we have the right .xml file, the original one or the modified one, we can import that file and its connections to the same machine or to a different one.
The command to see all wlan profiles defined in the machine :
– netsh wlan show profile
In this way we can see also what profiles have been created by the user and what others have been created using group policies.
The command to export one profile :
– netsh wlan export profile name=”profile name to export” folder=”folder where to store the .xml file”
If you want to export all the profiles just omit the name= modifier.
The command to import one profile :
– netsh wlan add profile filename=”path and name of the .xml file to import” user=current/all
If you omit the user= modifier the profile will be imported fot all users.
– April 17, 2008
Windows Version and Build Number : [PaintDesktopVersion]
If you want to show in desktop, lower-right corner, the version and build number of your Windows Operating System you have just to set to 1 the key PaintDesktopVersion into registry path:
HKEY_CURRENT_USER\Control Panel\Desktop
Posted in Registry Tips.
– April 1, 2008
