Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
22 Cards in this Set
- Front
- Back
Windows 7 uses two firewalls
|
Windows Firewall and the Windows Firewall with Advanced Security (WFAS).
|
|
full stealth
|
Stealth blocks external hosts
from performing Operating System (OS) fingerprinting You cannot disable the stealth feature of Windows 7. |
|
Boot time filtering
|
ensures that Windows Firewall is working from the instant the network interfaces become active
|
|
Network Location Awareness (NLA)
|
is a feature through which Windows 7 assigns a network
profile based on the properties of a network connection. |
|
reset Windows Firewall and WFAS to their out-of-the-box configuration
|
netsh advfirewall reset
|
|
On what basis can you create rules for Windows Firewall (as opposed to WFAS)
|
You can create rules for Windows Firewall only for programs and Windows 7
features. You cannot create rules for Windows Firewall based on port address or service. |
|
You can access the WFAS
|
typing Windows Firewall with Advanced Security into the Search Programs
|
|
Rule Scope
|
A rule scope allows you to specify whether a rule applies to specific source and destination addresses.
|
|
Connection Security Rules
|
Connection security rules are a special type of rule that deal with authenticated and encrypted traffic.
Connections can be authenticated using the Kerberos V5 protocol requiring a domain computer and user account or a domain computer account. |
|
export and import firewall
policies in the same .wfw format |
netsh advfirewall export or netsh advfirewall import
|
|
Network Level Authentication
|
Only clients running Windows Vista and Windows 7 support Network Level Authentication by default
|
|
If you reset Windows Firewall to its default settings,
|
you need to re-enable the Remote Desktop firewall rules manually
|
|
Remote Desktop Users
|
Only members of the Administrators and Remote Desktop Users local groups are able to make connections to a client running
Windows 7 using Remote Desktop |
|
What setting do you need to configure to allow Remote Desktop connections from computers running Windows XP Professional SP2.
|
You must configure Remote Desktop to allow connections from computers running any version of Remote Desktop, rather than only allowing connections from computers running Remote Desktop with Network Level Authentication.
|
|
What protocol must be present on local computers running Windows Server 2008 if you are going to forward Windows Remote Assistance invitations using
Easy Connect in a LAN environment? |
The Peer Name Resolution Protocol feature must be installed on Windows Server
2008 for clients running Windows 7 on a LAN to be able to use Easy Connect. |
|
Windows Remote Management Service
|
The Windows Remote Management service allows you to execute commands on a remote computer, either from the command prompt using WinRS or from Windows PowerShell.
|
|
Before you can use WinRS or Windows PowerShell what we have to do?
|
it is necessary to configure the target computer using the WinRM command.
WinRM quickconfig from an elevated command |
|
Executing WinRM quickconfig does the following:
|
Starts the WinRM service
Configures the WinRM service startup type to delayed automatic start Configures the LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users Configures the WinRM listener on http://* to accept WS-Man requests Configures the WinRM firewall exception |
|
You can use WinRS to execute command-line utilities or scripts on a remote computer
|
WinRS –r:RemoteComputerName
|
|
execute the Ipconfig command on a computer named Aberdeen
|
WinRS –r:Aberdeen ipconfig
|
|
run
the command net accounts, which displays information about a computer’s password policy |
WinRS –r:http://aberdeen.contoso.internal –u:Kim_Akers net accounts
|
|
The syntax of remote Windows
PowerShell commands |
Icm hostname {powershell-command}
|