Which MS-DOS command allows you to shut down a user remotely?

Which MS-DOS command allows you to shut down a user remotely?

• shutdown -i
• @echo on shutdown -i -s
• shutdown -s
• shutdown -s -t 

EXPLANATION

Enables you to shut down or restart local or remote computers one at a time.
For examples of how to use this command, see Examples.

Syntax

shutdown [/i | /l | /s | /r | /a | /p | /h | /e] [/f] [/m \\<ComputerName>] [/t <XXX>] [/d [p|u:]<XX>:<YY> [/c "comment"]] 

Parameters

Parameter	Description
/i	Displays the Remote Shutdown Dialog box. The /i option must be the first parameter following the command. If /i is specified, all other options are ignored.
/l	Logs off the current user immediately, with no time-out period. You cannot use /l with /m or /t.
/s	Shuts down the computer.
/r	Restarts the computer after shutdown.
/a	Aborts a system shutdown. Effective only during the timeout period. To use /a, you must also use the /m option.
/p	Turns off the local computer only (not a remote computer)—with no time-out period or warning. You can use /p only with /d or /f. If your computer does not support power-off functionality, it will shut down when you use /p, but the power to the computer will remain on.
/h	Puts the local computer into hibernation, if hibernation is enabled. You can use /h only with /f.
/e	Enables you to document the reason for the unexpected shutdown on the target computer.
/f	Forces running applications to close without warning users. Caution: Using the /f option might result in loss of unsaved data.
/m \\<ComputerName>	Specifies the target computer. Cannot be used with the /l option.
/t <XXX>	Sets the time-out period or delay to XXX seconds before a restart or shutdown. This causes a warning to display on the local console. You can specify 0-600 seconds. If you do not use /t, the time-out period is 30 seconds by default.
/d [p|u:]<XX>:<YY>	Lists the reason for the system restart or shutdown. The following are the parameter values: p Indicates that the restart or shutdown is planned. u Indicates that the reason is user defined. Note: If p or u are not specified, the restart or shutdown is unplanned. XX Specifies the major reason number (positive integer less than 256). YY Specifies the minor reason number (positive integer less than 65536).
/c "<Comment>"	Enables you to comment in detail about the reason for the shutdown. You must first provide a reason by using the /d option. You must enclose comments in quotation marks. You can use a maximum of 511 characters.
/?	Displays help at the command prompt, including a list of the major and minor reasons that are defined on your local computer.

Read More

Which is the oldest version of Windows in this list?

Which is the oldest version of Windows in this list?

• Windows NT 3.1
• Windows XP
• Windows ME
• Windows 98 

EXPLANATION

In May 1990, Microsoft released Windows 3.0, a new version of its MS-DOS-based Windows desktop environment. Windows 3.0 sold well, and the resulting shift in Microsoft's marketing strategy eroded their partnership with IBM—who wanted Microsoft to concentrate solely on developing OS/2 as its primary platform as opposed to building their future business around Windows.^[20] Users and developers were unsure of whether to adopt Windows or OS/2 due to these uncertainties (a situation magnified by the fact that the operating systems were incompatible with each other at the API level), while Microsoft's resources were also being drained by the simultaneous development of multiple operating systems.^[21][22]
In August 1990, as a response to the popularity of Windows 3.0, the NT OS/2 team decided to re-work the operating system to use an extended 32-bit port of the Windows API known as Win32. Win32 maintained the familiar structure of the 16-bit APIs used by Windows, which would allow developers to easily adapt their software for the new platform while maintaining a level of compatibility with existing software for Windows.^[23] With the shift to a Windows-like architecture, the operating system's shell was also changed from OS/2's Presentation Manager to Windows' Program Manager.^[24][25][26]
Due to these changes, NT was not presented at COMDEX 1990 as was originally planned.^[24] Neither the general public nor IBM knew about the transformation of NT OS/2 into Windows NT at the time.^[27] Although the companies did agree to a revised partnership where IBM and Microsoft would alternate developing major versions of OS/2 instead of collaborating on each version,^[28] IBM eventually learned of Microsoft's Windows NT plans in January 1991, and immediately ended the OS/2 partnership. IBM would solely develop OS/2 2.0 (as was planned under the amended version) and all future versions, without any further involvement from Microsoft.^[23][29]
In October 1991, Windows NT received its first public demonstration at COMDEX. In an effort to ensure software taking advantage of Windows NT was available upon its release (scheduled for late-1992), Microsoft also distributed a 32-bit software development kit to selected developers in attendance.^[30][31] The demonstration was positively received; PC Magazine called Windows NT "the modern reinvention of the operating system", but at the same time claimed that it was unlikely that the promised backward compatibility would be kept for the final release.^[32][33] In March 1992, Microsoft also released Win32s, which would allow Windows 3.1 to have partial compatibility with Windows NT programs for the purposes of developing software optimized for the platform.^[34]
At Microsoft's Win32 Professional Developers Conference in June 1992, Windows NT was demonstrated running on x86 and MIPS processors, while a beta version of Windows NT and an updated development kit were also made available.^[35] Concurrently, Microsoft announced a new version of its SQL Server product for Windows NT; Unix vendors feared that the software could be a killer app that would affect the market share of Unix systems.^[36][37] Concerns were also raised over NT's memory usage; while most computers of the era shipped with 4 megabytes of RAM, 16 MB was recommended for NTs. Due to the high cost of RAM at the time, critics thought that its high system requirements could affect the sales and adoption of Windows NT. Steps were taken to reduce its memory usage through methods such as paging.^{[38][39][40][41]}
Microsoft began releasing public beta builds of NT in October 1992, and a month later at COMDEX, a presentation focusing on third-party software for Windows NT was held.^[42][43][44] The final pre-release version of NT was released in March 1993, alongside the unveiling of the server version, Windows NT with LAN Manager. Although its stability and performance had improved, there were still fears that the OS could be released in an unfinished state or delayed further into 1993.^[45][46]

 

 

Read More

On an Apache webserver, what is the name of the file used to configure access to the web site?

On an Apache webserver, what is the name of the file used to configure access to the web site?

• .htaccess
• htaccess.txt
• htaccess.cfg
• htaccess

EXPLANATION

An .htaccess file also known as an hypertext access file is a directory-level configuration file supported by several web servers, used for configuration of site-access issues, such as URL redirection, URL shortening and Access-security control.
An .htaccess file provides various options for website owners to control the server environment variables and other parameters to enhance functionality of their websites. It is placed in the directories and sub-directories of the Apache document root. When you place an .htaccess file in the apache document root, the .htaccess file is detected and executed by the Apache Web Server.
These .htaccess files can be used to alter the configuration of the Apache Web Server to enable and disable additional functionality and features that the Apache Web Server software has to offer. When you are developing a PHP website and working with PHP and Apache, then you can use an .htaccess file for directory level configuration of Apache web server.
You should only use .htaccess files when you don't have root access to the main Apache server configuration file. An .htaccess file provides many features Some of these features include basic redirects, locking outside access to particular files, or more advanced functions such as content password protection or preventing image hotlinking.
However, use of .htaccess files should be avoided when possible. There are two main reasons to avoid the use of .htaccess files.
The first of these is server performance. When AllowOverride is set to allow the use of .htaccess files, httpd will look in every directory for .htaccess files. Thus, permitting .htaccess files causes a performance issue, whether or not you actually even use them! Also, the .htaccess file is loaded every time a document is requested.

Read More

Modern ethernet protocol relies on CSMA/CD to provide reliable communications. Does 802.11 WLANs also use CSMA/CD?

Modern ethernet protocol relies on CSMA/CD to provide reliable communications. Does 802.11 WLANs also use CSMA/CD?

• Yes - CSMA/CD will set proper throughput
• No - CSMA/CD is never used in wi-fi WLANs
• No - CSMA/CD is never used in modern networks
• Yes - CSMA/CD will setup channel number 

EXPLANATION

CSMA/CD isn't ever used for Wifi LANs but the question specifically uses the word "modern" and MODERN wired LANs don't use it either. Modern wired networks rely on collision detection being performed by the switch - and the explanation offered even says:
CSMA/CD - Carrier sense multiple access with collision detection - is a media access control method used most notably in early Ethernet technology for local area ..
Note: "... used most notably in EARLY Ethernet technology ..."
Refer: https://en.wikipedia.org/wiki/Carrier_sense_multiple_access_with_collision_detection

 

Read More

Which Exchange cmdlet shows who has access to a particular user's mailbox and what type of access they have?

Which Exchange cmdlet shows who has access to a particular user's mailbox and what type of access they have?

• Look-MailboxPermission -Identity username
• Open-MailboxPermission -Identity username
• Get-MailboxPermission -Identity username
• View-MailboxPermission -Identity username 

EXPLANATION

​This question seems to get asked a lot, and people are unaware how easy the answer really is. Here it is:

• List all mailboxes to which a particular user has Full Access permissions:
  

PS C:\> Get-Mailbox | Get-MailboxPermission -User vasil Identity             User                 AccessRights --------             ----                 ------------ HuKu                 Vasil Michev         {FullAccess} retail               Vasil Michev         {FullAccess} sharednew            Vasil Michev         {FullAccess} testplan2            Vasil Michev         {FullAccess} WC                   Vasil Michev         {FullAccess}

• List all shared/user/room/whatever mailboxes to which particular user has Full Access permissions:
  

PS C:\> Get-Mailbox -RecipientTypeDetails UserMailbox,SharedMailbox -ResultSize Unlimited | Get-MailboxPermission -User vasil Identity             User                 AccessRights --------             ----                 ------------ HuKu                 Vasil Michev         {FullAccess} retail               Vasil Michev         {FullAccess} sharednew            Vasil Michev         {FullAccess}testplan2            Vasil Michev         {FullAccess}

• List all mailboxes to which members of a particular security group have access:
  

PS C:\> Get-Mailbox | Get-MailboxPermission -User secgrp Identity             User                 AccessRights --------             ----                 ------------ Bathroom             secgrp               {FullAccess}

• List all mailboxes to which a user has Send As permissions:
  

PS C:\> Get-Mailbox | Get-RecipientPermission -Trustee vasil Identity                            Trustee                             AccessControlType                   AccessRights --------                            -------                             -----------------                   ------------ sharednew                           Vasil Michev                        Allow                               {SendAs}

• List all user mailboxes to which members of a particular security group have Send As access:
  

PS C:\> Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited | Get-RecipientPermission -Trustee secgrp Identity                            Trustee                             AccessControlType                   AccessRights --------                            -------                             -----------------                   ------------ HuKu                                secgrp                              Allow                               {SendAs}

• List all mailboxes to which a particular security principal has Send on behalf of permissions:
  

PS C:\> Get-Mailbox | ? {$_.GrantSendOnBehalfTo -match "vasil"} Name                      Alias                ServerName       ProhibitSendQuota ----                      -----                ----------       ----------------- Bathroom                  bathroom             amspr03mb084     49.5 GB (53,150,220,288 bytes) WC                        WC                   dbxpr03mb096     9.5 GB (10,200,547,328 bytes)

Read More