From LedHed's Wiki
Jump to: navigation, search

Page title matches

  • When setting up a mail server sometimes its handy to be able to test from the command line. If the server you're trying to test supports SASL authentication you can test AUTH LOGIN as follows.
    2 KB (335 words) - 00:30, 27 September 2013

Page text matches

  • ...to test dspam's correct functioning on your system. This exercise does not test the Web UI, but only the core dspam agent. Before running the test, you should have completed section 1.1's instructions for compiling and ins
    91 KB (14,532 words) - 23:27, 27 July 2009
  • ...to test dspam's correct functioning on your system. This exercise does not test the Web UI, but only the core dspam agent. Before running the test, you should have completed section 1.1's instructions for compiling and ins
    52 KB (8,420 words) - 22:47, 27 July 2009
  • ...to test dspam's correct functioning on your system. This exercise does not test the Web UI, but only the core dspam agent. Before running the test, you should have completed section 1.1's instructions for compiling and ins
    4 KB (537 words) - 18:03, 12 June 2009
  • You might want to run with verbose debug to test and ensure everything is
    7 KB (1,086 words) - 22:58, 27 July 2009
  • The easiest way to test is to snoop /var/log/squid/access.log for usernames.
    6 KB (916 words) - 00:11, 4 October 2013
  • ** /test Displays testing finctions
    7 KB (1,061 words) - 23:40, 25 August 2013
  • WBEMTest is a GUI utility that you can use to test WMI queries.
    222 B (31 words) - 23:27, 25 September 2013
  • When setting up a mail server sometimes its handy to be able to test from the command line. If the server you're trying to test supports SASL authentication you can test AUTH LOGIN as follows.
    2 KB (335 words) - 00:30, 27 September 2013
  • ...matched if one of the defined types match. Within a destination group the test order is domainlist, urllist, and expressionlist.
    32 KB (4,558 words) - 21:13, 29 September 2013
  • == Test Website Access from Command Line ==
    426 B (59 words) - 22:08, 29 November 2013
  • Sometimes you need to delete a DFS Namespace whether it was a test namespace or your DFS structure just changed. This can lead to 'orphaned' n
    1 KB (233 words) - 20:35, 7 December 2013
  • You can also test which DCs are nearest to your workstation in your site (copy nltest.exe fro
    29 KB (4,584 words) - 22:02, 11 December 2013
  • Set hostname to the FQDN of the computer/server you're wanting to test <br>
    1,012 B (137 words) - 05:32, 28 February 2015
  • === View SMART test results === === Perform SMART Test on drive ===
    614 B (95 words) - 17:51, 8 August 2015
  • *Test Mode (see what files will be deleted before deleting them)
    2 KB (363 words) - 00:32, 13 August 2016
  • === Test ===
    1 KB (147 words) - 18:27, 1 December 2016
  • 3. A communication test will begin and fail. Press OK to see the error results.<br> 7. Press B and save the settings. Do not run a connection test.<br>
    2 KB (219 words) - 00:04, 10 April 2017
  • Test-ComputerSecureChannel -Repair -Credential (Get-Credential)
    443 B (47 words) - 06:02, 17 May 2018
  • At this point your service permissions should be set. Have the non-admin user test out their new access. If there are any errors, check the Security Configura ...he effect that it couldn't read the template. Fortunately, I did this on a test server so I ignored the error and the service permissions applied just fine
    3 KB (549 words) - 07:13, 4 April 2024

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)