Netstumbler alternative / Wireless Scanning

The tool netstumbler is very nice but work only on Windows XP. If you have enough on some basic scanning you can use the following netsh command: netsh wlan show networks mode=bssid If you need some extra info you can use the tool InSSIDer. Screenshot:

November 21, 2010 · 1 min · thomasf

A revocation check could not be performed for the certificate

If this article helps you please consider a donation. I don’t like adds on my blog. When you get the RDP error “a revocation check could not be performed for the certificate” on a windows 7 workstation after you installed an SSL from a certification, you must disable enablecredsspsupport support. You can do this in the RDP file you are using. Open the *.rdp file in notepad and add the following line: ...

November 15, 2010 · 5 min · thomasf

Sysprep error Windows 2008 r2 and Windows 7

You can only run sysprep twice. If you get an error the 3rd time follow these steps to fix it: 1. Change the following Registry key value of GeneralizationState to 7. 2. Run ‘msdtc -uninstall’ and ‘msdtc -install’ to repair the DTC installation. 3. Then re-run sysprep again and see if the issue is resolved.

November 3, 2010 · 1 min · thomasf

Print Spooler Crash Troubleshooting Steps

(copy from: http://blogs.technet.com/b/perfguru/archive/2008/08/06/print-spooler-crash-troubleshooting-steps.aspx) The print processor tells the spooler to alter a job according to the document data type. It works together with the printer driver to move the spooled print jobs from the hard disk drive to the printer. The print monitors are the name of any component that processes the print job after it has spooled and are responsible for directing the output to the print device. Print monitors can be divided into two classes: Language monitors Port monitors Language monitors are typically used only for bi-directional printers. A bi-directional printer Supports two-way communication to answer status, and configurations questions sent to it. A Bi-directional printer can also give unsolicited status information about the job being printed, and error conditions such as paper out. Port monitors consist of user-mode DLLs. They are responsible for providing a communications path between the user-mode print spooler and the kernel-mode port drivers that access I/O port hardware. Print Spooler crash happens most of the time due to third party print processor and print monitor. We can set printers to use default print processor and monitor by machine changes in the registry called as Print hive cleaning Use Regedit to locate the Print key in the Registry: Click to highlight the Print key in Regedit and export the key as a .reg file for backup purposes (File > Export). Locate the Local Port Registry key: Confirm that the Driver value in the Local Port Registry key is set to Localspl.dll. If it is not, double-click the Driver value to edit the Data String and set it to Localspl.dll. Note any 3rd-party Monitors that are listed in the Monitors Registry key for future reference: The default Monitors are: ========================== AppleTalk Printing Devices BJ Language Monitor Local Port LPR Port PJL Language Monitor Standard TCP/IP Port USB Monitor Windows NT Fax Monitor ========================== Note: Not all of the above default Port Monitors will be present in all cases. You may also see the Microsoft Office Document Imaging Monitor which is installed by MS Office. The 2 types of monitors that may be listed here are Port Monitors and/or Language Monitors. As a general rule, Language Monitors will not have any printer ports defined in the Ports subkey and may be removed without causing a problem. Port Monitors such as HP Standard TCP/IP, however, may have active printers using this port type. If a 3rd-party Port Monitor is in use, with printers defined in the Ports subkey under the Port Monitor, you will need to convert the port(s) to a Standard TCP/IP Port ( Standard Port Monitor). To convert the printer ports from the 3rd-party Port Monitor to Standard TCP/IP Port Monitor, perform the following steps: Open the Printers and Faxes folder. Right-click the printer that was identified as using the 3rd-party Port Monitor and select Properties. In the Properties for the printer, click the Ports tab. On the Ports tab, click the Add Port button. In the Printer Ports dialog, select Standard TCP/IP and click the New Port button to start the Add Standard TCP/IP Printer Port Wizard. Click Next when the Add Standard TCP/IP Printer Port Wizard starts to specify the printer that will be using this new port. Enter the Printer Name or IP Address for the printer that will be using this new port and click Next. Note: The wizard automatically fills in the port name for you in the Port Name box. You can either accept this name or type the name that you want to use, and then click Next. Standard Port Monitor then sends a query to the print device. Based on the SNMP values that are returned, the device details are determined and the appropriate device options are displayed. If the print device cannot be identified, you must supply additional information about it. If the Additional Port Information Required page is displayed, perform one of the following tasks under Device Type: Click Standard, click the appropriate device in the list, and then click Next. -or- Click Custom, click Settings, specify the protocol settings ( RAW or LPR) and the SNMP status settings that you want to use, click OK, and then click Next. If the wizard prompts you for the print server protocol, specify the protocol that you want to use, either RAW or LPR. If the wizard prompts you to select a port, specify the port that you want to use in the Device Port box, and then click Next. Click Finish, and then click Close. On the Ports tab in the Properties for the printer, you should see that the printer is now set to use the new Standard TCP/IP Port that you just created. The new Standard TCP/IP port is also displayed in the Ports on this server list on the Ports tab in the Print Server Properties ( File > Server Properties from within the Printers folder) You can then delete the 3rd-party port from the Ports tab within the Print Server Properties. Repeat these steps for all printers that are using a 3rd-party Port Monitor. After moving all printers to the Standard TCP/IP Port Monitor, we can delete the 3rd-party Port Monitor’s Registry key under the Monitors key: For any other 3rd party Monitors that are identified under the Monitors key and are confirmed to NOT have any printer ports listed under the Ports subkey for the Monitor, we will need to perform the following 2 steps Identify printers configured to use the 3rd party Monitor. Delete the reference to the Monitor for that printer. Delete the Registry key for the 3rd party Monitor. Note: The Client Printer Port is the Citrix Metaframe Monitor used for autocreated client printers in Terminal Server sessions. Do not remove this Monitor unless it is confirmed to be related to the problem: ========================== Driver REG_SZ cpmmon.dll ========================== See the following article before removing Lexmark Monitors: 155516 How to Remove the Lexmark MarkVision Monitor http://support.microsoft.com/?id=155516 Note the name of the 3rd-party Monitor that is being removed. We will use this name to search the Print Registry key for references to this Monitor. Assume, for example, that the HP Master Monitor is installed: ========================== EOJTimeout REG_DWORD 0xea60 Driver REG_SZ HPBMMON.DLL ========================== In Regedit, click to highlight the Print key: Press F3, or click the Edit menu and select Find. In the Find What field, type the name of the 3rd-party Monitor that is being removed, HP Master Monitor in this example, and click Find Next. Identify printers that are configured to use the Monitor that we are removing, for example: ========================== Configuration File REG_SZ HPBF342E.DLL Data File REG_SZ HPBF342I.PMD Driver REG_SZ HPBF342G.DLL Help File REG_SZ HPBF342E.HLP ========================== Double-click the Monitor value to delete the 3rd party Monitor data string. In this example, delete the “HP Master Monitor” value. The Monitor value will be left with a blank data string, as follows: ========================== Configuration File REG_SZ HPBF342E.DLL Data File REG_SZ HPBF342I.PMD Driver REG_SZ HPBF342G.DLL Help File REG_SZ HPBF342E.HLP ========================== Repeat the steps above for all 3rd-party Monitors. Stop and restart the Print Spooler service for the changes take effect. Net stop spooler Net start spooler Note: In most cases, removing the 3rd party Monitors will not affect normal printing. If new problems are seen after removing the 3rd party Monitors, we can restore the backed up Print Registry key to restore the original configuration.. You can then perform the steps above again in smaller steps, stopping and starting the Print Spooler service more frequently, to determine if a specific component is required. If so, skip the removal of this component and continue removing the other 3rd-party items. Note: If the problem is easily reproducible, you may also individually remove the 3rd-party Monitors to try to narrow the problem down to a particular Monitor. This procedure will take more time and may require restarting the Print Spooler service multiple times. Remove 3rd party Print Providers by deleting the 3rd-party providers in the following Registry key: The default Print Providers are: Internet Print Provider Lanman Print Services The Client Printer Provider is the Citrix Metaframe provider used for autocreated client printers in Terminal Server sessions. Do not remove this Provider unless it is confirmed to be related to the problem: ========================== Name REG_SZ C:\Program Files\Citrix\system32\cdmprov.dll DisplayName REG_SZ Client Printer ========================== Stop and restart the Print Spooler service for the changes take effect. Net stop spooler Net start spooler Perform the following steps to confirm that all printers are configured to use the WinprintPrint Processor. Identify printers that are configured to use a 3rd party Print Processor. Change the 3rd party Print Processor to Winprint. Delete the Registry key for the 3rd party Print Processor. Note the name of the installed Print Processors under the following Registry key: The default Print Processor is Winprint: ========================== Driver REG_SZ localspl.dll ========================== Assume, for example, that the HPPRN05 is installed: ========================== Driver REG_SZ HPPRN05.DLL ========================== In Regedit, click to highlight the Print key: Press F3, or click the Edit menu and select Find. In the Find What field, type Print Processor and click Find Next. Identify the Print Processor being used for each printer: ========================== HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers\Client1 ChangeID REG_DWORD 0x1b9fa8c9 Status REG_DWORD 0x180 Name REG_SZ Client\XPWS Share Name REG_SZ ========================== Double-click the Print Processor value to change the 3rd party processor data string to Winprint: ========================== HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers\Client1 ChangeID REG_DWORD 0x1b9fa8c9 Status REG_DWORD 0x180 Name REG_SZ Client\XPWS Share Name REG_SZ ========================== Repeat the steps above for all 3rd-party Print Processors. Stop and restart the Print Spooler service for the changes to take effect. Net stop spooler Net start spooler Note: In most cases, changing the print processor to Winprint will not affect normal printing. If new problems are seen after changing the print processor, we can restore the backed up Print Registry key and restart the Print Spooler service to restore the original configuration. You can then perform the steps above again in smaller steps, stopping and starting the Print Spooler service more frequently, to determine if a specific component is required. If so, skip the removal of this component and continue removing the other 3rd party items. Additional steps to be done Check the Spool folder to see if there are any old files in the folder. When printing is working properly, the files in the Spool folder are deleted as the jobs are printed. The default Spool folder is: The Spool folder location can be confirmed by checking the DefaultSpoolDirectory Registry value in the following Registry key: Move any old files that are in the Spool folder to see if the problem still occurs. Corrupt files in the Spool folder can cause Print Spooler service problems. You may need to stop the Print Spooler service to move the files from the Spool folder. The Print Spooler service is, by default, dependent only upon the Remote Procedure Call (RPC) service, RPCSS. To confirm the Spooler dependencies, check the DependOnService value in the following Registry key: Confirm that the dependent services are started. If there are any other dependent services listed, in addition to RPCSS, edit the DependOnService Registry value to remove all dependencies except RPCSS. Configure the installed antivirus application to exclude scanning the Spool folder. There can be contention between the antivirus application and the Print Spooler service that may cause intermittent printing problems. If still issue persists we need to collect ADPlus crash dump of print spooler service. ADPlus is a tool that will allow us to get a memory dump from a process that is giving you problems. To get this tool, please install the “Debugging Tools for Windows" from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Once these tools are installed, do the following: 1. Create a directory called c:\adplus 2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is c:\Program Files\Debugging Tools for Windows 3. Type the following: " cscript adplus.vbs -hang -pn <mmc.exe> -o c:\adplus” 4. Do not interfere with the windows that is opened, just let it run minimized. 5. You will not be able to log off the system while you are monitoring. 6. When the crash occurs, please zip and send me the contents of the c:\adplus directory. For more information please see refer to this Knowledge Base article: 286350 HOWTO: Use Autodump+ to Troubleshoot “Hangs” and “Crashes”http://support.microsoft.com/?id=286350 After collecting the dump please contact Microsoft for the analysis.

October 14, 2010 · 11 min · thomasf

Hide Administrative tools and network places Windows 2008

By default on Windows 2008 R2 you cannot hide Administrative tools and Network places by default. You must create custom 2 policies: Network places (This cannot be a user key, so you must restart the (client) server :( ): CLASS MACHINE CATEGORY !!Custom CATEGORY !!ExplorerExtras POLICY !!HideNetworkInExplorer KEYNAME “SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\NonEnum” EXPLAIN !!HideNetworkInExplorer_Help VALUENAME “{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}” VALUEON NUMERIC 1 VALUEOFF NUMERIC 0 END POLICY END CATEGORY END CATEGORY [strings] Custom=“Custom Policies” ExplorerExtras=“Windows Explorer Extra’s” HideNetworkInExplorer=“Hide Network Icon in Explorer 2008/Vista” HideNetworkInExplorer_Help=“Enable this one to hide the icon, disable or unconfigure to show it…” ...

September 28, 2010 · 1 min · thomasf

WSS / Sharepoint Cannot access site from local server

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version Solution : http://support.microsoft.com/kb/896861 To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps: Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base: 281308 Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name Click Start, click Run, type regedit, and then click OK. In Registry Editor, locate and then click the following registry key: Right-click MSV1_0, point to New, and then click Multi-String Value. Type BackConnectionHostNames, and then press ENTER. Right-click BackConnectionHostNames, and then click Modify. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK. Quit Registry Editor, and then restart the IISAdmin service. ...

August 18, 2010 · 2 min · thomasf

TrendMicro Officescan 10 on Windows 2008 R2

When you install Officescan 10 on a Windows 2008 R2 server you get 2 errors: When you login to the webconsole you get the error: Your OfficeScan Session has timed out. Please log in again When you use the remote installerr you get the error: Incorrect parameter in the initialization file You can fix this problem by change the NTFS rights (Everyone/modify) on the maps. C:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV\TEMP C:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV\Web_OSCE\Web_console ...

July 28, 2010 · 1 min · thomasf

Windows Vista/2008 your user profile was not loaded correctly

After you removed the C:\users\someprofile\ you get the error “your user profile was not loaded correctly”. To fix this start regedit go to: HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList search the currupted profile and remove the key.

February 26, 2010 · 1 min · thomasf

[CCleaner] New version!

There is a new Crap Cleaner version released. You can download it here so you don’t have to install something on your pc.

December 23, 2009 · 1 min · thomasf

Speed up your firefox

How longer you use firefox how slower the automatic search will be. There is a plugin thats defragment the search database. Quote Vacuum Places Improved 1: Defragments your Firefox “Places” database (history/bookmarks) This greatly reduces the lag while typing in the address bar and the start-up time. This extension features configurable automatic cleaning, periodic reminder, and internationalization. URL: https://addons.mozilla.org/nl/firefox/addon/13878

November 18, 2009 · 1 min · thomasf