From a command line or from Run dialog box (Windows Key + R) enter this command
wuauclt /ShowWU
Showing posts with label Windows 7. Show all posts
Showing posts with label Windows 7. Show all posts
Wednesday, January 30, 2013
Tuesday, January 29, 2013
How to change your MTU size under Vista or Windows 7
- Find your MTU
netsh interface ipv4 show subinterfaces
- Find out what it should be
The host name should be a site you can not reach, -f denotes that icmp packets should not be fragmented, the -l 1472 sets the size of the packet (1472 = Ethernet Default MTU – Packet Header, where the Ethernet Default MTU is 1500 and the Packet Header is 28 bytes).
If the packet can’t be sent because it would need to be fragmented you will get something similar to this:
Packet needs to be fragmented but DF set.
Keep trying lowering packet sizes by 10 (i.e. -l 1460, 1450, 1440, etc.) until you get a successful ping request. Raise your packet sizes by one until you get a "Packet needs to be fragmented but DF set.". The last successful value plus 28 will be your MTU value.
In my case a packet size of 1464 succeeds but 1463 fails, so 1464 + 28 = 1492.
- Set your MTU
For more information you can read the following link.
Wednesday, May 30, 2012
Optimize Windows XP and Windows 7 for file sharing
Click on the "Start" menu and in the "Run" line type "Regedit" and hit Enter.
Navigate to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
The default value of the LargeSystemCache key is "0" (zero). Highlight "LargeSystemCache" and right click it. From the menu select "Modify".
In the new window change the value data from "0" to "1" (one) and click OK.
Next, locate the following key in the registry:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size
By default the "Size" value will be set to "0" or "1". Follow the procedure outlined above to modify the value and change it to "3".
Once you have updated these values close the Registry Editor and reboot the system for the new settings to take effect.
The changes we've made to the registry should resolve the Event ID 2017 and 2021 errors and Source Srv/Lanman errors in the Windows Event Log. This will ensure that shared files and folders remain accessible to network users without the need to reboot the system. This should also keep mapped network drives from disappearing as well as optimize overall network performance of the file server.
For more info read the following article
Navigate to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
The default value of the LargeSystemCache key is "0" (zero). Highlight "LargeSystemCache" and right click it. From the menu select "Modify".
In the new window change the value data from "0" to "1" (one) and click OK.
Next, locate the following key in the registry:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size
By default the "Size" value will be set to "0" or "1". Follow the procedure outlined above to modify the value and change it to "3".
Once you have updated these values close the Registry Editor and reboot the system for the new settings to take effect.
The changes we've made to the registry should resolve the Event ID 2017 and 2021 errors and Source Srv/Lanman errors in the Windows Event Log. This will ensure that shared files and folders remain accessible to network users without the need to reboot the system. This should also keep mapped network drives from disappearing as well as optimize overall network performance of the file server.
For more info read the following article
Tuesday, April 24, 2012
How to reset Winsock and TCP/IP stack in Windows 7
Open an elevated command prompt and then enter the following two commands:
netsh winsock reset catalog (resets winsock entries)
netsh int ip reset reset.log hit (resets TCP/IP stack)
After that reboot your computer.
netsh winsock reset catalog (resets winsock entries)
netsh int ip reset reset.log hit (resets TCP/IP stack)
After that reboot your computer.
Tuesday, January 31, 2012
Slow logins in Windows 7
According to Microsoft the welcome screen may be displayed for 30 seconds during the logon process after you set a solid color as the desktop background in Windows 7 or in Windows Server 2008 R2
To fix this configure the value of the DelayedDesktopSwitchTimeout registry entry. This value determines the time-out interval of a session before Windows 7 or Windows Server 2008 R2 switches between sessions.
To configure the value of the DelayedDesktopSwitchTimeout registry entry, follow these steps:
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\SystemDouble-click the DelayedDesktopSwitchTimeout registry entry.
In the Value data box, type 5, and then click OK.
On the File menu, click Exit.
To fix this configure the value of the DelayedDesktopSwitchTimeout registry entry. This value determines the time-out interval of a session before Windows 7 or Windows Server 2008 R2 switches between sessions.
To configure the value of the DelayedDesktopSwitchTimeout registry entry, follow these steps:
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\SystemDouble-click the DelayedDesktopSwitchTimeout registry entry.
In the Value data box, type 5, and then click OK.
On the File menu, click Exit.
Monday, May 30, 2011
How to Enable AHCI Support in Windows
From this site we read:
Windows 7 and Windows Vista does not install AHCI device driver if it does not detect presence of AHCI support on the system during installation. As the result, if you enable the AHCI in BIOS after Windows is installed, the system may crash and become unbootable.
If you have just notice that your motherboard does indeed support AHCI after you have installed Windows 7 or Windows Vista, but have previously been disabled, here is the trick that enable AHCI support in Windows OS. The step has to be done before AHCI is turned on in BIOS to avoid any system crash.
Type RegEdit into Start Search and hit Enter to start Registry Editor.
If the UAC dialog box prompts and asks "Do you want to allow the following program to make changes to this computer?", click Yes button.
In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci
In the right pane, right click on Start and select Modify.
Set the value data for "Start" to 0, and click OK.
Default value (when AHCI is disabled): 3 for Windows 7 and 4 for Windows Vista.
Close Registry Editor.
Restart the computer.
Go to BIOS configuration and enable the AHCI support. Save the settings and reboot computer again.
After system boots up, Windows will automatically install device drivers for AHCI. After installation completed, Windows will restart for one more time.
The hard disk drives are now supporting AHCI standard.
How to Check if AHCI is Enabled on Windows
If you are unsure if AHCI has been enabled or not in Windows operating system, here is a simple way to verify and determine if the AHCI is already enabled on the system.
Type Device Manager in Start Search and hit Enter.
If the UAC dialog box prompts and asks "Do you want to allow the following program to make changes to this computer?", click Yes button.
Expand IDE ATA/ATAPI controllers section.
If AHCI driver is installed in Windows, there will be entry that reads something similar to Standard AHCI 1.0 Serial ATA Controller or Intel(R) 5 Series 6 Port SATA AHCI Controller.
If you can’t find anything that specifies AHCI Controller, chance is your system don’t have AHCI support in Windows yet (if your system does support AHCI). Follow steps above to enable AHCI in Windows before turning AHCI on in BIOS level.
Windows 7 and Windows Vista does not install AHCI device driver if it does not detect presence of AHCI support on the system during installation. As the result, if you enable the AHCI in BIOS after Windows is installed, the system may crash and become unbootable.
If you have just notice that your motherboard does indeed support AHCI after you have installed Windows 7 or Windows Vista, but have previously been disabled, here is the trick that enable AHCI support in Windows OS. The step has to be done before AHCI is turned on in BIOS to avoid any system crash.
Type RegEdit into Start Search and hit Enter to start Registry Editor.
If the UAC dialog box prompts and asks "Do you want to allow the following program to make changes to this computer?", click Yes button.
In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci
In the right pane, right click on Start and select Modify.
Set the value data for "Start" to 0, and click OK.
Default value (when AHCI is disabled): 3 for Windows 7 and 4 for Windows Vista.
Close Registry Editor.
Restart the computer.
Go to BIOS configuration and enable the AHCI support. Save the settings and reboot computer again.
After system boots up, Windows will automatically install device drivers for AHCI. After installation completed, Windows will restart for one more time.
The hard disk drives are now supporting AHCI standard.
How to Check if AHCI is Enabled on Windows
If you are unsure if AHCI has been enabled or not in Windows operating system, here is a simple way to verify and determine if the AHCI is already enabled on the system.
Type Device Manager in Start Search and hit Enter.
If the UAC dialog box prompts and asks "Do you want to allow the following program to make changes to this computer?", click Yes button.
Expand IDE ATA/ATAPI controllers section.
If AHCI driver is installed in Windows, there will be entry that reads something similar to Standard AHCI 1.0 Serial ATA Controller or Intel(R) 5 Series 6 Port SATA AHCI Controller.
If you can’t find anything that specifies AHCI Controller, chance is your system don’t have AHCI support in Windows yet (if your system does support AHCI). Follow steps above to enable AHCI in Windows before turning AHCI on in BIOS level.
Wednesday, May 4, 2011
Friday, February 25, 2011
How to remove Service Pack 1 backup files from Windows 7
After a successful installation of Windows 7 SP1 you may want to save disk space deleting the backup files created by SP1 installer. After that you cannot uninstall SP1 from your computer.
From an elevated command prompt enter this command:
dism.exe /online /Cleanup-Image /spsuperseded
For more info read the Deployment Guide for Windows Server 2008 R2 with SP1 and Windows 7 with SP1
From an elevated command prompt enter this command:
dism.exe /online /Cleanup-Image /spsuperseded
For more info read the Deployment Guide for Windows Server 2008 R2 with SP1 and Windows 7 with SP1
Saturday, February 19, 2011
How to enable RAS tracing in Windows 7
Open an elevated command prompt
To enable RAS logging, run the command "netsh ras diagnostics set rastracing * enabled"
To enable RAS logging, run the command "netsh ras diagnostics set rastracing * disabled"
The trace logs are created and available at %windir%\tracing folder
RAS Error codes are listed at http://support.microsoft.com/kb/q163111
To enable RAS logging, run the command "netsh ras diagnostics set rastracing * enabled"
To enable RAS logging, run the command "netsh ras diagnostics set rastracing * disabled"
The trace logs are created and available at %windir%\tracing folder
RAS Error codes are listed at http://support.microsoft.com/kb/q163111
Wednesday, January 26, 2011
Sunday, January 23, 2011
How to use teredo protocol in Windows 7
In Windows 7 Microsoft have configured DNS so that the system will never resolve any name to an IPv6 address, as long as the system only has link-local and Teredo IPv6 addresses. The trick is to provide windows with a 6to4 address reducted from your private IPv4 address. Use the following link to create an IPv6 address from your IPv4 address and go to your LAN properties to give this IPv6 static address to your TCP/IPv6 component. In my case the address is 2002:c0a8:3709:: and the prefix is always 48. Do not assign a default gateway address.
Open an elevated command prompt and enter the command
netsh int ipv6 show route
to print the ipv6 routing table. You will see the index of the teredo tunneling interface. In my case the index is 16, so I enter the following command to create a default route through this interface:
netsh interface ipv6 add route ::/0 interface=16
Try to ping ipv6.google.com to see if it's working.
Enter this command to check if teredo is enabled
netsh int teredo show state
If state is offline then enter this command to activate teredo
netsh int teredo set state type=client
and then
netsh interface ipv6 delete route ::/0 interface=16
netsh interface ipv6 add route ::/0 interface=16
We assume here that the interface index is 16.
Windows 7 deactivates this route if there is no ipv6 traffic for a certain period of time. To disable this functionality use the local group policy:
Run gpedit.msc and navigate to Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> IPv6 Transition Technologies
Double click the "Teredo Default Qualified" setting, change it from "Not Configured" to "Enabled", and click OK, then close gpedit.msc
From an elevated command prompt enter the command gpupdate /force to force a refresh of the group policy.
In a windows domain environment teredo is always disabled. You must use the command
netsh int teredo set state type=enterpriseclient
to bypass this restriction
You must also open in your router/firewall the IPv4 udp port 3544 to the traffic travelling from your internal network to the Internet because this port is used from teredo protocol
For more info take a look at http://yorickdowne.wordpress.com/2008/01/26/ipv6-at-home-part-1-overview-teredo/
Open an elevated command prompt and enter the command
netsh int ipv6 show route
to print the ipv6 routing table. You will see the index of the teredo tunneling interface. In my case the index is 16, so I enter the following command to create a default route through this interface:
netsh interface ipv6 add route ::/0 interface=16
Try to ping ipv6.google.com to see if it's working.
Enter this command to check if teredo is enabled
netsh int teredo show state
If state is offline then enter this command to activate teredo
netsh int teredo set state type=client
and then
netsh interface ipv6 delete route ::/0 interface=16
netsh interface ipv6 add route ::/0 interface=16
We assume here that the interface index is 16.
Windows 7 deactivates this route if there is no ipv6 traffic for a certain period of time. To disable this functionality use the local group policy:
Run gpedit.msc and navigate to Computer Configuration -> Administrative Templates -> Network -> TCPIP Settings -> IPv6 Transition Technologies
Double click the "Teredo Default Qualified" setting, change it from "Not Configured" to "Enabled", and click OK, then close gpedit.msc
From an elevated command prompt enter the command gpupdate /force to force a refresh of the group policy.
In a windows domain environment teredo is always disabled. You must use the command
netsh int teredo set state type=enterpriseclient
to bypass this restriction
You must also open in your router/firewall the IPv4 udp port 3544 to the traffic travelling from your internal network to the Internet because this port is used from teredo protocol
For more info take a look at http://yorickdowne.wordpress.com/2008/01/26/ipv6-at-home-part-1-overview-teredo/
Thursday, January 13, 2011
How to connect to a SMB share in a Windows Server using an alias name
According to this Microsoft article when a client computer connects to a Microsoft Windows 2000-based computer or a Microsoft Windows Server 2003-based computer by using an alias name, the client may receive the following error message:
System error 52 has occurred.
A duplicate name exists on the network.
This problem can occur when you try to connect to the server by using a CNAME alias that is created in the DNS zone. For example, this problem may occur with a command similar to the following sample command
net view \\alias.domain name.com
where alias is a CNAME record that is created for the server in the domain name.com zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name.
To resolve this problem in Windows Server 2003, follow these steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
4. Quit Registry Editor.
3. Restart your computer.
You may also have to set the SPN (Service Principal Name) for the Alias Name:
setspn -a host/aliasname targetserver
setspn -a host/aliasname.contoso.com targetserver
The registry key that is mentioned is applicable only to SMB 1.0. To communicate over the SMB2.0 protocol, or CIFS (Common Internet File System), you do not have to set the registry key. SMB 2.0 allows for the functionality described in this article to work by default without additional configuration. Computers that run Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7 support both SMB 1.0 and SMB 2.0. Windows includes an SMB client component (Client for Microsoft Windows) and an SMB server component (File and Printer Sharing for Microsoft Windows). By default, SMB 2.0 is the file sharing protocol that is used when both client and server support it.
The SMB protocol revision to be used for file operations is decided during the negotiation phase. A Windows Vista or later client advertises to the server that it understands the new SMB 2.0 protocol. If the server understands SMB 2.0, SMB 2.0 is used for communication. Otherwise, the client and server use SMB 1.0. If SMB 1.0 is expected to be used, you can set the registry key that is mentioned above on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7.
System error 52 has occurred.
A duplicate name exists on the network.
This problem can occur when you try to connect to the server by using a CNAME alias that is created in the DNS zone. For example, this problem may occur with a command similar to the following sample command
net view \\alias.domain name.com
where alias is a CNAME record that is created for the server in the domain name.com zone. The server is not "listening" on the alias, and therefore is not accepting connections to that name.
To resolve this problem in Windows Server 2003, follow these steps:
1. Create the CNAME record for the file server on the appropriate DNS server, if the CNAME record is not already present.
2. Apply the following registry change to the file server. To do so, follow these steps:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
4. Quit Registry Editor.
3. Restart your computer.
You may also have to set the SPN (Service Principal Name) for the Alias Name:
setspn -a host/aliasname targetserver
setspn -a host/aliasname.contoso.com targetserver
The registry key that is mentioned is applicable only to SMB 1.0. To communicate over the SMB2.0 protocol, or CIFS (Common Internet File System), you do not have to set the registry key. SMB 2.0 allows for the functionality described in this article to work by default without additional configuration. Computers that run Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7 support both SMB 1.0 and SMB 2.0. Windows includes an SMB client component (Client for Microsoft Windows) and an SMB server component (File and Printer Sharing for Microsoft Windows). By default, SMB 2.0 is the file sharing protocol that is used when both client and server support it.
The SMB protocol revision to be used for file operations is decided during the negotiation phase. A Windows Vista or later client advertises to the server that it understands the new SMB 2.0 protocol. If the server understands SMB 2.0, SMB 2.0 is used for communication. Otherwise, the client and server use SMB 1.0. If SMB 1.0 is expected to be used, you can set the registry key that is mentioned above on Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7.
Thursday, September 23, 2010
Windows 7 / Vista loses local resources when connected to VPN
Starting with Vista there is a hidden configuration setting called UseRasCredentials.
If this is set to 1 Windows uses the credentials of the VPN connection for all further accesses (this is contrary to the behaviour of XP).
To fix this problem:
If this is set to 1 Windows uses the credentials of the VPN connection for all further accesses (this is contrary to the behaviour of XP).
To fix this problem:
- Locate the .pbk file that contains the entry that you dial. You can find this file in location C:\Users\Username
\AppData\Roaming\Microsoft\Network\Connections\Pbk - Open the file in Notepad.
- Locate the following entry: UseRasCredentials=1
- Modify the entry to the following: UseRasCredentials=0
- On the File menu, click Save, and the click Exit.
Sunday, September 12, 2010
How to enable administrative shares in windows 7
First use Network and Sharing Center to enable File and Print Sharing
Then run regedit and go to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
In this key enter a 32-bit word value named LocalAccountTokenFilterPolicy with value equal to 1.
Restart the system to activate the change.
To disable this policy delete this value or make it 0.
Then run regedit and go to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
In this key enter a 32-bit word value named LocalAccountTokenFilterPolicy with value equal to 1.
Restart the system to activate the change.
To disable this policy delete this value or make it 0.
Tuesday, September 7, 2010
Friday, September 3, 2010
Windows 7 deployment articles
Read these blog posts:
Capture and Apply Windows Images
Apply Images by Using ImageX
BCDboot Command-Line Options
Deploy a System Recovery Image
http://mikespcbabble.com/WinPE3.aspx
http://blog.brianleejackson.com/sysprep-a-windows-7-machine-start-to-finish-v2
http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part19.html
http://blog.brianleejackson.com/formatting-winpe-3-0-usb-flash-drive-dism
http://edge.technet.com/Media/Deploy-Windows-7-The-Easy-Way-Using-WDS-MDT-and-AIK-Step-By-Step/
http://www.the-d-spot.org/wordpress/2009/11/01/windows-7-lite-touch-installation-with-mdt-2010/
http://www.the-d-spot.org/wordpress/2009/11/16/windows-7-lite-touch-installation-with-mdt-2010-part-2/
http://www.cluberti.com/blog/2009/08/10/mdt-2010-and-deployment-from-a-usb-key/
http://www.cluberti.com/blog/2009/08/12/adding-additional-boot-options-to-your-deployment-usb-key/
http://www.delltechcenter.com/page/Dell+Business+Client+Operating+System+Deployment+-+The+.CAB+Files
http://driverpacks.net/
Capture and Apply Windows Images
Apply Images by Using ImageX
BCDboot Command-Line Options
Deploy a System Recovery Image
http://mikespcbabble.com/WinPE3.aspx
http://blog.brianleejackson.com/sysprep-a-windows-7-machine-start-to-finish-v2
http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part19.html
http://blog.brianleejackson.com/formatting-winpe-3-0-usb-flash-drive-dism
http://edge.technet.com/Media/Deploy-Windows-7-The-Easy-Way-Using-WDS-MDT-and-AIK-Step-By-Step/
http://www.the-d-spot.org/wordpress/2009/11/01/windows-7-lite-touch-installation-with-mdt-2010/
http://www.the-d-spot.org/wordpress/2009/11/16/windows-7-lite-touch-installation-with-mdt-2010-part-2/
http://www.cluberti.com/blog/2009/08/10/mdt-2010-and-deployment-from-a-usb-key/
http://www.cluberti.com/blog/2009/08/12/adding-additional-boot-options-to-your-deployment-usb-key/
http://www.delltechcenter.com/page/Dell+Business+Client+Operating+System+Deployment+-+The+.CAB+Files
http://driverpacks.net/
Wednesday, July 21, 2010
Friday, June 18, 2010
Problem displaying non-unicode fonts in Greek windows 7
When we run a non-unicode program in Greek Windows 7 there is a chance that we do not see the right fonts. The solution is to run regedit and go to the key
HKCU\Control Panel\International
and then modify the value Locale replacing 00000409 with 00000408
For the changes to take place we must logoff the current user and then logon again.
HKCU\Control Panel\International
and then modify the value Locale replacing 00000409 with 00000408
For the changes to take place we must logoff the current user and then logon again.
Tuesday, May 11, 2010
Enable and configure Windows PowerShell Remoting using Group Policy
Monday, May 3, 2010
How to connect from a 64-bit Windows 7 client to a 32-bit Windows Server 2003 fax server
Copy the following files:
Source machine: Windows Server 2003 32-bit fax server
Source Folder: C:\windows\system32\spool\drivers\w32x86\3
Destination machine: Windows 7 64-bit
Destination folder: C:\Windows\System32\spool\drivers\W32X86\3
Files to be copied:
fxsapi.dll
fxsdrv.dll
fxsres.dll
fxstiff.dll
fxsui.dll
fxswzrd.dll
Before we copy the files we must stop the spooler service on windows 7 client using the command
net stop spooler
Soon after we copy the files we must start the spooler again using the command
net start spooler
Source machine: Windows Server 2003 32-bit fax server
Source Folder: C:\windows\system32\spool\drivers\w32x86\3
Destination machine: Windows 7 64-bit
Destination folder: C:\Windows\System32\spool\drivers\W32X86\3
Files to be copied:
fxsapi.dll
fxsdrv.dll
fxsres.dll
fxstiff.dll
fxsui.dll
fxswzrd.dll
Before we copy the files we must stop the spooler service on windows 7 client using the command
net stop spooler
Soon after we copy the files we must start the spooler again using the command
net start spooler
Subscribe to:
Posts (Atom)