Posted on July 2nd, 2008 by thehabgroup
To use enable verbose status messages by editing the registry, follow these steps:
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
4. On the Edit menu, point to New, and then click DWORD Value.
5. Type verbosestatus, and then press ENTER.
6. Double-click the new key that you created, type 1 in the Value data box, and then click OK.
7. Quit Registry Editor.
Note Windows does not display status messages if the following key is present and the value is set to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages
Operating System Windows 2000 Windows XPOperating System Windows 2000 Windows XP
No Comments »
Filed under: Operating System, Windows XP, Windows 2000
Posted on July 2nd, 2008 by thehabgroup
To use enable verbose status messages by editing the registry, follow these steps:
| 1. |
Click Start, and then click Run. |
| 2. |
In the Open box, type regedit, and then click OK. |
| 3. |
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
|
| 4. |
On the Edit menu, point to New, and then click DWORD Value. |
| 5. |
Type verbosestatus, and then press ENTER. |
| 6. |
Double-click the new key that you created, type 1 in the Value data box, and then click OK. |
| 7. |
Quit Registry Editor. |
Note Windows does not display status messages if the following key is present and the value is set to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages
verbose status message Windows Windows 2000 Windows XPverbose status message Windows Windows 2000 Windows XP
No Comments »
Filed under: Windows XP, Windows 2000
Posted on July 2nd, 2008 by thehabgroup
How to modify visual effect on Windows XP for performance.
- Right Click on My Computer on the desktop of the Windows XP machine.
- Select properties.
- Select the Advanced tab -> Performance -> Settings
- Select the Adjust for best performance radio button which unchecks all visual effect features.
The Visual Effects tab in the Performance Options dialog box allows you to select the settings you want to use for the visual effects and performance of Windows XP. with an easy way to set your preferences for the and performance of Windows XP. You can choose one of the following options:
- Let Windows Windows choose what’s best for my computer
- Adjust for best performance
- Adjust for best appearance
- Custom
The custom option allows you to choose which visual effect you want toenable/disable. Adjusting for best apperance uses all of the effects listed; adjusting for best performance uses none of them.
performance Uncategorized visual effects Windows XP XPperformance Uncategorized visual effects Windows XP XP
No Comments »
Filed under: Windows XP
Posted on April 17th, 2008 by thehabgroup
Remote Installation Service Installations
The process of adding OEM Plug and Play drivers to RIS installations involves the same steps that are listed in the “Unattended Setup” section of this article, with two small adjustments:
1. Place the $oem$ folder at the same level as the \I386 folder of the RIS image. For example:
RemoteInstall\Setup\%language\Images\%dir_name%\i386
RemoteInstall\Setup\%language\Images\%dir_name%\$oem$\$1\Drivers
\NIC
\MODEM
\VIDEO
2. Modify the RIS image default template (Ristndrd.sif). In the [Unattended] section, change the OemPreinstall = key value from No to Yes, and then add the OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;), as follows:
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath = Drivers\NIC;Drivers\Modem;Drivers\Video
Note The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Note If one of the OEM-supplied drivers is for a network card device, the RIS server must have this file available when you boot into text-mode Setup.
For additional information about this process, click the article number below to view the article in the Microsoft Knowledge Base:
315279 (http://support.microsoft.com/kb/315279/EN-US/) How to Add a Third-Party OEM Network Adapter to an RIS Installation
3. Stop and then restart the BINL service on the RIS server. To do this, type the following commands at the command prompt, pressing ENTER after each one:
net stop “boot information negotiation layer”
net start “boot information negotiation layer”
ADS Operating System Windows XPADS Operating System Windows XP
No Comments »
Filed under: Operating System, ADS, Windows XP
Posted on February 21st, 2008 by thehabgroup
- Open Regedit
- Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
- if it does not already exist create the key: “NoDriveTypeAutoRun”=dword:000000b5
- Log out and log back in for the settings to take effect
CD Autorun Operating System Windows XPCD Autorun Operating System Windows XP
No Comments »
Filed under: Operating System, Windows XP
Posted on February 4th, 2008 by thehabgroup
- Start -> Run -> type Regedit
- Click on File, then choose “Connect Network Registry”.
- In the Select Computer search box either browse Active Directory to locate the remote server, or type its name in the dialog box.
- In the remote machine’s registry navigate to the following key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
- Under the Terminal Server key locate the value named fDenyTSConnection (REG_DWORD).
- Change the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled).
- Click OK and close Regedit.
- Changes should take effect without a reboot but to be sure type ’shutdown -m \\srv1 -r” at a CMD prompt
- Test connection
Terminal Services Windows XPTerminal Services Windows XP
No Comments »
Filed under: Windows XP, Terminal Services
Posted on January 29th, 2008 by thehabgroup
How to Customize Windows Task Bar Settings
1. Locate a clear area on the taskbar and right click and select properties:
2. Modify settings as you see as show the clock, quick launch bar etc.
3. Click the customize button and select the options that you want.
4. Click OK to save changes.
Operating System Windows XPOperating System Windows XP
No Comments »
Filed under: Operating System, Windows XP
Posted on January 29th, 2008 by thehabgroup
If you find that your desktop icons are corrupted/ garbled, wrong images appear or suffering from frequent redraws then you may need to increase the size of yoru icon cache. To increase the icon cache file (C:\Documents and Settings\Your User Name\Local Settings\Application Data\Iconcache.db) size
System Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer]
Value Name: Max Cached Icons
Data Type: REG_SZ (String Value)
Value Data: 100 - 4096 (default = 500) .
Consider modifying these registry keys as well:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\IconCache]
"Text"="Icon Cache Size"
"Type"="group"
"Bitmap"="SHDOC401.DLL,6"
"HelpID"="update.hlp#51140"
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionexplorerAdvancedIconCacheSmall]
"RegPath"="SoftwareMicrosoftWindowsCurrentVersionExplorer"
"Text"="1024 Icons"
"Type"="radio"
"CheckedValue"="1024"
"ValueName"="Max Cached Icons"
"DefaultValue"="2048"
"HKeyRoot"=dword:80000002
"HelpID"="update.hlp#51140"
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionexplorerAdvancedIconCacheMedium]
"RegPath"="SoftwareMicrosoftWindowsCurrentVersionExplorer"
"Text"="2048 Icons"
"Type"="radio"
"CheckedValue"="2048"
"ValueName"="Max Cached Icons"
"DefaultValue"="2048"
"HKeyRoot"=dword:80000002
"HelpID"="update.hlp#51140"
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionexplorerAdvancedIconCacheLarge]
"RegPath"="SoftwareMicrosoftWindowsCurrentVersionExplorer"
"Text"="4096 Icons"
"Type"="radio"
"CheckedValue"="4096"
"ValueName"="Max Cached Icons"
"DefaultValue"="2048"
"HKeyRoot"=dword:80000002
"HelpID"="update.hlp#51140"
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionexplorerAdvancedIconCacheHuge]
"RegPath"="SoftwareMicrosoftWindowsCurrentVersionExplorer"
"Text"="8192 Icons"
"Type"="radio"
"CheckedValue"="8192"
"ValueName"="Max Cached Icons"
"DefaultValue"="2048"
"HKeyRoot"=dword:80000002
"HelpID"="update.hlp#51140"
Operating System Windows XPOperating System Windows XP
No Comments »
Filed under: Operating System, Windows XP
Posted on August 23rd, 2007 by thehabgroup
If your client computers fail to appear on the computers page of the WSUS admin console then apply the following troubleshooting steps to help isolate the problem:
- Ensure that “Configure Automatic Updates” policy (Group Policy Object Editor -> Computer Configuration,->Administrative Templates-> Windows Components,->Windows Update) is configured with one of the following options:• Notify for download and notify for install: This option notifies a logged-on administrative user before the download and before the installation of the updates.
• Auto download and notify for install: This option automatically begins downloading updates and then notifies a logged-on administrative user before installing the updates.
• Auto download and schedule the install: If Automatic Updates is configured to perform a scheduled installation, you must also set the day and time for the recurring scheduled installation.
• Allow local admin to choose setting.
- Restart the Automatic updates services on the problem computer(s). From a CMD prompt type net stop wuauserv && net start wuauserv
- Verify that you clients can self-update. See http://go.microsoft.com/fwlink/?linkid=79983
- Verify that your clients have received the relevant Windows Update policy. An easy way to verify this is to check the properties of Automatic Updates (Control Panel - > Automatic Updates). If the properties of the AU page are greyed out then it is likely the policy was applied.
- Verify the SUS settings on the problem client. Download the Windows Update Client Diagnostic (http://technet.microsoft.com/en-us/wsus/bb466192.aspx) run against a problem client. A report will be generated on the clients status.
- If some clients appear in the WSUS console then you can be convinced that the server settings are correct.
- Check the IIS logs on the WSUS server for any relevant errors. Location: %windir%\system32\LogFiles\W3SVC1
- Ensrue that the problem client can communicate with the WSUS server by browsing to http://WSUSServerName/selfupdate/wuident.cab. If the download prompt appears then communication is fine. Otherwise investigate.
- Edit the following registry keys on the problem client manually: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\
Value name: WUServer
Registry Value Type: Reg_SZ
This value sets the WSUS server by HTTP name (for example, http://IntranetWSUS).
Value name: WUStatusServer
Registry Value Type: Reg_SZ
This value sets the WSUS statistics server by HTTP name (for example, http://IntranetWSUS).HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
Add any one of the following settings:
• Value name: NoAutoUpdate
Value data: 0 or 1
• 0: Automatic Updates is enabled (default).
• 1: Automatic Updates is disabled.
Registry Value Type: Reg_DWORD
• Value name: AUOptions
Value data: 1 to 4
• 1: Keep my computer up to date has been disabled in Automatic Updates.
• 2: Notify of download and installation.
• 3: Automatically download and notify of installation.
• 4: Automatically download and scheduled installation.
Registry Value Type: Reg_DWORD
• Value name: ScheduledInstallDay
Value data: 0 to 7
• 0: Every day.
• 1 through 7: The days of the week from Sunday (1) to Saturday (7).
Registry Value Type: Reg_DWORD
• Value name: ScheduledInstallTime
Value data: n, where n equals the time of day in a 24-hour format (0-23).
Registry Value Type: Reg_DWORD
• Value name: UseWUServer
Value data: Set this value to 1 to configure Automatic Updates to use a server that is running Software Update Services instead of Windows Update.
Registry Value Type: Reg_DWORD
• Value name: RescheduleWaitTime
Value data: m, where m equals the time to wait between the time Automatic Updates starts and the time it begins installations where the scheduled times have passed. The time is set in minutes from 1 to 60, representing 1 minute to 60 minutes)
Registry Value Type: Reg_DWORD
- It may sound silly but refresh the Computers page in the WSUS administration console
Windows XP WSUS WSUS administration console WSUS client computersWindows XP WSUS WSUS administration console WSUS client computers
No Comments »
Filed under: Windows XP, WSUS
Posted on August 23rd, 2007 by thehabgroup
If you have a stand alone networked Windows Xp computer then it is likely exposed to all manner of threats such as hackers, viruses and malware. The following tips will provide a defense wall against some of these threats:
- Ensure that you keep up to date with the latest Microsoft security bulletins (http://www.microsoft.com/technet/security/current.aspx), hotfixes and Windows updates.
- Verify that all harddisk partitions are formatted with NTFS
- Delete or disable all non-required local accounts
- Protect the Registry from Anonymous access
The default permissions do not restrict remote access to the registry. Only administrators should have remote access to the registry, because the registry editing tools support remote access by default. To restrict network access to the registry:
Add the following key to the registry:
1. Open the registry editor in 32 bit mode with the command “regedt32”
2. Hive
3. HKEY_LOCAL_MACHINE \SYSTEM
4. Key
5. \CurrentControlSet\Control\SecurePipeServers
6. Value Name
7. \winreg
8. Select winreg, click the Security menu, and then click Permissions.
9. Set the Administrators permission to Full Control, make sure no other users or groups are listed, and then click OK
- Set Strong Password Values
Use the Local Security Policy snap-in (gpedit.msc from Start -> Run) to strengthen the system policies for password acceptance. Microsoft suggests that you make the following changes:
1. Set the minimum password length to at least 10 characters
2. Set a minimum password age appropriate to your network (typically between 1 and 7 days)
3. Set a maximum password age appropriate to your network (typically no more than 45 days)
4. Set a password history maintenance (using the “Remember passwords” option) of at least 5
- Rename the Administrator’s account
- Establish a decoy account named “Administrator” with no privileges. Scan the security event log regularly looking for attempts to use this account.
- Set up the audit policies:
Go to Administrative Tools\Local Policies\Audit Policy
Set:
• Audit account logon events to Success/Failure
• Audit account management to Success/Failure
• Audit directory service access to Success/Failure
• Audit logon events to Success/Failure
• Audit object access to Success/Failure
• Audit policy change to Success/Failure
• Audit privilege use to Success/Failure
• Audit system events to Success/Failure
- Set User rights Assignment Policies: Go to Administrative Tools\Local Policies\User Rights Assignment Set:
• Access this computer from the network to: Administrators, Authenticated Users
• Act as part of the Operating System: Revoke all security groups and accounts
• Add workstation to domains: Administrators
• Allow log on locally: Administrators, Backup Operators
• Allow log on through Terminal Services: Administrators
• Change the system time: Administrators
• Debug programs: Revoke all security groups and accounts
• Deny access to this computer from the network: Anonymous Logon, Built-in Administrator, Guests, all
• Deny log on as batch job: Guests, Guest
• Deny log on through Terminal Services: Built-in Administrator, Guests, all Non-operating System service accounts, Guest
• Enable computer and user accounts to be trusted for delegation: Revoke all security groups and accounts
• Impersonate a client after authentication: Local Service, Network Service
• Lock pages in memory: Administrators
• Log on as batch job: Revoke all security groups and accounts
• Profile single process: Administrators
• Restore files and directories: Administrators (unless this is a backup server)
• Shut down the system: Administrators
• Synchronize directory service data: Revoke all security groups and accounts
- Set Security options policy Go to Administrative Tools\Local Policies\Security Options
- Set:
• Devices: Restrict CD-Rom access to locally logged-on user only: Administrators
• Devices: Restrict floppy access to locally logged-on user only: Administrators
• Domain Controller: Allow server operators to schedule tasks: Disabled
• Domain Controller: Refuse machine account password changes: Disabled
• Domain member: Require strong (Windows 2000 or later) session key: Enabled
• Interactive logon: Do not display last user name: Enabled
• Interactive logon: Message title for users attempting to log on:
• Interactive logon: Number of previous logons to cache: 0
• Interactive logon: Require Domain controller authentication to unlock workstation: Enabled
• Microsoft Network client: Digitally sign communications (Always): Enabled
• Microsoft Network Server: Digitally sign communications (Always): Enabled
• Microsoft Network Server: Digitally sign communications (If client agrees): Enabled
• Network access: Do not allow anonymous enumeration of SAM accounts and shares: Enabled
• Network Access: Do not allow storage of credentials or .Net passports for network authentication: Enabled
• Network access: Named Pipes that can be accessed anonymously: None
• Network access: Shares that can be accessed anonymously: None
• Network access: Do not store LAN Manager hash value on next password change: Enabled
• Network security: Minimum session security for NTLM SSP based (including secure RPC) clients: Enable all settings
• Network security: Minimum session security for NTLM SSP based (including secure RPC) servers: Enable all settings
• System Objects: Default owner for objects created by members of the Administrators group: Object Creator
• System settings: Optional subsystems: None
- Install reputable Antivirus software and update virus definitions daily
- Install firewall sofware or configure to allow only needed ports/applications network access
- Apply the following registry keys (note ensure that you make backup of the keys before proceeding:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\
Security Consideration for Network Attacks
Subkey RegistryValue Entry Format Value
EnableICMPRedirect DWORD 0
SynAttackProtect DWORD 1
EnableDeadGWDetect DWORD 0
EnablePMTUDiscovery DWORD 0
KeepAliveTime DWORD 300,000
DisableIPSourceRouting DWORD 2
TcpMaxConnectResponseRetransmissions DWORD 2
TcpMaxDataRetransmissions DWORD 3
PerformRouterDiscovery DWORD 0
TCPMaxPortsExhausted DWORD 5=========================================================================HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\
Explorer\AFD.SYS Settings
Subkey RegistryValue Entry Format Value
DynamicBacklogGrowthDelta DWORD 10
EnableDynamicBacklog DWORD 1
MinimumDynamicBacklog DWORD 20
MaximumDynamicBacklog DWORD 20000
Disable Autorun: Disable Autorun for all drives
Subkey RegistryValue Entry Format Value
NoDriveTypeAutoRun DWORD 0xFF
=========================================================================
HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\
Make Screensaver Password Protection Immediate: The
time in seconds before the screen saver grace period
expires (0 recommended)
Subkey RegistryValue Entry Format Value
ScreenSaverGracePeriod String 0
=========================================================================
HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\Eventlog\Security\
Security Log Near Capacity Warning: Percentage threshold
for the security event log at which the system will generate
a warning
Subkey RegistryValue Entry Format Value
WarningLevel DWORD 90
See Also:
Security Terminology
Windows 2003 Security Services Reference
Security Windows XPSecurity Windows XP
1 Comment »
Filed under: Windows XP, Security